I have a pretty simple pipeline that promotes an application from build to production. The simplified job flow is as follows:
- deploy to dev
- deploy to prod
We are using the semver resource and a maven resource for uploading / downloading the artifact.
What I am trying to do is keep a separate version that represents the previous deployed version and create a job that will ‘roll back’ to that version if triggered.
Since we are using semver - versions are stored in files after a get step. What I am having problems with is accessing a version file during a get step of the maven resource. I see that resources allow a specific version to be passed in, but not via a file.
Does anyone have an example similar to what I am trying to do, or am I going down an anti-pattern path?