[
https://issues.jboss.org/browse/JBIDE-13286?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13286:
----------------------------------------
You would put a comment on every jira mentioned in the change log ?
won't that pollute jira very fast ?
Ideally, we're using as few commits as possible to fix a jira, so it should not be too
much pollution. But in worst case, it can be...
Another related interest would be to have jenkins kick of builds
against pullrequests and report if it makes the build fail or not.
There seems to be a Jenkins plugin for that:
https://wiki.jenkins-ci.org/display/JENKINS/Github+pull+request+builder+p... However, it
would require duplicating the amount of jobs.
jobs should generate comment in JIRA recording job URL, BUILD#, and
more detailed commit info (committer + comments)
--------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13286
URL:
https://issues.jboss.org/browse/JBIDE-13286
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.1.x
Is it possible to pull the git hash value used for a given build, look into github for
the matching JIRA #, and drop a comment into the JIRA to the tune of:
"Spinning in <buildURL> >= BUILD_NUMBER"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira