Feature Request: Allow multiple tags in the Automated Builds Configuration

Currently, you can only specify one tag per automated build.

Instead, I would like to propose that multiple could be used. This would allow the common pattern of tagging releases that follow semantic versioning; e.g. :1.2.3, :1.2, :1

I was imagining something like (using ; as a separator):

Tag  /^v([0-9]+)\.([0-9]+)\.([0-9]+)$/   {\1}.{\2}.{\3};{\1}.{\2};{\1}

This would cut down on the amount of resources needed; currently to do the same thing you have to repeat the build 3 times:

Tag  /^v([0-9]+)\.([0-9]+)\.([0-9]+)$/   {\1}.{\2}.{\3}
Tag  /^v([0-9]+)\.([0-9]+)\.([0-9]+)$/   {\1}.{\2}
Tag  /^v([0-9]+)\.([0-9]+)\.([0-9]+)$/   {\1}

Note: You have to do it this way because the “Docker Tag” can’t be the same.

1 Like