Previous: CI for Webdesign projects       Next: Deployment workflows

The steps below are used by a Java Programmer to publish Java widgets and other software as JAR files, simply by saving their changes to Github.

The flow is quite simple: every time the source code of an extension project is checked into Github, CircleCI is notified. CircleCI pulls the source code from Github and builds the JAR files. If all unit tests pass then the JAR files are published to Artifactory, where they can be pulled down during application builds.

This is now our standard way to prepare and publish Java code so it can be reused by Web Design projects.

Programers do Java development using the Eclipse IDE:

Programmers develop the Java software for widgets and other functionality, and debug their code by running the Designer in Eclipse.

Changes can be saved to our source code repository from within Eclipse, using the Git Perspective:

Alternatively, the programmers can commit their changes using Git commands in Terminal, or by using the GitHub for Mac application:

The project can be seen at Github, our source code repository:

The push to Github triggers a build of the project at CircleCI, our Continuous Integration service:

When the building and testing succeeds, the resulting jar files are pushed to Artifactory (http://repo.tooltwist.com), so the Java software can be used by web design projects:

CI for Java projects (Advanced)