[
https://issues.apache.org/jira/browse/CLOUDSTACK-10268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386911#comment-16386911
]
ASF GitHub Bot commented on CLOUDSTACK-10268:
---------------------------------------------
khos2ow commented on issue #2433: CLOUDSTACK-10268: Fix and enhance package
script
URL: https://github.com/apache/cloudstack/pull/2433#issuecomment-370598448
I'm +1 on testing (may be individually on different environments). I don't
think automated test would give us much needed information anyway (it helps
regardless anyway).
What I would do is:
- build with `--use-timestamp`
- once RPMs
- once DEBs
- build systemvm. preferably with
```bash
VERSION=$(mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}'
--non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec)
TIMESTAMP=$(date +%s)
VERSION=$(echo $VERSION | sed 's/\-SNAPSHOT/\-'${TIMESTAMP}'/g')
./build.sh systemvmtemplate $VERSION $BUILD_NUMBER
```
- manually deploy the whole thing
What to look for:
- .rpm or .deb file to have a name like `cloudstack-xxx-<epoch>.[deb|rpm]`
- when logged in the UI > About Cloudstack should have the full version
`4.12.0.0-<epoch>`
- when ssh in the systemvm `cat /etc/cloudstack-release` should have the
full version `4.12.0.0-<epoch>`
- from UI > Infrastructure > VR should detect correctly to upgrase
- when upgraded should show the full version in the UI (`4.12.0.0-<epoch>`)
----------------------------------------------------------------
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:
us...@infra.apache.org
> Fix and enhance package script
> ------------------------------
>
> Key: CLOUDSTACK-10268
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10268
> 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.0.0
>
>
> * new flag `-T, --use-timestamp` to use `timestamp` when POM version contains
> SNAPSHOT
> ** in the final artifacts (jar) name
> ** in the final package (rpm, deb) name
> ** in `/etc/cloudstack-release` file of SystemVMs
> ** in the Management Server > About dialog
> * 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`
> ** `cloudstack-management_x.y.z.a-NAME-NUMBER~xenial_all.deb`
> * branding string can be overriden with newly added `-b, --brand` flag
> * handle the new format version for VR version
> * 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
(v7.6.3#76005)
