Continuous Delivery with Jenkins: the Good, the Bad and the Ugly - JAX DevOps 2018
2 likes1,012 views
The document discusses continuous delivery using Jenkins, highlighting its advantages and challenges, including its integration capabilities and community support. It covers the setup of Jenkins pipelines using plugins like the Blue Ocean and the Delivery Pipeline Plugin, emphasizing a convention-over-configuration approach. Additionally, it includes best practices for infrastructure as code and efficient testing within CI/CD workflows.
Continuous Delivery with Jenkins: the Good, the Bad and the Ugly - JAX DevOps 2018
- 1. Continuous Delivery with Jenkins: the Good, the Bad and the Ugly Tommy Tynjä @tommysdk tynja.com diabol.se diabol.se/blog github.com/Diabol
- 7. Plugins
- 14. What requirements do we have on a CI / CD tool?
- 15. Run on premise Infrastructure as code Deployment support Isolated builds using containersCustomisable Scalable Good pipeline visualisation Community Reasonable price
- 16. Goals Satisfy our customers Good ways of working with Jenkins
- 17. Comparing CI/CD tools Jenkins, GoCD, TeamCity, Concourse, Drone, Bamboo
- 18. Comparing CI/CD tools Jenkins, GoCD, TeamCity, Concourse, Drone, Bamboo
- 19. Open source and good community Many integrations / plugins exist We already know it! Why Jenkins?
- 20. Traditional build jobs with downstream dependencies
- 21. 🔵 🔆 Deploy 🔵 🔆 Test 🔵 🔆 Build
- 22. 🔵 🔆 Deploy 🔵 🔆 Integration Test 🔵 🔆 Build 🔵 🔆 Regression Test 🔵 🔆 Static code analysis
- 31. Jenkinsfile
- 32. https://plugins.jenkins.io/workflow-cps-global-lib Pipeline: Shared Groovy Libraries ID: workflow-cps-global-lib
- 34. $ tree ├── src │ └── Example.groovy ├── test │ └── ExampleTest.groovy └── vars └── deliveryPipeline.groovy
- 35. $ tree ├── src │ └── Git.groovy ├── test │ └── GitTest.groovy └── vars └── deliveryPipeline.groovy
- 36. $ tree ├── src │ ├── Build.groovy │ ├── Deployment.groovy │ ├── Git.groovy │ ├── Validation.groovy │ └── Version.groovy ├── test │ ├── BuildTest.groovy │ ├── DeploymentTest.groovy │ ├── GitTest.groovy │ ├── ValidationTest.groovy │ └── VersionTest.groovy └── vars └── deliveryPipeline.groovy
- 37. Easy to adopt Convention over configuration
- 38. deliveryPipeline { maintainer = 'Team 1337' projectName = 'order-service' type = 'library' language = 'java' }
- 42. jenkins-pipeline-dsl-latest 🔵 🔆 Tag 🔵 🔆 Test 🔵 🔆 Compile
- 45. Infrastructure as code? Not enough!
- 46. Short feedback cycles Continuous Delivery
- 49. ├── jenkins-agent │ ├── certificates │ │ └── ... │ └── Dockerfile
- 50. ├── jenkins-agent ├── jenkins-master │ ├── certificates │ ├── init.groovy.d │ ├── Dockerfile │ └── plugins.txt └── build.gradle
- 51. 1. Build containers 2. Run tests 3. Upload (4. Deploy)
- 53. class PluginTest extends Specification { @Shared @ClassRule JenkinsMasterContainer jenkinsContainer = new JenkinsMasterContainer() @Shared Map<String, String> configuredPlugins = collectEntriesFromPluginsTxt() @Shared List<Plugin> installedPlugins
- 54. class PluginTest extends Specification { @Shared @ClassRule JenkinsMasterContainer jenkinsContainer = new JenkinsMasterContainer() @Shared Map<String, String> configuredPlugins = collectEntriesFromPluginsTxt() @Shared List<Plugin> installedPlugins
- 55. @Unroll def 'Plugin is installed: #pluginId'() { given: 'A configured plugin' Plugin plugin = installedPlugins.find { it.shortName == pluginId } expect: 'Plugin is present' plugin where: pluginId << configuredPlugins.keySet() }
- 58. init.groovy.d BitbucketServerEndpoint endpoint = new BitbucketServerEndpoint(server, url, manageWebHooks, credentialsId)
- 59. Jenkins pipeline for Jenkins
- 60. Summary Challenges Everything as code Continuous Delivery of Continuous Delivery
- 61. Thank you! Tommy Tynjä @tommysdk tynja.com diabol.se diabol.se/blog github.com/Diabol