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
      • Pod
    • Helm Chart
    • OAuth2 Proxy
    • Isito-EnvoyFilter
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Vault
    • Longhorn – Storage
    • VictoriaMetrics
    • MetalLB
    • Kong Gateway
  • CI/CD
    • ArgoCD
    • ArgoWorkflows
    • Argo Events
    • Spinnaker
    • Jenkins
    • Harbor
    • TeamCity
    • Git
      • Bitbucket
  • Coding
    • DevSecOps
    • Terraform
      • GCP – Google Cloud
      • AWS – Amazon Web Service
      • Azure Cloud
    • Golang
    • Laravel
    • Python
    • Jquery & JavaScript
    • Selenium
  • Log, Monitor & Tracing
    • DataDog
    • Prometheus
    • Grafana
    • ELK
      • Kibana
      • Logstash
  • BareMetal
    • NextCloud
  • Toggle search form

[TeamCity] Kotlin DSL – Lesson 4 – Build Chains

Posted on August 9, 2022August 9, 2022 By nim No Comments on [TeamCity] Kotlin DSL – Lesson 4 – Build Chains

Mình có 2 object là:

object Build : BuildType({
    name = "Build"

    vcs {
        root(DslContext.settingsRoot)
    }
...


object Package: BuildType({
    name = "Package"

    vcs {
        root(DslContext.settingsRoot)
    }
...

Giờ bạn muốn setup Package sẽ run sau Build

Cách 1: bạn set thêm trong object Package dependencies

object Package : BuildType({
    name = "Package"

    vcs {
        root(DslContext.settingsRoot)
    }

    steps {
        maven {
            name = "Nim custom step Package"
            goals = "clean package"
            runnerArgs = "-Dmaven.test.failure.ignore=true"
        }
    }

    ##Look at below
    dependencies {
        snapshot(Build) {}
    }

Cách 2 là config trong project

version = "2022.04"

project {

    buildType(Build)
    buildType(Package)

    sequential {
        buildType(Build)
        buildType(Package)
    }
}

sau khi bạn thay đổi thì bạn push lên github đẻ teamcity trigger

import jetbrains.buildServer.configs.kotlin.*
import jetbrains.buildServer.configs.kotlin.buildFeatures.freeDiskSpace
import jetbrains.buildServer.configs.kotlin.buildSteps.maven
import jetbrains.buildServer.configs.kotlin.triggers.vcs

/*
The settings script is an entry point for defining a TeamCity
project hierarchy. The script should contain a single call to the
project() function with a Project instance or an init function as
an argument.

VcsRoots, BuildTypes, Templates, and subprojects can be
registered inside the project using the vcsRoot(), buildType(),
template(), and subProject() methods respectively.

To debug settings scripts in command-line, run the

    mvnDebug org.jetbrains.teamcity:teamcity-configs-maven-plugin:generate

command and attach your debugger to the port 8000.

To debug in IntelliJ Idea, open the 'Maven Projects' tool window (View
-> Tool Windows -> Maven Projects), find the generate task node
(Plugins -> teamcity-configs -> teamcity-configs:generate), the
'Debug' option is available in the context menu for the task.
*/

version = "2022.04"

project {

    buildType(Build)
    buildType(Package)

    sequential {
        buildType(Build)
        buildType(Package)
    }
}

object Build : BuildType({
    name = "Build"

    vcs {
        root(DslContext.settingsRoot)
    }

    steps {
        maven {
            name = "Nim custom step Build"
            goals = "clean compile"
            runnerArgs = "-Dmaven.test.failure.ignore=true"
        }
    }

    features {
        freeDiskSpace {
            requiredSpace = "1gb"
            failBuild = true
        }
    }

    triggers {
        vcs {
            branchFilter = """
                +:lesson1
                +:lesson2
                +:main
            """.trimIndent()
        }
    }

    features {
        freeDiskSpace {
            requiredSpace = "1gb"
            failBuild = true
        }
    }
})

object Package : BuildType({
    name = "Package"

    vcs {
        root(DslContext.settingsRoot)
    }

    steps {
        maven {
            name = "Nim custom step Package"
            goals = "clean package"
            runnerArgs = "-Dmaven.test.failure.ignore=true"
        }
    }

    triggers {
        vcs {
        }
    }
})

và giờ ta khám phá teamcity

Bạn thấy là 2 build đã được chạy
bạn sé thấy 1 thể hiện trên UI

Giờ mình sẽ cùng demo parallel build (chạy xong xong builds) trên teamcity
Bạn để config trong join nhé

import jetbrains.buildServer.configs.kotlin.*
import jetbrains.buildServer.configs.kotlin.buildFeatures.freeDiskSpace
import jetbrains.buildServer.configs.kotlin.buildSteps.maven
import jetbrains.buildServer.configs.kotlin.triggers.vcs

/*
The settings script is an entry point for defining a TeamCity
project hierarchy. The script should contain a single call to the
project() function with a Project instance or an init function as
an argument.

VcsRoots, BuildTypes, Templates, and subprojects can be
registered inside the project using the vcsRoot(), buildType(),
template(), and subProject() methods respectively.

To debug settings scripts in command-line, run the

    mvnDebug org.jetbrains.teamcity:teamcity-configs-maven-plugin:generate

command and attach your debugger to the port 8000.

To debug in IntelliJ Idea, open the 'Maven Projects' tool window (View
-> Tool Windows -> Maven Projects), find the generate task node
(Plugins -> teamcity-configs -> teamcity-configs:generate), the
'Debug' option is available in the context menu for the task.
*/

version = "2022.04"

project {

    buildType(Build)
    buildType(FastTest)
    buildType(SlowTest)
    buildType(Package)

    sequential {
        buildType(Build)
        parallel {
            buildType(FastTest)
            buildType(SlowTest)
        }
        buildType(Package)
    }
}

object Build : BuildType({
    name = "Build"

    vcs {
        root(DslContext.settingsRoot)
    }

    steps {
        maven {
            name = "Nim custom step Build"
            goals = "clean compile"
            runnerArgs = "-Dmaven.test.failure.ignore=true"
        }
    }

    features {
        freeDiskSpace {
            requiredSpace = "1gb"
            failBuild = true
        }
    }

    triggers {
        vcs {
            branchFilter = """
                +:lesson1
                +:lesson2
                +:main
            """.trimIndent()
        }
    }

    features {
        freeDiskSpace {
            requiredSpace = "1gb"
            failBuild = true
        }
    }
})

object Package : BuildType({
    name = "Package"

    vcs {
        root(DslContext.settingsRoot)
    }

    steps {
        maven {
            name = "Nim custom step Package"
            goals = "clean package"
            runnerArgs = "-Dmaven.test.failure.ignore=true"
        }
    }

    triggers {
        vcs {
        }
    }
})

object FastTest : BuildType({
    name = "FastTest"

    vcs {
        root(DslContext.settingsRoot)
    }

    steps {
        maven {
            name = "Nim custom step FastTest"
            goals = "clean test"
            runnerArgs = "-Dmaven.test.failure.ignore=true -Dtest=*.unit.*Test"
        }
    }

    triggers {
        vcs {
        }
    }
})



object SlowTest : BuildType({
    name = "SlowTest"

    vcs {
        root(DslContext.settingsRoot)
    }

    steps {
        maven {
            name = "Nim custom step SlowTest"
            goals = "clean test"
            runnerArgs = "-Dmaven.test.failure.ignore=true -Dtest=*.integration.*Test"
        }
    }

    triggers {
        vcs {
        }
    }
})
TeamCity

Post navigation

Previous Post: [Vault] Eliminate Kubernetes Secrets With Secrets Store CSI Driver (SSCSID)
Next Post: [TeamCity] Kotlin DSL – Lesson 5 – Build Chain Refactoring

More Related Articles

[TeamCity] Installing and configuring TeamCity 2017 TeamCity
[Teamcity] How does TeamCity login and pull/push images to the private Docker HUB TeamCity
[TeamCity] Kotlin DSL – Lesson 3 – DSL Deep Dive TeamCity
[TeamCity] Kotlin DSL – Lesson 5 – Build Chain Refactoring TeamCity
[Team City] Working with Projects and Build Configurations TeamCity
[Teamcity] Why does TeamCity can’t find tag and branch on git TeamCity

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

  • [Azure] The subscription is not registered to use namespace ‘Microsoft.ContainerService’ May 8, 2025
  • [Azure] Insufficient regional vcpu quota left May 8, 2025
  • [WordPress] How to add a Dynamic watermark on WordPress. May 6, 2025
  • [vnet/Azure] VNet provisioning via Terraform. April 28, 2025
  • [tracetcp] How to perform a tracert command using a specific port. April 3, 2025

Archives

  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • 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
    • NextCloud
  • CI/CD
    • Argo Events
    • ArgoCD
    • ArgoWorkflows
    • Git
      • Bitbucket
    • Harbor
    • Jenkins
    • Spinnaker
    • TeamCity
  • Coding
    • DevSecOps
    • Golang
    • Jquery & JavaScript
    • Laravel
    • NextJS 14 & ReactJS & Type Script
    • Python
    • Selenium
    • Terraform
      • AWS – Amazon Web Service
      • Azure Cloud
      • GCP – Google Cloud
  • Kubernetes & Container
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Docker
    • Helm Chart
    • Isito-EnvoyFilter
    • Kong Gateway
    • Kubernetes
      • Ingress
      • Pod
    • Longhorn – Storage
    • MetalLB
    • OAuth2 Proxy
    • Vault
    • VictoriaMetrics
  • Log, Monitor & Tracing
    • DataDog
    • ELK
      • Kibana
      • Logstash
    • Fluent
    • Grafana
    • Prometheus
  • Uncategorized
  • Admin

Copyright © 2025 NimTechnology.