diff --git a/README.md b/README.md
index da68e93187ecd82f5240db9fd5ade045a23584f4..74fb05aa17981d02d4fe23b5ecabd9b0568e35df 100644
--- a/README.md
+++ b/README.md
@@ -61,7 +61,12 @@ cpublish {
 
 If a commit lands on master, and `cpublish.skip` is false, you can have confidence that the gradle `project.version` includes a new value. Running `gradle uploadArchives` to publish a new release will work.
 
-TODO: currently depend on Jenkins to tag the release, provide a task to do this from Gradle
+After the `uploadArchives` task completes, you can have Jenkins tag the release and push the tag to the repository.
+
+1. In your Jenkins build job, in the **Build** section, add a `Execute system Groovy script` step, and have it run a copy of the provided [artifact-version.groovy](artifact-version.groovy).
+2. In the same job, in the **Post-build actions** section, add a `Git Publisher` step, and configure it:
+
+![Git Publisher configuration screenshot](git-publisher-config.png)
 
 ## Developing the plugin
 
diff --git a/git-publisher-config.png b/git-publisher-config.png
new file mode 100644
index 0000000000000000000000000000000000000000..939c7ff9f36deb90c7c09b7b73b8cd6e68f8580e
Binary files /dev/null and b/git-publisher-config.png differ