JDK 官网: https://www.oracle.com/java/technologies/downloads/#java8-linux

安装JDk

root@vms81:~# cd /opt/
root@vms81:/opt# tar xf jdk-8u333-linux-x64.tar.gz
root@vms81:/opt/jdk1.8.0_333# vim ~/.bashrc
export JAVA_HOME=/opt/jdk1.8.0_333
export PATH=$JAVA_HOME/bin:$PATH
export CLASSPATH=.root@vms81:/opt/jdk1.8.0_333# source ~/.bashrc
root@vms81:/opt/jdk1.8.0_333# java -version
java version "1.8.0_333"
Java(TM) SE Runtime Environment (build 1.8.0_333-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.333-b02, mixed mode)

部署jenkins

war包方式

Jenkins war包：http://mirrors.jenkins.io/war-stable/
java -jar jenkins.war --httpPort=28080nohup java -jar jenkins.war --httpPort=28080 &

官网:https://www.jenkins.io/zh/download/

容器方式

设置权限

[root@master jenkins]# vim jenkins-clusterRoleBinding.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:name: jenkins-clusterRoleBinding
roleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: jenkins-clusterRole
subjects:- kind: ServiceAccountname: jenkins-sanamespace: jenkins # 默认命名空间下也需要添加此行[root@master jenkins]# more  jenkins-clusterRole.yaml
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:name: jenkins-clusterRole
rules:- apiGroups: ["extensions", "apps"]resources: ["deployments"]verbs: ["create", "delete", "get", "list", "watch", "patch", "update"]- apiGroups: [""]resources: ["services"]verbs: ["create", "delete", "get", "list", "watch", "patch", "update"]- apiGroups: [""]resources: ["pods"]verbs: ["create","delete","get","list","patch","update","watch"]- apiGroups: [""]resources: ["pods/exec"]verbs: ["create","delete","get","list","patch","update","watch"]- apiGroups: [""]resources: ["pods/log"]verbs: ["get","list","watch"]- apiGroups: [""]resources: ["secrets"]verbs: ["get"][root@master jenkins]# more jenkins-sa.yaml
apiVersion: v1
kind: ServiceAccount
metadata:name: jenkins-sanamespace: jenkins

挂载

[root@master jenkins]# more jenkins-pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:name:  jenkinsnamespace: jenkins
spec:resources:requests:storage: 5GiaccessModes:- ReadWriteManystorageClassName: mysc1       # 提前设置了sc

设置deployment

[root@master jenkins]# more jenkins-deploy.yaml
apiVersion: apps/v1
kind: Deployment
metadata:name: jenkins-deploy         #deployment名称namespace: jenkins
spec:replicas: 1selector:matchLabels:app: jenkinstemplate:metadata:labels:app: jenkinsspec:terminationGracePeriodSeconds: 10     #优雅停止podserviceAccount: jenkins-sa            #后面还需要创建服务账户containers:- name: jenkinsimage: jenkins/jenkins:2.346.1-jdk8 #镜像版本(2.346.1默认安装的jdk11版本，如果想安装jdk8可以指定version：2.346.1-jdk8)imagePullPolicy: IfNotPresentports:- containerPort: 8080                #外部访问端口name: webprotocol: TCP- containerPort: 50000              #jenkins save发现端口name: agentprotocol: TCPresources:limits:cpu: 2memory: 1Girequests:cpu: 1memory: 512MilivenessProbe:httpGet:path: /loginport: 8080initialDelaySeconds: 30          #容器初始化完成后，等待30秒进行探针检查timeoutSeconds: 5failureThreshold: 12          #当Pod成功启动且检查失败时，Kubernetes将在放弃之前尝试failureThreshold次。放弃生存检查意味
着重新启动Pod。而放弃就绪检查，Pod将被标记为未就绪。默认为3.最小值为1readinessProbe:httpGet:path: /loginport: 8080initialDelaySeconds: 30timeoutSeconds: 5failureThreshold: 12volumeMounts:                       #需要将jenkins_home目录挂载出来- name: jenkins-homemountPath: /var/jenkins_homeenv:- name: LIMITS_MEMORYvalueFrom:resourceFieldRef:resource: limits.memorydivisor: 1Mi- name: JAVA_OPTS # -Dhudson.model.DownloadService.noSignatureCheck=true 关闭源配置检查，否则换源后可能无法使用value: -Xmx$(LIMITS_MEMORY)m -XshowSettings:vm -Dhudson.slaves.NodeProvisioner.initialDelay=0 -Dhudson.slaves.NodeProvis
ioner.MARGIN=50 -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85 -Duser.timezone=Asia/Shanghai -Dhudson.model.DownloadService.noSignat
ureCheck=true -Dhudson.model.UpdateCenter.updateCenterUrl=https://mirrors.tuna.tsinghua.edu.cn/jenkins/updates/securityContext:fsGroup: 1000volumes:- name: jenkins-homepersistentVolumeClaim: claimName: jenkins

