This document discusses how the author's organization improved their release process from taking half a day to only half an hour by moving from Maven to Gradle. They built a continuous integration pipeline in Jenkins using Gradle that allowed incremental and parallel compiling, testing, and deployment of changes. This enabled developing features on long-lived branches with automatic validation and fast feedback through commit status APIs and automated approvals and deployments.

1. THERE IS NO SNAPSHOT
Hvordan vi senket release fra halv dag til halv time

2. YOU WILL LEARN
Compile once
Gradle

3. DISCLAIMER
It’s JVM

4. BACKGROUND
• Monolitt
• 46 modules
• ca 2100 .scala

5. • Build
• Test
• Integrasjonstest
• Release
• Deploy
• Maven

6. COMPILE, COMPILE, COMPILE
Compile +
test
Integration-test
mvn release

7. COMPILE, COMPILE, COMPILE
Compile +
test
Integration-test
mvn release
25-60 mins 50-120 mins 60-120 mins

8. SUM
• min 2t 30 mins
• til tider 5t eller mer
• samtidige bygg == crash

9. TENK NYTT

10. HOW?

11. COMPILE, COMPILE, COMPILE
Compile +
test
Integration-test
mvn release

12. COMPILE, COMPILE, COMPILE
Compile +
test Snapshots

13. COMPILE, COMPILE, COMPILE
Compile +
1.10.69 test
major.minor.buildnumber

14. OTHERS
????

15. DOOR #1

16. MAVEN

17. DOOR #2

18. SBT

20. DOOR #3

22. GRADLE

23. PROS
• Inkrementell og parallell
kompilering
• Zinc
• Deployscripts i Groovy
• Unittest buildscripts
• gradle wrapper
• Stort community
• ++

25. PLUGINS
Promoted
Build
Clone
Workspace Copy Artifact
Parameterized
Trigger Gradle

26. PLUGINS (NICE)
Cloudbees
Folders Build Pipeline
Git Pull
Request
Builder
Job Config Disk Usage
History
Jenkins slaves

27. PSEUDO EKSEMPEL

28. Default parameter
VERSION=0.9

29. echo version=${VERSION}.${BUILD_NUMBER} >>
gradle.properties

30. gradle.properties:
version=0.9.3

31. gradle clean test assemble --parallel

32. archive artifact:
embedded-jetty-app.jar

33. archive workspace

34. Trigger
Send med JOB_NAME, BUILD_NUMBER, Git commit

35. Clone workspace

36. gradle integrationtest -x compileScala (++)

37. git pull ${init_job_git_commit}

38. Sjekk for snapshot avhengigheter

39. Logg inn som PROD-deploy-bruker

40. Press Play on tape

41. curl slack.com channel #prod: “ we have liftoff”

42. Promote to PROD

43. PROMOTED BUILD

44. PROMOTED BUILD

Foretrekk
Build Pipeline

45. git tag v0.9.3

46. Keep build forever (look Ma! No Nexus/Artifactory!)

47. IN REAL LIFE
Create release version in JIRA
Update minor version in step one

48. CLEAN, COMPILE,
TEST,INTEGRATIONTEST
• avg = 25 mins
• spikes på 30+ mins skyldes
samtidige pull request bygg
• alle bygg har final
versjonsnummer
• who broke the build?

49. WILL MY PULL REQUEST COMPILE?

52. Github flow
The git-flow process is designed largely around the “release”.
We don’t really have “releases” because we deploy to
production every day – often several times a day.

53. COMMIT STATUS API
https://github.com/blog/1227-commit-status-api

57. FFS-666 master

59. WILL YOU
APPROVE MY
PULL REQUEST?

60. DEPLOY
Feature toggle
Release branch

61. WILL YOU SUM IT UP
• Bygg alt med unikt nummer
• Kompiler én gang
• Gradle(sbt) > Maven

63. ANSWER
YOUR
QUESTIONS
I WILL