当前位置:   article > 正文

docker方式 部署jenkins服务,实现持续集成(CI/CD)功能

docker方式 部署jenkins服务,实现持续集成(CI/CD)功能

一、背景:

因公司需求,需要部署一套jenkins自动化部署服务,并且是通过docker容器的方式部署的。

二、jenkins简介:

什么是Jenkins ?

 Jenkins是一个开源软件,是基于Java开发的一种持续集成工具,用于监控持续重复的工作,旨在提供一个开放易用的软件平台,使软件项目可以进行持续集成( CI/CD)。

三:CICD流程简介: 

持续集成( CI/CD)是什么?

CI(Continuous Integration)始终指持续集成 ,CD(Continuous Delivery/Continuous Deployment)是持续交付和/或持续部署,总结为如下三点。

  • 持续集成
  • 持续交付
  • 持续部署

cicd基本流程:

四、docker部署jenkins服务:

1、拉取jenkins镜像:

docker search jenkinsci/blueocean

docker pull jenkinsci/blueocean

  1. [root@iZwz9ippftvoxv000lpl0tZ ~]# docker search jenkinsci/blueocean
  2. NAME DESCRIPTION STARS OFFICIAL
  3. jenkinsci/blueocean https://jenkins.io/projects/blueocean 732
  4. [root@iZwz9ippftvoxv000lpl0tZ ~]# docker pull jenkinsci/blueocean
  5. Using default tag: latest
  6. latest: Pulling from jenkinsci/blueocean
  7. 97518928ae5f: Already exists
  8. f4d84728e541: Already exists
  9. 419d112ff4fa: Already exists
  10. ecf8c1881f75: Already exists
  11. 78b59c3bfdb7: Already exists
  12. 2ff43df4e763: Already exists
  13. aac7818be7cc: Already exists
  14. 2913a3e94ae4: Already exists
  15. f75b1dac4ec0: Already exists
  16. 3d3fbe6f1850: Already exists
  17. 07ef919d711b: Already exists
  18. 5b96e9c30f6a: Already exists
  19. 83dcd37be04b: Already exists
  20. 6beb8929489c: Already exists
  21. 476e95021232: Already exists
  22. 9add339bd1dd: Already exists
  23. ecb71d48971e: Already exists
  24. 384cd4783059: Already exists
  25. latest: Pulling from jenkinsci/blueocean
  26. Digest: sha256:f27933313986f7fb0b5784aa6520ebddc455ce258cbf4d13a3e3cf9d4c94d992
  27. Status: Image is up to date for jenkinsci/blueocean:latest
  28. docker.io/jenkinsci/blueocean:latest

 2、部署jenkins服务:

执行部署jenkins容器服务命令:

