]
Denis Golovin updated JBIDE-13372:
----------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
improve usability of jiralint emails
------------------------------------
Key: JBIDE-13372
URL:
https://issues.jboss.org/browse/JBIDE-13372
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Priority: Minor
Fix For: 4.2.x
Could these be reformatted to list the names of the offenders at the top of the email, so
we don't have to waste time scanning to see whose name is associated w/ the
incorrectly versioned jiras?
Better, can they simply be sent to the people who've set bad fixVersions, rather than
the whole list? The only person who needs to see the email below is Snjezana.
{code}
-------- Original Message --------
Subject: Weekly jira sanity check - jbosstools-jiralint - Build # 138 - Still Unstable!
Date: Sun, 13 Jan 2013 00:01:28 -0500 (EST)
From: ci-builds(a)redhat.com
To: external-exadel-list(a)redhat.com
This is the weekly check for jira problems.
Please fix the issues outlined below if there are any. Thank you!
jbosstools-jiralint - Build # 138 - Still Unstable:
Check console output at
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint/138/ to view the
results.
1 tests 1 failure(s) / -2
1 tests failed.
FAILED: ToolsIllegalFixVersion.ToolsIllegalFixVersion.JBIDE-13332_snjeza
Error Message:
https://jira.jboss.org/browse/JBIDE-13332 (last update: 22 days, 10:21:51.551414) ->
Issue have been resolved with an illegal fix version, i.e. an .x version, LATER or no fix
version at all. This means it will not be shown in the right release notes so neither
developers or users can see where things happend. Please adjust the issue so it correctly
states the proper fix version! Thank you! See
http://bit.ly/aTUeGq for how to track down
right fix versions.
Stack Trace:
JBIDE-13332: Update list of quickstarts to be consistent with current
goals(https://jira.jboss.org/browse/JBIDE-13332)
{code}
--
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: