You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The artifacts generated in Devtron CI, in case of tag-based builds, should have the same tags as that of given in Bitbucket/Github/Gitlab..
🎤 Pitch
In Devtron, in case of tag-based builds, the artifacts generated have the tags in format of: {tag-given}-{env-id}-{pipeline-id} But it would be helpful to just propagate the same tags as given in version control without the env id or pipeline id.
✌️ Solution
Propagate the same tag as given in version control.
🔄️ Alternative
Alternate way could be using Devtron's custom tags feature, but there as well counter needs to be given and it won't take the same tag given in version control. Additionally, it will require manual efforts to give the same tag that is already given in version control.
👀 Have you spent some time to check if this issue has been raised before?
abhibhaw
changed the title
Feature: Propogate tags of Bitbucket/Github/Gitlab directly in CI artifact tags
Feature: Propagate tags of Bitbucket/Github/Gitlab directly in CI artifact tags
Dec 15, 2023
🔖 Feature description
The artifacts generated in Devtron CI, in case of tag-based builds, should have the same tags as that of given in Bitbucket/Github/Gitlab..
🎤 Pitch
In Devtron, in case of tag-based builds, the artifacts generated have the tags in format of:
{tag-given}-{env-id}-{pipeline-id}
But it would be helpful to just propagate the same tags as given in version control without the env id or pipeline id.✌️ Solution
Propagate the same tag as given in version control.
🔄️ Alternative
Alternate way could be using Devtron's custom tags feature, but there as well counter needs to be given and it won't take the same tag given in version control. Additionally, it will require manual efforts to give the same tag that is already given in version control.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
AB#6872
The text was updated successfully, but these errors were encountered: