Finding Jira's issue should be optional

[hugoseabra]

Sometimes, during the flow, we do not reference any Jira's issue. So, when that happens, the plugin breaks the pipeline.

What if finding Jira's issue would be optional?

drone-jira/plugin/plugin.go

Line 82 in 898ec6b

if issue == "" {

[bradrydzewski]

according the Jira API docs you must provide one or more issue keys (min value 1). I have not tried to use the API without an issue key, but based on the docs, it sounds like this would result in an API failure. So not sure we can make this optional unless it is supported by Jira.

A list of deployments to submit to Jira. Each deployment may be associated with one or more Jira issue keys, and will be associated with any properties included in this request.
Min items: 1

perhaps if no issue number is found, the plugin should exit with a warning message and a zero exit code, which would prevent the overall pipeline from failing?

[miraldo]

any update on this issue, I have the same problem and I can't find a solution.

it would be great to exit without errors on pipeline.

any workaround?

[christophka]

The workaround that we ended up is to ignore failures on this particular step, using failure: ignore
https://docs.drone.io/pipeline/docker/syntax/steps/#failure

Maybe that helps someone :)

[miraldo]

I had already implemented your suggestion here, but thank you very much.