Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Fri, 21 Sep 2012 08:46:08 +1100 (NCT)
From: "edison su (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <1700474857.104917.1348177568287.JavaMail.jiratomcat@arcas>
In-Reply-To: <2041564781.50320.1347027247737.JavaMail.jiratomcat@arcas>
Subject: [jira] [Closed] (CLOUDSTACK-44) Jenkins build process needs to use
 the correct version number for the tar.gz file name and the RPM/DEB package
 versions.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

edison su closed CLOUDSTACK-44.
-------------------------------

    Resolution: Fixed
    
> 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