Azure Devops Pull Request and Jenkins behind corporate network

4
votes

I'm trying to figure out how can I connect my Jenkins Build server to the Azure DevOps Pull Request. My Jenkins Server is behind a corporate firewall, I don't have any way to have access to this server outside of the corporate network.

Due to the corporate network rules I cannot add a hook in Azure to call my Jenkins server, but my server can have access to the Microsoft Azure web site.

I tried to run the VSTS Agent with success on my Linux Jenkins server. It works, but It doesn't do what I would need to do. I don't want to change all my build process to build my application inside this Agent. I really want to be able to launch a Jenkins Pipeline build from my server and forward the build result to the Azure DevOps.

I cannot use the Jenkins VM provided by Azure DevOps, because my Jenkins build process has to run some regression test tool on real hardware unit in our lab to flag the build as a success.

So in other word:

1- I cannot use the VSTS agent because I need to use my Jenkins Build Server

2- I cannot use the Jenkins VM provided by Azure DevOps because I need to have access to real Hardware Unite

3- I think I cannot instrument my Jenkins to see if we have a new Pull Request branch, because I will not be able to send the Jenkins build result to the Microsoft Azure DeveOps server.

Anybody had to do something like that?

Any reading to suggest?

Thanks!

1
azure-devopsjenkins-pipelinejenkins-plugins

1 Answers

1
votes

Since one-way communication is going to be possible (from Jenkins to Azure DevOps), you'll have to do the following:

  • Set up your Jenkins pipeline to periodically poll Azure DevOps for new PR branches and build PRs
  • Set up a branch policy for approval from external services
  • Have Jenkins post the build status back to the external service API so that Azure DevOps knows whether the build has succeeded or failed