FYI, I've reconfigured most of the Bamboo-plans.only committers of a build will get a notification of a broken build and the first success, so there's no notification sent to mojo-dev.I'm already talking with Ben about the unstable builds, but this is a good hint. -Robert Date: Mon, 12 Dec 2011 11:54:18 +0000 From: [email protected] To: [email protected] Subject: [mojo-dev] Re: [Bamboo] MOJO > versions-maven-plugin > #11 has FAILED. Change made by stephenconnolly.
These are failing with Maven 2.x as the local repository contains some Maven 3.x touched metadata (and therefore cannot parse the "new" metadata for -SNAPSHOTs) On 12 December 2011 11:49, Codehaus Bamboo <[email protected]> wrote: MOJO > versions-maven-plugin > #11 has failed. Code has been updated by stephenconnolly. 2/2 jobs failed with 0 failing tests. Failing Jobs Integration Tests (Default Stage) Duration: 11 minutes Tests: 41 passed Logs | Artifacts Unit Tests (Default Stage) Duration: 1 minute Tests: 41 passed Logs | Artifacts Code Changes See full change details stephenconnolly [MVERSIONS-136] property-updates-report contains a typo o Fixed typo (15554) Actions View Online Add Comments Link to JIRA issue Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
