This is depending on the OS installation choices, security choices, etc…
failure: repodata/repomd.xml.asc from jenkins: [Errno 256] No more mirrors to try.
https://pkg.jenkins.io/redhat/repodata/repomd.xml.asc: [Errno 14] HTTPS Error 404 - Not Found
Based on how Jenkins is delivering the yum repo these are how the repo files should be delivered:
https://pkg.jenkins.io/redhat-stable/jenkins.repo:
[jenkins-stable]
name=Jenkins-stable
baseurl=https://pkg.jenkins.io/redhat-stable
gpgcheck=1
repo_gpgcheck=0
gpgkey=https://pkg.jenkins.io/redhat-stable/jenkins.io.key
and
https://pkg.jenkins.io/redhat/jenkins.repo:
[jenkins]
name=Jenkins
baseurl=https://pkg.jenkins.io/redhat
gpgcheck=1
repo_gpgcheck=0
gpgkey=https://pkg.jenkins.io/redhat/jenkins.io.key
I highlighted the changed portions. If those are changed accordingly, the problem should be moot.
But having the repo GPG signed is a good thing.
v/r,
Jason Pyeron
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5a8a2b6e-740f-4afb-b9d2-4d0db2e810da%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0a2c01d62f96%240a8e34e0%241faa9ea0%24%40pdinc.us.
Well on systems where both repos exist, there is a conflict in name.
Think of it this way…
Jenkins enabled=0
Jenkins-stable enabled=1
Happily auto updating…..
Oh no, there is an issue – the fix is in Jenkins v.x.y.z, stable is not there yet.
yum –enablerepo=jenkins update
@phew, now we have this bleeding edge fix, when the stable repo has a newer version # it will get upgraded.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGOwr%3Dao5XMcpdjZE-FNV2qg594Ssv9KCrf_Wc6GODQqw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0ad601d62fbc%24792763b0%246b762b10%24%40pdinc.us.
That file is only used when setting up the yum repository the first time. Your change will not change anyone’s file configured in the past. So no your change will not break anyone.
The changes will only be seen by those newly following the instructions at https://pkg.jenkins.io/redhat/ or at https://pkg.jenkins.io/redhat-stable/ .
For that fact, it is important that each repository section has a unique name, without that things could get weird at best or just not work.
v/r,
Jason
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGD3LpkhiPub-1SKYsmSkCWjbVhVFfG%2B1Ttab3nuggA8g%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0aff01d62fc1%2495a54c00%24c0efe400%24%40pdinc.us.