[HAP-341] Commit messages are not configurable and do not accept user input Created: 18/Sep/12  Updated: 01/May/13  Resolved: 18/Mar/13

Status: Resolved
Project: Jenkins Artifactory Plug-in
Component/s: Gradle, Release Management
Affects Version/s: 2.1.2
Fix Version/s: 2.1.5

Type: Bug Priority: Blocker
Reporter: Seth Goings Assignee: Shay Yaakov (Inactive)
Resolution: Fixed Votes: 1
Labels: None

Attachments: PNG File Screen1.png     PNG File Screen2.png    
Issue Links:


In my environment we use git hooks to make sure that commit messages contain JIRA issues... however, I found that the artifactory release plugin doesn't accept my changes to the commit messages (either tag/branch creation, or next version comment).

You can see in Screen1.png I specify commit messages:
EI-1040: blah blah

But in Screen2.png, the commit is denied by our git hook due to the lack of a JIRA issue.
[artifactory-release] Release version 1.0.0 is the actual commit message.

Besides this fact, it would be nice if I could specify a default commit message (or template) that would auto populate these commit messages for me without having to edit them when I'm actually staging a release.

Comment by Seth Goings [ 29/Jan/13 ]

Any updates?

Comment by Shay Yaakov (Inactive) [ 28/Feb/13 ]


I've committed the fix, a SNAPSHOT is available to download from here
As for your other suggestion regarding the default commit messages, we have an open issue to trigger a release build automatically via REST call (HAP-381).
This issue will give you the ability to customize those messages as well.

Comment by Douglas Borg [ 01/May/13 ]

I just tested this out with the released version of the plugin. Thanks a lot!

Generated at Fri Jun 05 23:54:51 UTC 2020 using Jira 8.5.3#805003-sha1:b4933e02eaff29a49114274fe59e1f99d9d963d7.