On 03/26/2013 06:15 PM, Max Rydahl Andersen wrote:
> new Juno-based 4.22.2 target platform listed in the parent pom
was NOT
> used to run the jobs for 4.0.1.CR1a / 6.0.1.CR1a.
Which jobs was it exactly this was missed in ?
All of them. Templated jobs == global mistakes when important steps like
this are missed. :(
An idea i've had lately is actually that we have tests for the
various
TP changes
to verify the version we think is in there is actually in there. Then it
would
not wait until after the build to be noticed.
Sounds like a reasonable idea, but what would you test? The JBDS
installer content? The build logs? Because only JBDS installers
*include* the TP; the rest simply refer to it (in the logs) when
building and testing. And if it was OK in JBDS installer build but wrong
elsewhere, testing the installer wouldn't conclusively prove that you
also built the projects or the JBT aggregate using the correct TP
version(s).
That's a mailing list. Did you mean a new JIRA?
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com