Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Configuration Management (Plan) #23

Open
torsknod2 opened this issue Feb 16, 2025 · 1 comment
Open

Configuration Management (Plan) #23

torsknod2 opened this issue Feb 16, 2025 · 1 comment
Assignees
@torsknod2
Labels
aspice-relevant Reduces ASPICE gaps documentation Improvements or additions to documentation enhancement New feature or request

Comments

@torsknod2
Copy link
Owner

torsknod2 commented Feb 16, 2025 •
edited
Loading

Write a Configuration Managent Plan and implement it via GitHub workflow(s), GitHub settings, ...

Ideas:

  • Baselining
    • See Define version scheme #36
    • Have integration branches for major, minor and patch branches, branching of from their base
    • Have enhancement and bug branches
    • Enhancement and bug branches get merged into integration branches
    • Every commit in any branch gets a unique version e.g. in all alire.toml files
    • Every commit gets tagged with the version in the alire.toml files.
  • Releases
    • Everything tagged can become a release
    • Auto-Release happens if
      • All tests passed
      • Source code stmt+mcdc coverage is 100%
      • Object code branch coverage is 100%
      • Documentation could be generated successfully
      • No manual override of merges since last release
      • All issues having a milestone less or equal to the version are resolved.
      • No open PRs, not even drafts, to the integration branch.
      • No open PRs, not even drafts, having a milestone less or equal to the version to be released.
      • No integrated PR since the last release has a label block-auto-release.
      • No integrated PR since the last release links to an issue, which has a label block-auto-release.
    • After successful release, the integration branch gets (b)locked. I guess they cannot be achieved, because the tag references the last commit in there and it might be a basis for a future integration branch.
  • Have manually executable workflows to create new major, minor, patch integration branches based on the tag before
  • Create a Configuration Item List, first inspired by ISO 26262-6 and ASPICE SWE.3 and SWE.4
@torsknod2 torsknod2 added documentation Improvements or additions to documentation enhancement New feature or request labels Feb 16, 2025
@torsknod2 torsknod2 self-assigned this Feb 16, 2025
@codeautopilot CodeAutopilot
Copy link

codeautopilot bot commented Feb 16, 2025

Your organization has reached the subscribed usage limit. You can upgrade your account by purchasing a subscription at Stripe payment link

This comment was generated by AI. Information provided may be incorrect.

Current plan usage: 100%

Have feedback or need help?
Documentation
support@codeautopilot.com

@torsknod2 torsknod2 added the aspice-relevant Reduces ASPICE gaps label Feb 18, 2025
@torsknod2 torsknod2 mentioned this issue Feb 19, 2025
Merged
torsknod2 added a commit that referenced this issue Feb 19, 2025
@torsknod2
Enhance Project Automation, CI/CD, and Documentation (#50)
55e4236 
This PR introduces comprehensive improvements to streamline development
workflows and enhance project quality, addressing several open issues:

# Project Automation 🤖
- Add automatic project assignment workflow for issues and PRs (Closes
#37)
  - Automatically assigns new issues/PRs to project boards
  - Includes bulk assignment capability for existing items
  - Implements secure runner configuration with egress traffic control

# CI/CD and Quality Assurance ✅
- Enhance test result visibility and coverage reporting
  - Add AUnit XML test results publishing to Codecov (Closes #26)
  - Implement automated PR comments for test results (Closes #25)
  - Remove redundant Python setup in coverage workflow
- Implement robust version management
  - Add version tag validation against alire.toml
  - Add Python scripts for semantic version checking
- Ensure version consistency across the project (Partially addresses
#36)

# Documentation and Developer Experience 📚
- Improve project documentation
  - Add status badges for issue metrics (Closes #48)
  - Enhance API documentation section
  - Add links to test coverage and verification results
  - Update GitHub page information (Closes #27)
- Configure GitHub Copilot chat locale to English

# Technical Implementation
- New Workflows:
   - `.github/workflows/automatic-project-assignment.yaml`
   - `.github/workflows/ensure_tags_match_alire_toml_version.yaml`
- Enhanced Workflows:
   - Modified `.github/workflows/cicd.yaml` for test results

# Related Issues
This PR contributes to the following issues:
- Project Management (#38)
- Configuration Management (#23)
- Unit Test Coverage (#5)

Note: While this PR doesn't fully resolve all related issues, it lays
the groundwork for better project management, documentation, and test
coverage tracking.
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@torsknod2 torsknod2

Labels
aspice-relevant Reduces ASPICE gaps documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@torsknod2