设置svc

[root@master jenkins]# more jenkins-svc.yaml
apiVersion: v1
kind: Service
metadata:name: jenkins-agent
spec:selector:app: jenkinstype: NodePortports:- name: agentport: 50000targetPort: agent
---
apiVersion: v1
kind: Service
metadata:name: jenkins-web
spec:selector:app: jenkinsports:- name: webport: 8080targetPort: web

设置ingress

[root@master jenkins]# more jenkins-ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:name: jenkins-webnamespace: jenkinsannotations:nginx.ingress.kubernetes.io/rewrite-target: /
spec:ingressClassName: nginxrules:- host: 域名  http:paths:- path: /pathType: Prefixbackend:service:name: jenkins-webport:number: 8080

创建(apply)所有所需yaml文件

[root@master jenkins]# kubectl apply -f .
clusterrole.rbac.authorization.k8s.io/jenkins-clusterRole created
clusterrolebinding.rbac.authorization.k8s.io/jenkins-clusterRoleBinding created
deployment.apps/jenkins-deploy created
ingress.networking.k8s.io/jenkins-web created
persistentvolumeclaim/jenkins created
serviceaccount/jenkins-sa created
service/jenkins-agent created
service/jenkins-web created

检查

[root@master jenkins]# kubectl get all
NAME                                  READY   STATUS    RESTARTS   AGE
pod/jenkins-deploy-5654789768-vs9w9   1/1     Running   0          14mNAME                    TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)           AGE
service/jenkins-agent   NodePort    10.108.161.246   <none>        50000:30524/TCP   14m
service/jenkins-web     ClusterIP   10.101.34.109    <none>        8080/TCP          14mNAME                             READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/jenkins-deploy   1/1     1            1           14mNAME                                        DESIRED   CURRENT   READY   AGE
replicaset.apps/jenkins-deploy-5654789768   1         1         1       14m

访问ingress中设置的域名来访问jenkins

密码保存在运行的jenkins容器中

[root@master jenkins]# kubectl exec -it jenkins-deploy-5654789768-vs9w9 -- bashjenkins@jenkins-deploy-5654789768-vs9w9:/$ cat /var/jenkins_home/secrets/initialAdminPassword
939257093bc24356a7d53fc617259e7c       --------> 初始管理员密码

安装插件(后期更新插件一定要先备份插件–家目录下的plugins文件)

常用插件选择

Active ChoicesVersion
参数化构建插件  Blue Ocean
pipeline 的可视化UI插件Convert To PipelineVersion
将自由风格项目转换为Pipeline项目Declarative Pipeline Migration Assistant APIVersion
Declarative Pipeline Migration AssistantVersion
Delivery PipelineVersion
Pipeline项目相关插件Git ParameterVersion
git参数化构建Hidden ParameterVersion
Hidden参数化构建Kubernetes CLIVersion
Kubernetes Client APIVersion
Kubernetes CredentialsVersion
KubernetesVersion
k8s相关插件List Git Branches ParameterVersion
查看git branches的插件Parameterized Remote TriggerVersion
Parameterized Trigger plugin
根据已经完成构建的结果，触发新Job或者传递参数Pipeline相关插件

安装gitlab

下载地址: https://mirrors.tuna.tsinghua.edu.cn/gitlab-ce/yum/el7/

