[
https://issues.apache.org/jira/browse/CLOUDSTACK-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459989#comment-13459989
]
edison su commented on CLOUDSTACK-44:
-------------------------------------
The build number can be fully customized on jenkins now, as we don't use
hudsonbuild any more. e.g.
http://jenkins.cloudstack.org/job/build-4.0-ubuntu1204/ and
http://jenkins.cloudstack.org/job/build-4.0-rhel63/
> Jenkins build process needs to use the correct version number for the tar.gz
> file name and the RPM/DEB package versions.
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-44
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-44
> Project: CloudStack
> Issue Type: Bug
> Affects Versions: pre-4.0.0
> Reporter: Chip Childers
> Assignee: Pradeep Soundararajan
> Priority: Critical
> Fix For: pre-4.0.0
>
>
> The Jenkins binary build processes are producing version numbers for the
> packages and the tar.gz archive that use 4.0.[buildnumber]. We need a way to
> change this, so that the version string is controlled and matches our
> documented release numbering process.
> The job build number should be embedded somewhere, but I think there's a
> specific place for that within the spec and deb config files.
--
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
