Persist `:release` node from gitlab-ci.yml
Problem to solve
Persist the :release
node which was added to gitlab-ci.yml
in !19298 (merged)
Intended users
- Rachel (Release Manager)
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
Further details
if the :release
node is not in fact persisted, it will not be usable by downstream processes such as the efforts to create a release by the runner
Proposal
-
Persist
:release
node from gitlab-ci.yml
Testing
- Node should be available for runner down stream
Designs
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Sean Carroll added typefeature label
added typefeature label
- Sean Carroll added Category:Release Orchestration devopsrelease [DEPRECATED] + 1 deleted label
added Category:Release Orchestration devopsrelease [DEPRECATED] + 1 deleted label
- Sean Carroll mentioned in merge request !19298 (merged)
mentioned in merge request !19298 (merged)
- Sean Carroll changed the description
Compare with previous version changed the description
- Sean Carroll changed title from Persist :release node from gitlab-ci.yml to Persist {+
:release
+} node from gitlab-ci.ymlchanged title from Persist :release node from gitlab-ci.yml to Persist {+
:release
+} node from gitlab-ci.yml - Contributor
@sean_carroll - can you explain why we need to persist the release node?
- Author Developer
@jmeshell it was news to me that it was not already being persisted
It was highlighted in this maintainer review !19298 (comment 269121548). Work will need to be undertaken to understand what needs to be done and then to apply it. This will be an upstream dependency for #38352 (closed)
Collapse replies - Contributor
I see @sean_carroll - can you include in the issue description the consqences of it not persisting so I can prioritize this for %12.8
- Author Developer
@jmeshell at this point it is not certain that it is not persisted. It will require some research to determine this.
My understanding is that if the
:release
node is not in fact persisted, it will not be usable by downstream processes such as the efforts to create a release by the runner. - Contributor
@sean_carroll - got it. I tweaked the description to be inclusive of this.
1 - Author Developer
@jmeshell as we are going to start on the Runner - Release creation in 12.9, I think this should be prioritized.
- Contributor
@sean_carroll can you add a weight & then I’ll pull it into ~workflow::ready for development
- Author Developer
Weight: 1
- investigation and possible persistence
If persistence is needed, once the investigation is done it should be a simple matter.
1 - Contributor
moved into ~workflow::ready for develop & added ~ReleaseP2
1
- Kamil Trzciński mentioned in issue #196171 (closed)
mentioned in issue #196171 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue #196480 (closed)
mentioned in issue #196480 (closed)
- Jackie Porter changed milestone to %12.8
changed milestone to %12.8
- Jackie Porter added 1 deleted label
added 1 deleted label
- Jackie Porter removed milestone
removed milestone
- Jackie Porter added cicdplanning label
added cicdplanning label
- Jackie Porter added cicdactive label and removed cicdplanning label
added cicdactive label and removed cicdplanning label
- Jackie Porter changed the description
Compare with previous version changed the description
- Jackie Porter changed milestone to %Backlog
changed milestone to %Backlog
- Jackie Porter added workflowscheduling label
added workflowscheduling label
- Jackie Porter added needs weight label
added needs weight label
- Sean Carroll unassigned @sean_carroll
unassigned @sean_carroll
- Sean Carroll changed weight to 1
changed weight to 1
- Jackie Porter removed needs weight label
removed needs weight label
- Jackie Porter added workflowready for development label and removed workflowscheduling label
added workflowready for development label and removed workflowscheduling label
- 🤖 GitLab Bot 🤖 added [deprecated] Accepting merge requests label
added [deprecated] Accepting merge requests label
- Sean Carroll assigned to @sean_carroll
assigned to @sean_carroll
- Sean Carroll added workflowin dev label and removed workflowready for development label
added workflowin dev label and removed workflowready for development label
- Sean Carroll mentioned in epic &2510 (closed)
mentioned in epic &2510 (closed)
- Sean Carroll created merge request !26385 (merged) to address this issue
created merge request !26385 (merged) to address this issue
- Sean Carroll mentioned in merge request !26385 (merged)
mentioned in merge request !26385 (merged)
- Sean Carroll marked the checklist item Persist
:release
node from gitlab-ci.yml as completedmarked the checklist item Persist
:release
node from gitlab-ci.yml as completed - Sean Carroll added workflowin review label and removed workflowin dev label
added workflowin review label and removed workflowin dev label
- Sean Carroll changed milestone to %12.9
changed milestone to %12.9
- 🤖 GitLab Bot 🤖 removed [deprecated] Accepting merge requests label
removed [deprecated] Accepting merge requests label
- Kamil Trzciński closed via merge request !26385 (merged)
closed via merge request !26385 (merged)
- Kamil Trzciński mentioned in commit 5dfbaf36
mentioned in commit 5dfbaf36