UPS Admin Console Process

Manual Steps

Before integrating a new version of aerogear-unifiedpush-server-admin-ui into the aerogear-unifiedpush-server it needs to be released which means :

• Run grunt to generate a distribution.

• Change version in package.json to a stable version (i.e 0.0.10).

• Tag with this version.

• Bump to next development version (i.e 0.0.11-dev).

• Commit the release version, the tag and the next dev version (2 commits and 1 tag)

Once this done, the dist folder needs to be copied into the webapp folder of the Unified Push Server repository :

• Create a branch in UPS.

• Copy dist folder from the Admin UI repository to the webapp folder of the Unified Push Server repository.

• Commit and/or Add changes.

• Push to remote

• Open a PR.

Using the Grunt Task

As you can see, there are quite a lot of manual steps to perform a release. Therefore, a new Grunt task has been introduced : release.

Instructions

Let's start by generating your local config file which will contain the loca pathes to the different folders needed for the release process. This local-config.json is not meant to be added to source control. Here are the different fields :

{
	"home": "/home/sebastien/aerogear/aerogear-unified-push-server-admin-ui", (1)
	"ups_repo": "<PATH TO YOUR UPS REPO FOR RELEASE (IN CLEAN STATE)>", (2)
        "webapp": "<PATH TO YOUR UPS REPO>/src/main/webapp", (3)
	"jbossweb": "<PATH TO YOUR JBOSS/WILDFLY DIRECTORY>/standalone/deployments/ag-push.war", (4)
}

(1) : The home folder of admin-ui project, this field will be filled in automatically.

(2) : The location of a Unified Push Server repository. When doing a release, this repo will be used to have the new admin ui updates. It might be a good idea to use a "fresh" clone from the master, to be sure to just add the latest release and not adding assets you might have been using during development.

(3) and (4) : Variables to be used during development time. When running grunt server , Grunt is watching for any changes and applies these to your exploded WAR (jbossweb) and to your repo used for development (webapp). This way you can test / check your changes without redeploying.

By typing grunt release all the steps described in the Manuel Steps instructions will be done automatically for you, except pushing your changes to the remotes and open the Pull Request. A prompt will be displayed for the tag and the next version, using the default computed for you should be okay in the most cases.

.