Closed evertonmc closed 3 years ago
Thanks for your feedback. Currently, when selecting latest release
, the orchestrator will find and re-deploy a latest available release regardless status of the target stage (i.e. it may re-run failed stages, if any).
It might be possible to add target stage status filter for latest release deployment, so it will only proceed with successfully deployed stages. I will add this to the backlog.
cool, thanks. Use case: recreate environment every morning with last successful release of every component.
Meanwhile, you can try tagging last successful release artifact using this extension and using artifact tag filter for the orchestrator job.
1) Successfully deploy stage 2) Add stage name tag to the deployed artifact (using task above 3) Run orchestrator with filter artifact tag = stage name
Thanks, but this only works for build artifacts coming from the same project as the release pipeline, which don't apply for me
This will be addressed in the next release.
Is it possible to trigger a release with the artifacts of the last successful release?![image](https://user-images.githubusercontent.com/5794688/66898580-c014e200-eff9-11e9-8390-54f56a888d26.png)