As part of the migration of maven releases away from archiva and to gitlab we need to provide the gitlab api token to the release jobs. The release process (via wmf-jvm-parent-pom) expects the environment to provide a CI_RELEASE_TOKEN environment variable containing the appropriate secret. The token should be sourced from the gitlab UI. A token has already been created for jenkins and temporarily stored as a gitlab CI variable, visible to members of the project.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T367315 [Epic] Replace Archiva with Gitlab artifact repositories | |||
| Resolved | Gehel | T367322 Create a Maven package registry in Gitlab | |||
| Resolved | EBernhardson | T379203 Add CI_RELEASE_TOKEN secret for {name}-maven-release jobs in jenkins |
Event Timeline
Comment Actions
@hashar could you help out with this? I've added you as a member to the gitlab repo as well so you should be able to lookup the token to be added.
Comment Actions
Small aside: per IRC conversation with @bd808 , I updated the CI/Jenkins Wikitech page with references to Jenkins secrets.
It's lacking a lot of details, if anyone could help me flesh it out it would be appreciated.
Comment Actions
https://integration.wikimedia.org/ci/manage/credentials/ is the secrets store I know of. T106452: Composer activity from Cloud VPS hosts can be rate limited by GitHub is an example of a past task that uses this system to modify the runtime environment for some Jenkins jobs.
Comment Actions
Mentioned in SAL (#wikimedia-releng) [2025-11-12T18:36:11Z] <jnuche> Updated expired release token for wmf-packages in integration Jenkins - T379203