Thanks for your suggestion @ashwilliams1.
In this case, would the build be tagged as a promoted deployment, though?
I am currently doing this and having a deployment step just after building, however this sort of drops Drone’s deployment functionality as those are not listed under the deployment tab.
Ideally we could have:
- name: build
- go build
- go test
# if build passes, promote it
- name: promote
- drone build promote
- name: deploy
and, then adding another pipeline responsible for only perform the deployment? Based on the promotion itself? This way we know that deployments always reflect what’s listed on Drone.
Would there be any way to trigger a promotion event from inside a pipeline, or perhaps, simply a way to tag a build as deployed by keeping the pipeline steps you have suggested?
Or perhaps you would have another suggestion?
Thanks in advance