Skip to content

NimTechnology

Trình bày các công nghệ CLOUD một cách dễ hiểu.

  • Kubernetes & Container
    • Docker
    • Kubernetes
      • Ingress
    • Helm Chart
    • Isito-EnvoyFilter
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Vault
    • Longhorn – Storage
    • VictoriaMetrics
  • CI/CD
    • ArgoCD
    • ArgoWorkflows
    • Spinnaker
    • Jenkins
  • Coding
    • Terraform
      • GCP – Google Cloud
      • AWS – Amazon Web Service
    • Golang
    • Laravel
    • Jquery & JavaScript
    • Git
    • Selenium
  • Log & Monitor
    • Prometheus
    • Grafana
    • ELK
      • Kibana
      • Logstash
  • BareMetal
  • Toggle search form

[jenkins] Scripted Pipeline lesson 2: Docker

Posted on November 14, 2021November 14, 2021 By nim No Comments on [jenkins] Scripted Pipeline lesson 2: Docker

Đầu tiền bạn cần cài đặt plugin sau:

Contents

  • 1) Prepare
    • 1.1) install Plugin Docker pipeline
    • 1.2) approve
    • 1.3) Needing vm jenkins that have docker
  • 2) Docker Images
  • 3)Docker Args
  • 4) Docker AlwaysPull
  • 5) Docker Custom Workspace
  • 6) RegistryUrl CredentialsId
  • 7) Dockerfile
  • 8) Dockerfile Directory
  • 9) Dockerfile Filename
  • 10) Dockerfile AdditionalBuildArgs
  • 11) Dockerfile Custom Workspace

1) Prepare

1.1) install Plugin Docker pipeline

1.2) approve

Sau đó khi run build nó sẽ cần bạn approve 1 số thứ

1.3) Needing vm jenkins that have docker

[Jenkins] Install Jenkins in VM or Physical Server
Bạn cần phải jenkins trên vm để run được 1 số khái báo bằng docker.
Xem hướng dẫn của mình.

Sau đó cấu hình kết nối giữa jenkins master và agent.

[Jenkins] Hướng dẫn kết nối kết nối Jenkins master và Agent

2) Docker Images

GIờ hình ta đã có hết mọi thứ, mình sẽ cung cấp cho bạn file script

node('jenkins-vm'){
    stage('build'){
        def  mavenImage = docker.image("maven:latest")
        
        mavenImage.inside{
            sh "mvn -v"
        }
    }
}
Đây là log rất chi tiết và dễ hiểu

3)Docker Args

Bài này chúng ta thêm env trong lúc run container.

node('jenkins-vm'){
    stage('build'){
        def  mavenImage = docker.image("maven:latest")
        
        mavenImage.inside('-e myEnv=nimtechnology', {
            sh 'echo $myEnv'
        })
    }
}
Bạn để ý đây là nháy đơn
Nếu để là nháy kép “” thì sẽ bị như lỗi trên

Còn nếu bạn nghe lời mình sẽ ko lỗi

4) Docker AlwaysPull

Chúng ta có pipeline script, Lúc nào jenkins của pull image

node('jenkins-vm'){
    stage('build'){
        def  mavenImage = docker.image("maven:latest")
        
        mavenImage.pull()
        
        mavenImage.inside('-e myEnv=nimtechnology', {
            sh 'echo $myEnv'
        })
    }
}

5) Docker Custom Workspace

node('jenkins-vm'){
    stage('build'){
        ws('/var/lib/jenkins/workspace/nodeDockerCustomWorkspace'){
            def  mavenImage = docker.image("maven:latest")
            
            mavenImage.inside('-e myEnv=nimtechnology', {
                sh 'echo $myEnv'
            })
        }
    }
}

6) RegistryUrl CredentialsId

node('jenkins-vm'){
    stage('build'){
        def  mavenImage = docker.withRegistry('https://docker.nimtechnology.com'){
            docker.image('docker.nimtechnology.com/dockerhub/kennethreitz/httpbin').inside{
                sh 'printenv'
            }
        }
    }
}

7) Dockerfile

node('jenkins-vm'){
    stage('build'){
        checkout([
            $class: 'GitSCM', 
            branches: [[name: "origin/master"]], 
            userRemoteConfigs: [[
                url: 'https://github.com/mrnim94/pipeline-agent-dockerfile.git'
            ]]
        ])
        def  myCustomUbuntuImage = docker.build("my-ubuntu:my-latest")
        
        myCustomUbuntuImage.inside{
            sh 'cat /etc/lsb-release'
        }
        
    }
}

