First is that your pipeline steps are limited to master and feature/* branches. A Tag is a pointer to a commit sha and has no formal association with a branch. Your steps will therefore never execute for a branch. Consider the following modification:
i think i figure out what my problem is: drone exec seems to be evaluating one single pipeline and in my case i have two of them. if i pass --pipeline Deploy to docker exec the execution is as expected.
i honestly expected that drone exec behaves similar to a drone agent in case of multiple pipelines and it will execute the first one that matches the criteria. doesn’t seem to be the case. is it by design or a bug?
i see, thank you so much for the info. if you don’t mind me asking: how does the server figures out which pipeline to run?
i’m pretty sure in our setup we don’t have anything that we configure to pick the right pipeline so there must be something somewhere that figures out which pipeline to execute. all our services have multiple pipelines in a single .drone.yml
hmm…i don’t think we are talking about the same thing here. how does the named pipeline gets picked? or maybe i should ask: how does the server knows which named pipeline to send to the agent?
above i have two named pipelines in the same file and i definitely don’t pick which one to run, something is doing that.
if you look at my example i have two pipelines: one named Build which triggers by a push to certain branch names and one named Deploy that is triggered by a tag. so something decides…oh, the event i received from the hook is a tag event…let me see which pipeline would match event: tag AND the tag name matches"…that piece. makes sense?