-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Cross-Project Epic] CI Build / Weekly Release process should use consistent quay tags for sha-version/next and 7.yy.z/latest #19291
Comments
I don't think it makes sense to have a special tag for those. For starters, there might be multiple of those refactorings going on in parallel (next1, next2)? And second, I think a format like "dashboard_react_ci", etc. would be more descriptive and allow use to have a whole parallel ci/latest/sha, etc. tag stream going. |
Right but my point is that TODAY, "next" has special meaning and so should not be considered the same as "nightly", when only ONE project uses it for ci builds (che-theia), while everyone else uses nightly. And so as to offend everyone equally, we can move to "ci" for ALL nightly/next/ci builds, rather than a mix of terms. |
I think nobody understand Also |
Note this commit doesn't update the RELATED_IMAGE env var for project clone in make-release.sh, so `next` will be used there for now. Signed-off-by: Angel Misevski <amisevsk@redhat.com>
Forgot about this thread, so getting back to it now.
|
sorry but I find |
having chectl with two channels, one being |
If everyone is good with :next then I'm happy to start moving the :nightly tags to :next so we're consistent across all of Che. (Meanwhile in operatorhub, the convention for unreleased content a |
👍 regarding another topic about multi-arch (and travis usage or not) maybe we'll end up with images having arch suffix as well I like also about having also sha-versioned tags (it was already there in your proposal) |
Re: the chectl rollback to specific-version (or relative-date) ... probably useful. I've linked to the related rollback issues above. |
|
Note about:
some projects pulls resources from other project, like che-operator(devworkspace, devworkspace-che-operators), chectl (helm charts, che operator deployment). |
for pulling resources, we can send triggers to other projects as well |
Change-Id: Ia1c826f1848bbf2f80c1a86469b6790329b36a0b Signed-off-by: nickboldt <nboldt@redhat.com>
Starting this week, we'll start removing the :nightly tags from the release process and from quay. |
Status:
Additionally, it seems many projects use a different naming convention for its :next build action file, and as part of this epic we should clean that up too, so where it makes sense, we have next-build:
Other variations:
|
Change-Id: Ia1c826f1848bbf2f80c1a86469b6790329b36a0b Signed-off-by: nickboldt <nboldt@redhat.com>
Done:
Still to do for consistency:
And then we need to purge the old :nightly tags to avoid confusion (from all the other projects) |
regarding #20149 |
the following sidecar images have been deleted from Quay.io |
Is your task related to a problem? Please describe.
Today we use a harvest medley of terms to describe daily and continuous integration builds across the various Che projects. Some examples include:
Che Theia uses next to mean continuous integration builds; also pushes a sha-versioned tag
Che Dashboard used to use next-react to mean "a huge refactoring project that isn't stable yet and will eventually replace the current dashboard, but needs its own fork/branch/tag stream", and next to mean continuous integration builds; does NOT push sha-versioned tags
Che server uses latest for releases, and nightly for a daily build (last one 14 hrs ago, but last commits 8 hrs ago); does NOT push sha-versioned tags
Che machine exec uses nightly to mean continuous integration builds; also pushes a sha-versioned tag
Che devfile registry uses nightly to mean continuous integration builds; also pushes a sha-versioned tag
Describe the solution you'd like
Change to a more consistent naming convention for continuous integration builds, large refactorings, and releases:
"ci" for "continuously building new images on every commit""next" for special case refactorings (eg., Dashboard Next or Plugin Registry 3.0)In addition to impacting GH action workflows to use different tags, this will impact:
Describe alternatives you've considered
Enjoy the multicultural experience that is guessing what each project means by "nightly", "next", or "latest".
Additional context
The text was updated successfully, but these errors were encountered: