Connect Your On-premise Resources to Jenkins in the Cloud

Two of the most common RFE’s for DEV@cloud centered around connecting back to resources behind the firewall or running builds on specific operating systems not available in the cloud (e.g., Mac OS builds).

Recently, we launched a feature called “On-premise Executors (OPEs) [1]” that addresses these use cases. OPE’s lets teams connect their slaves to the Jenkins master on DEV@cloud. The benefit is that customers can continue using the master - as well as slaves on DEV@cloud - for regular builds and use on-premise executors for specific OSs or stacks.

This feature also enables customers to use resources behind their firewall (such as source code, test databases, etc.) with the Jenkins master in the cloud. The on-premise executors will have direct access to these on-premise resources.

Customers would have had to run their own masters before this feature was available.

This feature is available as part of the DEV@cloud Enterprise subscription tier and customers need to upgrade their subscription and pre-buy (for the month) the number of executors they want. A number of our existing customers are using it today.

Finally, if all you care about is connecting to the on-premise resources, as opposed to running a slave with a custom software stack, then the VPN feature (in beta) would be the way to go. Email me if you will like to participate in the beta program. I do hope that you give the new features a spin! 

1. On-premise executors
2. VPN to on-premise resources

 

- Harpreet Singh
Senior Director, Product Management
CloudBees
www.cloudbees.com



Harpreet has 15 years of experience in the software industry. Prior to CloudBees, he was at Oracle and Sun for 10 years in various roles, including leading the marketing efforts for Java EE 6 and GlassFish 3.1. He was also product manager for Hudson, launching it within Sun’s GlassFish portfolio.

Add new comment