Bamboo Tagger plugin

Hey Ross,

Cool to see your submission.

This is definitely one we wanted to do for a while now - so it's cool that you're on it here!

One idea - for the tag - you might want to use the meta-data substitution syntax that we use for other configuration screens (e.g. ${bamboo.buildNumber})? Some information on how to do this is here: http://docs.atlassian.com/atlassian-bamboo/2.0/com/atlassian/bamboo/build/AbstractSubstitutionBean.html

Cheers,
Edwin

This plug-in would be real useful – if I could get it to work!

I have set up:

Post Actions
Tag Successful Builds
Tag: foo_%d{yyyyMMdd}
Destination: svn://svn.foo.test/bar/tags/

This is what happens:

  2008-04-24 16:26:04,163 ERROR [pool-8-thread-1] [SubversionTagger] 
  org.tmatesoft.svn.core.SVNException: svn: Commit failed (details follow):
  svn: Path 'tags/foo_20080424' not present

Any ideas?

Just looking at the source code, for the subversion tagger, I see the following

    getSvnClientManager(svnRepository).getCopyClient().doCopy(
        SVNURL.parseURIDecoded(svnRepository.getRepositoryUrl()),

        SVNRevision.HEAD, destinationUrl, false,         "Automatic copy from Bamboo");I'm concerned that the use of HEAD will mean you are not necessarily tagging the version that has just been built?

Hi Ross,

It would be nice to support JiraVersions variables such as bamboo.custom.jiraversion.name, bamboo.custom.jiraversion.rawname,bamboo.custom.jiraversion.type, bamboo.custom.jiraversion.released when defining tag labels! 

Do you probably know some quick workaround or solution?

Thanks 

Can anyone let me know if this is working now?

For clarity....  all version related info that the end user would want is correct on the JiraVersion plugin page, i.e.:

Note that it's jiraversion and not jiraversions.
This is because the variables represent the actual version returned from jira, and thus is labeled as "jiraversion".
The other variables mentioned (jiraversions.jira.projectkey and others) are used internally by the plugin and thus "jiraversions" denotes that the variable belongs to the JiraVersions plugin.

Hope that helps clear up the naming a bit.

-Jonathan

Hi,

I have installed Bamboo Tagger Plugin and configured Tag Label as follows:

•success_%d

However, when I look at tag created in my CVS history in Eclipse, I will see this:

•success_12-47-2008<ProjectKey-BuildPlanKey-BuildNumber>

I was wondering why I am getting 47 as month number instead of 9 which is the current month.

I appreciate your help
BR//Bahman

Ok what am I doing wrong?

I have tried every possible option that I can think of for tagging the build with the subversion revision number

Tag Successful Build

Tag = v8.3.${custom.svn.revision.number} or
Tag = v8_3_${custom.svn.revision.number} or
Tag = v8_3_${bamboo.buildNumber} or
Tag = v8.3.${bamboo.buildNumber}

What am I doing wrong.

-Phillip Hancock

or

Hi,

Will it be possible to implement CVS tag command as well (not only rtag) ?

Thanks,

Andrei.

Bamboo Tagger doesn't play nice with our pre-commit hook which requires a valid issue key to be found. Instead of hardcoding this value

com/atlassian/bamboo/plugin/tagger/svn/SubversionTagger.java:                    "Automatic copy from Bamboo");

could we have it in some text input field so it enables custom commit messages (with e.g. a JIRA issue key).