Jenkins Docker
•
51 gostaram•65,285 visualizações
Docker and Jenkins. Orchestrating Continuous Delivery Through the use of build pipelines, Continuous Delivery will enable faster and more frequent build, test and deployment cycles of software. To ensure that what you are delivering has the required quality: how do we build a continuous delivery pipeline in the real world? In this session, instead of relying on static step configurations, we are going to demonstrate how to code a pipeline using Jenkins and Gradle and how Docker can help on this task. The end result is faster application releases with higher quality.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (20)
Semelhante a Jenkins Docker
Semelhante a Jenkins Docker (20)
Mais de Alex Soto
Mais de Alex Soto (20)
Último
Último (20)
Jenkins Docker
- 1. Orchestrating Continuous Delivery D O C K E R A N D J E N K I N S .
- 2. A L E X S O T O B - L O R D O F T H E J A R S . C O M alexsotob lordofthejars
- 3. S O F T W A R E I S E A T I N G T H E W O R L D alexsotob lordofthejars
- 14. K E Y I S A U T O M A T I O N alexsotob lordofthejars
- 18. S P E E D + F R I C T I O N = H E A T alexsotob lordofthejars
- 19. G O - G O - G O alexsotob lordofthejars
- 20. C O N T A I N E R S C O D I F Y O S C O N F I G alexsotob lordofthejars
- 22. $ docker run $ docker run --ti ubuntuti ubuntu::12.1012.10 bash bash [[a2ba2b]] apt apt--getget update update [[a2ba2b]] apt apt--getget install curl install curl [[a2ba2b]] exit exit $ docker commit $ docker commit --m m "curl installed""curl installed" a2b username a2b username//imageimage $ docker build $ docker build .. H O W I B U I L D A D O C K E R I M A G E ? alexsotob lordofthejars
- 24. J E N K I N S : D O C K E R A N D C D Docker Hub Notification: triggers downstream jobs when a tagged container is pushed to Docker Hub alexsotob lordofthejars
- 25. J E N K I N S : D O C K E R A N D C D Docker Hub Notification: triggers downstream jobs when a tagged container is pushed to Docker Hub Docker Traceability: identifies which build pushed a particular container, displays on Jenkins builds page alexsotob lordofthejars
- 26. J E N K I N S : D O C K E R A N D C D Docker Hub Notification: triggers downstream jobs when a tagged container is pushed to Docker Hub Docker Traceability: identifies which build pushed a particular container, displays on Jenkins builds page Docker Custom Build Environment: specifies customized build environments as Docker containers alexsotob lordofthejars
- 27. J E N K I N S : D O C K E R A N D C D Docker Hub Notification: triggers downstream jobs when a tagged container is pushed to Docker Hub Docker Traceability: identifies which build pushed a particular container, displays on Jenkins builds page Docker Custom Build Environment: specifies customized build environments as Docker containers Docker: use a docker host to dynamically provision a slave, run a single build, then tear-down alexsotob lordofthejars
- 28. J E N K I N S : D O C K E R A N D C D Docker Hub Notification: triggers downstream jobs when a tagged container is pushed to Docker Hub Docker Traceability: identifies which build pushed a particular container, displays on Jenkins builds page Docker Custom Build Environment: specifies customized build environments as Docker containers Docker: use a docker host to dynamically provision a slave, run a single build, then tear-down Build and Publish : builds projects that have a Dockerfile and pushes the resultant tagged image to Docker Hub alexsotob lordofthejars
- 29. B U I L D , T E S T , & D E P L O Y D O C K E R I M A G E F R O M J E N K I N S alexsotob lordofthejars
- 30. D O C K E R H U B N O T I F I C A T I O N P L U G I N alexsotob lordofthejars
- 33. D O C K E R T R A C E A B I L I T Y P L U G I N alexsotob lordofthejars
- 37. D O C K E R P L U G I N alexsotob lordofthejars
- 39. D O C K E R C U S T O M B U I L D E N V I R O N M E N T P L U G I N alexsotob lordofthejars
- 42. B U I L D A N D P U B L I S H P L U G I N alexsotob lordofthejars
- 46. N O M O R E B U I L D J O B S / U P / D O W N S T R E A M S P L E A S E ! ! ! ! alexsotob lordofthejars
- 47. Continuous Delivery as Code P I P E L I N E P L U G I N alexsotob lordofthejars
- 48. F E A T U R E S O F P I P E L I N E P L U G I N Configuration in Source Repositories
- 49. F E A T U R E S O F P I P E L I N E P L U G I N Configuration in Source Repositories Less click-and-type, more code
- 50. F E A T U R E S O F P I P E L I N E P L U G I N Configuration in Source Repositories Less click-and-type, more code From simple to complex
- 51. F E A T U R E S O F P I P E L I N E P L U G I N Configuration in Source Repositories Less click-and-type, more code From simple to complex Survives Jenkins restarts & connection losses ($)
- 52. F E A T U R E S O F P I P E L I N E P L U G I N Configuration in Source Repositories Less click-and-type, more code From simple to complex Survives Jenkins restarts & connection losses ($) Reusable Definitions
- 53. F E A T U R E S O F P I P E L I N E P L U G I N Configuration in Source Repositories Less click-and-type, more code From simple to complex Survives Jenkins restarts & connection losses ($) Reusable Definitions Build history/trend segregated per branches
- 54. F E A T U R E S O F P I P E L I N E P L U G I N Configuration in Source Repositories Less click-and-type, more code From simple to complex Survives Jenkins restarts & connection losses ($) Reusable Definitions Build history/trend segregated per branches UI ($ -> OSS)
- 57. stage stage 'assemble-binaries''assemble-binaries' nodenode(('linux''linux')) {{ unstash unstash 'source''source' withEnvwithEnv(([["SOURCE_BUILD_NUMBER=${env.BUILD_NUMBER}""SOURCE_BUILD_NUMBER=${env.BUILD_NUMBER}"]])) {{ gradle gradle 'assemble''assemble' }} }} input messageinput message:: "Deploy Application to QA ?""Deploy Application to QA ?" stage namestage name:: 'Deploy to QA''Deploy to QA',, concurrency concurrency:: 11 node node {{ echo echo "Application Deployed to QA.""Application Deployed to QA." }} J E N K I N S F I L E ( 2 / 3 ) alexsotob lordofthejars
- 59. D O C K E R P I P E L I N E I N T E G R A T I O N
- 63. D I F F E R E N T W A Y S O F D O I N G S A M E T H I N G S W I T H D S L alexsotob lordofthejars
- 64. S I M P L E B U I L D F O R P I P E L I N E P L U G I N alexsotob lordofthejars
- 66. L E T ' S W I N D D O W N alexsotob lordofthejars
- 67. C O N C L U S I O N S Automation is the Key alexsotob lordofthejars
- 68. C O N C L U S I O N S Automation is the Key Docker Simplifies Environment Problems alexsotob lordofthejars
- 69. C O N C L U S I O N S Automation is the Key Docker Simplifies Environment Problems Jenkins is Ready For Docker and CD alexsotob lordofthejars
- 70. C O N C L U S I O N S Automation is the Key Docker Simplifies Environment Problems Jenkins is Ready For Docker and CD Pipleline as Code gives you Freedom alexsotob lordofthejars
- 71. O N L Y O N E P I E C E O F T H E J I G S A W alexsotob lordofthejars
- 72. F O L L O W T H E R U L E S , A D A P T T O Y O U R N E E D S alexsotob lordofthejars
- 73. C L O U D B E E S J E N K I N S
- 74. It is not necessary to change. Survival is not mandatory. W . E D W A R D S D E M I N G alexsotob lordofthejars
- 75. Q U E S T I O N S alexsotob lordofthejars