- TeamCity allows building software projects and managing build pipelines for continuous integration and delivery (CI/CD) - A build pipeline in TeamCity refers to the sequence of build steps such as compiling code, running tests, and deploying artifacts that are automatically triggered by code changes - The document demonstrates how to define a build pipeline in TeamCity using Kotlin DSL that compiles and packages a Java application project and its dependency library project

1. Build Pipelines
with TeamCity
@antonarhipov

2. Build pipeline
Step 4Step 2 Step 3Step 1

3. Build pipeline
Step 4Step 2 Step 3Step 1

4. Build pipeline
Step 4Step 2 Step 3Step 1 Result

5. Build pipeline
Step 4Step 2 Step 3Step 1
More
steps
Result

6. CI/CD pipeline
AuditTest PackageCompile
Test
Build pipeline a.k.a CI pipeline
TEST PRODDEV
CD pipeline
.rpm SW

8. Check out sources
Compile
Run tests
Generate report
Publish the results

9. Looks
simple!
Check out sources
Compile
Run tests
Generate report
Publish the results

10. Looks
simple!Why do
I need a
“pipeline”?
Check out sources
Compile
Run tests
Generate report
Publish the results

11. How long it takes to run
the tests?

12. Check out sources
Compile
Run tests
Generate report
Publish the results

13. Check out sources
Compile
Run fast tests
Generate report
Publish the results

14. Check out sources
Compile
Run fast tests
Generate report
Publish the results
Run
integration,
UI
tests

15. Check out sources
Compile
Run fast tests
Generate report
Publish the results
Run
integration,
UI
tests
Pipeline!!

16. Build Test
Check out sources
Compile
Run fast tests
Generate report
Publish the results
Run
integration,
UI
tests

17. Test
Reports &
notifications
Build

18. UI-testing
Reports &
notifications
Build
Integration
testing
More
integration
testing

19. Tests
Reports &
notifications
Build Tests
Tests
Build

20. Tests
Reports &
notifications
Build Tests
Tests
Build
Dependencies

21. Tests
Reports &
notifications
Build Tests
Tests
Build
Dependencies

22. TeamCity @ JetBrains
1800+ projects
10000+ build configurations
500+ agents
Average build time ~25 mins
est 2006

23. Build chains

24. Build chains

25. Step 1
Step 2
Step 3
Step 4

26. Step 1
Step 2
Step 3
Step 4
rev 1
rev 2
rev 3

27. Step 1
Step 3
Step 4
rev 1
rev 3
rev 3
Step 2

28. Step 1
Step 3
Step 4
rev 1
rev 3
rev 3
Step 2

29. rev 1
rev 3
rev 3
Step 1
Step 3
Step 2
Step 4

30. rev 3
“snapshot dependency”
Step 1
Step 3
Step 2
Step 4
rev 1
rev 3

35. Demo

36. import jetbrains.buildServer.configs.kotlin.v2018_1.*
version = "2018.1"
project {
}

37. object ApplicationVcs : GitVcsRoot({
name = "ApplicationVcs"
url = "http://localhost:3000/anton/application.git"
})

38. object ApplicationVcs : GitVcsRoot({
name = "ApplicationVcs"
url = "http://localhost:3000/anton/application.git"
})
// alternatively you could write this, but...
val applicationVcs = GitVcsRoot {
id("ApplicationVcs")
name = "ApplicationVcs"
url = "http://localhost:3000/anton/application.git"
}

39. import jetbrains.buildServer.configs.kotlin.v2018_1.*
version = "2018.1"
project {
vcsRoot(ApplicationVcs)
}
object ApplicationVcs : GitVcsRoot

40. object Application : BuildType({
name = "Application"
artifactRules = """
target/application-1.0-SNAPSHOT.jar
""".trimIndent()
vcs {
root(ApplicationVcs)
}
steps {
maven {
goals = "clean package"

41. object Application : BuildType({
name = "Application"
artifactRules = """
target/application-1.0-SNAPSHOT.jar
""".trimIndent()
vcs {
root(ApplicationVcs)
}
steps {
maven {
goals = "clean package"
//alternatively, this also works, but
val application = BuildType {
id("Application")
name = "Application"
…

42. object Application : BuildType({
name = "Application"
artifactRules = """
target/application-1.0-SNAPSHOT.jar
""".trimIndent()
vcs {
root(ApplicationVcs)
}
steps {
maven {
goals = "clean package"

43. object Application : BuildType({
name = "Application"
artifactRules = …
vcs {
root(ApplicationVcs)
}
steps {
maven {
goals = "clean package"
}
}

44. object Application : BuildType({
name = "Application"
artifactRules = …
vcs { root(ApplicationVcs) }
steps {
maven {
goals = "clean package"
}
}
})

45. import jetbrains.buildServer.configs.kotlin.v2018_1.*
version = "2018.1"
project {
vcsRoot(ApplicationVcs)
buildType(Application)
}
object Application : BuildType

46. object Application : BuildType({
name = "Application"
dependencies {
dependency(Library) {
snapshot {}
artifacts {
artifactRules = "library-*.jar"
}
}
}

47. object Application : BuildType({
name = "Application"
dependencies {
dependency(Library) {
snapshot {}
artifacts {
artifactRules = "library-*.jar"
}
}
}

48. object Application : BuildType({
name = "Application"
dependencies {
dependency(Library) {
snapshot {}
artifacts {
artifactRules = "library-*.jar"
}
}
}

49. import jetbrains.buildServer.configs.kotlin.v2018_1.*
version = "2018.1"
project {
vcsRoot(ApplicationVcs)
vcsRoot(LibraryVcs)
buildType(Library)
buildType(Application)
}

50. https://medium.com/@antonarhipov/building-dependant-maven-projects-d2b71963827a
ApplicationLibrary
refs/heads/master
refs/heads/feature-001
refs/heads/feature-002
refs/heads/master
refs/heads/feature-001
refs/heads/feature-002
github.com/antonarhipov/library.git github.com/antonarhipov/application.git
library-1.0.0-SNAPSHOT.jar
Branches

51. Demo

52. @antonarhipov
?anton.arhipov@jetbrains.com
jetbrains.com/teamcity
medium.com/@antonarhipov