JUC 2014: Boston
Jenkins User Conference
Wednesday, 18 June 2014 - 8:00am to 6:30pm
The Jenkins User Conference focuses on Continuous Integration (CI) as the fundamental best practice for enterprise software development. Our presenters are experienced Jenkins open source developers, executives, business managers, architects and authors who are luminaries within the Jenkins community. They represent the many organizations around the world who are leveraging the use of Jenkins within the application development lifecycle.
Jenkins has various ways to “chain” projects together: triggers, promotions, copied artifacts, etc. However, assembling these into a complex continuous deployment pipeline can be painful.
Jenkins is great. We know it well enough, though, to realize that it’s also not a silver bullet.
Discuss the experience of using Jenkins to manage the full stack integration build and testing for DealerTrack 2.0 for 6+ distributed scrum teams. Topics include:
Jenkins API is a Python module that accesses Jenkins resources and configuring jobs. It combines Jenkins REST and API. In this talk we will demonstrate how to use this module by creating, configuring and triggering a job and seeing the results.
Come to our show where we talk about what CloudBees sees as challenges of deploying, operating, and using large-scale Jenkins installations, and what we are doing to help those users succeed; we’ll talk about Jenkins in the continuous delivery era and our efforts in this space, such as Chef/Puppe
Ever wished that you could fully automate your Integration, Tests and Delivery process for Node.js? In this talk we will demonstrate the full flow of dev, texts and distribution of your Node.js code to your production servers, without losing control.
We have used the power of Jenkins to build our Symfony2 Application, send a message using RabbitMQ to a consumer in the app ready to re-deploy itself. Jenkins builds are triggered by creating and accepting merge requests inside of GitLab.
Jenkins CI provides a robust framework for the integration and standardization of scientific workflows.
More information is a good thing. Normally parameterized build input such as notes, Git branches, and bug tracking issues are lost once a build has completed. The only historical reference is in a report. Consequently, this data cannot easily be reused for future builds.
What if I told you Continuous Delivery with Jenkins was the key to Innovation? Choose Digital uses Jenkins to automate all of our testing and deployment.
This session will discuss two key components of our deployment pipeline: Continuous integration of Chef code and automated deployment of Java applications. CI jobs for Chef code run static analysis and then provision, configure and test EC2 instances.
Jenkins may start small in a company, but it often spreads across departments faster than a virus. And the bigger the installation, the more care you need to take in setting up your Jenkins infrastructure.
Lessons learned from running Jenkins for five days with no prior knowledge.
Continuous delivery helps you release more, more often, for less. This year it’s high on the C-Level agenda and so it should be - it’s a game changer for IT.
At MEDITECH, we needed a way to get individual files from a code base with 260 million lines of source code to build after a commit. This talk is about the issues we encountered, and how we eventually succeeded.
Every enterprise customer engagement is unique and time-sensitive, so it’s imperative that a CI tool is flexible, powerful and customizable enough to handle each unique project — quickly.