ARA Features Unique to Release Engineer

Jenkins Plugins for Automating Continuous Delivery

The Release Engineer plug-in allows Jenkins to call Release Engineer as a step in a job. This enables you to utilize Jenkins to orchestrate your Continuous Integration process, while Release Engineer does the heavy lifting of packaging the application stack and deploying it across your Continuous Delivery environments, without the use of one-off script and without the use of any endpoint agents or Jenkins Executors.

Download the Jenkins Plugin from GitHub.

Solving the Jenkins Security Issue

Release Engineer eliminates the need for you to install a Jenkins 'Executor' on all of your delivery 'endpoints.' For large environments, this is essential to reduce the security risk of having a Jenkins agent running on all testing and production servers.

Jenkins and Release Engineer

Configuration of the Release Engineer Jenkins Plugin

The basic configuration includes the following:

  • Username and Password - Determines security access to the various objects within Release Engineer, including the Applications and Components that are available from the Jenkins Plug-In.
  • Target Environment - A Release Engineer Environment contains all of the Servers that will be deployed to.
  • Application - A Release Engineer Application contains all of the Components that make up a deployment. It is deployed against an Environment.
  • Wait for Deployment to Complete - This tells Jenkins to wait until Release Engineer is finished with the deployment before moving on to the next step in the Job. If this option is chosen, the remaining steps in the Job will only run if the deployment was successful. If left unchecked, Jenkins will continue to the next step in the Job as soon as Release Engineer begins the deployment, and ignore the success or failure of the deployment.
  • Use Advanced Version Selection - If this is checked, other options will appear that will allow you to take advantage of the capabilities that are available with Applications within Release Engineer. These include:
    • Find Latest Version - If Latest Version is approved, create a new version
    • Use Component Selection
    • Set Component Attributes
    • Set Application Attributes

Enterprise Platform support

Release Engineer runs on a Linux or Windows server, includes a web based UI and supports software deployments to multiple platforms and can support a deployments that include cross platforms. It also supports WebSphere Deployments, database deployments and integrates with external repositories for retrieving binaries.

Platform Support Includes:

Windows 2008, Windows 2012
Solaris, HP-UX, AIX, Linux
Ubantu, Redhat, SuSe, Debian
Tandem, Stratus, IBM iSeries, OpenVMS, Unisys, IBM 4690
IBM WebSphere
Jetty, Tomcat, Cloud Foundry
Microsoft IIS
Microsoft SQL Server