-
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
Enable CI builds for che-incubator/configbump, including updated secrets #21988
Comments
che-incubator/configbump
repositoryche-incubator/configbump
, including updated secrets
@nickboldt could you please take a look? it is very weird to see |
Note thas as part of this update, we could also switch from alpine to ubi8 as the base from which images are built. Figure if no one has cared about configbump for >2yrs https://quay.io/repository/che-incubator/configbump?tab=tags it's time to update it so it can benefit from our weekly base image update checks/PR generation. |
I think |
we'd use ubi8 micro (under 30M), not the full 214M ubi8 image.
|
Then |
@dmytro-ndp has asked for something to do for Day of Learning / H&H so I've given him this issue to work on when he has time. |
@nickboldt: did I understand it correctly, that you had suggested to change versioning of configbump from 0.1.0 to Eclipse Che version, like che-machine-exec? |
Yeah, might as well align to the other che-incubator projects and make per-sprint releases simpler. https://quay.io/repository/che-incubator/configbump?tab=tags To see how secrets are used, check out:
See also this tool to list names of secrets in a repo, or push updates to secrets https://github.com/nickboldt/github-secrets-generator |
Note as part of having CI builds we should verify that che-incubator/configbump#68 (review) is merged and triggers a new CI build |
che-incubator/configbump
, including updated secrets
Is this still needed? |
Yes, we need a way to build a fresh image. The latest one is 2 y.o |
Added to sprint plan for DTW. https://github.com/orgs/eclipse/projects/53/views/2?filterQuery=%5BDevToolsWeek%5D+&pane=issue&itemId=38362130 |
Ready to merge (needs codeowner approval): Once merged, can update this PR and merge it too: |
Vastly better: However need to fix that CVE -- see https://github.com/che-incubator/configbump/pull/100/files |
CVE fixed. Working on a fix for tagging next, as job is failing in https://github.com/che-incubator/configbump/actions/runs/6225852133/job/16897423038 --> https://github.com/che-incubator/configbump/pull/103/files |
When run from the 7.74.x branch (where I already pushed my changes) the job passed: https://github.com/che-incubator/configbump/actions/runs/6226555508/job/16899641726 So the PR should be safe to merge now |
Hmm. tag-release failed in https://github.com/che-incubator/configbump/actions/runs/6227605614 but passed in https://github.com/che-incubator/configbump/actions/runs/6226555508 will assume for now this is fixed and verify further next week for the 7.75 release, when we don't have an existing branch and tag to contend with. |
Is your task related to a problem? Please describe
Currently there is no way to release a new version of
che-incubator/configbump
since release action fails [1] with the error message:Credentials are outdated.
[1] https://github.com/che-incubator/configbump/actions/runs/4103246296
Describe the solution you'd like
Stretch goals:
Additional context
#21883
The text was updated successfully, but these errors were encountered: