플로그인 링크 https://plugins.jenkins.io/jobConfigHistory/ 추천 설정법 경로: Manage Jenkins -> Configure System -> Job Config History Use different history directory than default history 데이터를 다른 곳으로 위치하고 싶을 때 설정 (Default: $JENKINS_HOME/config-history) 좀 더 빠른 디스크를 사용한다거나 해당 디스크의 inode를 관리하고 싶을 경우 사용 Max number of history entries to keep 이 숫자는 최소(약 1000개)로 유지하는 것이 좋습니다. 비워두면 모든 항목이 유지됩니다. Max number of history..
JobConfigHistory Plugin is a plugin designed to maintain the history of what has changed in the Jenkins job configuration and the system configuration. When a save operation is performed in Jenkins, then the history of what was changed (diff) and who made the changes (user) is saved. It could be a manual save from the UI or a programmatic save. Recommended configuration There are many customizat..
'Manage Jenkins' menu -> 'Manage Plugins' menu -> 'Avaiable' tab Search plugins using a keyword 'theme' Check the plugins as below Simple Theme Theme Manager Dark Theme Material Theme Solarized Theme Check the plugins -> Click 'Install without restart' 'Manage Jenkins' menu -> 'Configure System' menu -> Search 'Built-in Themes'
관련 내용: www.jenkins.io/doc/book/system-administration/security/configuring-content-security-policy/ Configuring Content Security Policy Jenkins – an open source automation server which enables developers around the world to reliably build, test, and deploy their software www.jenkins.io .css 나 .js 요청 시 아래와 같은 메시지가 발생할 경우가 있다. Refused to apply inline style because it violates the following Content ..
Many older builds per Jenkins Job have a significant impact on performance. Below is a script that looks for the old build count for each Job. get_build_count_for_each_job.sh https://github.com/mcpaint/scripts/blob/master/jenkins/get_build_count_for_each_job.sh # Input your Jenkins domain domain=https:// # Input directory with Jenkins jobs job_dir=/mcpaint/jenkins_home/jobs IFS=$'\n' jo..
Jenkins의 각 잡마다 오래된 빌드가 많을 경우 성능에 많은 영향을 끼친다. 각 잡마다 오래된 빌드 개수를 구하는 스크립트를 작성해 본다. get_build_count_for_each_job.sh https://github.com/mcpaint/scripts/blob/master/jenkins/get_build_count_for_each_job.sh # Input your Jenkins domain domain=https:// # Input directory with Jenkins jobs job_dir=/mcpaint/jenkins_home/jobs IFS=$'\n' jobs=(`ls -1 $job_dir`) for job in "${jobs[@]}"; do build_dir=$job_dir/$jo..
Environment variablesenvironment 에다가 설정하면 된다.사용할 때는 $변수명 형태로 사용하면 된다.예제pipeline { environment { PROJECT = "my_project" PHASE = "alpha" } agent { label "BUILD"} stages { stage("START") { steps { sh 'echo "project: $PROJECT, phase: $PHASE"' } } }}
참고자료- Declarative Pipeline: Notifications and Shared Libraries : https://jenkins.io/blog/2017/02/15/declarative-notifications/- Extending with Shared Libraries: https://jenkins.io/doc/book/pipeline/shared-libraries/ 저장소를 만들자공유 라이브러리를 저장할 저장소를 생성한다.디렉토리 구성은 아래와 같이 한다. vars 밑에 넣어두면 된다. (root) +- src # Groovy source files | +- org | +- foo | +- Bar.groovy # for org.foo.Bar class +- vars | +- foo.gr..
- Total
- Today
- Yesterday
- rundeck
- iTerm2
- 플레이북
- Docker
- 리눅스
- Shell Script
- openssl
- rsync
- Playbook
- 데브옵스
- ssl
- 파이프라인
- 엔시블
- URL Encoding
- vagrant
- Config History
- PostgreSQL
- 엔서블
- Linux
- 젠킨스
- Jenkins
- Nexus
- JVM
- nginx
- groovy
- 쓰레드덤프
- Password manager
- Ansible
- Thread Dump
- DevOps
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | |||
5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31 |