Setup a free github account, if you have not already one

Log to your account at https://github.com/<your account>

Create an empty github repository

Name the repository abendrot-test, check 'Initialize this repository with a README' and select maven .gitignore.

Create and clone immediately your repository. I assume that you know how to. If not, Github Bootcamp.

Clone abendrot from https://github.com/cthiebaud/abendrot.git; checkout the initial state, i.e. the first commit

Compare yours (abendrot-test) and mine (abendrot) directories

Open eclipse, switch to java perspective

Create a new dynamic Web project:

• File
• New
• Other...
• scroll down and open folder 'Web'
• Dynamic Web Project
• click Next >

Set project name to abendrot-test, change project location from default to te location where you cloned your abendrot-test from Github, accept all other defaults, click Next >

Change the sources directory from eclipse default src to maven default src/main/java

Change the output folder from eclipse default build/classes to maven default target/classes, click Next >

Change the webapp folder from eclipse default WebContent to maven default src/main/webapp, click Finish

Be polite and say 'no, thanks', when you are invited to change perspective.

Convert to maven Project. Right-click on the project name in the package explorer to open the context menu, select

• Configure
• Convert to Maven Project

Set your groupID, set artifactID to 'abendrot-test', and change packaging type to 'war'.

From Eclipse menu,

• File
• New
• Other...
• scroll down and open folder 'Web'
• HTML File
• click Next >

Select parent folder 'abendrot-test/src/main/webapp', name your page index.html, click Next >

Select HTML5 format, click Finish

Start 'Run As' wizard on the index.html file we've just created

• Right click on index.html
• Run As
• Run on Server

Select 'Manually define a new server', select 'Apache' folder, choose Tomcat7, make sure that 'Server's host name' is localhost, click Next >

Point the wizard to the $TOMCAT_HOME you've just downloaded

Click Finish, Eclipse starts Tomcat and open the page in its internal browser. The page is empty.

Add <h1>Hello , World!</h1> to index.html, save, back to the browser, refresh, the content is displayed, no restart needed.

Right-click on the project name in the package explorer to open the context menu, select

• Team
• Share Project ...

Select Git Source Code Management System, then select your local repo.

Give EGit some time to digest the git repo, and the Egit decorations will eventually appear in the package explorer.

Commit to local git, then push to remote git on Github.

Checkout state #2 of abendrot, i.e. commit 42da300...

Compare yours and mine directories

Open and login to https://travis-ci.org/profile# and hook your project to travis.ci

On https://travis-ci.org/, your build is under the tab 'My Repositories' :

There is a SAP HANA Cloud Deployment Plugin for Maven named nwcloud-maven-plugin on Github ! It has been developed by SAP Research, but it is not included in HANA Cloud distribution. The reason for it being that SAP HANA Cloud is build tool agnostic, as already mentionned.

There does not seem to be any public version of the nwcloud-maven-plugin binaries, at least not in any well known repository such as maven central, therefore, to use it, one must build it. That's what I did, build worked like a charm: version 1.0.1.RELEASE is published to my personal public nexus repositoy. Even if compiling the plugin was a snap, you may not want to go through the exercice. Include the pluginRepositories section below in your pom.xml, your maven build will directly grab nwcloud-maven-plugin binaries from my personal nexus repository, no need to compile.

  <!-- my own repos were I deployed nwcloud-maven-plugin -->
  <pluginRepositories>
    <pluginRepository>
      <id>public.releases.buildeventhub.net</id>
      <url>http://buildeventhub.net:8081/nexus/content/repositories/releases/</url>
      <releases>
        <enabled>true</enabled>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
    </pluginRepository>
    <pluginRepository>
      <id>public.snapshots.buildeventhub.net</id>
      <url>http://buildeventhub.net:8081/nexus/content/repositories/snapshots/</url>
      <releases>
        <enabled>false</enabled>
      </releases>
      <snapshots>
        <enabled>true</enabled>
      </snapshots>
    </pluginRepository>
  </pluginRepositories>

Configuration of nwcloud-maven-plugin is done through a nwcloud.properties file. This is well documented in the plugin documentation. Since version 1.0.1.RELEASE, it isn't necessary to include the HANA Cloud account password in the nwcloud.properties file; credential can be stored in the user home, à la maven, in the ~/.m2/settings.xml maven file; just follow the the Using encrypted passwords section of the documentation for the complete how-to. If you choose to keep the password in the nwcloud.properties file, to avoid submitting inadvertently your private password to your public github, you should include immediately nwcloud.properties in .gitignore, commit localy and push to remote.

