Our builds are failing with a new kind of error that is absolutely crazy-making. It seems that our builds can no longer access the p2 repository of the latest successful Papyrus-Neon-Developer
build, although they can access the latest successful Papyrus-Neon and Papyrus-Neon-Extra builds without trouble.
So, as you can see, the build thinks it can’t get the metadata for the developer build. However, I have no trouble from my computer using the same URL to access that repository,
and it like it has all the same metadata files as the repositories that the build can access. The p2.index files, in particular, are identical.
Any ideas? I re-started the Papyrus-RT HIPP instance, but that didn’t help. Does the server machine that hosts our HIPP need to be restarted? Thinking maybe something is
borked in the networking stack.
The only meaningful difference that I can think of between these Papyrus build repositories is that we actually get the Papyrus-Neon and Papyrus-Neon-Extra builds by re-direction
through a composite repository on the build server that is specified by a file-scheme URL. Our TPs reference the developer build by an http-scheme URL directly to the Hudson job because Papyrus doesn’t publish the developer builds on the download server.
But, in the end, it’s all HTTP anyways.
This will cause all of our builds, both the Gerrit and the production builds, to fail until it is resolved.