cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhinandan Prateek (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-1049) provide a way to extract commit sha1 from packages generated on jenkins
Date Fri, 04 Oct 2013 12:24:44 GMT

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

Abhinandan Prateek updated CLOUDSTACK-1049:
-------------------------------------------

    Fix Version/s:     (was: 4.2.0)
                   4.2.1

> 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.1
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message