[root@worker-2 ~]# wget https://mirrors.tuna.tsinghua.edu.cn/gitlab-ce/yum/el7/gitlab-ce-15.1.0-ce.0.el7.x86_64.rpm
[root@worker-2 ~]# rpm -ivh gitlab-ce-15.1.0-ce.0.el7.x86_64.rpm
[root@worker-2 ~]# vim  /etc/gitlab/gitlab.rb
external_url 'http://git.域名.com'
[root@worker-2 ~]# gitlab-ctl reconfigure
一千年以后

关闭不需要的进程

reconfigure  会自动启动进程,* runit_service[gitlab-kas] action restart (up to date)
[2022-07-01T16:50:02+08:00] INFO: directory[/var/opt/gitlab/gitlab-workhorse/sockets] sending restart action to runit_service[gitlab-workhorse] (delayed)
Recipe: gitlab::gitlab-workhorse* runit_service[gitlab-workhorse] action restart (up to date)
[2022-07-01T16:50:02+08:00] INFO: env_dir[/opt/gitlab/etc/node-exporter/env] sending restart action to runit_service[node-exporter] (delayed)
Recipe: monitoring::node-exporter* runit_service[node-exporter] action restart (up to date)
[2022-07-01T16:50:03+08:00] INFO: env_dir[/opt/gitlab/etc/gitlab-exporter/env] sending restart action to runit_service[gitlab-exporter] (delayed)
Recipe: monitoring::gitlab-exporter* runit_service[gitlab-exporter] action restart (up to date)
[2022-07-01T16:50:03+08:00] INFO: env_dir[/opt/gitlab/etc/redis-exporter/env] sending restart action to runit_service[redis-exporter] (delayed)
Recipe: monitoring::redis-exporter* runit_service[redis-exporter] action restart (up to date)
[2022-07-01T16:50:04+08:00] INFO: env_dir[/opt/gitlab/etc/prometheus/env] sending restart action to runit_service[prometheus] (delayed)
Recipe: monitoring::prometheus* runit_service[prometheus] action restart (up to date)
[2022-07-01T16:50:04+08:00] INFO: file[Prometheus config] sending run action to execute[reload prometheus] (delayed)* execute[reload prometheus] action run[2022-07-01T16:50:05+08:00] INFO: execute[reload prometheus] ran successfully- execute /opt/gitlab/bin/gitlab-ctl hup prometheus
[2022-07-01T16:50:05+08:00] INFO: env_dir[/opt/gitlab/etc/alertmanager/env] sending restart action to runit_service[alertmanager] (delayed)
Recipe: monitoring::alertmanager* runit_service[alertmanager] action restart (up to date)
[2022-07-01T16:50:05+08:00] INFO: env_dir[/opt/gitlab/etc/postgres-exporter/env] sending restart action to runit_service[postgres-exporter] (delayed)
Recipe: monitoring::postgres-exporter* runit_service[postgres-exporter] action restart (up to date)
[2022-07-01T16:50:06+08:00] INFO: env_dir[/opt/gitlab/etc/grafana/env] sending restart action to runit_service[grafana] (delayed)
Recipe: monitoring::grafana* runit_service[grafana] action restart (up to date)
[2022-07-01T16:50:06+08:00] INFO: Chef Infra Client Run complete in 169.994230781 seconds

[root@izbp1bllim99f4pkb4xtetz ~]# gitlab-ctl stop prometheus
ok: down: prometheus: 0s, normally up
[root@izbp1bllim99f4pkb4xtetz ~]# gitlab-ctl stop grafana
ok: down: grafana: 1s, normally up
[root@izbp1bllim99f4pkb4xtetz ~]# gitlab-ctl stop gitlab-exporter
ok: down: gitlab-exporter: 1s, normally up

访问网站(默认账号位root)

如果刷新了页面或者忘记设置密码 ----重新设置密码

[root@izbp1bllim99f4pkb4xtetz ~]# gitlab-rails console -e production
--------------------------------------------------------------------------------Ruby:         ruby 2.7.5p203 (2021-11-24 revision f69aeb8314) [x86_64-linux]GitLab:       15.1.0 (6bea4379525) FOSSGitLab Shell: 14.7.4PostgreSQL:   13.6
------------------------------------------------------------[ booted in 17.31s ]
Loading production environment (Rails 6.1.4.7)
irb(main):001:0> user = User.where(id: 1).first
=> #<User id:1 @root>
irb(main):002:0> user.password =  '密码'
=> "密码"
irb(main):003:0> user.password_confirmation = '密码'
=> "密码"
irb(main):004:0> user.save!
=> true
irb(main):005:0> exit

导入master的公钥

在gitlab中创建组和项目

gitlab 面密登录

[root@master ~]# more  .gitconfig
[user]email = 邮箱@qq.comname = 账户
[credential]helper = store
[http]sslVerify = false[root@master ~]# more .git-credentials
https://{username}:{password}@github.com输入命令
[root@master ~]# git config --global credential.helper store# 上步操作已经添加了ssh密钥,这边就可以免密提交/拉取

gitlab凭据设置

Jenkins pipeline

Jenkins pipeline语法：https://www.jenkins.io/doc/book/pipeline/syntax/
中文文档：https://www.jenkins.io/zh/doc/book/pipeline/syntax/

参数

参数化构建

尝试1

尝试 2

不勾选使用参数化构建过程

pipeline {agent anyparameters {string(name: 'PERSON', defaultValue: 'Mr Jenkins', description: 'Who should I say hello to?')}stages {stage('Example') {steps {echo "Hello ${params.PERSON}"}}}
}

input和options 的用法

