GITLAB_WORKHORSE_VERSION being a symlink to VERSION might break the release process
As of gitlab-org/gitlab@c3977c8d, GITLAB_WORKHORSE_VERSION
is a symlink to VERSION
since it's now part of the gitlab-rails codebase.
When we fetch the file contents of GITLAB_WORKHORSE_VERSION
from the API, the contents will be the file it points to (i.e., VERSION
) rather than the contents of the linked file, which broke our auto-deploy process. We fixed it in gitlab-org/release-tools!1389 (merged), but as @skarbek pointed out, we still use this in the monthly CNG image release process: https://gitlab.com/gitlab-org/release-tools/-/blob/master/lib/release_tools/public_release/cng_image_release.rb#L16.
We can't simply remove this version file entry in the release process since it may break backports prior to the codebase merges, but I'm not sure of that.
🤖
Auto-Summary Discoto Usage
Points
Discussion points are declared by headings, list items, and single lines that start with the text (case-insensitive)
point:
. For example, the following are all valid points:
#### POINT: This is a point
* point: This is a point
+ Point: This is a point
- pOINT: This is a point
point: This is a **point**
Note that any markdown used in the point text will also be propagated into the topic summaries.
Topics
Topics can be stand-alone and contained within an issuable (epic, issue, MR), or can be inline.
Inline topics are defined by creating a new thread (discussion) where the first line of the first comment is a heading that starts with (case-insensitive)
topic:
. For example, the following are all valid topics:
# Topic: Inline discussion topic 1
## TOPIC: **{+A Green, bolded topic+}**
### tOpIc: Another topic
Quick Actions
Action Description /discuss sub-topic TITLE
Create an issue for a sub-topic. Does not work in epics /discuss link ISSUABLE-LINK
Link an issuable as a child of this discussion
Last updated by this job
-
⏫ ROOT Identify simplification to release and packaging code now that workhorse is part of GitLab repository gitlab-org/gitlab#324194 -
◀ PARENT release-tools gitlab-org/gitlab#324194 (comment 527282293) - Omnibus will require
GITLAB_WORKHORSE_VERSION
for versions < 13.9.X #1617 (comment 527838528) - Only auto-deploy tagging was affected by this and gitlab-org/release-tools!1389 (merged) fixed it #1617 (comment 528014370)
- We will propagate a bogus workhorse version to CNG Images and Omnibus, but they both ignore it now #1617 (comment 528014370)
- CNG will require
GITLAB_WORKHORSE_VERSION
for versions < 13.8.X #1617 (comment 528029794)