Replies: 1 comment
-
What you describe does not entirely match the philosophy and abilities of what Kargo can do today. If you tag a new version, and your CI system builds an entirely new image, this produces new Besides this, the usage of a mutable To create something that kind of resembles what you describe, there are a couple of options:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
So, here's something we do now. A push to main builds "something". Just whatever meets the requirements for a pull request to main. I build a container and I tag it
latest
and I replace the oldlatest
because it doesn't represent the main branch anymore. I trigger some reload of the development environment with the new latest.Now, I want to take a version and say "yeah, this is good" and give it a tagged release like v1.2. I used to use a git-tag to create that tag, and then trigger a build that builds a docker container with the tag v1.2.
In Kargo, the development environment is running "latest". But now I want to promote the versioned number up, because it's a real trackable version. But I can't promote the one that's in the Development stage, because it's 'latest' not 'v1.2'.
What am I missing here?
Beta Was this translation helpful? Give feedback.
All reactions