Hi Mike,

This seems the common problem of the repositories.
https://repository.jboss.org and https://origin-repository.jboss.org.
Whereas you don't have the version of org.codehaus.jettison:jettison:1.3.5-SNAPSHOT" in https://repository.jboss.org/nexus/content/groups/public/org/codehaus/jettison/jettison/ [there is only 1.4.0-SNAPSHOT]
you have it in https://origin-repository.jboss.org/nexus/content/groups/public/org/codehaus/jettison/jettison/.

We are asked to NOT use the origin-repositoriesjboss.org rather the repositories.jboss.org that should be a mirror of the origins.
I don't know why this happens. It was fixed X times but somehow it raises again.

I only looked this dependency, but I assume for all others it is the same issue.

I put David Lhaky in CC since he fixed this once for us.

Michael

On Mon, Jul 1, 2019 at 11:33 AM Michael Anstis <manstis@redhat.com> wrote:
Michael,

I've added another commit to Daniele's PR for appformer and this appears to make it green locally (Jenkins has been retriggered too).

However looking at kie-wb-common, I get this error:

[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 13.42 s <<< FAILURE! - in org.kie.workbench.common.screens.server.management.backend.StandaloneControllerMultinodeIT
[ERROR] org.kie.workbench.common.screens.server.management.backend.StandaloneControllerMultinodeIT Time elapsed: 13.419 s <<< ERROR!
java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive org.kie.workbench.common.screens.server.management.backend.StandaloneControllerMultinodeIT.createWorkbenchWarDeployment()
at org.kie.workbench.common.screens.server.management.backend.StandaloneControllerMultinodeIT.createWorkbenchWarDeployment(StandaloneControllerMultinodeIT.java:80)
Caused by: org.eclipse.aether.resolution.DependencyResolutionException: The following artifacts could not be resolved: org.codehaus.jettison:jettison:jar:1.3.8, javax.mail:mail:jar:1.4.5, mysql:mysql-connector-java:jar:5.1.47, jaxen:jaxen:jar:1.1.6, xml-resolver:xml-resolver:jar:1.2: Cannot access jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) in offline mode and the artifact org.codehaus.jettison:jettison:jar:1.3.8 has not been downloaded from it before.
at org.kie.workbench.common.screens.server.management.backend.StandaloneControllerMultinodeIT.createWorkbenchWarDeployment(StandaloneControllerMultinodeIT.java:80)
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: The following artifacts could not be resolved: org.codehaus.jettison:jettison:jar:1.3.8, javax.mail:mail:jar:1.4.5, mysql:mysql-connector-java:jar:5.1.47, jaxen:jaxen:jar:1.1.6, xml-resolver:xml-resolver:jar:1.2: Cannot access jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) in offline mode and the artifact org.codehaus.jettison:jettison:jar:1.3.8 has not been downloaded from it before.
at org.kie.workbench.common.screens.server.management.backend.StandaloneControllerMultinodeIT.createWorkbenchWarDeployment(StandaloneControllerMultinodeIT.java:80)
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Cannot access jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) in offline mode and the artifact org.codehaus.jettison:jettison:jar:1.3.8 has not been downloaded from it before.
at org.kie.workbench.common.screens.server.management.backend.StandaloneControllerMultinodeIT.createWorkbenchWarDeployment(StandaloneControllerMultinodeIT.java:80)
Caused by: org.eclipse.aether.transfer.RepositoryOfflineException: Cannot access jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) in offline mode
at org.kie.workbench.common.screens.server.management.backend.StandaloneControllerMultinodeIT.createWorkbenchWarDeployment(StandaloneControllerMultinodeIT.java:80)

It appears that some dependencies can no longer be resolved.

Do I need additional repositories configured in my Maven settings.xml to build following your changes?!

With kind regards,

Mike

On Fri, Jun 28, 2019 at 7:14 PM Gonzalo Munoz Fernandez <gmunozfe@redhat.com> wrote:
Hi Michael,

5 failing tests for jBPM (those related to XES module) are due to Apache commons-cli version. At least, 1.4 is needed here, but it's taken 1.3.1.

In the jbpm-xes module pom, it has this property to overwrite it
<version.commons-cli>1.4</version.commons-cli>

but it must have been changed in the parent ip bom.

Regards,
Gonzalo

On Fri, Jun 28, 2019 at 4:32 PM Michael Biarnes Kiefer <mbiarnes@redhat.com> wrote:
Hi,

Before merging all PRs related to the replacement of jboss-ip-bom I wanted you to know
the all reps not listed here are green.
The repos that build successful but tests failed are:

appformer ..:
appformer-pullrequest - UNSTABLE (build successful but https://rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/KIE/job/master/job/pullrequest/job/appformer-pullrequests/24/
9 failed test and 7 spotbug warnings)
appformer-compile downstream build failed because of drools-wb failure (this is soved)

droolsjbpm-knowledge ..:
droolsjbpm-knowledge-pullrequest - OK
droolsjbpm-knowledge-downstream build failed because of drools-wb failure (this is fixed)

jbpm ..:
jbpm-pullrequest - UNSTABLE (build successful but 10 test failures https://rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/KIE/job/master/job/pullrequest/job/jbpm-pullrequests/22 )

kie-wb-common ..:
kie-wb-common-pullrequest - UNSTABLE (build successful but 125 test failures https://rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/KIE/job/master/job/pullrequest/job/kie-wb-common-pullrequests/225/testReport/ )

drools-wb ..:
drools-wb-pullrequest - UNSTABLE (build successful but 41 test failures https://rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/KIE/job/master/job/pullrequest/job/drools-wb-pullrequests/75/testReport )

optaplanner-wb ..:
optaplanner-wb-pullrequest - UNSTABLE (build successful but 6 test failures https://rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/KIE/job/master/job/pullrequest/job/optaplanner-wb-pullrequests/11/testReport )

The only strange behaviour I get is in drools.
drools ..:
drools-pullrequest OK
drools-compile-downstream-build : failed because of downstream drools-wb itself - not as downstream repository it built

drools and optaplanner-employee-rostering is executing right now and I suppose there will not be any failures.

Here my proposals:
1. For saving time and finish with this task I would merge all PRs.
Looking at the failures I would say the reps will build but a bunch of tests will fail that we have to fix later on.
The master branch has to be stabilized.

2. The other option would be to fix the tests right now and to repeat the builds until they're green.
But until then there can't be any "merges" to the master branch, otherwise we dive into a never ending story.

–
Michael Biarnés Kiefer
Release Engineer
EMEA ENG Product-Middleware
Red Hat SL Barcelona Spain

–
Michael Anstis
Principal Software Engineer
Red Hat

–
Michael Biarnés Kiefer
Release Engineer
EMEA ENG Product-Middleware
Red Hat SL Barcelona Spain