We finally set up a dedicated jenkins job, triggered after each new commit to the sal master branch, and triggering a build of sal before building a sam docker image and pushing it under a sepcific tag (dev-<date>). Waiting for any new update to sal (on activeeon side) before checking on your side if you managed to consider the new pushed image.
We finally set up a dedicated jenkins job, triggered after each new commit to the sal master branch, and triggering a build of sal before building a sam docker image and pushing it under a sepcific tag (dev-<date>). Waiting for any new update to sal (on activeeon side) before checking on your side if you managed to consider the new pushed image.