VPC (and QPC?) cannot handle new Adoptium repository names
At present the VagrantPlaybookCheck job's FORK parameters take a username for the infrastructure and build repository forks. It assumes that the repository underneath there will be the origin AdoptOpenJDK names of openjdk-infrastructure and openjdk-build whereas anyone forking from the adoptium repositories will have names of infrastructure and temurin-build instead, this preventing them from executing. We should either:
- Switch to the new names and assume everyone is using them
- Detect which of the two exists and use that
- Change the definition of the
FORKparameter to allow specification of the respository name too e.g.sxa/infrastructure
@Haroon-Khel Is this now complete?
It's complete for the VPC. I haven't yet investigated the damage on the QPC. WIll do soon
Marking this as complete as QPC does not have this problem