...
Santuario release done (and done again)
Bumped log4slog4shib to fix some modern compiler issues
Most of SP work is done unless I can think of something else to actually deprecate (vs. all the stuff I really want to deprecate)
Tested cpp-linbuild process successfully
IdP odds and ends
Tom
Maven Central :
Looks like we will not publish artifacts to Central due to indemnity clause in ToS :
Priority is to firewall our Nexus instance and host our repo via Apache at :
https://build.shibboleth.net/maven
for backwards compat with our POMs will need to redirect
https://build.shibboleth.net/nexus/content/groups/public
to
https://build.shibboleth.net/maven/releaseshttps://build.shibboleth.net/nexus/content/repositories/snapshots
to
https://build.shibboleth.net/maven/snapshotshttps://build.shibboleth.net/nexus/content/repositories/thirdparty-snapshots
to
https://build.shibboleth.net/maven/thirdparty-snapshotsand remove thirdparty/ when “Rod’s Rules” are in place
As to whether someone else publishes to Central (for us), I think they would need to indemnify us but we do not really exist (as a legal entity).
Looking for confirmation - technical details in the agenda above.Making some progress running Nexus/Jenkins in ECS/Fargate using Docker Compose (which wraps CloudFormation) - is that ok ?
Plan is to use docker-compose.yml as infrastructure-as-code, open to alternatives (awscli, AWS console, Terraform) but this seems simplest / easiest.
Working through IdP browser tests in Jenkins with Jetty 9.4 versions (a) up to 9.4.43 as well as (b) 9.4.44 and up (conditional build step to inject idp-jetty-base version)
...