Today we continue our series of on-demand training videos with a simple introduction to the DevOps concept of “continuous everything” followed by specific examples of how Nexus works with other pieces of the software supply chain, such as Jenkins, Hudson and Atlassian Bamboo.
We start with the first steps to get your builds using Nexus as the components source. This will allow you to rely on the performance of Nexus within your network. With this configuration, your builds are not wasting time looking for components in a number of external repositories and then downloading them again and again. In order to show Nexus at the heart of a basic CI process, we are providing the following step-by-step examples.
- Nexus at the Heart of Continuous*
- Accessing Components from Nexus in Jenkins – Part 1
- Accessing Components from Nexus in Jenkins – Part 2
- Accessing Components from Nexus in Hudson- Part 1
- Accessing Components from Nexus in Hudson – Part 2
- Accessing Components from Nexus in Atlassian Bamboo
If you are not a member of the community, please join us and you too will have immediate assess to this series, along with others such as “The Nexus 2 Minute Challenge“, “Nexus Professional and Smart Proxy” and “Empowering Release with the Nexus Staging Suite“.
To get you started, here’s the first video in the Heart of Continuous* series. Join the community to have access to the other 20 modules in the series.
Latest posts by Manfred Moser (see all)
- Integration with Nexus Repository 3 - June 8, 2016
- Sonatype Automated Deployments with Atlassian Bitbucket Pipelines - May 24, 2016
- Migrating to Nexus Repository 3 – Easy Peasy - May 11, 2016
- Puppet-eering the Nexus Repository Manager - May 2, 2016
- Impressions from DevOpsDays Vancouver 2016 - April 19, 2016