Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

[spec] Stable releases for Crucible installs #348

Closed
wants to merge 1 commit into from

Conversation

rafaelfolco
Copy link
Contributor

Add a mechanism for installing stable releases that are "locked- down".

Add a mechanism for installing stable releases that are "locked-
down".
Comment on lines +20 to +29
#project-name project-type git-repo-url branch
rickshaw core /rickshaw master
multiplex core /multiplex master
roadblock core /roadblock master
...
hwlatdetect benchmark /bench-hwlatdetect main
tracer benchmark /bench-tracer main
...
ftrace tool /tool-ftrace master
testing doc /testing-repo master
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think we should switch to the "new" subproject config idea (JSON) as part of this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so. Not a dependency, just a convenience, as we are changing crucible config/default_projects.

## Proposed change
"Locked down" release by pinning all sub-projects to a commit that is
verified by CI after code merges. Sub-projects includes core and benchmark
repositories. Stable releases must be labeled to be an "out of the box"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I follow what you mean by "out of the box" here...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For regression testing, "out of the box" Crucible would be crucible-2024.2, not the upstream latest merged code. We can avoid this and just call it a stable release 2024.2.

@rafaelfolco
Copy link
Contributor Author

on behalf of #351

@rafaelfolco rafaelfolco closed this Jul 8, 2024
@rafaelfolco rafaelfolco deleted the stable-release branch August 9, 2024 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

"Release" mechanism for installing "consistent" versions of Crucible
2 participants