Community
Participate
Working Groups
No fresh builds here: http://download.eclipse.org/eclipse/downloads/eclipse3x.php nor here: http://download.eclipse.org/eclipse/downloads/ No new tags here: http://git.eclipse.org/c/platform/eclipse.platform.releng.maps.git
we are transitioning to the eclipse.org hardware. PW
(In reply to comment #1) > we are transitioning to the eclipse.org hardware. > > PW Paul is there any ETA? Why did we stop the normal N-builds before having a working solution?
(In reply to comment #2) > > Paul is there any ETA? Why did we stop the normal N-builds before having a > working solution? We lost the normal builds when Kim left (the IBM ones). It was either spend time fixing scripts to continue building within IBM or spend the time fixing the scripts to build on the foundation hardware. PW
(In reply to comment #3) > (In reply to comment #2) > > > > Paul is there any ETA? Why did we stop the normal N-builds before having a > > working solution? > > We lost the normal builds when Kim left (the IBM ones). It was either spend > time fixing scripts to continue building within IBM But they weren't broken, were they? We could have just let them run until something really breaks and not going for I-builds.
(In reply to comment #4) > But they weren't broken, were they? We could have just let them run until > something really breaks and not going for I-builds. They were broken as far as I know. Kim's internal userid was deactivated, and we could no longer use her committer ID to sign or push to the foundation. PW
(In reply to comment #4) > But they weren't broken, were they? We could have just let them run until > something really breaks and not going for I-builds. Yes her IBM account has been deactivated. Also the physical Eclipse build lab at IBM is being dismantled this week. Our office is moving and we do not have a build lab in the new location. The plan all along was to move builds to eclipse.org and we have now run out of time. I'm going to mark as dup of bug 355430 since that is where all relevant progress is being discussed. *** This bug has been marked as a duplicate of bug 355430 ***