-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
It seems that hudson "sometimes" puts the wrong build-number in the environment.
I developed a small maven plugin which writes build-number, build-id and
revision to a properties file. Sometimes however, the build-number in the
environment differs from the actual hudson-build number. The difference can be
up to 3 builds. After some time, the build-numbers are synchronous again.
I don't know how to reproduce this issue, it may correlates with the "Hudson
building jobs twice"-bug which I am also experiencing.
Hudson-Version: 0.123
Project-Type: Maven2
Container: Tomcat 5.5
OS: Linux (Debian Etch)
I noticed that in your build Hudson is reusing the Maven process. I suspect that
has something to do with this. Would it be possible for you to look at some of
the past failures and see if there's any correlation between failures and maven
process reuse?
How does your plugin learns the build number? Through system property or through
environment variable?