Replies: 9 comments 4 replies
-
|
@stephan-herrmann @jarthana @srikanth-sankaran @iloveeclipse @noopur2507 @jjohnstn @HannesWell @jukzi @akurtakov others.. flagging to have a faster consensus |
Beta Was this translation helpful? Give feedback.
-
|
All the repos have Jenkinsfiles that were used for verification so from that POV the project should be fine even with new JIPP . |
Beta Was this translation helpful? Give feedback.
-
If the data is OK, we are fine. If not, we are at point 2. anyway. So why not try 1. ? Y builds do not make much sense without working master build and known master state. However, what is more interesting, is platform (SDK) build that is also down. I believe there all jobs were defined in code, so it would be 1. too. => eclipse-platform/eclipse.platform.releng.aggregator#3005 |
Beta Was this translation helpful? Give feedback.
-
|
Option 1 - It makes sense to try the backup first. |
Beta Was this translation helpful? Give feedback.
-
|
Just want to link my response from eclipse-platform/eclipse.platform.releng.aggregator#3005 (comment) I don't know the JDT JIPP in detail, so I cannot say much about it. The only thing I remember is that in the context of #3244 a free-style job was created, which would be lost in case a clean new JIPP is created. |
Beta Was this translation helpful? Give feedback.
-
|
Issue raised at https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5974 |
Beta Was this translation helpful? Give feedback.
-
|
For completeness: we had more than one free-style job (see also several "run.javac" jobs), so restoring from backup will be convenient, thanks. None of those jobs have relevantly complex configuration though, so losing the old config wouldn't be a great loss. Actually, for those jobs where I'm the only one active, I'd appreciate if the strategy remains unchanged, as that's what I'm familiar with (and I don't think we need to see every configuration experiment in our git history). OTOH, if someone wants to step up and take responsibility (who?), then a change of strategy would surely be fine. |
Beta Was this translation helpful? Give feedback.
-
|
FYI: the jdt jenkins is back butPR's can't be built yet because it seems that not all data (or not at all???) is restored on https://repo.eclipse.org/content/repositories/ :-( |
Beta Was this translation helpful? Give feedback.
-
|
SDK build works now, Jenkins too, closing. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Dear JDT Committers (not just JDT.Core),
Hope you have seen the message : https://www.eclipse.org/lists/eclipse.org-committers/msg01496.html. Quoting from the message verbatim :
"
To avoid prolonging the outage any further, we have two options:
"
I am more inclined towards option 1, but however would like to have a discussion here before we raise an helpdesk issue to this effect.
Point to note here is that the last known JDT version is of March 5, 2025.
Opinions/suggestions - welcome.
Regards,
Manoj
Beta Was this translation helpful? Give feedback.
All reactions