docker run -p 8080:8080 -p 8081:8081 -p 50000:50000 --name jenkins -v jenkins_data:/var/jenkins_home jenkinsci/blueocean

  1. [root@iZwz9ippftvoxv000lpl0tZ ~]# docker run -p 8080:8080 -p 8081:8081 -p 50000:50000 --name jenkins -v jenkins_data:/var/jenkins_home jenkinsci/blueocean
  2. Running from: /usr/share/jenkins/jenkins.war
  3. webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
  4. 2024-04-17 08:01:21.037+0000 [id=1] INFO org.eclipse.jetty.util.log.Log#initialized: Logging initialized @675ms to org.eclipse.jetty.util.log.JavaUtilLog
  5. 2024-04-17 08:01:21.151+0000 [id=1] INFO winstone.Logger#logInternal: Beginning extraction from war file
  6. 2024-04-17 08:01:21.183+0000 [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath
  7. 2024-04-17 08:01:21.277+0000 [id=1] INFO org.eclipse.jetty.server.Server#doStart: jetty-9.4.45.v20220203; built: 2022-02-03T09:14:34.105Z; git: 4a0c91c0be53805e3fcffdcdcc9587d5301863db; jvm 11.0.16.1+1
  8. 2024-04-17 08:01:21.620+0000 [id=1] INFO o.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
  9. 2024-04-17 08:01:21.675+0000 [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node0
  10. 2024-04-17 08:01:21.675+0000 [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults
  11. 2024-04-17 08:01:21.680+0000 [id=1] INFO o.e.j.server.session.HouseKeeper#startScavenging: node0 Scavenging every 600000ms
  12. 2024-04-17 08:01:22.278+0000 [id=1] INFO hudson.WebAppMain#contextInitialized: Jenkins home directory: /var/jenkins_home found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
  13. 2024-04-17 08:01:22.595+0000 [id=1] INFO o.e.j.s.handler.ContextHandler#doStart: Started w.@1b1637e1{Jenkins v2.346.3,/,file:///var/jenkins_home/war/,AVAILABLE}{/var/jenkins_home/war}
  14. 2024-04-17 08:01:22.638+0000 [id=1] INFO o.e.j.server.AbstractConnector#doStart: Started ServerConnector@5b12b668{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}
  15. 2024-04-17 08:01:22.638+0000 [id=1] INFO org.eclipse.jetty.server.Server#doStart: Started @2278ms
  16. 2024-04-17 08:01:22.646+0000 [id=23] INFO winstone.Logger#logInternal: Winstone Servlet Engine running: controlPort=disabled
  17. 2024-04-17 08:01:22.937+0000 [id=30] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization
  18. 2024-04-17 08:01:23.318+0000 [id=31] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins
  19. 2024-04-17 08:01:28.570+0000 [id=31] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins
  20. 2024-04-17 08:01:28.630+0000 [id=30] INFO jenkins.InitReactorRunner$1#onAttained: Started all plugins
  21. 2024-04-17 08:01:28.718+0000 [id=30] INFO jenkins.InitReactorRunner$1#onAttained: Augmented all extensions
  22. WARNING: An illegal reflective access operation has occurred
  23. WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v7.Java7$1 (file:/var/jenkins_home/war/WEB-INF/lib/groovy-all-2.4.21.jar) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class,int)
  24. WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v7.Java7$1
  25. WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
  26. WARNING: All illegal access operations will be denied in a future release
  27. 2024-04-17 08:01:30.446+0000 [id=31] INFO jenkins.InitReactorRunner$1#onAttained: System config loaded
  28. 2024-04-17 08:01:30.447+0000 [id=31] INFO jenkins.InitReactorRunner$1#onAttained: System config adapted
  29. 2024-04-17 08:01:30.448+0000 [id=31] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all jobs
  30. 2024-04-17 08:01:30.453+0000 [id=29] INFO jenkins.InitReactorRunner$1#onAttained: Configuration for all jobs updated
  31. 2024-04-17 08:01:30.496+0000 [id=45] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Download metadata
  32. 2024-04-17 08:01:30.506+0000 [id=45] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Download metadata. 8 ms
  33. 2024-04-17 08:01:30.601+0000 [id=30] INFO jenkins.install.SetupWizard#init:
  34. *************************************************************
  35. *************************************************************
  36. *************************************************************
  37. Jenkins initial setup is required. An admin user has been created and a password generated.
  38. Please use the following password to proceed to installation:
  39. 436c75eef44d4db1a72f47da0300f659
  40. This may also be found at: /var/jenkins_home/secrets/initialAdminPassword
  41. *************************************************************
  42. *************************************************************
  43. *************************************************************
  44. 2024-04-17 08:01:46.417+0000 [id=30] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization
  45. 2024-04-17 08:01:46.532+0000 [id=22] INFO hudson.lifecycle.Lifecycle#onReady: Jenkins is fully up and running

注意这里可以获取Jenkins控制台登陆密码,后面会需要用到。

3、登入jenkins服务:

这样利用你访问机器的IP地址+8080 即可出现jinkens的界面

 会显示如下的内容

这里需要输入上面的获取到密码:436c75eef44d4db1a72f47da0300f659 

4、初始化jenkins服务: 

上面输入密码之后就会跳转到如下界面
注:这里选择推荐的插件

选择之后弹出如下:

创建一个管理员用户: 

 

保存之后,需要重启一下jenkins服务。然后登入一下jenkins。

到此,jenkins服务的部署就完成了。

声明:本文内容由网友自发贡献,不代表【wpsshop博客】立场,版权归原作者所有,本站不承担相应法律责任。如您发现有侵权的内容,请联系我们。转载请注明出处:https://www.wpsshop.cn/w/凡人多烦事01/article/detail/463383
推荐阅读
相关标签
  

闽ICP备14008679号