Hi, beyond base images which are more obvious, we're looking at using image builder to bundle up our actual application docker images. Something like what's described here with chained pipelines. The challenge we're having is that we'd like to do something like the following: "Our Base Image" -> fooapp, but it's not really clear how to handle needing to concurrently support multiple versions of 'fooapp'.
For instance, fooapp:1.2.3/1 is in production (based on a 'fooapp' pipeline, and the fooapp:1.2.3 recipe). If there's a base image update, Image Builder automatically creates a fooapp:1.2.3/2. So far so good. What's not clear, is how to handle the 'next' version, say 1.2.4, that's in our test environment, we also want 1.2.4/1,2... concurrently as well.
We'd obviously have the 1.2.4 version of the fooapp recipe, but only one recipe/version can be associated with a pipeline at a given time. And pipelines themselves have no concept of versioning. The only thing i've been able to come up with is a kludge of tacking the version onto the pipeline name, which aside from being difficult to manage, also loses the build history, etc across versions.
Any suggestions would be greatly appreciated.
