Jenkins pipeline triggered by jira

[David Plesu]

Hello,

I hope you are doing well!

I would like to ask you a question regarding the Jenkis.

Let me make a brief introduction on our case:

- Our jira is in Cloud

- Our jenkins is in AWS and is not discoverable to the inthernet.

I installed in Jira the plugin (free version) that connect the jenkins with jira + we configurated the Jira Plugin on Jenkins site. 

Now when we commit something on a pipeline we see the build id in Jira + URL.

We want to be able to trigger a job pipeline from Jira. But our Jenkins is only for the domain.

Please advise how to do it.

And the process - to have a field with some jira automation to send a post webhook.

Or with scriptrunner in the post functions for example.

Or to have a specific issue that will be connected with the pipeline, and when we change the status then the pipeline will be triggered.

Thank you

Best regards,

David.

[Mark Rekveld - Marvelution]

Hi @David Plesu 

You can take a look at the Jenkins Integration for Jira app. Using this app, you can connect your private Jenkins site, using the "Accessible Through Tunneling" method and trigger any job that is enabled for data processing.

Feel free to reach out if you need help.

Cheers,
Mark

Disclaimer, I'm the developer of the app mentioned.

[David Plesu]

Hello @Mark Rekveld - Marvelution ,

Thank you for the response :) 

I know about this pugin, but we are looking for a free integration.

Regards,

David.

[Mark Rekveld - Marvelution]

Hi @David Plesu 

I'm not sure a free app is available at the moment, especially one that can connect to Jenkins behind a firewall.

Cheers,
Mark

[David Plesu]

Hello,

I understand this, the solution is to use the webhook - and to set up proxy.

What is your opinion about that?

Regards,

David.

[Mark Rekveld - Marvelution]

Hi @David Plesu 

I don't think its as simple as a webhook and the proxy server.

You will also need to interpret and translate the webhook event to trigger the correct job in Jenkins.

Using a webhook will, I think, also limit the ability to trigger jobs in Jenkins, as sending webhook events is not something a user can do directly. He/She will need to transition an issue in order for the webhook to trigger.

Also, I'm not sure if you will be able to reuse issue data as build parameters, but may be wrong on this.

Webhook can be done, but will require quite a bit of work.

In the end its the question if your time invested in building and maintaining a webhook solution is cheaper then the subscription costs of an app.

Cheers,
Mark

[David Plesu]

We tought to set a proxy firewall in front of the Jenkins - but not sure that is the best approach here + not sure if we will get the approval!

Thanks!