Blog




Today we released the first public version of the SJMP! Its current version is 0.2.0, so expect that there are some rough edges and plenty of use cases still unsupported.

The smartics JIRA Maven Plugin supports updating information on a JIRA server to integrate into our Maven build process.

This plugin is one additional building block for the automation of process around the projectdoc Toolbox for Confluence. Together with the Doctype Maven Plugin and the Apptools Maven Plugin this is the third plugin to make daily tasks simple and fast to execute.

None of the plugin goals requires a POM file to be present. In case such a POM file or the Maven Settings file is present, information (like the URL to the issue management system or the credentials for the JIRA server) will used.

Currently the following use cases are supported:

  1. Adding new versions from the commandline
  2. Adding issues that depend in a root issue from the commandline (such as there is a new feature in the Doctypes MP and we need to add issues in the Doctype Add-ons)
  3. Checking differences between the Maven POM and the JIRA Project (because the REST Client API does not support more currently)

We also have the help and usage goal to support users directly on the commandline.

The main use case for us us is to created related issues. If we have a new feature with our Doctype Maven Plugin that generates a new artifact into existing doctype add-ons or fixes a bug on generated artifacts, then users of these add-ons need to be informed. This is typically done by adding a new issue to the individual doctype add-on projects, explaining briefly that this new feature exists or an issue has been solved. With this plugin the related issues can be created automatically, link to the root issue, and be set to a fixed state. No manual steps involved.

Use Cases

So here are some usage examples with goals of this plugin.

Use Dry Run!

 

Use -DdryRun to check what will be executed and changed on JIRA without actually changing anything!

Add Versions

Run

mvn smartics-jira:versions 

on a project to add the current version and the next micro, minor, and major version on JIRA.
For instance, if your project is currently in version 2.3.1-SNAPSHOT, running the above command will ensure that the related project (identified with the issue management in your project's POM) on your JIRA server will have versions 2.3.12.3.2 (next micro), 2.4.0 (next minor), and 3.0.0 (next major) configured. If any version already exists, that's fine. If not, it will be created.

See Update Versions for more details.

Sync Project

Run

mvn smartics-jira:sync 

on a project to check the differences in name, description, and URL between this information in the POM and on the JIRA project.

Create dependent Issues

Run

mvn smartics-jira:issues -DrootIssue=MYPROJ-1 -DprojectKeys=MYOTHERPROJ1,MYOTHERPROJ2

to create dependent issues in upstream projects. This is useful if a change in one project has positive effect, like fixing a bug or adding a new feature, without the other projects needing to be touched.

In version 0.2.1: Local and global Parameter Names

 

Note that each parameter you specify on the command line may be made unique with the prefix smartics-jira (e.g. smartics-jira.projectKeys) with the next version of this plugin.

To keep the command line short, the prefix is not necessary.




Link

Link

Posts