At least builds on our HIPP had to download every Maven dependency (Maven plugins & project dependencies) again :Īlso, we are now seeing consistent build failures, which is odd as the requested artifact should be in Central: I'm afraid the switch hasn't be transparent to the HIPPs. Otherwise, let's see how it scale by using it through September and decide whether it worths it after Oxygen.1 (Sept 27). If it happens to cause any trouble, the revert is easy and fast to deploy. It's usually a low usage/vacation period, so any issue won't affect too many projects. I think a good window for testing it at a larger scale is right after M1 (August 11). I'd propose then to replace this global setting:įrom the little testing I made, it seems reliable and very fast. This service has known up and down since its inception in 2015, but it has been rebooted (hopefully for the best) since ( ). While the stability has improved since the migration to a new machine, and while we have ideas how to improve it even more (see bug 500244 comment 12), I think we should try another (cheapest) alternative: use the Google maven central mirror. This also came with the side effect of putting a lot of pressure on as any downtime has the vicious side-effect of failing all (maven based-) builds (search for all bugs about build failing because of being down). At that point, projects were experiencing very slow download speed from maven central and mirroring it locally helped a lot. Some time ago ago (see bug bug 492412 comment 56), has been set up as a maven central mirror globally for all HIPPs.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |