|
|
| 第1行： |
第1行： |
| − | | + | [[category:desktop]] |
| − | | + | =cmus 康姆斯= |
| − | | + | ==*cmus-remote == |
| − | | |
| − | 仔细总结一下，我们会发现，除了编写代码，我们每天有相当一部分时间花在了编 译、运行单元测试、生成文档、打包和部署等烦琐且不起眼的工作上，这就是构建。如果我们现在还手工这样做，那成本也太高了，于是有人用软件的方法让这一系 列工作完全自动化，使得软件的构建可以像全自动流水线一样，只需要一条简单的命令，所有烦琐的步骤都能够自动完成，很快就能得到最终结果。
| |
| − | | |
| − | Maven真比自己的“规范化Ant”强大？其实他不知道自己只是在重新发明轮子，Maven已经有一大把现成的插件，全世界都在用，你自己不用写任何代码！
| |
| − | | |
| − | =现在一般更新在 站内资源 如下 [[基于Docker的Jenkins持续集成]]=
| |
| − | | |
| − | [[基于Docker的Jenkins持续集成]] | |
| − | | |
| − | =常用CI/CD=
| |
| − | 最最流行的，也是使用最多的Jenkins
| |
| − | 有着持续集成DNA的ThoughtWorks GO。理念："Deployment as pipeline" （华为容器平台应该是基于GO做的二次开发实现）
| |
| − | Atlassian工具链之一的Bamboo
| |
| − | 与Gitlab紧密集成的Gitlab CI
| |
| − | 专为开源打造的Travis CI，与Github紧密集成
| |
| − | 使用Python语言实现的Buildbot，相信Pythoner看到会喜欢
| |
| − | | |
| − | =安装= | |
| − | == 通过docker-compose安装== | |
| − | [[基于Docker的Jenkins持续集成]]
| |
| − | | |
| − | ==已放弃普通安装已放弃的方法== | |
| − | ip 192.168.0.16
| |
| − | | |
| | <pre> | | <pre> |
| − | 已放弃
| + | cmus-remote -u |
| − | docker pull jenkins
| + | cmus-remote -s |
| − |
| |
| − | [root@localhost ~]# docker images
| |
| − | REPOSITORY TAG IMAGE ID CREATED SIZE
| |
| − | jenkins latest cd14cecfdb3a 2 weeks ago 696MB
| |
| − | | |
| − | docker run --name=jenkins -it -u root -d -p 8080:8080 -p 50000:50000 -v /data/jenkins:/var/jenkins_home cd14cecfdb3a
| |
| − | | |
| − | --name=jenkins 命名
| |
| − | -it 交互模式运行 | |
| − | -u root root权限 | |
| − | -d 后台运行 | |
| − | -p 8080:8080 映射端口 | |
| − | -p 50000:50000 映射端口
| |
| − | -v /data/jenkins:/var/jenkins_home 映射目录
| |
| − | 3f08dc4f3f5d 本地镜像ID docker images name 命令可查看ID eg #docker images jenkins
| |
| − | | |
| − | | |
| − | #官方
| |
| − | mkdir -p /data/jenkins-data
| |
| − | docker run \
| |
| − | --name=jenkins \
| |
| − | -u root \
| |
| − | --rm \
| |
| − | -d \
| |
| − | -p 8080:8080 \
| |
| − | -p 50000:50000 \
| |
| − | -v /data/jenkins-data:/var/jenkins_home \
| |
| − | -v /var/run/docker.sock:/var/run/docker.sock \
| |
| − | jenkinsci/blueocean
| |
| − | | |
| − | | |
| − | | |
| − | #在运行docker容器时可以加如下参数来保证每次docker服务重启后容器也自动重启：
| |
| − | $docker run --restart=always
| |
| − | #如果已经启动了则可以使用如下命令：
| |
| − | $docker update --restart=always <CONTAINER ID>
| |
| − | | |
| − | | |
| − | | |
| − | 登入容器：
| |
| − | docker exec -it jenkins /bin/bash
| |
| − | | |
| − | | |
| − | | |
| − | 同步容器时间
| |
| − | 在Dockerfile中加入
| |
| − | RUN cp /usr/share/zoneinfo/Asia/Shanghai /etc/localtime && ntpdate cn.pool.ntp.org
| |
| − | 或
| |
| − | 容器运行后把容主机的/usr/share/zoneinfo/Asia/Shanghai 复制到容器的/etc/localtime
| |
| − | | |
| − | #先cp 到 /data/jenkins
| |
| − | cp /usr/share/zoneinfo/Asia/Shanghai /data/jenkins
| |
| − | | |
| − | plubs
| |
| − | Publish Over SSH
| |
| − | | |
| − |
| |
| − | Maven Integration
| |
| − | | |
| − | Build
| |
| − | clean install
| |
| | </pre> | | </pre> |
| − | | + | ==* cmus == |
| − | | |
| − | [https://jenkins.io/zh/doc/book/installing/#docker 安装Jenkins zh]
| |
| − | | |
| − | http://cn.jenkins.io/doc/book/installing/
| |
| − | | |
| − | 安装请见 [[Docker入门]]
| |
| − | | |
| − | [http://www.cnblogs.com/stulzq/p/8627360.html 使用Docker安装Jenkins]
| |
| − | | |
| − | [https://www.cnblogs.com/stulzq/p/9297260.html Jenkins 集群搭建]
| |
| − | | |
| − | =jenkins使用= | |
| − | | |
| | <pre> | | <pre> |
| − | 要先安装maven 什么的
| + | 康姆斯 |
| | | | |
| | + | 应该可以写配置文件的吧 |
| | | | |
| − | Build
| + | ~/.config/cmus/rc |
| − | Root POM pom.xml
| |
| − | Goals and options clean install
| |
| | | | |
| | + | set output_plugin=alsa |
| | + | set dsp.alsa.device=default |
| | + | set mixer.alsa.device=default |
| | + | set mixer.alsa.channel=Master |
| | | | |
| − | Post Steps
| |
| − | Ex shell
| |
| − | cd /var/jenkins_home/workspace/doll-api-test/target
| |
| − | | |
| | | | |
| | + | 导入音乐 :a /music/pach/ |
| | + | 要绝对路径 |
| | | | |
| − | sen build aritcle
| |
| | | | |
| − | ex command #记得要要全局那加ssh server
| |
| | | | |
| | + | 播放或重播音乐 x |
| | + | 暂停 c |
| | + | 播放下一首音乐 b |
| | + | 播放上一首音乐 z |
| | + | 激活随机播放 s |
| | + | 清空当前文件列表 :clear |
| | + | 保存播放列表 :save /path/to/playlist |
| | + | 加载播放列表 :load /path/to/playlist |
| | + | 在7个不同的功能界面之间切换 数字键1-7 |
| | + | 退出播放器 q |
| | | | |
| | + | 设置输出 |
| | | | |
| − | </pre>
| + | :set output_plugin=pulse |
| | | | |
| − | ==gradle ==
| |
| − | Gradle是一个基于Apache Ant和Apache Maven概念的项目自动化建构工具。它使用一种基于Groovy的特定领域语言来声明项目设置，而不是传统的XML。
| |
| − | 当前其支持的语言限于Java、Groovy和Scala，计划未来将支持更多的语言。
| |
| | | | |
| − | 和maven同级,更简洁一些
| + | e 添加到队列菜单 |
| | | | |
| | + | y 添加到列表菜单 整列添加过去了 |
| | | | |
| − | https://docs.gradle.org/current/userguide/userguide.html
| + | 常用组合键 |
| | | | |
| − | ==maven==
| + | Ctrl + R 切换单曲循环 |
| − | <pre>
| |
| | | | |
| − | 我试过 好像不用安装 jdk的呀 docker化的jenkins
| + | Ctrl + I 切换左右菜单 |
| | | | |
| − | 安装在configureTools 全局配置那里 要加上maven 和填写版本 以这个为目录名 例如下面的maven3.6.2
| + | H J K L 快退 上 下 快进 |
| | | | |
| | + | 音量调节 |
| | | | |
| | + | - = |
| | | | |
| − | Build->Goals and options ->clean install -Pbeta -Dmaven.test.skip=true
| + | 删除选项 |
| − | </pre>
| |
| | | | |
| − | [https://blog.csdn.net/xlgen157387/article/details/68961371 Jenkins部署Maven多环境项目（dev、beta、prod）的参数设置]
| + | shift + D |
| | | | |
| − | [https://blog.csdn.net/u011781521/article/details/76696677 Jenkins系列(三)----Maven项目配置详解]
| + | 更新缓存 |
| | | | |
| | + | u |
| | | | |
| − | ===maven 配置文件 ===
| + | 刷新 |
| − | <pre>maven 配置 可以在母机修改 注意 要先至少跑个工程后 才会安装maven 生成这个目录了
| |
| | | | |
| − | 有时要密码的 ,格式要小心 烦死了
| + | Ctrl + L |
| | | | |
| − | /data/docker/volumes/docker4jenkins_jenkins_home/_data/tools/hudson.tasks.Maven_MavenInstallation/maven/conf/settings.xml
| |
| | | | |
| − | /docker/jenkins_home/tools/hudson.tasks.Maven_MavenInstallation/jenkins-in-maven/conf下修改setting.xml文件。
| + | 播放 |
| − | 母机可能的目录
| |
| − | /home/data/docker/volumes/docker4jenkins_jenkins_home/_data/tools/hudson.tasks.Maven_MavenInstallation/maven3.6.2/conf
| |
| | | | |
| | + | 选中，使用 Enter 播放，z上 一首，b 下一首，c 暂停，x 播放，v 停止 |
| | | | |
| | + | 菜单查看模式 |
| | | | |
| − | 位置
| + | 输入 1: 普通模式 |
| − | 153 <mirror>
| |
| − | 154 <id>mirrorId</id>
| |
| − | 155 <mirrorOf>repositoryId</mirrorOf>
| |
| − | 156 <name>Human Readable Name for this Mirror.</name>
| |
| − | 157 <url>http://my.repository.com/repo/path</url>
| |
| − | 158 </mirror>
| |
| − | 159 -->
| |
| − | 160 <mirror>
| |
| − | 161 <id>nexus</id>
| |
| − | 162 <mirrorOf>*</mirrorOf>
| |
| − | 163 <url>http://192.168.4.189:8081/repository/maven-public/</url>
| |
| − | 164 </mirror>
| |
| − | 165 </mirrors>
| |
| | | | |
| | + | 输入2: 简单模式 |
| | | | |
| − | 公用的方便安装的如下配置
| + | 输入3: 列表模式 |
| − | <mirrors>
| |
| − | <!-- mirror | |
| − | | Specifies a repository mirror site to use instead of a given repository. The repository that
| |
| − | | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
| |
| − | | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
| |
| − | |
| |
| − | <mirror>
| |
| − | <id>mirrorId</id>
| |
| − | <mirrorOf>repositoryId</mirrorOf>
| |
| − | <name>Human Readable Name for this Mirror.</name>
| |
| − | <url>http://my.repository.com/repo/path</url>
| |
| − | </mirror>
| |
| − | -->
| |
| − | <mirror>
| |
| − | <id>alimaven</id>
| |
| − | <name>aliyun maven</name>
| |
| − | <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
| |
| − | <mirrorOf>central</mirrorOf>
| |
| − | </mirror>
| |
| − | </mirrors>
| |
| | | | |
| | + | 输入4: 队列模式 |
| | | | |
| | | | |
| | | | |
| − | #lx
| |
| − | <servers>
| |
| − | <server>
| |
| − | <id>nexus</id>
| |
| − | <username>admin</username>
| |
| − | <password>lxtxadmin123</password>
| |
| − | </server>
| |
| − | </servers>
| |
| | | | |
| − | <mirrors>
| |
| − | <mirror>
| |
| − | <id>nexus</id>
| |
| − | <mirrorOf>*</mirrorOf>
| |
| − | <url>http://192.168.4.189:8081/repository/maven-public/</url>
| |
| − | </mirror>
| |
| − | <!-- <mirror>-->
| |
| − | <!-- <id>nexus-aliyun</id>-->
| |
| − | <!-- <mirrorOf>central</mirrorOf>-->
| |
| − | <!-- <name>Nexus aliyun</name>-->
| |
| − | <!-- <url>http://maven.aliyun.com/nexus/content/groups/public</url>-->
| |
| − | <!-- </mirror>-->
| |
| | | | |
| − | </mirrors>
| |
| | | | |
| | | | |
| − | </pre>
| + | 数字1~7可以切换界面，具体如下： |
| − | [https://blog.csdn.net/w13511069150/article/details/93161141 Jenkins修改Maven配置]
| |
| | | | |
| − | [https://blog.csdn.net/xxsstf/article/details/84991931 Jenkins使用， maven插件配置修改]
| + | 1.Library view |
| | | | |
| | + | 默认打开的界面，按照歌手或专辑名排列 |
| | | | |
| − | [https://yq.aliyun.com/articles/752222 Maven国内可用下载速度快的仓库镜像(阿里Maven镜像地址)]
| + | 2.Sorted library view |
| | | | |
| − | [https://www.cnblogs.com/xiao987334176/p/11433636.html Jenkins配置maven]
| + | 所有的歌曲的列表 |
| | | | |
| − | ===snapshot快照仓库和release发布仓库===
| + | 3.Playlist view 播放里按 y就可以添加到这里了 |
| − | maven中的仓库分为两种，snapshot快照仓库和release发布仓库。snapshot快照仓库用于保存开发过程中的不稳定版 本，release正式仓库则是用来保存稳定的发行版本。定义一个组件/模块为快照版本，只需要在pom文件中在该模块的版本号后加上-SNAPSHOT即可(注意这里必须是大写)。release版本不允许修改，每次进行release版本修改，发布必须提升版本号。而snapshot一般是开发过程中的迭代版本，snapshot更新后，引用的项目可以不修改版本号自动下载构建。
| |
| | | | |
| − | [https://www.cnblogs.com/molao-doing/articles/6379216.html MAVEN snapshot快照和release发布库的区别、作用]
| + | 类似于歌单，可以按需组织歌曲 |
| | | | |
| − | [https://www.cnblogs.com/EasonJim/p/6852840.html Maven快照机制（SNAPSHOT）]
| + | 4.Play Queue view |
| | | | |
| − | [http://www.huangbowen.net/blog/2016/01/29/understand-official-version-and-snapshot-version-in-maven/ 理解Maven中的SNAPSHOT版本和正式版本]
| + | 当前播放队列 |
| | | | |
| − | ==git branch==
| + | 5.Browser |
| − | 这里应该 填写上操作过程 在我的geany上
| |
| | | | |
| − | [https://blog.csdn.net/jackyzheng/article/details/78750047 goodJenkins Git Parameter 插件配置过程]
| + | 可以浏览文件，添加歌曲之类的 |
| | | | |
| − | [https://my.oschina.net/u/3493518/blog/1510531 Jenkins插件之——git Parameter插件]
| + | 6.Filters view |
| | | | |
| | + | 显示用户定义的过滤设置 |
| | | | |
| − | [https://blog.csdn.net/hwhua1986/article/details/53841741 Jenkins：使用Git Parameter插件实现tag或分支的选择性构建]
| + | 7.Settings view |
| | | | |
| − | [https://blog.csdn.net/u012076316/article/details/52056107 jenkins构建时支持git选择分支]
| + | 显示所有的快捷键设置。 |
| | | | |
| − | [https://blog.csdn.net/qq_20641565/article/details/79132797 jenkins插件Git Parameter Plug-In分支构建项目]
| |
| | | | |
| − | [http://buxin-2008.iteye.com/blog/2357340 jenkins进行git多分支的docker镜像构建]
| |
| | | | |
| − | ==android==
| |
| − | [ https://blog.csdn.net/youshi520000/article/details/81027940 Android 使用 Jenkins 实现自动化打包【流程】&【踩坑]
| |
| − |
| |
| − |
| |
| − | == Jenkins的初级应用（2）-Invoke Phing targets==
| |
| − | [https://www.cnblogs.com/hodge01/p/9367498.html Jenkins的初级应用（2）-Invoke Phing targets]
| |
| − |
| |
| − | ==启动==
| |
| − | ===supervisor===
| |
| − | <pre>
| |
| − | #配合supervisor，把Jenkins直接变成一个服务。
| |
| − | #可以在Linux上创建一个ci用户，然后，用supervisor启动并指定9090端口：
| |
| − | # /etc/supervisor/conf.d/ci.conf
| |
| − |
| |
| − | [program:ci]
| |
| − | command=java -jar /home/ci/jenkins.war --httpPort=9090
| |
| − | user=ci
| |
| − | autostart=true
| |
| − | autorestart=true
| |
| − | startsecs=30
| |
| − | startretries=5
| |
| − | </pre>
| |
| − |
| |
| − | =权限控制=
| |
| − |
| |
| − | ==Role-based Authorization Strategy==
| |
| − |
| |
| − | 可选插件-->Role-based Authorization Strategy
| |
| − |
| |
| − |
| |
| − | 超级用户 root root
| |
| − | other evan
| |
| − | group ops java admin
| |
| − |
| |
| − | ==基于项目(job)==
| |
| − | <pre>
| |
| − | Project roles 创建一个 dev 只配置所以 dev开头的内网项目
| |
| − |
| |
| − | Role to add dev
| |
| − | Pattern dev.* #配置
| |
| − |
| |
| − | 选择【 Manage Roles】
| |
| − | 在【Global roles】创建一个新的全局角色 anyone，该角色不开放系统权限，只读.
| |
| − |
| |
| − | 然后把你的号添加到 Global roles
| |
| − |
| |
| − | Assign Roles-- Item roles 里面 加入你的号 并勾上 dev
| |
| − |
| |
| − |
| |
| − | 注意: Global roles 必要有 你要给别人用的用户名，不登录了什么 都没提示全局没有读权限 </pre>
| |
| − | ==lxtx eg==
| |
| − | <pre>
| |
| − | pre 倒好这里有个前端小哥 就叫 wusiyi
| |
| − |
| |
| − | Manage Roles 角色管理 -- Global roles: Role to add role name 为desk 全给read
| |
| − |
| |
| − | Item roles : role to add :Frontend_h5 Pattern: (?i)stage-.*|prod-hailuo-sdk-doc|bcb-blockchain-h5|k8s-local-nuxt-snsdev-hailuo-open-website 这个权限就看你给了
| |
| − |
| |
| − |
| |
| − |
| |
| − | Assign Roles分配角色 Global roles: wusiyi 选择在 desk ; Item roles:Frontend_h5 和上面的 role to add 对应
| |
| − |
| |
| − | </pre>
| |
| − |
| |
| − | ==权限see also==
| |
| − |
| |
| − | [https://blog.csdn.net/Gred01/article/details/78587290 Jenkins教程四基于Role-based Authorization Strategy的用户权限管理]
| |
| − |
| |
| − | [https://my.oschina.net/u/3413394/blog/1576357 enkins教程四 基于【Role-based Authorization Strategy】的用户权限管理]
| |
| − |
| |
| − | [https://www.jianshu.com/p/7e148bcfb96e Jenkins使用教程之用户权限管理（包含插件的安装）]
| |
| − |
| |
| − | [https://www.jianshu.com/p/6c274d9b22ad Jenkins自动化部署-权限管控篇 (六)]
| |
| − |
| |
| − | =插件=
| |
| − |
| |
| − | ==dashboard 插件==
| |
| − | dashboard 插件 [https://wiki.jenkins-ci.org/display/JENKINS/Dashboard+View Dashboard View]
| |
| − | 用来自定义自己的主页,例如对下列的 jenkins 的主页
| |
| − |
| |
| − | == Wall display==
| |
| − | 用来将 jobs 的状态更加直观地显示在大屏幕上
| |
| − |
| |
| − | === ssh server===
| |
| − |
| |
| − | ====troubleshooting====
| |
| − | <pre>
| |
| − |
| |
| − | jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection. Message: [Failed to connect session for config [win8r2]. Message [USERAUTH fail]]
| |
| − | 在jenkins 上使用publish over ssh ,报上述错误,
| |
| − |
| |
| − | ssh server
| |
| − | 1. 配置里面添加 jenkins pri key 2.远程被 jenkins 的远程那里添加jenkin的pub key
| |
| | | | |
| | </pre> | | </pre> |
| − | https://ask.csdn.net/questions/379784
| |
| − |
| |
| − | =NODE=
| |
| − | jenkins plugin 要安装 node
| |
| − |
| |
| − | alpine 里面也要安装 node.js alpine
| |
| − | https://wiki.linuxchina.net/index.php/Alpine#docker
| |
| − |
| |
| − |
| |
| − | [https://blog.csdn.net/wanchaopeng/article/details/87934293 jenkins打包nodejs]
| |
| − |
| |
| − | [https://www.cnblogs.com/vipzhou/p/7890016.html jenkins学习之自动打包构建nodejs应用]
| |
| − |
| |
| − | =xk=
| |
| − | <pre>
| |
| − | dev 开发环境
| |
| − | beta 测试环境
| |
| − | release 正式环境
| |
| − | </pre>
| |
| − |
| |
| − | =DB =
| |
| − |
| |
| − | [https://www.jianshu.com/p/e0c1fbc98f0d Jenkins自动化部署-数据库篇 (五)]
| |
| − |
| |
| − | [https://stackoverrun.com/cn/q/11775565 需要在Jenkins管道脚本中执行SQL脚本的工作策略]
| |
| − |
| |
| − | [https://www.zhihu.com/question/61737048 jenkins 进行持续集成的时候，关于SQL执行的问题]
| |
| − |
| |
| − | [https://www.jianshu.com/p/e0c1fbc98f0d Jenkins自动化部署-数据库篇 (五)]
| |
| − |
| |
| − | =磁盘处理=
| |
| − | [[Jenkins服务器磁盘空间管理]]
| |
| − |
| |
| − | =trouble shooting=
| |
| − | == WeChat.java:[266,43] 找不到符号 ==
| |
| − | <pre>
| |
| − | [ERROR] /root/.jenkins/workspace/release_read/xtwl_service/src/main/java/org/platform_service/universal/pay/WeChat.java:[266,43] 找不到符号
| |
| − |
| |
| − | Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project xtwl_service: Compilation failure
| |
| − |
| |
| − | 原来是我用了 clean package -Prelease 之前还替换了配置文件 哈哈 </pre>
| |
| − |
| |
| − | == offline ==
| |
| − | 点击Continue，大部分人都会出现这个界面，毕竟在天朝，我们先选择跳过
| |
| − |
| |
| − |
| |
| − | ==project lxtx-hello-admin-dao: Could not resolve dependencies for project com.lxtx.hello:lxtx ==
| |
| − | <pre>
| |
| − | Waiting for Jenkins to finish collecting data
| |
| − | [ERROR] Failed to execute goal on project lxtx-hello-admin-dao: Could not resolve dependencies for project com.lxtx.hello:lxtx-hello-admin-dao:jar:0.0.1: Could not find artifact com.lxtx.im:lxtx-admin-base-service:jar:0.1.6 in central (https://repo.maven.apache.org/maven2) -> [Help 1]
| |
| − | [ERROR]
| |
| − | [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
| |
| − | [ERROR] Re-run Maven using the -X switch to enable full debug logging.
| |
| − | [ERROR]
| |
| − | [ERROR] For more information about the errors and possible solutions, please read the following articles:
| |
| − | [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
| |
| − | [ERROR]
| |
| − | [ERROR] After correcting the problems, you can resume the build with the command
| |
| − | [ERROR] mvn <goals> -rf :lxtx-hello-admin-dao
| |
| − | </pre>
| |
| − |
| |
| − | === soult===
| |
| − | <pre>
| |
| − |
| |
| − | docker dir
| |
| − | /var/jenkins_home/.m2/settings.xml
| |
| − |
| |
| − | 母鸡目录
| |
| − | /volumes/docker4jenkins_jenkins_home/_data/.m2/settings.xml
| |
| − |
| |
| − | <?xml version="1.0" encoding="UTF-8"?>
| |
| − |
| |
| − | <!--
| |
| − | Licensed to the Apache Software Foundation (ASF) under one
| |
| − | or more contributor license agreements. See the NOTICE file
| |
| − | distributed with this work for additional information
| |
| − | regarding copyright ownership. The ASF licenses this file
| |
| − | to you under the Apache License, Version 2.0 (the
| |
| − | "License"); you may not use this file except in compliance
| |
| − | with the License. You may obtain a copy of the License at
| |
| − |
| |
| − | http://www.apache.org/licenses/LICENSE-2.0
| |
| − |
| |
| − | Unless required by applicable law or agreed to in writing,
| |
| − | software distributed under the License is distributed on an
| |
| − | "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
| |
| − | KIND, either express or implied. See the License for the
| |
| − | specific language governing permissions and limitations
| |
| − | under the License.
| |
| − | -->
| |
| − |
| |
| − | <!--
| |
| − | | This is the configuration file for Maven. It can be specified at two levels:
| |
| − | |
| |
| − | | 1. User Level. This settings.xml file provides configuration for a single user,
| |
| − | | and is normally provided in ${user.home}/.m2/settings.xml.
| |
| − | |
| |
| − | | NOTE: This location can be overridden with the CLI option:
| |
| − | |
| |
| − | | -s /path/to/user/settings.xml
| |
| − | |
| |
| − | | 2. Global Level. This settings.xml file provides configuration for all Maven
| |
| − | | users on a machine (assuming they're all using the same Maven
| |
| − | | installation). It's normally provided in
| |
| − | | ${maven.home}/conf/settings.xml.
| |
| − | |
| |
| − | | NOTE: This location can be overridden with the CLI option:
| |
| − | |
| |
| − | | -gs /path/to/global/settings.xml
| |
| − | |
| |
| − | | The sections in this sample file are intended to give you a running start at
| |
| − | | getting the most out of your Maven installation. Where appropriate, the default
| |
| − | | values (values used when the setting is not specified) are provided.
| |
| − | |
| |
| − | |-->
| |
| − | <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
| |
| − | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| |
| − | xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
| |
| − | <!-- localRepository
| |
| − | | The path to the local repository maven will use to store artifacts.
| |
| − | |
| |
| − | | Default: ${user.home}/.m2/repository
| |
| − | -->
| |
| − | <localRepository>D:\tools\apache-maven-3.3.9-bin\apache-maven-3.3.9\repository</localRepository>
| |
| − |
| |
| − |
| |
| − | <!-- interactiveMode
| |
| − | | This will determine whether maven prompts you when it needs input. If set to false,
| |
| − | | maven will use a sensible default value, perhaps based on some other setting, for
| |
| − | | the parameter in question.
| |
| − | |
| |
| − | | Default: true
| |
| − | <interactiveMode>true</interactiveMode>
| |
| − | -->
| |
| − |
| |
| − | <!-- offline
| |
| − | | Determines whether maven should attempt to connect to the network when executing a build.
| |
| − | | This will have an effect on artifact downloads, artifact deployment, and others.
| |
| − | |
| |
| − | | Default: false
| |
| − | <offline>false</offline>
| |
| − | -->
| |
| − |
| |
| − | <!-- pluginGroups
| |
| − | | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
| |
| − | | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
| |
| − | | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
| |
| − | |-->
| |
| − | <pluginGroups>
| |
| − | <!-- pluginGroup
| |
| − | | Specifies a further group identifier to use for plugin lookup.
| |
| − | <pluginGroup>com.your.plugins</pluginGroup>
| |
| − | -->
| |
| − | <pluginGroup>org.sonatype.plugins</pluginGroup>
| |
| − | <pluginGroup>org.sonarsource.scanner.maven</pluginGroup>
| |
| − | </pluginGroups>
| |
| − |
| |
| − | <!-- proxies
| |
| − | | This is a list of proxies which can be used on this machine to connect to the network.
| |
| − | | Unless otherwise specified (by system property or command-line switch), the first proxy
| |
| − | | specification in this list marked as active will be used.
| |
| − | |-->
| |
| − | <proxies>
| |
| − | <!-- proxy
| |
| − | | Specification for one proxy, to be used in connecting to the network.
| |
| − | |
| |
| − | <proxy>
| |
| − | <id>optional</id>
| |
| − | <active>true</active>
| |
| − | <protocol>http</protocol>
| |
| − | <username>proxyuser</username>
| |
| − | <password>proxypass</password>
| |
| − | <host>proxy.host.net</host>
| |
| − | <port>80</port>
| |
| − | <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
| |
| − | </proxy>
| |
| − | -->
| |
| − | </proxies>
| |
| − |
| |
| − | <!-- servers
| |
| − | | This is a list of authentication profiles, keyed by the server-id used within the system.
| |
| − | | Authentication profiles can be used whenever maven must make a connection to a remote server.
| |
| − | |-->
| |
| − | <servers>
| |
| − | <!-- server
| |
| − | | Specifies the authentication information to use when connecting to a particular server, identified by
| |
| − | | a unique name within the system (referred to by the 'id' attribute below).
| |
| − | |
| |
| − | | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
| |
| − | | used together.
| |
| − | | -->
| |
| − | <server>
| |
| − | <id>nexus</id>
| |
| − | <username>admin</username>
| |
| − | <password>lxtxadmin123</password>
| |
| − | </server>
| |
| − |
| |
| − |
| |
| − | <!-- Another sample, using keys to authenticate.
| |
| − | <server>
| |
| − | <id>siteServer</id>
| |
| − | <privateKey>/path/to/private/key</privateKey>
| |
| − | <passphrase>optional; leave empty if not used.</passphrase>
| |
| − | </server>
| |
| − | -->
| |
| − | </servers>
| |
| − |
| |
| − | <!-- mirrors
| |
| − | | This is a list of mirrors to be used in downloading artifacts from remote repositories.
| |
| − | |
| |
| − | | It works like this: a POM may declare a repository to use in resolving certain artifacts.
| |
| − | | However, this repository may have problems with heavy traffic at times, so people have mirrored
| |
| − | | it to several places.
| |
| − | |
| |
| − | | That repository definition will have a unique id, so we can create a mirror reference for that
| |
| − | | repository, to be used as an alternate download site. The mirror site will be the preferred
| |
| − | | server for that repository.
| |
| − | |-->
| |
| − | <mirrors>
| |
| − | <!-- mirror
| |
| − | | Specifies a repository mirror site to use instead of a given repository. The repository that
| |
| − | | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
| |
| − | | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
| |
| − | |
| |
| − | <mirror>
| |
| − | <id>mirrorId</id>
| |
| − | <mirrorOf>repositoryId</mirrorOf>
| |
| − | <name>Human Readable Name for this Mirror.</name>
| |
| − | <url>http://my.repository.com/repo/path</url>
| |
| − | </mirror>
| |
| − | -->
| |
| − | <!--
| |
| − | <mirror>
| |
| − | <id>nexus-aliyun</id>
| |
| − | <mirrorOf>central</mirrorOf>
| |
| − | <name>Nexus aliyun</name>
| |
| − | <url>http://maven.aliyun.com/nexus/content/groups/public</url>
| |
| − | </mirror>
| |
| − |
| |
| − | <mirror>
| |
| − | <id>nexus-aliyun</id>
| |
| − | <mirrorOf>central</mirrorOf>
| |
| − | <name>Nexus aliyun</name>
| |
| − | <url>http://maven.aliyun.com/nexus/content/groups/public</url>
| |
| − | </mirror>-->
| |
| − |
| |
| − | <mirror>
| |
| − | <id>nexus</id>
| |
| − | <mirrorOf>*</mirrorOf>
| |
| − | <url>http://192.168.4.189:8081/repository/maven-public/</url>
| |
| − | </mirror>
| |
| − | <!--
| |
| − | <mirror>
| |
| − | <id>repo2</id>
| |
| − | <mirrorOf>central</mirrorOf>
| |
| − | <name>Human Readable Name for this Mirror.</name>
| |
| − | <url>http://repo2.maven.org/maven2/</url>
| |
| − | </mirror> -->
| |
| − | </mirrors>
| |
| − |
| |
| − | <!-- profiles
| |
| − | | This is a list of profiles which can be activated in a variety of ways, and which can modify
| |
| − | | the build process. Profiles provided in the settings.xml are intended to provide local machine-
| |
| − | | specific paths and repository locations which allow the build to work in the local environment.
| |
| − | |
| |
| − | | For example, if you have an integration testing plugin - like cactus - that needs to know where
| |
| − | | your Tomcat instance is installed, you can provide a variable here such that the variable is
| |
| − | | dereferenced during the build process to configure the cactus plugin.
| |
| − | |
| |
| − | | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
| |
| − | | section of this document (settings.xml) - will be discussed later. Another way essentially
| |
| − | | relies on the detection of a system property, either matching a particular value for the property,
| |
| − | | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
| |
| − | | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
| |
| − | | Finally, the list of active profiles can be specified directly from the command line.
| |
| − | |
| |
| − | | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
| |
| − | | repositories, plugin repositories, and free-form properties to be used as configuration
| |
| − | | variables for plugins in the POM.
| |
| − | |
| |
| − | |-->
| |
| − | <profiles>
| |
| − | <!-- profile
| |
| − | | Specifies a set of introductions to the build process, to be activated using one or more of the
| |
| − | | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
| |
| − | | or the command line, profiles have to have an ID that is unique.
| |
| − | |
| |
| − | | An encouraged best practice for profile identification is to use a consistent naming convention
| |
| − | | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
| |
| − | | This will make it more intuitive to understand what the set of introduced profiles is attempting
| |
| − | | to accomplish, particularly when you only have a list of profile id's for debug.
| |
| − | |
| |
| − | | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
| |
| − | <profile>
| |
| − | <id>jdk-1.4</id>
| |
| − |
| |
| − | <activation>
| |
| − | <jdk>1.4</jdk>
| |
| − | </activation>
| |
| − |
| |
| − | <repositories>
| |
| − | <repository>
| |
| − | <id>jdk14</id>
| |
| − | <name>Repository for JDK 1.4 builds</name>
| |
| − | <url>http://www.myhost.com/maven/jdk14</url>
| |
| − | <layout>default</layout>
| |
| − | <snapshotPolicy>always</snapshotPolicy>
| |
| − | </repository>
| |
| − | </repositories>
| |
| − | </profile>
| |
| − | -->
| |
| − |
| |
| − | <!--
| |
| − | | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
| |
| − | | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
| |
| − | | might hypothetically look like:
| |
| − | |
| |
| − | | ...
| |
| − | | <plugin>
| |
| − | | <groupId>org.myco.myplugins</groupId>
| |
| − | | <artifactId>myplugin</artifactId>
| |
| − | |
| |
| − | | <configuration>
| |
| − | | <tomcatLocation>${tomcatPath}</tomcatLocation>
| |
| − | | </configuration>
| |
| − | | </plugin>
| |
| − | | ...
| |
| − | |
| |
| − | | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
| |
| − | | anything, you could just leave off the <value/> inside the activation-property.
| |
| − | |
| |
| − | <profile>
| |
| − | <id>env-dev</id>
| |
| − |
| |
| − | <activation>
| |
| − | <property>
| |
| − | <name>target-env</name>
| |
| − | <value>dev</value>
| |
| − | </property>
| |
| − | </activation>
| |
| − |
| |
| − | <properties>
| |
| − | <tomcatPath>/path/to/tomcat/instance</tomcatPath>
| |
| − | </properties>
| |
| − | </profile>
| |
| − | -->
| |
| − | <profile>
| |
| − | <id>nexus</id>
| |
| − | <repositories>
| |
| − | <repository>
| |
| − | <id>central</id>
| |
| − | <url>http://central</url>
| |
| − | <releases><enabled>true</enabled></releases>
| |
| − | <snapshots><enabled>true</enabled></snapshots>
| |
| − | </repository>
| |
| − | </repositories>
| |
| − | <pluginRepositories>
| |
| − | <pluginRepository>
| |
| − | <id>central</id>
| |
| − | <url>http://central</url>
| |
| − | <releases><enabled>true</enabled></releases>
| |
| − | <snapshots><enabled>true</enabled></snapshots>
| |
| − | </pluginRepository>
| |
| − | </pluginRepositories>
| |
| − | </profile>
| |
| − | </profiles>
| |
| − |
| |
| − | <!-- activeProfiles
| |
| − | | List of profiles that are active for all builds.
| |
| − | | -->
| |
| − | <activeProfiles>
| |
| − | <activeProfile>nexus</activeProfile>
| |
| − | </activeProfiles>
| |
| − |
| |
| − | </settings>
| |
| − | </pre>
| |
| − |
| |
| − | ==[[Jenkins更多错误]]==
| |
| − |
| |
| − | =进阶=
| |
| − | [https://www.cnblogs.com/shenh/p/8963688.html jenkins + pipeline构建自动化部署]
| |
| − |
| |
| − |
| |
| − | [https://blog.csdn.net/wh211212/article/details/77482138 Jenkins + Pipeline 构建流水线发布]
| |
| − |
| |
| − |
| |
| − | [https://www.cnblogs.com/puresoul/p/4828913.html Jenkins内置环境变量的使用]
| |
| − |
| |
| − | https://www.w3cschool.cn/jenkins/jenkins-5h3228n2.html
| |
| − |
| |
| − | =参考=
| |
| − |
| |
| − | [https://jenkins-zh.cn/ Jenkins 中文社区]
| |
| − |
| |
| − | [https://www.cnblogs.com/along21/p/9724036.html Jenkins持续集成01—Jenkins服务搭建和部署]
| |
| − |
| |
| − | [[Jenkins用户手册]]
| |
| − |
| |
| − | [https://jenkins.io/doc/book/installing/#docker Installing Docker]
| |
| − |
| |
| − | [https://blog.csdn.net/jackyzheng/article/category/6849960 jenkins docs ]
| |
| − |
| |
| − | [http://www.cnblogs.com/dcba1112/archive/2011/05/01/2033805.html Maven的安装、配置及使用入门]
| |
| − |
| |
| − | [https://zh.wikipedia.org/wiki/Apache_Maven Apache Maven]
| |
| − |
| |
| − | [https://zh.wikipedia.org/wiki/Gradle Gradle是一个基于Apache Ant和Apache Maven概念的项目自动化建构工具]
| |
| − |
| |
| − | [https://www.jianshu.com/p/1eff16f60297 Maven 使用教程]
| |
| − |
| |
| − | [https://www.jianshu.com/p/60fb231a160e Jenkins学习之自动构建部署maven项目 have emailetc]
| |
| − |
| |
| − | [https://www.liaoxuefeng.com/article/001463233913442cdb2d1bd1b1b42e3b0b29eb1ba736c5e000 使用Jenkins进行持续集成]
| |
| − |
| |
| − | [http://blog.51cto.com/fluagen/40086 学习maven的使用，看到一篇很实用的入门教程(菜鸟级入门)]
| |
| − |
| |
| − | [http://blog.51cto.com/215687833/1916915 使用Jenkins 自动部署发布]
| |
| − |
| |
| − | [https://www.cnblogs.com/yjmyzz/p/jenkins-tutorial-part-1.html jenkins 入门教程(上)]
| |
| − |
| |
| − | [https://www.cnblogs.com/yjmyzz/p/jenkins-tutorial-part-2.html jenkins 入门教程(中)]
| |
| − |
| |
| − | [https://www.cnblogs.com/yjmyzz/p/jenkins-tutorial-part-3.html jenkins 入门教程(下)]
| |
| − |
| |
| − |
| |
| − |
| |
| − | [https://blog.csdn.net/true100/article/details/47950215 Android项目利用jinkens自动打包]
| |
| − |
| |
| − | [http://blog.51cto.com/linuxg/1792086 Jenkins 持续集成平台构建之使用nexus搭建maven私有仓库]
| |
| − |
| |
| − | [https://www.liaoxuefeng.com/article/001463233913442cdb2d1bd1b1b42e3b0b29eb1ba736c5e000 liaoxuefeng使用Jenkins进行持续集成]
| |
| − |
| |
| − | [https://blog.csdn.net/yelllowcong/article/details/78285230 Jenkins之配置Maven和JDK-yellowcong]
| |
| − |
| |
| − | [https://www.cnblogs.com/yangxia-test/p/4354328.html Jenkins学习二：Jenkins安装与配置]
| |
| − |
| |
| − | [https://blog.csdn.net/Gred01/article/details/78481606 基于Linux实现Jenkins+maven+git+tomcat的自动化构建部署项目]
| |
| − |
| |
| − | [https://blog.csdn.net/gbenson/article/details/50970289 Linux平台搭建Jenkins+Maven+Shell实现自动化构建部署]
| |
| | | | |
| − | ==docker==
| |
| − | [https://juejin.im/post/5994d93ef265da24843e416c Jenkins与Docker的持续集成实践]
| |
| | | | |
| − | [https://www.cnblogs.com/xuezhigu/p/6690783.html 基于Docker构建带有Rsync的Jenkins]
| + | https://wiki.archlinux.org/index.php/Cmus |
| | | | |
| − | [https://www.cnblogs.com/soar1688/p/6833540.html Jenkins Docker安装及Docker build step插件部署配置] | + | [https://jlk.fjfi.cvut.cz/arch/manpages/man/cmus-tutorial.7 cmus-tutorial] |
| | | | |
| − | [https://www.kubernetes.org.cn/5230.html 原创：jenkins+github+docker+maven自动化构建部署]
| + | =moc = |
| | | | |
| − | == 权限==
| + | Moc，Music on Console的缩写，双面板音乐播放器，右侧为播放列表，左侧为文件管理器。支持声音控制、重复播放。 |
| − | [https://blog.whsir.com/post-1785.html jenkins权限管理，不同用户显示不同项目]
| |
| | | | |
| − | [https://www.cnblogs.com/zz0412/p/jenkins_jj_14.html Jenkins进阶系列之——14配置Jenkins用户和权限]
| + | 主页：http://moc.daper.net/ |
| | | | |
| − | [https://www.jianshu.com/p/7e148bcfb96e Jenkins使用教程之用户权限管理（包含插件的安装）]
| + | https://blog.csdn.net/GCQ19961204/article/details/109157588?utm_medium=distribute.pc_relevant.none-task-blog-title-3&spm=1001.2101.3001.4242 |
| | | | |
| − | [https://blog.csdn.net/itfootball/article/details/71404912 Jenkins用户权限管理] | + | =see also= |
| | + | [https://blog.csdn.net/cumo7370/article/details/107421863?utm_medium=distribute.pc_relevant.none-task-blog-BlogCommendFromMachineLearnPai2-4.pc_relevant_is_cache&depth_1-utm_source=distribute.pc_relevant.none-task-blog-BlogCommendFromMachineLearnPai2-4.pc_relevant_is_cache linux命令行音乐播放器_3个用于Linux的命令行音乐播放器] |
| | | | |
| − | ==maven==
| |
| − | [https://blog.csdn.net/xlgen157387/article/details/68961371 Jenkins部署Maven多环境项目（dev、beta、prod）的参数设置]
| |
| | | | |
| − | [http://bookong.iteye.com/blog/2036633 通过Maven和Jenkins插件解决Java项目的配置管理]
| + | https://wiki.archlinux.org/index.php/Cmus |
| | | | |
| − | ==优化==
| + | https://www.howtoing.com/install-cmus-music-player-in-linux/ |
| − | [http://softcook.logdown.com/posts/728344-method-for-reducing-the-jenkins-project-build-disk-space 减少jenkins项目构建磁盘空间的方法]
| |
| | | | |
| − | [https://blog.csdn.net/ZZY1078689276/article/details/77531325 Jenkins丢弃旧的构建]
| + | https://jlk.fjfi.cvut.cz/arch/manpages/man/cmus-tutorial.7 |
| | | | |
| − | [https://blog.csdn.net/qq_27791709/article/details/78835912 Jenkins-工作区清理插件]
| |
| | | | |
| − | [[category:ops]]
| + | [https://jlk.fjfi.cvut.cz/arch/manpages/man/cmus-remote.1 cmus-remote] |
