[jira] [Commented] (LUCENE-4949) nightly builds have wrong version - need to simplify jenkins config tweaks needed after a release

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (LUCENE-4949) nightly builds have wrong version - need to simplify jenkins config tweaks needed after a release

Sebastian Nagel (Jira)

    [ https://issues.apache.org/jira/browse/LUCENE-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638470#comment-13638470 ]

Hoss Man commented on LUCENE-4949:
----------------------------------

If you look at the config for the apache jenkins 4x jobs, you can see that problem comes from how the jobs are configured to include hte jenkins build identife in the version info.

they have the following env variable set...

{noformat}
VERSION=4.1-${BUILD_ID}
{noformat}

...which is then used by the ant target via a command line sys prop like so...

{noformat}
version=$VERSION
{noformat}
Which means...

1) all nightly 4.x builds have been claiming that they are "4.1-*" nightly builds (example "solr-4.1-2013-04-22_10-31-16.tgz") for a long time
2) that this jenkins instance (and any similar jenkins or other continuous build instances) that want to create automated snapshot builds from a lucene/solr branch need to have their config updated anytime the version number changes on that branch otherwise they are lying.

Proposal...

We should introduce some simple, optional, "version.suffix" type property that can be used automated build systems like jenkins to easily set the build date or build number or whatever as a part of the version number, relying on the info on the branch to set the dominate pieces of hte version, so that a jenkins config could simply run something like...

{noformat}
ant -Dversion.suffix="-${BUILD_ID}" prepare-release-no-sign
{noformat}

...and never need to change as new releases are generated off this branch.

(We could even consider setting this property up so that it included the jenkins BUILD_ID by default, not sure if anyone cares about that though)

               

> nightly builds have wrong version - need to simplify jenkins config tweaks needed after a release
> -------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-4949
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4949
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Hoss Man
>
> Right now, if you look at the configuration for these two apache jenkins jobs...
> * https://builds.apache.org/job/Lucene-Artifacts-4.x/
> * https://builds.apache.org/job/Solr-Artifacts-4.x/
> ..you can see that even though they are building off of the 4.x branch, and even though the 4.x branch says the next version is 4.4, the artifacts from these jobs are labeled as if they will be 4.1 releases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]