RE: Issue with Deployment Versioning Manager

GABRIELTAY — Wed, 29 May 2019 01:42:46 GMT

I did not perform the actions "updateLocalRepo" and "addContent" since I have committed my changes to the repo manually.

I'm following the steps as described here.

#3: Build master generates new RC deployment package (buildAllApps)

In this use case, all additions made by the team have been incorporated into the remote repository and have gone through sufficient testing. The build master is now ready to promote a new package to the higher environment. The new package should include all additions and changes since the last deployment. The build master will:

(If not done previously) Update version-manager.properties with the appropriate fields. See the Script Setup section for details.
Run the script, using buildAllApps as the action flag. The build master must provide the username and password for authenticating against their version control system (-vc_username, -vc_password). To get a specific set of changes, input a value for the -start_hash option and the -end_hash option. This will generate the package with all new and changed files between the two hash options.
1. NOTE: the package will NOT include the changes introduced in the start hash, but WILL include changes introduced in the end hash.

> version-application -action buildAllApps -vc_username <VC_USERNAME> -vc_password <VC_PASSWORD> -start_hash ac37459 -end_hash 6e83b42

When the script is executed, it generates a package at the location specified by the packagePath field in version-manager.properties"

RE: Issue with Deployment Versioning Manager

Harsha Sharma — Tue, 28 May 2019 09:20:49 GMT

Please verify if your setup is in line with the steps mentioned in this link.

RE: Issue with Deployment Versioning Manager

GABRIELTAY — Mon, 27 May 2019 16:46:15 GMT

I'm on version 19.1 btw