You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Chip Childers (JIRA)" <ji...@apache.org> on 2013/06/04 20:55:31 UTC

[jira] [Updated] (CLOUDSTACK-1049) provide a way to extract commit sha1 from packages generated on jenkins

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

Chip Childers updated CLOUDSTACK-1049:
--------------------------------------

    Fix Version/s:     (was: 4.1.0)
    
> provide a way to extract commit sha1 from packages generated on jenkins
> -----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1049
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1049
>             Project: CloudStack
>          Issue Type: Wish
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0
>         Environment: CloudStack-non-OSS-49-rhel6.3.tar.gz
>            Reporter: Sanjeev N
>            Assignee: Pradeep Soundararajan
>             Fix For: 4.2.0
>
>
> QA environments deployed from jenkins artifacts (rpms, debs) need to have a way to post the commit sha1 of the package. This will help make bug reports faster to track. Packaging should however have a flag to disable this when a release build is made.
> Downstream distros doing their own packaging shouldn't have to assume they are building from a git tree.

--
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