Hi YuLing,

The trick with validate-autorelease jobs is to search for the keyword [FATAL]. This will almost always bring you to the exact problem with the build.

[FATAL] Non-resolvable parent POM: Could not find artifact org.opendaylight.odlparent:odlparent:pom:1.6.0-validate-v201602102102 in opendaylight-mirror (http://nexus.opendaylight.org/content/repositories/public/) and 'parent.relativePath' points at wrong local POM @ line 10, column 11

As you can see it's failing because something is pulling in Beryllium artifacts. There are a few reasons this may occur.

1) Your patch submission includes a pom with incorrect parent configuration

2) You need to rebase your patch

3) Some project merged code ignoring validate-autorelease results and caused this issue

I see that your patch for build #95 is not running into 1, or 2. So I think 3 is the cause. I'll investigate and try to track down which project is breaking us now.

Regards,

Thanh

On 10 February 2016 at 17:20, YuLing Chen <yulingchen54@...> wrote:

Hi Thanh,

We just submitted two patch sets to the master branch and hit tsdr-validate-autorelease build failure. The error messages from the console output were unclear to me... could you help to take a look to see what went wrong?

https://jenkins.opendaylight.org/releng/job/tsdr-validate-autorelease-boron/95/consoleFull

Thanks very much,

YuLing

_______________________________________________
release mailing list
release@...
https://lists.opendaylight.org/mailman/listinfo/release

Hi alto-dev,

One of your recent changes caused validate-autorelease to fail build for all projects. The cause is that this patch [1] which was merged without first being rebased since it was submitted before we branched stable/beryllium so had out of date build results.

I reverted with the patch [2] to resolve this issue and unblock development for all projects. You will need to resubmit your patch from [1] and resolve any build issues.

Regards,

Thanh

[1] https://git.opendaylight.org/gerrit/32048/

[2] https://git.opendaylight.org/gerrit/34429/

On 10 February 2016 at 20:26, Thanh Ha <thanh.ha@...> wrote:

Hi YuLing,

The trick with validate-autorelease jobs is to search for the keyword [FATAL]. This will almost always bring you to the exact problem with the build.

[FATAL] Non-resolvable parent POM: Could not find artifact org.opendaylight.odlparent:odlparent:pom:1.6.0-validate-v201602102102 in opendaylight-mirror (http://nexus.opendaylight.org/content/repositories/public/) and 'parent.relativePath' points at wrong local POM @ line 10, column 11

As you can see it's failing because something is pulling in Beryllium artifacts. There are a few reasons this may occur.

1) Your patch submission includes a pom with incorrect parent configuration

2) You need to rebase your patch

3) Some project merged code ignoring validate-autorelease results and caused this issue

I see that your patch for build #95 is not running into 1, or 2. So I think 3 is the cause. I'll investigate and try to track down which project is breaking us now.

Regards,

Thanh

On 10 February 2016 at 17:20, YuLing Chen <yulingchen54@...> wrote:

Hi Thanh,

We just submitted two patch sets to the master branch and hit tsdr-validate-autorelease build failure. The error messages from the console output were unclear to me... could you help to take a look to see what went wrong?

https://jenkins.opendaylight.org/releng/job/tsdr-validate-autorelease-boron/95/consoleFull

Thanks very much,

YuLing

_______________________________________________
release mailing list
release@...
https://lists.opendaylight.org/mailman/listinfo/release