[
https://issues.apache.org/jira/browse/CLOUDSTACK-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802001#comment-13802001
]
Rayees Namathponnan commented on CLOUDSTACK-1049:
-------------------------------------------------
Fixed this with below in RR
https://reviews.apache.org/r/14843/
Chip - with this change packaging wont break, if we are building outside git
tress. command "cloudstack-sccs" returns blank
> 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: Rayees Namathponnan
> Fix For: 4.3.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 was sent by Atlassian JIRA
(v6.1#6144)
