 | New homepage
The plug-in is being maintained by its owner/maintainers from a new home. The plug-in is still compatible with Hudson, however, the entry points for documentation and issue reporting have been combined in order to provide a single point of entry. |
Plugin Information
This plugin enables users to set a revision (a version) for the Hudson job.
The job revision sets the JOB_REVISION environment variable.
That's often useful for the traceability when there are multiple branches of a product.
Comments (3)
Jan 10, 2011
Peter Schuetze says:
Does the job revision automatically increase when saving the config without chan...Does the job revision automatically increase when saving the config without changing the value manually? This would be an helpful feature for me, since I would typically forget to change the revision manually, which renders the revision number useless. In addition, I will not maintain the server indefinitely. The maintainers after me are more likely to forget this, since the maintenance will slow down in the future.
Jan 11, 2011
Gregory Boissinot says:
The job revision is not automatically updated when you saves your Hudson Job con...The job revision is not automatically updated when you saves your Hudson Job configuration. In my opinion, you must be able to save n times your job configuration without any impact on the value of hudson revision.
The hudson revision value has to be given by the team in charge of the job.
Set the job revision value has to be done at the same level as the other steps. The Hudson maintener is not in charge of this kind of configuration.
Jan 11, 2011
Peter Schuetze says:
Sorry, I had a different understanding what the revision was referring to. I wou...Sorry, I had a different understanding what the revision was referring to. I would have used it to mark the revisions of a build script. I would use for the main (may be even minor) version the app version that can be build. Then I would count up the next element by one every time I save the configuration. This would be my revision number of the job. This would help me to keep track of the revision, that my build script is at.
In combination with the scm-sync-configuration plugin, this would be extremely useful. For identifying the job configuration for a specific run. Currently I have to use the timestamp.