[
https://issues.jboss.org/browse/DROOLS-2503?page=com.atlassian.jira.plugi...
]
Geoffrey De Smet updated DROOLS-2503:
-------------------------------------
Description:
-
repository.jboss.org is a load-balancing proxy for the jboss nexus. Nowadays it should
offer much faster reads than the master one and barely slower writes (and we read far more
than we write).
-
origin-repository.jboss.org is the actual nexus master instance, which we must not
contact directly as a good citizen.
Over 2 years ago, someone added a hack to workaround temporary stability issues with
repository.jboss.org that made us go directly to
origin-repository.jboss.org
https://github.com/kiegroup/droolsjbpm-build-bootstrap/blob/master/pom.xm...
That was never rolled back. Replace those 2 lines to use
repository.jboss.org instead and
remove the comment.
Suggested actions::
- Replace those 2 lines to use
repository.jboss.org instead and remove the comment
- Look for the use of
origin-repository.jboss.org in all repo's and change that too.
-- the errai/uberfire/appformer parent pom might use it too
- Delete your local .m2/repository and do a full downstream build.
- Adjust any jenkins jobs (both blessed jobs and PR jobs) that have hard coded
origin-repository.jboss.org somewhere
was:
-
repository.jboss.org is a load-balancing proxy for the jboss nexus. Nowadays it should
offer much faster reads than the master one and barely slower writes (and we read far more
than we write).
-
origin-repository.jboss.org is the actual nexus master instance, which we must not
contact directly as a good citizen.
Over 2 years ago, someone added a hack to workaround temporary stability issues with
repository.jboss.org that made us go directly to
origin-repository.jboss.org
https://github.com/kiegroup/droolsjbpm-build-bootstrap/blob/master/pom.xm...
Replace those 2 lines to use
repository.jboss.org instead and remove the comment
Suggested actions::
- Replace those 2 lines to use
repository.jboss.org instead and remove the comment
- Look for the use of
origin-repository.jboss.org in all repo's and change that too.
-- the errai/uberfire/appformer parent pom might use it too
- Delete your local .m2/repository and do a full downstream build.
- Adjust any jenkins jobs (both blessed jobs and PR jobs) that have hard coded
origin-repository.jboss.org somewhere
Do not use
origin-repository.jboss.org, use
repository.jboss.org
instead in kie-parent pom
------------------------------------------------------------------------------------------
Key: DROOLS-2503
URL:
https://issues.jboss.org/browse/DROOLS-2503
Project: Drools
Issue Type: Task
Components: build
Reporter: Geoffrey De Smet
Assignee: Piotr Szubiakowski
Priority: Blocker
-
repository.jboss.org is a load-balancing proxy for the jboss nexus. Nowadays it should
offer much faster reads than the master one and barely slower writes (and we read far more
than we write).
-
origin-repository.jboss.org is the actual nexus master instance, which we must not
contact directly as a good citizen.
Over 2 years ago, someone added a hack to workaround temporary stability issues with
repository.jboss.org that made us go directly to
origin-repository.jboss.org
https://github.com/kiegroup/droolsjbpm-build-bootstrap/blob/master/pom.xm...
That was never rolled back. Replace those 2 lines to use
repository.jboss.org instead and
remove the comment.
Suggested actions::
- Replace those 2 lines to use
repository.jboss.org instead and remove the comment
- Look for the use of
origin-repository.jboss.org in all repo's and change that too.
-- the errai/uberfire/appformer parent pom might use it too
- Delete your local .m2/repository and do a full downstream build.
- Adjust any jenkins jobs (both blessed jobs and PR jobs) that have hard coded
origin-repository.jboss.org somewhere
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)