pipeline {agent anyoptions {             # 可以加一行超时参数 单位可以是时分秒(复数)timeout(time: 10, unit: 'SECONDS') }stages {stage('Example') {input {message "Should we continue?"ok "Yes, we should."submitter "alice,bob"parameters {string(name: 'PERSON', defaultValue: 'Mr Jenkins', description: 'Who should I say hello to?')}}steps {echo "Hello, ${PERSON}, nice to meet you."}}}
}

when

内置条件

branch当正在构建的分支与模式给定的分支匹配时，执行这个阶段, 例如: when { branch 'master' }。注意，这只适用于多分支流水线。
environment当指定的环境变量是给定的值时，执行这个步骤, 例如: when { environment name: 'DEPLOY_TO', value: 'production' }
expression当指定的Groovy表达式评估为true时，执行这个阶段, 例如: when { expression { return params.DEBUG_BUILD } }
not当嵌套条件是错误时，执行这个阶段,必须包含一个条件，例如: when { not { branch 'master' } }
allOf当所有的嵌套条件都正确时，执行这个阶段,必须包含至少一个条件，例如: when { allOf { branch 'master'; environment name: 'DEPLOY_TO', value: 'production' } }
anyOf当至少有一个嵌套条件为真时，执行这个阶段,必须包含至少一个条件，例如: when { anyOf { branch 'master'; branch 'staging' } }
在进入 stage 的 agent 前评估 when默认情况下, 如果定义了某个阶段的代理，在进入该`stage` 的 agent 后该 stage 的 when 条件将会被评估。但是, 可以通过在 when 块中指定 beforeAgent 选项来更改此选项。 如果 beforeAgent 被设置为 true, 那么就会首先对 when 条件进行评估 , 并且只有在 when 条件验证为真时才会进入 agent 。

并行

声明式流水线的阶段可以在他们内部声明多隔嵌套阶段, 它们将并行执行。 注意，一个阶段必须只有一个 steps 或 parallel 的阶段。 嵌套阶段本身不能包含进一步的 parallel 阶段, 但是其他的阶段的行为与任何其他 stage 相同。任何包含 parallel 的阶段不能包含 agent 或 tools 阶段, 因为他们没有相关 steps。另外, 通过添加 failFast true 到包含 parallel`的 `stage 中， 当其中一个进程失败时，你可以强制所有的 parallel 阶段都被终止。
示例

pipeline {agent anystages {stage('Non-Parallel Stage') {steps {echo 'This stage will be executed first.'}}stage('Parallel Stage') {when {branch 'master'}failFast trueparallel {                  // parallel下的stage属于同一级的,同时进行stage('Branch A') {agent {label "for-branch-a"}steps {echo "On Branch A"}}stage('Branch B') {agent {label "for-branch-b"}steps {echo "On Branch B"}}}}}
}

BlueOcean

用blueocean 创建流水线

选择git仓库后会生成一串ssh密钥,放入gitlab的ssh中,jenkins就可以拉取gitlab的代码

设置流水线

提交到matser

配置jenkins使用jenkinsfile

script 步骤需要 [scripted-pipeline]块并在声明式流水线中执行。 对于大多数用例来说,应该声明式流水线中的“脚本”步骤是不必要的， 但是它可以提供一个有用的"逃生出口"。 非平凡的规模和/或复杂性的 script 块应该被转移到 共享库 。
示例pipeline {agent anystages {stage('Example') {steps {echo 'Hello World'script {def browsers = ['chrome', 'firefox']for (int i = 0; i < browsers.size(); ++i) {echo "Testing the ${browsers[i]} browser"}}}}}
}

jenkins实践

实践(多job调用)

修改jenkinsfile已支持调用job(gitlab-test)

调用成功

DevOps-持续集成持续部署一相关推荐

敏捷开发，持续集成/交付/部署, DevOps总结
文章目录敏捷开发入门教程一.迭代开发二.增量开发三.敏捷开发的好处 3.1 早期交付 3.2 降低风险四.如何进行每一次迭代五.敏捷开发的价值观六.十二条原则七.参考链接持续集成/交 ...
使用Jenkins在Azure Web App上进行ASP.NET Core应用程序的持续集成和部署（CI/CD）–第4天
目录主题路线图 Jenkins 先决条件使用Jenkins Azure Pipeline在Azure上的ASP.NET Core应用程序的CI/CD 创建新的管道作业添加参数添加管道脚本运 ...
使用Jenkins在Azure Web App上进行ASP.NET Core应用程序的持续集成和部署（CI/CD）–第3天
目录主题路线图先决条件 Azure Active Directory和服务主体创建一个Azure Active Directory和服务主体将应用程序集成到角色将Jenkins与Azure ...
使用Jenkins在Azure Web App上进行ASP.NET Core应用程序的持续集成和部署（CI/CD）–第2天
目录主题路线图先决条件将ASP.NET Core应用发布到Azure应用服务在Azure上配置Jenkins 在Azure上创建Jenkins服务器解锁Jenkins 结论主题本系列文 ...
使用Jenkins在Azure Web App上进行ASP.NET Core应用程序的持续集成和部署（CI/CD）–第1天
目录介绍路线图 DevOps 持续集成持续部署 Jenkins Azure Web App服务主题先决条件安装Jenkins 先决条件下载并安装 Jenkins插件让它运行安装自定义 ...
应该如何做好持续集成和部署？
应该如何做好持续集成和部署? 前言持续集成和部署是每一个互联网开发团队都必须要面对的问题,由于业务和技术团队快速增长,技术积累较弱,所以一个高效的,可持续的运维规范尤为重要. 高效可持续的运维环境需 ...
敏捷/持续集成/持续交付/DevOps基本理论全面解析
1 辨析敏捷/持续集成/持续交付/DevOps 2 持续集成 2.1 为何会有持续集成? 敏捷开发解决了单体应用的开发和每日构建的问题. 而单体应用拆分成微服务,就需要有一套方案来组装这些微服务,使其 ...
.NET Core 从 Github到 Nuget 持续集成、部署
一.前言 Nuget 作为一个.NET研发人员,我想你都不会陌生,他为我们提供非常方便的程序包管理,不管是版本,还是包的依赖都能轻松应对,可以说是我们的好助手.而 Nuget 除了官方nuget.or ...
持续集成持续部署持续交付_如何开始进行持续集成
持续集成持续部署持续交付 Everything you need to know to get started with continuous integration: branching strat ...
持续集成持续部署持续交付_自动持续开发和交付混合移动应用程序
持续集成持续部署持续交付对于当今的组织而言,提供移动应用程序本质上是一项业务需求. 开发应用程序的第一步之一就是了解不同的类型(本机,混合(或跨平台)和Web),以便您可以确定哪种类型最能满足您的需 ...

DevOps-持续集成持续部署一