I’m using plugins/downstream image to trigger the downstream jobs, however, the trigger on the downstream job will be successful when we have committed the latest code on the latest build, but assuming the downstream repo have the latest build with promoting or rollback options. Downstream jobs don’t work as expected. Since the trigger of the downstream job is the deployment pipeline but not the build pipeline. Do I miss something here? how do we trigger the code build of downstream jobs instead of Deploy pipeline of downstream jobs?
I would think downstream jobs should trigger or restart the build from the branches tab instead of the activity feed. Since activity feed can promote job or triggered for the build.
I would think downstream jobs should trigger or restart the build from the branches tab instead of the activity feed. Since activity feed can promote job or triggered for the build.
the ability to trigger a build by branch was not added until Drone version 1.7 which was released a few months ago. The reason this plugin attempts to restart a build is because early versions of Drone only had a restart endpoint.
we received a pull request to change how this plugin works, however, this would be a breaking change which would violate our strict commitment to backward compatibility. You can find the pull request here:
for teams that want different behavior, our recommendation is to either fork the plugin and modify to suit your needs or create a new plugin.
