[00:37:12] <derenrich>	 hi. i'm trying to trigger a release upon tagging a commit in gitlab. i think i'm doing it right but when i try to trigger the release i get an error `release-cli: command not found
[00:37:12] <derenrich>	 ` (see https://gitlab.wikimedia.org/repos/future-audiences/citation-needed-chrome-extension/-/jobs/258827)
[00:37:18] <derenrich>	  seems like this is a gitlab setup issue e.g. https://forum.gitlab.com/t/release-cli-command-not-found/97983
[10:31:03] <jelto>	 GitLab needs a short maintenance in 30 minutes
[11:06:25] <jelto>	 Maintenance finished
[14:59:24] <bd808>	 "ERROR: Job failed: prepare environment: waiting for pod running: pulling image "docker-hub-mirror.cloud.releng.team/library/python:3.12": image pull failed: Back-off pulling image "docker-hub-mirror.cloud.releng.team/library/python:3.12". Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information" -- https://gitlab.wikimedia.org/toolforge-repos/wikibugs2/-/pipelines/52349/failures
[15:15:16] <dancy>	 bd808: Taking a look
[16:44:35] <bd808>	 dancy: I kind of love that you explicitly used "blah" as the dummy value. :)
[16:45:54] <dancy>	 That was the suggested value in the related bug report that I found. :-)
[16:58:28] <dancy>	 bd808: Workarounds applied and docker-hub-mirror restarted w/ empty storage. 
[16:59:26] <bd808>	 thanks dancy 
[17:43:01] <derenrich>	 reposting the above: hi. i'm trying to trigger a release upon tagging a commit in gitlab. i think i'm doing it right but when i try to trigger the release i get an error `release-cli: command not found ` (see https://gitlab.wikimedia.org/repos/future-audiences/citation-needed-chrome-extension/-/jobs/258827)
[18:17:28] <dancy>	 derenrich: Taking a look...
[18:17:32] <derenrich>	 thanks
[18:23:00] <dancy>	 https://docs.gitlab.com/ee/ci/yaml/index.html#release has the answer.
[18:24:19] <dancy>	 The short answer is add `image: registry.gitlab.com/gitlab-org/release-cli:latest` to the job.. but that means you'll probably need a separate job just for the release part. separated from the build part.
[18:24:47] <dancy>	 Which means you'll need a way to transfer the artifacts from the build job to the release job.. lemme dig up those docs.
[18:25:40] <dancy>	 OR! you can make your existing job download the release-cli binary first..  instructions are here: https://gitlab.com/gitlab-org/release-cli/-/blob/master/docs/examples/download-release-cli-from-generic-packages/index.md
[18:26:02] <dancy>	 That's lower hanging fruit.
[18:27:15] <derenrich>	 ok thanks i'll take a look
[20:19:19] <wikibugs>	 10GitLab-Application-Security-Pipeline, 06Security-Team, 07SecTeam-Processed, 07Security: Update golang gosec security template to use go 1.22 - https://phabricator.wikimedia.org/T364560#9787100 (10CodeReviewBot) sbassett merged https://gitlab.wikimedia.org/repos/security/gitlab-ci-security-templates/-/mer...
[20:19:20] <wikibugs>	 10GitLab-Application-Security-Pipeline, 06Security-Team, 07SecTeam-Processed, 07Security: Refactor gosec appsec include based upon testing from T364560 - https://phabricator.wikimedia.org/T364586#9787101 (10CodeReviewBot) sbassett merged https://gitlab.wikimedia.org/repos/security/gitlab-ci-security-templa...
[20:30:33] <wikibugs>	 10GitLab-Application-Security-Pipeline, 06Security-Team, 07SecTeam-Processed, 07Security: Refactor gosec appsec include based upon testing from T364560 - https://phabricator.wikimedia.org/T364586#9787129 (10sbassett) 05Open→03Resolved p:05Triage→03Low
[20:31:36] <wikibugs>	 10GitLab-Application-Security-Pipeline, 06Security-Team, 07SecTeam-Processed, 07Security: Update golang gosec security template to use go 1.22 - https://phabricator.wikimedia.org/T364560#9787141 (10sbassett) 05Open→03Resolved p:05Triage→03Low