Archive for 5월, 2018

article/ansible_html_report.md at master · hatsari/article · GitHub

2018/05/25

article/ansible_html_report.md at master · hatsari/article · GitHub

https://github.com/hatsari/article/blob/master/ansible_html_report/ansible_html_report.md

Advertisements

Usage – Ansible-CMDB

2018/05/25

Usage – Ansible-CMDB

http://ansible-cmdb.readthedocs.io/en/latest/usage/

jenkins – change user id to include dot(.) char

2018/05/24

add init.groovy.d/init.groovy

// SECURITY-786 change user id to include dot(.) char // default : /^[\w-]+$
hudson.security.HudsonPrivateSecurityRealm.ID_REGEX=/^[\w-\.]+$/

notice : hudson.model.HudsonPrivateSecurityRealm.ID_REGEX (X)

 

지메일을 오프라인으로 사용하는 법 – ITWorld Korea

2018/05/21

지메일을 오프라인으로 사용하는 법 – ITWorld Korea

http://www.itworld.co.kr/news/109389

Continuous Delivery with Kubernetes the Hard Way

2018/05/21

Continuous Delivery with Kubernetes the Hard Way

https://www.infoq.com/articles/continuous-delivery-kubernetes

k8s and site mesh utube

2018/05/20

https://t.co/E2vdRSO3em?ssr=true

Kubernetes for the Spring Developer

2018/05/20

Kubernetes for the Spring Developer

https://www.infoq.com/presentations/kubernetes-spring

When using tags in Jenkins Pipeline

2018/05/17

—-
When using tags in Jenkins Pipeline
// Jenkins Blog

One common pattern for automated releases I have seen and used relies on Git tags as the catalyst for a release process. The immutable nature of releases and the immutable nature of tags can definitely go hand in hand, but up until few months ago Jenkins Pipeline was not able to trigger effectively off of Git tags.

In this post I want to briefly share how to use tags to drive behaviors in Jenkins Pipeline. Consider the following contrived Jenkinsfile, which contains the three basic stages of Build, Test, and Deploy:

pipeline { agent any stages { stage('Build') { steps { sh 'make package' } } stage('Test') { steps { sh 'make check' } } stage('Deploy') { when { tag "release-*" } steps { echo 'Deploying only because this commit is tagged...' sh 'make deploy' } } } }

Of particular note is the when condition on the “Deploy” stage which is applying the tag criteria. This means the stage would only execute when the Pipeline has been triggered from a tag in Git matching the release-* Ant-style wildcard.

In practice, this means that all pull requests, and branch-based Pipeline Runs result in the stage being skipped:

Not Deployed!

When I push a release-1.0 tag, the Pipeline will then be triggerd and run the “Deploy” stage:

Deployed!

Out of the box, Pipelines won’t trigger off of the presence of tags, which means that a Multibranch Pipeline must have a configuration update to know that it must Discover Tags.

Configuring

From the configuration screen of a Multibranch Pipeline (or GitHub Organization Folder), Discovering tags can be enabled by adding the appropriate “Behavior” to the Branch Source configuration:

Configuring the Multibranch Pipeline

CloudBees for ServiceNow | CloudBees

2018/05/17

CloudBees for ServiceNow | CloudBees

https://www.cloudbees.com/blog/cloudbees-servicenow

kubernetes 에서 Pod 균등 분배하기 — Steemit

2018/05/17

kubernetes 에서 Pod 균등 분배하기 — Steemit

https://steemit.com/kubernetes/@calmlake79/kubernetes-pod