cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-10268) Fix and enhance package script
Date Wed, 07 Feb 2018 08:54:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-10268:

rhtyd commented on issue #2433: CLOUDSTACK-10268: Fix and enhance package script
   @DaanHoogland see comments above on why I initially was -1 on it.
   Will investigate bo failure separately, but found this from last run. LGTM based on the
built packages: (the identifer shapebluexxxx is the jenkins build id)
   ![screenshot from 2018-02-07 09-51-25](

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Fix and enhance package script
> ------------------------------
>                 Key: CLOUDSTACK-10268
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Packaging
>            Reporter: Khosrow Moossavi
>            Priority: Minor
>             Fix For: 4.12
> - if there's a "branding" string in the POM version (e.g. `x.y.z.a-NAME[-SNAPSHOT]`),
> the branding name will be used in the final generated pacakge name such as following:
> `cloudstack-management-x.y.z.a-NAME.NUMBER.el7.centos.x86_64`
> - branding string can be overriden with newly added `-b, --brand` flag
> - new flag `-T, --use-timestamp` to use `timestamp` in final package name where POM
> version contains SNAPSHOT
> - fix long opts (they were broken)
> - tolerate and show a warning message for unrecognized flags
> - usage help reformat

This message was sent by Atlassian JIRA

View raw message