This document discusses best practices for releasing software projects with Gradle, including updating the project version, interacting with version control systems like Git to tag releases, connecting to issue trackers, and publishing releases. It provides code snippets for tasks like versioning, tagging releases in Git, reading the Git branch and commit, and reacting to the build result. The document also includes puzzles and links for further information.

2. Releasing with
Gradle
snippets,puzzles,(best)practices
René Gröschke
Principal Engineer, Gradleware
Gradle Exchange 2014

3. Motivation
#gradlesummit 3/27

4. When doing a Release
#gradlesummit
update your project version
deal with your vcs (tagging, branching)
publish/deploy the released distribution
interact with your issue tracker
double check your dependencies
rollback if build failed
...
·
·
·
·
·
·
·
4/27

5. releasing manually?
#gradlesummit 5/27


6. #gradlesummit 6/27

7. demo app
#gradlesummit 7/27

8. project versioning
declaring a project version
#gradlesummit
// not optimal
version = "1.1-SNAPSHOT"
// better
version = file("version.txt").text
...
BUILD.GRADLE
8/27

9. project versioning (2)
put some semantics in your project version!
#gradlesummit
version = MyVersion.load(file("version.properties"))
class MyVersion {
int major, minor, bugfix, build
String toString(){
"${major}.${minor}.${bugfix}.${build}"
}
...
}
BUILD.GRADLE
9/27

10. puzzle #1a (major|minor|bugfix) release
#gradlesummit 10/27

11. source versioning
interacting with your vcs (option 1)
#gradlesummit
buildscript {
repositories { jcenter() }
dependencies { classpath 'org.ajoberstar:gradle-git:0.8.0' }
}
import org.ajoberstar.grgit.*
ext.repo = Grgit.open(file('.'))
task tagRelease << {
repo.tag.add {
name = version
message = "Release of ${version}"
}
}
BUILD.GRADLE
11/27

12. source versioning (2)
interacting with your vcs (option 2)
#gradlesummit
task tagGitWorkspace(type:Exec){
commandLine 'git', 'tag', project.version.toString()
}
BUILD.GRADLE
12/27

13. source versioning (3)
sidenote: reading branch/commit via file io
#gradlesummit
def branch = file(".git/HEAD").text - "ref: refs/heads/"
def commitId = file(".git/refs/heads/$branch").text
BUILD.GRADLE
13/27

14. puzzle #2a clean working copy
#gradlesummit 14/27

15. connect your issue tracker
worth the effort
#gradlesummit
keep version stati in sync
document tackled issues
check project status
...
·
·
·
·
15/27

16. #gradlesummit 16/27

17. connect your issue tracker (2)
getting started
#gradlesummit
explore the api of your tool of choice!
jira, youtrack, trello, github
REST is your friend
REST is easy with gradle & groovy
...
·
·
·
·
·
17/27

18. #gradlesummit
"but we have a custom tool!?"
GET RID OF IT!
18/27

19. puzzle #3connect your issue tracker
#gradlesummit 19/27

20. publishing
depends on your product
#gradlesummit
maven repository, bintray, maven-central out of the box
s3, ftp, ssh via custom gradle tasks
feed proprietary tools (e.g. liverebel)
...
·
·
·
·
20/27

21. when something went wrong...
option 1
#gradlesummit 21/27

22. when something went wrong...
option 2: react on your build result
#gradlesummit
...
gradle.addBuildListener(new BuildAdapter(){
void buildFinished(def result){
result.failure ? gitReset() : gitPush()
}
})
...
BUILD.GRADLE
22/27

23. links and pointers
#gradlesummit
gradle.org
gradleware.com
semantic version library
Gradle-Git Plugin (more than just a git plugin)
Gradle SVN Kit plugin
liverebel
my demo app
·
·
·
·
·
·
·
23/27

24. Q&A
#gradlesummit 24/27

25. Thanks for listening!
twitter @breskeby
www www.gradleware.com
github github.com/breskeby

26. references
#gradlesummit
http://devopsreactions.tumblr.com/post/70883605526/final-straight-on-a-
project
http://www.youtube.com/watch?v=UyLUCnTdu7o
http://devopsreactions.tumblr.com/post/49078186169/go-live-day
·
·
·
26/27