Hi Thomas, Thanks for the reply, I am going to give this a try - it sounds quite straight forward.
I'll update with how I get on. Thanks, Navu On Thursday, November 29, 2012 7:30:04 AM UTC, Thomas Ferris Nicolaisen wrote: > > On Wednesday, November 28, 2012 6:40:09 PM UTC+1, Navu wrote: > >> Hi, >> >> Has anyone had any experience with tagging in Git/Jenkings? >> >> Every time we deploy, we normally tag the release (with SVN) and release >> that tag/version. Is it possible to deploy tags from Jenkins and Git? There >> is a Jenkins Git Parameter plugin, but that doesn't seem to work. >> >> Thanks in advance >> Navu >> > > We have a dedicated "tagging" Jenkins job that runs a script that runs > `git tag $releaseVersion` and then `git push origin $releaseVersion`. > > We run it as a parameterized job: > - Check "This build is parameterized" > - Add Parameter -> String Parameter > - Name: releaseVersion > - Default value: <empty> > - Description: The version to release > > Now when you hit Build, Jenkins will prompt you to enter a version number > that will be accessible to your build steps. > > Just try it out yourself on a little toy-project. Should be pretty easy. > You can just Execute Shell build step to run the git commands above in > order (Jenkins will replace the variables with the value at build time). > > See https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build for > more info. > > --
