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
My company has over a dozen microservices that we release based on a tag. This is a very manual process with SlashDeploy currently. Would it be possible to allow a comma separated list of repos in the /deploy command. For example, then we could do:
/deploy owner/repo1@refs/tags/v1.2.0,owner/repo2@refs/tags/v1.2.0,owner/repo3@refs/tags/v1.2.0 to production
Alternatively, a new predicate could be added for tag. For example an at <tag> predicate:
/deploy owner/repo1 at v1.2.0 to production
Combining with the comma-separated list of repos we would have:
/deploy owner/repo1,owner/repo2,owner/repo3 at v1.2.0 to production
That would be a very streamlined way to release a specific version of multiple repos.
The text was updated successfully, but these errors were encountered:
@strobus thanks for submitting this request. I've scheduled this feature to work on next and will update the progress here. The first approach looks better as it can support multiple repos with different tags, so it's more flexible that way. I hope it will improve your workflow then ✌️
My company has over a dozen microservices that we release based on a tag. This is a very manual process with SlashDeploy currently. Would it be possible to allow a comma separated list of repos in the /deploy command. For example, then we could do:
Alternatively, a new predicate could be added for tag. For example an
at <tag>
predicate:Combining with the comma-separated list of repos we would have:
That would be a very streamlined way to release a specific version of multiple repos.
The text was updated successfully, but these errors were encountered: