SRE-2772 ci: get rid of Intel reference #471
Conversation
grom72
changed the title
|
Test stage provisionNodes on EL 9 with master Repo completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/pipeline-lib/job/PR-471/1/display/redirect |
|
Test stage provisionNodes on EL 8 with slurm completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/pipeline-lib/job/PR-471/1/display/redirect |
|
Test stage provisionNodes on Leap 15 with slurm completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/pipeline-lib/job/PR-471/1/display/redirect |
|
Test stage provisionNodes on EL 9 with master Repo completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/pipeline-lib/job/PR-471/2/display/redirect |
|
Test stage provisionNodes on EL 8 with slurm completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/pipeline-lib/job/PR-471/2/display/redirect |
|
Test stage provisionNodes on Leap 15 with slurm completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/pipeline-lib/job/PR-471/2/display/redirect |
Get rid of the tight connection to the hpdd.intel.com artifactory. Instead, use an HPE address Signed-off-by: Tomasz Gromadzki <[email protected]>
Signed-off-by: Tomasz Gromadzki <[email protected]>
Signed-off-by: Tomasz Gromadzki <[email protected]>
osalyk
force-pushed
the
grom72/sre-2772-get-rid-of-intel-reference
branch
from
0fcb789 to
76ca25e
Compare
There was a problem hiding this comment.
I think we will want to refactor this in the future to make it more neutral and disable some features of the build if the site specific repos are not known.
Nothing should be using provisionNodesV1 any more.
The e-mails that got sent in error were due to a couple of bugs in Jenkins that should be fixed now.
SRE-2772 ci: get rid of link to any Intel specific services/addresses like Jenkins or artifactory or emails
Instead, use an HPE address