8) Dockerfile Directory

node('jenkins-vm'){
    stage('build'){
        checkout([
            $class: 'GitSCM', 
            branches: [[name: "origin/master"]], 
            userRemoteConfigs: [[
                url: 'https://github.com/mrnim94/pipeline-agent-dockerfile-dir.git'
            ]]
        ])
        def  myCustomUbuntuImage = docker.build("my-ubuntu:my-latest", "./dockerfileDir")
        
        myCustomUbuntuImage.inside{
            sh 'cat /etc/lsb-release'
        }
        
    }
}

9) Dockerfile Filename

node('jenkins-vm'){
    stage('build'){
        checkout([
            $class: 'GitSCM', 
            branches: [[name: "origin/master"]], 
            userRemoteConfigs: [[
                url: 'https://github.com/mrnim94/pipeline-agent-dockerfile-filename.git'
            ]]
        ])
        def  myCustomUbuntuImage = docker.build("my-ubuntu:my-latest", "--file myCustomNameDockerfile .")
        
        myCustomUbuntuImage.inside{
            sh 'cat /etc/lsb-release'
        }
        
    }
}

10) Dockerfile AdditionalBuildArgs

node('jenkins-vm'){
    stage('build'){
        checkout([
            $class: 'GitSCM', 
            branches: [[name: "origin/master"]], 
            userRemoteConfigs: [[
                url: 'https://github.com/mrnim94/pipeline-agent-dockerfile.git'
            ]]
        ])
        def  myCustomUbuntuImage = docker.build("my-ubuntu:my-latest", "--tag my-dockerfile:example .")
        
        myCustomUbuntuImage.inside{
            sh 'cat /etc/lsb-release'
        }
        
    }
}

11) Dockerfile Custom Workspace

node('jenkins-vm'){
    stage('build'){
        ws('/var/lib/jenkins/workspace/nodeDockerCustomWorkspace'){
            checkout([
                $class: 'GitSCM', 
                branches: [[name: "origin/master"]], 
                userRemoteConfigs: [[
                    url: 'https://github.com/mrnim94/pipeline-agent-dockerfile.git'
                ]]
            ])
            def  myCustomUbuntuImage = docker.build("my-ubuntu:my-latest", "--tag my-dockerfile:example .")
            
            myCustomUbuntuImage.inside{
                sh 'cat /etc/lsb-release'
            }
        }
    }
}
Jenkins

Post navigation

Previous Post: [Jenkins] Install Jenkins in VM or Physical Server
Next Post: [Istio] why does workload inject Istio that workload always connects fail database? – hold Application

More Related Articles

[jenkins] Scripted Pipeline lesson 1: Introduction Jenkins
[Jenkins] Using pod template to run Jenkins agent on Kubernetes. Jenkins
[Jenkins] Share Libraries 3: Import library class. Jenkins
[Jenkins] Lesson 19: Trigger other jobs through Jenkins Pipeline Jenkins
[Jenkins] Scripted Pipeline lesson 11: Options _ SkipStagesAfterUnstable Jenkins
[Jenkins] Build-Self Jenkins agent Docker and Runing a view Apps on this ones Jenkins

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Tham Gia Group DevOps nhé!
Để Nim có nhiều động lực ra nhiều bài viết.
Để nhận được những thông báo mới nhất.

Recent Posts

  • Protected: My Assignment  June 24, 2022
  • [Spinnaker] Spinnaker writes too many logs – Reduce spinnaker log level June 22, 2022
  • [Jenkins] Jobs will be created automatically by Jenkins Job Builder June 20, 2022
  • [Postgresql] Install postgresql client and trying a few command postgresql. June 20, 2022
  • [Mount/Nextcloud] How do you mount a hard disk that was used windows into Linux. June 19, 2022

Archives

  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021

Categories

  • BareMetal
  • CI/CD
    • ArgoCD
    • ArgoWorkflows
    • Jenkins
    • Spinnaker
  • Coding
    • Git
    • Golang
    • Jquery & JavaScript
    • Laravel
    • Selenium
    • Terraform
      • AWS – Amazon Web Service
      • GCP – Google Cloud
  • Kubernetes & Container
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Docker
    • Helm Chart
    • Isito-EnvoyFilter
    • Kubernetes
      • Ingress
    • Longhorn – Storage
    • Vault
    • VictoriaMetrics
  • Log & Monitor
    • ELK
      • Kibana
      • Logstash
    • Grafana
    • Prometheus
  • Uncategorized
  • Admin

Copyright © 2022 NimTechnology.