For you reference, here is the complete nwcloud.properties file I am currently using, including super sensitive password information, of course.

Adapt this nwcloud.properties to your context. Then, launch for example :

$ mvn com.sap.research:nwcloud-maven-plugin:1.0.1.RELEASE:status

To avoid having to type the full plugin identity before the goal (groupID:artifactID:version:goal e.g. com.sap.research:nwcloud-maven-plugin:1.0.1.RELEASE:status), you may want to " (...) search in settings.xml for the pluginGroups tag and insert com.sap.research as an artifact group that contains plugins.", as quoted from the nwcloud-maven-plugin documentation.

<pluginGroups>
    <!--pluginGroup
     | Specifies a further group identifier to use for plugin lookup.
    -->
    <pluginGroup>com.sap.research</pluginGroup>
</pluginGroups>

$ mvn nwcloud:status

Finally, Add this xml fragment to the <build><plugins> section of pom.xml:

<plugin>
  <groupId>com.sap.research</groupId>
  <artifactId>nwcloud-maven-plugin</artifactId>
  <version>1.0.1</version>
  <executions>
    <execution>
      <id>after.deploy</id>
      <phase>deploy</phase>
      <goals>
        <goal>stop</goal>
        <goal>deploy</goal>
        <goal>start</goal>
      </goals>
    </execution>
  </executions>
</plugin>

With all this, a maven deploy will automatically trigger the upgrade of the application in the cloud!. e.g.

$ mvn clean deploy -DaltDeploymentRepository=[your_repo_id]::default::[your_repo_url]

cf. Maven Deploy Plugin for -DaltDeploymentRepository syntax. If you do not know what that means, and have no time for a maven tutorial right now, enter :

$ mvn clean deploy -DaltDeploymentRepository=my_repo::default::file:///tmp/my_repo

Configure maven-git-commit-id-plugin as described in section "The easier way: generate git.properties" of the README. Cf. xml snippet:

Add a GitRepositoryState java class to hold git properties. Grab code from here

Add a index.jsp java server page to display a Github ribbon. The ribbon points back to abendrot sources in Github. Moreover, the ribbon points to the very commit that has been build to produce the application (not sure to be crystal clear ... anyhow, you got it). Moreover, if you have deployed from a directory where there are uncommited changes to github, the ribbon will not be deployed at all. Grab code from here

Rename index.html to helloworld.html. Now, index.jsp is the default landing page of abendrot web application.

Do not forget to add abendrot/src/main/resources/git.properties to .gitignore. The file will be generated at each build, it must not be kept as a source file.

First of all, to perform a release, it is mandatory to store the HANA Cloud account password outside the project directory, in the user home (~/.m2/settings.xml) as described in the Automate Section above.

Add <scm> and <distributionManagement> sections to your pom.xml. Open the accordion below to look at mine. Cut, adapt to your context, and paste into your pom.xml. As before, in case you do not have a maven repository where to deploy through HTTP, use your file system, replace http://.../repositories/[releases|snapshots] with something like file:///tmp/my_repo/[releases|snapshots]

In order to perform a fully automated & unattended release, to avoid to be prompted for username and password during the process, we need to instruct maven where to find our credentials.

1. In general, maven stores credentials in ~/.2/settings.xml, cf. http://maven.apache.org/settings.html#Servers.
2. Encryption is recommended, but not mandatory, cf. http://maven.apache.org/guides/mini/guide-encryption.html.
3. Finally, a piece of glue between maven and git is required: the project.scm.id property, cf. http://maven.apache.org/plugins/maven-release-plugin/faq.html#credentials.

Ensure that your project directory is clean. That means that

1. you have pulled the last vesion from Github,
2. all your modifications have been commited and pushed to Github, and
3. there are no local files that are not explicitely declared in a .gitignore file.

$ cd to the new directory

$ cd abendrot-release/

Run a dry test. Loop until successful.

$ mvn clean deploy

Run prepare phase of the release process, e.g.:

$ mvn release:prepare --batch-mode -DreleaseVersion=0.0.3 -Dtag=abendrot-0.0.3 -DdevelopmentVersion=0.0.4-SNAPSHOT

Run perform phase of the release process, e.g.:

$ mvn release:perform --batch-mode