Stop populating/maintaining the third party repo.
Description
Environment
Activity
I believe that my work is done here (for now)…
@Tom Zeller can you do the stuff with the JENKINS agents (settings.xml) and pulling the plug on the external view of nexus (and adding whatever config is needed to get at it from a SSH tunnel) ?
@Tom Zeller Just a heads up.
It is quite safe/expected/good to remove references to the “old” shib-thirdparty repo (the one starting https://build.shibboleth.net/nexus/content/repositories/thirdparty
) from the CI agents,
Also, I am not aware of any reason why nexus needs to be exposed outside the firewall any more - although I think that something needs to be done to make http://127.0.0.1:1583/build
work (it doesn’t, whereas http://127.0.0.1:1583/jenkins
does).
I’ll be assigning this case to you to get this stuff one as soon as I have finished the pom-juggling. But the work doesn’t need to wait for that.
Right. I’ll get that done. It should to be done in tandem with changes to the CI system so I may wait for the weekend to actually push it. I don’t want to wait any later because of pending OpenSSH releases.

Yes, xmlsectool is at the bottom of our list of things that need to stay the way they are. I did change it around to be closer to standard a few months back, and nearly went the whole hog and separated out the distribution stuff.
So, don’t worry about that, I can switch it over fairly quickly if needed (having reworked the MDA already, I have a lot of stuff I can just cut and paste).
I would guess @Ian Young would concur that whatever we have to tweak to get xmlsectool in line is best if we have a model that seems to work reasonable well for everything else. Even just splitting the xmlsectool distribution into a separate module isn’t that hard.
We are tantalizingly close to being able to stop having to maintain this nexus repository (although we need to keep the data).
I said yesterday that we could do it now, but I had forgotten the 4.1 tree. Working needing done is
Add M2 checking to OpenSAML (maint-3.4), Spring Extensions (maint-5) and java support (maint-7). (Rod)
The IdP is done and tested nightly
Remove central-disabled from any CI build (Rod)
At this I would assert that the need for third party population will be done and I will aim to get this done ASAP. There after
Document M2 checking (== -D net.shibboleth.maven.enforcer.rules.checkM2=true) as part of the build (Rod)
Add to the release profile?
Add a different profile?
Remove central-disabled from the (mainline) parent pom (Rod)
Remove access to trusted third party pom in Jenkins Agents (Tom)
Declare victory (All)