Re: [cross-project-issues-dev] Some LocationTech builds failing after repo.locationtech.org maintenance
This is a repo.locationrech.org <http://repo.locationrech.org/> specific issue. I'm looking into it. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 2 oct. 2019 à 22:50, Jim Hughes a écrit : > > Hi all, > > The recent maintenance has caused the LocationTech GeoMesa and LocationTech > SFCurve builds to fail. Some other builds (e.g. JTS) are still using > repo.locationtech.org properly. I entered a bug yesterday > (https://bugs.eclipse.org/bugs/show_bug.cgi?id=551682). > > The issues started immediately after the maintenance on > repo.locationtech.org. Are any other builds having issues after the > maintenance? > > Cheers, > > Jim > > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Nexus (repo.eclipse.org and repo.locationtech.org) maintenance
> repo.locationtech.org <http://repo.locationtech.org/> will be moved to a new > host on Fri. 09/27 @ 10am CEST (4am EDT). It should be unavailable for less > than 2 hours. Done. repo.locationtech.org <http://repo.locationtech.org/> will slowly be available again as soon as the new DNS propagates. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Nexus (repo.eclipse.org and repo.locationtech.org) maintenance
Both upgrades successfully completed. repo.locationtech.org <http://repo.locationtech.org/> was offline for less than 5min and repo.eclipse.org <http://repo.eclipse.org/> was offline for about 15min. Thanks. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 24 sept. 2019 à 17:48, Mikaël Barbero > a écrit : > > Hi, > > We will have to perform some maintenance on repo.eclipse.org > <http://repo.eclipse.org/> and repo.locationtech.org > <http://repo.locationtech.org/> which may affect their availability and as > such disturb some build jobs. > > repo.locationtech.org <http://repo.locationtech.org/> will be updated to > latest version tomorrow Wed. 09/25 @ 11am CEST (5am EDT). If all goes well, > it should be unavailable for less than 1 hour. > > repo.eclipse.org <http://repo.eclipse.org/> will also be updated to latest > version tomorrow Wed. 09/25 @ 12am CEST (6am EDT). It should be equally > unavailable for less than 1 hour. > > repo.locationtech.org <http://repo.locationtech.org/> will be moved to a new > host on Fri. 09/27 @ 10am CEST (4am EDT). It should be unavailable for less > than 2 hours. > > Thanks for your patience during these maintenance windows. > > Cheers, > > Mikaël Barbero > Team Lead - Release Engineering | Eclipse Foundation > 📱 (+33) 642 028 039 | 🐦 @mikbarbero > Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open > Innovation and Collaboration > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Nexus (repo.eclipse.org and repo.locationtech.org) maintenance
Hi, We will have to perform some maintenance on repo.eclipse.org <http://repo.eclipse.org/> and repo.locationtech.org <http://repo.locationtech.org/> which may affect their availability and as such disturb some build jobs. repo.locationtech.org <http://repo.locationtech.org/> will be updated to latest version tomorrow Wed. 09/25 @ 11am CEST (5am EDT). If all goes well, it should be unavailable for less than 1 hour. repo.eclipse.org <http://repo.eclipse.org/> will also be updated to latest version tomorrow Wed. 09/25 @ 12am CEST (6am EDT). It should be equally unavailable for less than 1 hour. repo.locationtech.org <http://repo.locationtech.org/> will be moved to a new host on Fri. 09/27 @ 10am CEST (4am EDT). It should be unavailable for less than 2 hours. Thanks for your patience during these maintenance windows. Cheers, Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] EPL 2.0.0 Licence
2.0.0 (and 2.0.1) have been removed as per https://bugs.eclipse.org/bugs/show_bug.cgi?id=537927 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=537927>. Note that the license feature version does not reflect the license version per se. It's still EPL 2.0. Good catch with the composite* children sizes. I've fixed the entries. Cheers, Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 2 sept. 2019 à 18:08, DEVILLE Pauline a écrit : > > Hello, > > We just seen that the epl licence 2.0.0 is not reachable anymore via > http://download.eclipse.org/cbi/updates/license/ > <http://download.eclipse.org/cbi/updates/license/>. Is it in the goal that > everyone point on epl licence version 2.0.2 ? > > By the way, we where looking for what was wrong in our job about licencing > and we noticed that the CompositeArtifacts.xml and CompositeContent.xml seems > strange since the children size is 4 but there is only 3 children (see [1]). > > Best Regards, > Pauline > > 1: > > > > > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > <mailto:cross-project-issues-dev@eclipse.org> > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev > <https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev> signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] SimRel 2019-09 Repository Quality
Fully agree with Mickael here. Ed, what about bringing this topic to the next planning council call? We can then define the list of checks that should fail a build (I guess we should come up with a list extracted from https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#Required_Bundle_forms_and_formats <https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#Required_Bundle_forms_and_formats> and what your report support as of today)? Let's discuss the technical details on your ticket https://bugs.eclipse.org/bugs/show_bug.cgi?id=550361 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=550361> Thanks for your help in making p2 repos better! Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 2 sept. 2019 à 10:52, Mickael Istria a écrit : > > On Mon, Sep 2, 2019 at 10:44 AM Ed Merks <mailto:ed.me...@gmail.com>> wrote: > But whose builds will fail? > > The whole SimRel build fails for everyone. It's not really a matter of > pointing fingers to who should do what, it's more a matter of enforcing a > quality gate for the project delivery. > And then, if this quality gate is not reached, we see the build failing, it > annoys everyone and we can either fix the necessary parts, or threaten them > of removal from SimRel unless they get fixed promptly. > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Mac signing: service outage
Hi, The macOS signing service is back online. Thanks everyone for your patience. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 23 août 2019 à 20:18, Matthew Ward a > écrit : > > Hello, > > I just wanted to let everyone know that we have experienced a failure in > the mac signing service. We are working to restore it, but have had to > reach out to Apple for assistance. > > At this time I expect us to have things operational again by EOD Monday Aug > 26th. Should we be able to restore it sooner we will do so. > > If you have any questions please let me know. > > -Matt. > > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Gerrit Jenkins Builds fail with "access denied"
The referenced build is from August 2nd when we effectively faced an issue (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=549741 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=549741>). It has been resolved since then and new gerrit triggered build are not facing this issue anymore. Thanks. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 5 août 2019 à 07:56, Becker, Matthias a écrit : > > Dear all, > > since yesterday gerrit builds > e.g.https://ci.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/19426/console > > <https://ci.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/19426/console>fail > with: > > 15:24:36 Fetching upstream changes from > git://git.eclipse.org/gitroot/platform/eclipse.platform.ui.git > > 15:24:36 > /usr/local/bin/git --version # timeout=10 > 15:24:36 > /usr/local/bin/git fetch --tags --progress > git://git.eclipse.org/gitroot/platform/eclipse.platform.ui.git > +refs/heads/*:refs/remotes/origin/* > 15:24:36 ERROR: Error cloning remote repo 'origin' > 15:24:36 hudson.plugins.git.GitException: Command "/usr/local/bin/git fetch > --tags --progress > git://git.eclipse.org/gitroot/platform/eclipse.platform.ui.git > +refs/heads/*:refs/remotes/origin/*" > returned status code 128: > 15:24:36 stdout: > 15:24:36 stderr: fatal: remote error: access denied or repository not > exported: /gitroot/platform/eclipse.platform.ui.git > > What’s going on here? > > Regards, > Matthias > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > <mailto:cross-project-issues-dev@eclipse.org> > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev > <https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev> signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] HIPP6 is down
HIPP6 is now operating normally. Thanks. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 2 août 2019 à 18:33, Mikaël Barbero > a écrit : > > All JIPPs have been restarted. We're still monitoring closely hipp6 to see if > the cleanup we've made will be enough. > > Thanks again for your patience. > > Mikaël Barbero > Team Lead - Release Engineering | Eclipse Foundation > 📱 (+33) 642 028 039 | 🐦 @mikbarbero > Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open > Innovation and Collaboration > >> Le 2 août 2019 à 11:38, Mikaël Barbero >> > <mailto:mikael.barb...@eclipse-foundation.org>> a écrit : >> >> We're still troubleshooting the issue. We're trying to mitigate the >> inconvenience as much and as fast as we can. >> >> Good news is that some JIPPs have been restored and they look healthy. >> >> Follow ticket https://bugs.eclipse.org/bugs/show_bug.cgi?id=549714 >> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=549714> for latest update. >> >> Thanks for your patience. >> >> Mikaël Barbero >> Team Lead - Release Engineering | Eclipse Foundation >> 📱 (+33) 642 028 039 | 🐦 @mikbarbero >> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open >> Innovation and Collaboration >> >>> Le 1 août 2019 à 19:40, Mikaël Barbero >>> >> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit : >>> >>> Hi, >>> >>> We're again facing an outage with HIPP6. All JIPPs on the machine are >>> affected. We're investigating. >>> >>> If you want to track the issue, here is the ticket >>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=549714 >>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=549714> >>> >>> Thanks. >>> >>> Mikaël Barbero >>> Team Lead - Release Engineering | Eclipse Foundation >>> 📱 (+33) 642 028 039 | 🐦 @mikbarbero >>> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open >>> Innovation and Collaboration >>> >> > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] HIPP6 is down
All JIPPs have been restarted. We're still monitoring closely hipp6 to see if the cleanup we've made will be enough. Thanks again for your patience. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 2 août 2019 à 11:38, Mikaël Barbero > a écrit : > > We're still troubleshooting the issue. We're trying to mitigate the > inconvenience as much and as fast as we can. > > Good news is that some JIPPs have been restored and they look healthy. > > Follow ticket https://bugs.eclipse.org/bugs/show_bug.cgi?id=549714 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=549714> for latest update. > > Thanks for your patience. > > Mikaël Barbero > Team Lead - Release Engineering | Eclipse Foundation > 📱 (+33) 642 028 039 | 🐦 @mikbarbero > Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open > Innovation and Collaboration > >> Le 1 août 2019 à 19:40, Mikaël Barbero >> > <mailto:mikael.barb...@eclipse-foundation.org>> a écrit : >> >> Hi, >> >> We're again facing an outage with HIPP6. All JIPPs on the machine are >> affected. We're investigating. >> >> If you want to track the issue, here is the ticket >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=549714 >> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=549714> >> >> Thanks. >> >> Mikaël Barbero >> Team Lead - Release Engineering | Eclipse Foundation >> 📱 (+33) 642 028 039 | 🐦 @mikbarbero >> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open >> Innovation and Collaboration >> > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] HIPP6 is down
We're still troubleshooting the issue. We're trying to mitigate the inconvenience as much and as fast as we can. Good news is that some JIPPs have been restored and they look healthy. Follow ticket https://bugs.eclipse.org/bugs/show_bug.cgi?id=549714 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=549714> for latest update. Thanks for your patience. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 1 août 2019 à 19:40, Mikaël Barbero > a écrit : > > Hi, > > We're again facing an outage with HIPP6. All JIPPs on the machine are > affected. We're investigating. > > If you want to track the issue, here is the ticket > https://bugs.eclipse.org/bugs/show_bug.cgi?id=549714 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=549714> > > Thanks. > > Mikaël Barbero > Team Lead - Release Engineering | Eclipse Foundation > 📱 (+33) 642 028 039 | 🐦 @mikbarbero > Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open > Innovation and Collaboration > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] HIPP6 is down
Hi, We're again facing an outage with HIPP6. All JIPPs on the machine are affected. We're investigating. If you want to track the issue, here is the ticket https://bugs.eclipse.org/bugs/show_bug.cgi?id=549714 Thanks. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] HIPP6 machine is down
Hi, We're experiencing an outage on the HIPP6 machine. All Jenkins instances running on it are affected (see list below). Usually, the team in EU is able to restart those machines via hardware management interface, but this interface is not responding either. So we will have to wait for Ottawa to wake up to fix the issue. Thanks for your patience. Affected JIPP: datatools ditto ecoretools emf emfstore geogig geomesa jdt leshan libims mpc nebula oomph opencert openj9 proj4j scout unide virgo xpect xsemantics Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Bugzilla down
Thanks for the heads up. We are already working on it. Cheers, Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 22 juil. 2019 à 11:41, Laurent Goubet a écrit : > > Hi, > > We cannot connect to the bugzilla at https://bugs.eclipse.org/bugs/ > <https://bugs.eclipse.org/bugs/> (long waiting time ultimately leading to > 404), trying to access https://www.eclipse.org/ <https://www.eclipse.org/> > ends up in error 502, and we're getting errors from builds looking like some > of the connections to download.eclipse.org get dropped as well. Anyone else > encountering this issue? > > Regards, > > -- > Laurent Goubet > CONSULTANT > +33 2 51 13 51 42 > > <https://www.obeo.fr/> > 7 Boulevard Ampère - Carquefou - France > obeo.fr <https://www.obeo.fr/> | twitter <https://twitter.com/obeo_corp> | > linkedin > <https://www.linkedin.com/company/obeo>___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Staging for SimRel 2019-06 Release Candidate 1 (RC1) is complete
Hi, The staging repository for 2019-06 RC1 is complete and ready for EPP. To confirm that everything works as expected, please test => http://download.eclipse.org/staging/2019-06/ <http://download.eclipse.org/staging/2019-06/> This will become the official "RC1 Simultaneous Milestone" on Friday. => http://download.eclipse.org/releases/2019-06/ <http://download.eclipse.org/releases/2019-06/> Thanks for all contributions. Please remember to test early and often! Regards, Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Please enable simrel aggregation gerrit jobs
Done. Thanks for the reminder. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 3 juin 2019 à 04:55, Sravan K Lakkimsetti a > écrit : > > Hi, > > Simrel aggregation gerrit validation jobs are disabled. Can you please enable > them We would like to contribute to RC1. We already created a gerrit patch > https://git.eclipse.org/r/#/c/143105/ <https://git.eclipse.org/r/#/c/143105/> > we are waiting for verified +1 from the gerrit job. > > Thanks and Regards, > Sravan > > Sravan Kumar Lakkimsetti > IBM India Pvt Ltd, > Embassy Golf Links Business Park, D Block, > Off Indiranagar-Kormangla Inner Ring Road, > Bangalore - 560071, India > Phone: 91-80-41776858 signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] SimRel 2019-06 Milestone 3 (M3) is available
Hi, The 2019-06 M3 update repository is now available from: => http://download.eclipse.org/releases/2019-06/ <http://download.eclipse.org/releases/2019-06/> The M3 EPP packages will be available soon: => https://www.eclipse.org/downloads/packages/release/2019-06/m3 <https://www.eclipse.org/downloads/packages/release/2019-06/m3> Thank you all for your contributions. Cheers, Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Staging for SimRel 2019-06 Milestone 3 (M3) is complete
Hi, The staging repository for 2019-06 M3 is complete and ready for EPP. To confirm that everything works as expected, please test => http://download.eclipse.org/staging/2019-06/ This will become the official "M3 Simultaneous Milestone" on Friday. => http://download.eclipse.org/releases/2019-06/ Thanks for all contributions. Please remember to test early and often! Regards, Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Late contribution to SimRel 2019-06 M3 due to conflict
Hi, The contribution has been merged and integrated into final staging for M3. Thanks. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 30 mai 2019 à 09:53, Ondrej Dockal a écrit : > > Hi, > > I would like to proceed now with merging RedDeer contribution for > org.eclipse.simrel.build [1], I am curious if it is late or not, so please > give an green/red if I can merge the commit now. > > We had conflicting dependency for org.apache.lucene in bundle > org.eclipse.datatools.sqltools [2], I have already patched everything and it > seems to be good to go now. > > Regards, > > Ondrej Dockal > > RedDeer project lead > > [1]: https://git.eclipse.org/r/#/c/143046/ > <https://git.eclipse.org/r/#/c/143046/> > [2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=547771 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=547771>___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Staging for SimRel 2019-06 Milestone 1 (M1) is complete
Hi, The staging repository for 2019-06 M1 is complete and ready for EPP. To confirm that everything works as expected, please test => http://download.eclipse.org/staging/2019-06/ <http://download.eclipse.org/staging/2019-06/> This will become the official "M1 Simultaneous Milestone" on Friday. => http://download.eclipse.org/releases/2019-06/ <http://download.eclipse.org/releases/2019-06/> Thanks for all contributions. Please remember to test early and often! Cheers,, Mikael Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Initialization for 2019-06
Hi Wim, > what about also creating an ../updates/latest, ../orbit/latest and > ../packages/latest This is ultimately the responsibility of their dedicated projects: respectively platform, orbit and EPP. Cheers, Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] JDK12 GA available on CI instances
JDK12 has been installed on CI instances. Latest symlinks that used to point at EA have been updated accordingly For details, see https://wiki.eclipse.org/Jenkins#JDK <https://wiki.eclipse.org/Jenkins#JDK> (for new infra) and https://wiki.eclipse.org/Jenkins#Tools_.28and_locations.29 <https://wiki.eclipse.org/Jenkins#Tools_.28and_locations.29> (for old infra). If you don't see it available on your JIPP, feel free to open a ticket to ask for it to be added. Thanks. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] URGENT!! Re: The Eclipse IDE 2019-03 release is available now!
It has been fixed. Denis said: "Our bandwidth controller was struck with lower bandwidth". Thanks. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 21 mars 2019 à 09:39, Mikaël Barbero > a écrit : > > There seem to be something wonky since yesterday https://status.eclipse.org > <https://status.eclipse.org/>, even though download server sends bits > continuously https://accounts.eclipse.org/committertools/infra-status > <https://accounts.eclipse.org/committertools/infra-status> > > We're having a look. > > Thanks for your patience. > > Mikaël Barbero > Team Lead - Release Engineering | Eclipse Foundation > 📱 (+33) 642 028 039 | 🐦 @mikbarbero > Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open > Innovation and Collaboration > >> Le 21 mars 2019 à 09:03, Daniel Megert > <mailto:daniel_meg...@ch.ibm.com>> a écrit : >> >> Either the download servers are overwhelmed by all the folks who eagerly >> want to get 2019-03 or there's an infrastructure issue. Our Jenkins jobs >> failed not being able to fetch things, and currently I am unable to download >> our latest build. >> >> cc'ed webmaster >> >> Dani >> >> >> >> From:Ed Merks mailto:ed.me...@gmail.com>> >> To:cross-project-issues-dev@eclipse.org >> <mailto:cross-project-issues-dev@eclipse.org> >> Date:21.03.2019 07:43 >> Subject:Re: [cross-project-issues-dev] URGENT!! Re: The Eclipse IDE >> 2019-03 release is available now! >> Sent by:cross-project-issues-dev-boun...@eclipse.org >> <mailto:cross-project-issues-dev-boun...@eclipse.org> >> >> >> >> Christian, >> If I try to regenerate the product catalog with a clean cache (so that >> failures don't just use old cached information), I get the sea of failures >> below. So my conclusion is that the server is currently not able to serve >> repository metadata. I don't see that fact on the following stats page >> though: >> https://accounts.eclipse.org/committertools/infra-status >> <https://accounts.eclipse.org/committertools/infra-status> >> org.eclipse.equinox.p2.core.ProvisionException: No repository found at >> http://download.eclipse.org/releases/2019-03 >> <http://download.eclipse.org/releases/2019-03>. >> at >> org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:398) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:498) >> at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:117) >> at >> org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.fail(CachingRepositoryManager.java:353) >> at >> org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:244) >> at >> org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:476) >> at >> org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:110) >> at >> org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:105) >> at >> org.eclipse.oomph.setup.internal.installer.ProductCatalogGenerator.loadLatestRepository(ProductCatalogGenerator.java:902) >> at >> org.eclipse.oomph.setup.internal.installer.ProductCatalogGenerator.generate(ProductCatalogGenerator.java:629) >> at >> org.eclipse.oomph.setup.internal.installer.ProductCatalogGenerator.access$1(ProductCatalogGenerator.java:573) >> at >> org.eclipse.oomph.setup.internal.installer.ProductCatalogGenerator$RepositoryLoader$LoadJob.perform(ProductCatalogGenerator.java:1911) >> at org.eclipse.oomph.util.WorkerPool$Worker.run(WorkerPool.java:428) >> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) >> org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at >> http://download.eclipse.org/technology/epp/packages/kepler/content.jar >> <http://download.e
Re: [cross-project-issues-dev] URGENT!! Re: The Eclipse IDE 2019-03 release is available now!
There seem to be something wonky since yesterday https://status.eclipse.org <https://status.eclipse.org/>, even though download server sends bits continuously https://accounts.eclipse.org/committertools/infra-status <https://accounts.eclipse.org/committertools/infra-status> We're having a look. Thanks for your patience. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 21 mars 2019 à 09:03, Daniel Megert a écrit : > > Either the download servers are overwhelmed by all the folks who eagerly want > to get 2019-03 or there's an infrastructure issue. Our Jenkins jobs failed > not being able to fetch things, and currently I am unable to download our > latest build. > > cc'ed webmaster > > Dani > > > > From:Ed Merks > To:cross-project-issues-dev@eclipse.org > Date:21.03.2019 07:43 > Subject:Re: [cross-project-issues-dev] URGENT!! Re: The Eclipse IDE > 2019-03 release is available now! > Sent by:cross-project-issues-dev-boun...@eclipse.org > > > > Christian, > If I try to regenerate the product catalog with a clean cache (so that > failures don't just use old cached information), I get the sea of failures > below. So my conclusion is that the server is currently not able to serve > repository metadata. I don't see that fact on the following stats page though: > https://accounts.eclipse.org/committertools/infra-status > <https://accounts.eclipse.org/committertools/infra-status> > org.eclipse.equinox.p2.core.ProvisionException: No repository found at > http://download.eclipse.org/releases/2019-03 > <http://download.eclipse.org/releases/2019-03>. > at > org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:398) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:117) > at > org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.fail(CachingRepositoryManager.java:353) > at > org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:244) > at > org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:476) > at > org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:110) > at > org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:105) > at > org.eclipse.oomph.setup.internal.installer.ProductCatalogGenerator.loadLatestRepository(ProductCatalogGenerator.java:902) > at > org.eclipse.oomph.setup.internal.installer.ProductCatalogGenerator.generate(ProductCatalogGenerator.java:629) > at > org.eclipse.oomph.setup.internal.installer.ProductCatalogGenerator.access$1(ProductCatalogGenerator.java:573) > at > org.eclipse.oomph.setup.internal.installer.ProductCatalogGenerator$RepositoryLoader$LoadJob.perform(ProductCatalogGenerator.java:1911) > at org.eclipse.oomph.util.WorkerPool$Worker.run(WorkerPool.java:428) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at > http://download.eclipse.org/technology/epp/packages/kepler/content.jar > <http://download.eclipse.org/technology/epp/packages/kepler/content.jar>. > at > org.eclipse.equinox.internal.p2.repository.CacheManager.updateCache(CacheManager.java:431) > at > org.eclipse.equinox.internal.p2.repository.CacheManager.createCache(CacheManager.java:262) > at > org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.getLocalFile(SimpleMetadataRepositoryFactory.java:69) > at > org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.load(SimpleMetadataRepositoryFactory.java:89) > at > org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:63) > at > org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:770) > at sun.reflect.NativeMeth
[cross-project-issues-dev] Hugo (gohugio.io) latest version update
Hi, I just installed v0.54.0 in /shared/common/hugo/0.54.0. /shared/common/hugo/latest still points to /shared/common/hugo/0.37.1 I will update the symlink in 2 weeks (on March 19th). Thanks. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] SimRel 2019-03 Milestone 3 (M3) is available
Hi, The 2019-03 M3 update repository is now available (since last Friday actually) from: => http://download.eclipse.org/releases/2019-03/ <http://download.eclipse.org/releases/2019-03/> The EPP Packages will be available soon: => https://www.eclipse.org/downloads/packages/release/2019-03/m3 <https://www.eclipse.org/downloads/packages/release/2019-03/m3> Thanks everyone for participating! Regards, Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Maintenance on the build infrastructure
All instances have been updated to latest and greatest Jenkins version. Thanks for your patience. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 21 févr. 2019 à 11:28, Mikaël Barbero > a écrit : > > Hi, > > We need to do some maintenance on the build infrastructure and all Jenkins > instances will eventually need to be restarted. > > You may see your instance being set in quiet mode at some point (no more job > will started in this mode until next restart) or just unavailable during the > restart. > > We expect all of the maintenance work to be completed by tomorrow CET > afternoon. We will keep you posted when we're done. > > Thanks. > > Mikaël Barbero > Team Lead - Release Engineering | Eclipse Foundation > 📱 (+33) 642 028 039 | 🐦 @mikbarbero > Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open > Innovation and Collaboration > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Maintenance on the build infrastructure
Hi, We need to do some maintenance on the build infrastructure and all Jenkins instances will eventually need to be restarted. You may see your instance being set in quiet mode at some point (no more job will started in this mode until next restart) or just unavailable during the restart. We expect all of the maintenance work to be completed by tomorrow CET afternoon. We will keep you posted when we're done. Thanks. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] An update about Jenkins/JIPP infrastructure migration
Hi, Last summer, we announced that we were setting up a new infrastructure for CI instances. This infrastructure is still based on Jenkins but going forward will run on a cluster powered by RedHat OpenShift Container Platform (Kubernetes). We’re happy to announce that we are now ready to start the migration of existing Jenkins instances. The first instance to be migrated will be the CBI one <https://ci.eclipse.org/cbi> and it will happen in the next couple of days. We will also start reaching out to projects to announce, when the migration will happen. Don’t call us, we will call you, very soon. :) We don’t expect much disruption, and most projects will only need to change minor things in their build settings. You can track the global effort with the top level ticket #544221 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=544221> on Bugzilla. We have setup a Migration FAQ <https://wiki.eclipse.org/CBI/Jenkins_Migration_FAQ> on the Eclipse wiki. We will shortly publish a blog posts serie <https://blogs.eclipse.org/> that will provide more insights into what projects can expect from the new infrastructure, how we ended with today's technological stack, and into the technical details of the implementation. Feel free to let us know if you have any concerns or questions in the meantime. Cheers, Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] git.eclipse.org access blocked
It works for me. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 7 janv. 2019 à 09:08, Andrey Loskutov a écrit : > > Looks like git.eclipse.org access is blocked. > > Not sure if I'm only one who is unable to access git.eclipse.org, in case > anyone else has troubles, here is the bug: > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=543207 > > > Kind regards, > Andrey Loskutov > > Спасение утопающих - дело рук самих утопающих > > http://google.com/+AndreyLoskutov > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Bugzilla failing to send emails
No, they are lost unfortunately. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 14 déc. 2018 à 09:47, Ed Willink a écrit : > > Hi > > Can the missing Bugzilla notifications be (re-)sent please? > > Regards > > Ed Willink > > > On 10/12/2018 13:40, Denis Roy wrote: >> I am on this. >> >> >> >> Denis >> >> >> >> On 2018-12-10 7:03 a.m., Jonah Graham wrote: >>> Hi folks, >>> >>> Bugzilla is failing to send emails. I and others are getting an Internal >>> Error when editing bugs. >>> >>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=542581 >>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=542581> >>> >>> Thanks, >>> Jonah >>> >>> >>> >>> ~~~ >>> Jonah Graham >>> Kichwa Coders Ltd. >>> www.kichwacoders.com <http://www.kichwacoders.com/> >>> >>> >>> ___ >>> cross-project-issues-dev mailing list >>> cross-project-issues-dev@eclipse.org >>> <mailto:cross-project-issues-dev@eclipse.org> >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev >>> <https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev> >> >> ___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev >> <https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev> > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > Virus-free. www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Java 11 recommendations
Ed, See https://wiki.eclipse.org/Jenkins#JDK <https://wiki.eclipse.org/Jenkins#JDK> to see what versions we provide in build environments. There is also a note about new Oracle JDK licensing. HTH. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 11 déc. 2018 à 21:16, Mike Milinkovich > a écrit : > > > There is no policy on the Java version. But I don’t understand why anyone > would elect to use Java under the OTN license when you could also use it > under the GPL+CE? > > Mike Milinkovich > mike.milinkov...@eclipse-foundation.org > <mailto:mike.milinkov...@eclipse-foundation.org> > (m) +1.613.220.3223 > > On Dec 11, 2018, at 12:10 PM, Ed Willink <mailto:e...@willink.me.uk>> wrote: > >> Hi >> >> Is there an EF policy on what Java 11 should be used? >> >> https://www.computerweekly.com/opinion/Beware-of-Oracles-developer-Trojan >> <https://www.computerweekly.com/opinion/Beware-of-Oracles-developer-Trojan> >> >> suggests that the Oracle JDK that I have used in the past may no longer be >> appropriate. >> >> Please advise. >> >> Regards >> >> Ed Willink >> >> >> >> --- >> This email has been checked for viruses by Avast antivirus software. >> https://www.avast.com/antivirus <https://www.avast.com/antivirus> >> >> ___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev >> <https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev> > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] download.eclipse.org timeouts
We're on it. Thanks for the report. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 16 oct. 2018 à 08:52, Christian Dietrich a > écrit : > > Already did https://bugs.eclipse.org/bugs/show_bug.cgi?id=540161 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=540161> > Am 16.10.18 um 08:48 schrieb Andrey Loskutov: >> Me too no download working (South Germany) :-( >> Please report bug. >> Kind regards, >> Andrey Loskutov >> >> Спасение утопающих - дело рук самих утопающих >> >> http://google.com/+AndreyLoskutov <http://google.com/+AndreyLoskutov> >> *Gesendet:* Dienstag, 16. Oktober 2018 um 08:46 Uhr >> *Von:* "Mickael Istria" <mailto:mist...@redhat.com> >> *An:* "Cross project issues" >> <mailto:cross-project-issues-dev@eclipse.org> >> *Betreff:* [cross-project-issues-dev] download.eclipse.org timeouts >> Hi, >> From France (over Numericable/SFR ISP), download.eclipse.org >> <http://download.eclipse.org> <http://download.eclipse.org/> seems stuck. >> A user also reported that on Twitter 2 hours ago: >> https://twitter.com/chip_uni/status/1052047649237426177 >> <https://twitter.com/chip_uni/status/1052047649237426177> >> Should I open a bug about it or is there one already open? >> >> -- >> Mickael Istria >> Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/> >> <https://www.eclipse.org/downloads/eclipse-packages/> developer, for >> Red Hat Developers <https://developers.redhat.com/> >> <https://developers.redhat.com/> >> ___ cross-project-issues-dev >> mailing >> list cross-project-issues-dev@eclipse.org >> <mailto:cross-project-issues-dev@eclipse.org> To change your delivery >> options, >> retrieve your password, or unsubscribe from this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> >> >> >> ___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Eclipse.org timeouts for bugzilla, gerrit, git
Do you still face the issue? We had an issue with connection limits, but Denis increased them and it now works for me. Cheers, Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 12 oct. 2018 à 13:56, Mikaël Barbero > a écrit : > > I'm experiencing the same issue currently. However, I see no evidence that > the issue is on the infra side. > > Will keep you posted. > > Thanks. > > Mikaël Barbero > Team Lead - Release Engineering | Eclipse Foundation > 📱 (+33) 642 028 039 | 🐦 @mikbarbero > Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open > Innovation and Collaboration > >> Le 12 oct. 2018 à 13:27, Andrey Loskutov > <mailto:losku...@gmx.de>> a écrit : >> >> Hi, >> >> Looks like eclipse.org <http://eclipse.org/> is hardly accessible: I get >> extremely large response times or timeouts for bugzilla, gerrit, git. >> >> Kind regards, >> Andrey Loskutov >> >> Спасение утопающих - дело рук самих утопающих >> >> http://google.com/+AndreyLoskutov <http://google.com/+AndreyLoskutov> >> ___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Eclipse.org timeouts for bugzilla, gerrit, git
I'm experiencing the same issue currently. However, I see no evidence that the issue is on the infra side. Will keep you posted. Thanks. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 12 oct. 2018 à 13:27, Andrey Loskutov a écrit : > > Hi, > > Looks like eclipse.org is hardly accessible: I get extremely large response > times or timeouts for bugzilla, gerrit, git. > > Kind regards, > Andrey Loskutov > > Спасение утопающих - дело рук самих утопающих > > http://google.com/+AndreyLoskutov > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] JDK 11 and 12ea available for JIPPs
Hi, JDK 11 GA as well as JDK 12ea+13 have been made available to all JIPPs in /shared/common/java. See [1] and [2] for complete list of available tools. If you need the Jenkins JDK Tool to be added to your instance, just open a bug to ask for it. The global Maven toolchain has been changed accordingly as well. Note that we've deleted all previous Oracle's early access builds in accordance with [3]. We also added an early access version of JDK 12. Both JDK 11 GA and JDK 12ea+13 are Oracle GPL+CE [4] builds of OpenJDK available from http://jdk.java.net <http://jdk.java.net/>. Note that the new Oracle Technology Network License Agreement for Oracle Java SE [5] is substantially different from the licenses under which previous versions of the JDK were offered. Previous versions of Oracle JDK were offered under the Oracle Binary Code License (BCL) for Java SE [6]. As such, starting with JDK 11, the Eclipse Foundation won't provide any new version of the JDK from Oracle licensed under the -commercial- Oracle Technology Network (OTN) terms. Previous version (JDK 10 and earlier), will stay available as is. See the differences between Oracle's OpenJDK Builds (GPL+CE) and Oracle JDK (OTN) on Oracle Director of Product Management's blog post [7]. Thanks. [1] https://wiki.eclipse.org/Jenkins#Tools_.28and_locations.29 <https://wiki.eclipse.org/Jenkins#Tools_.28and_locations.29> [2] https://wiki.eclipse.org/Jenkins#Tools_.28and_locations_on_the_default_JNLP_agent_container.29 <https://wiki.eclipse.org/Jenkins#Tools_.28and_locations_on_the_default_JNLP_agent_container.29> [3] https://www.oracle.com/technetwork/licenses/ea-license-noexhibits-1938914.html <https://www.oracle.com/technetwork/licenses/ea-license-noexhibits-1938914.html> [4] http://openjdk.java.net/legal/gplv2+ce.html <http://openjdk.java.net/legal/gplv2+ce.html> [5] https://www.oracle.com/technetwork/java/javase/terms/license/javase-license.html <https://www.oracle.com/technetwork/java/javase/terms/license/javase-license.html> [6] https://www.oracle.com/technetwork/java/javase/terms/license/index.html <https://www.oracle.com/technetwork/java/javase/terms/license/index.html> [7] https://blogs.oracle.com/java-platform-group/oracle-jdk-releases-for-java-11-and-later <https://blogs.oracle.com/java-platform-group/oracle-jdk-releases-for-java-11-and-later> Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Jenkins jobs don't have access to /home/data/httpd/download.eclipse.org/*
On Friday we had to restart the hipp6 machine. For some reasons, /home/data/httpd/download.eclipse.org <http://download.eclipse.org/> was not properly re-mounted at restart. I did it manually and everything should be ok now. Cheers, Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 24 juin 2018 à 08:05, Ed Merks a écrit : > > FYI, > > There seems to be a critical failure with Jenkin's jobs being able to access > anything under /home/data/httpd/download.eclipse.org/*. > > I noticed this for Oomph's jobs on Friday and opened this Bugzilla report on > Saturday: > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=527772 > > But it seems a more general problem because my attempt to manage EMF's update > site to publish the release update site (so that the mirror starts) also > fails for the same type of reason: > > org.eclipse.equinox.p2.core.ProvisionException: No repository found at > file:/home/data/httpd/download.eclipse.org/modeling/emf/emf/builds/milestone/latest > > Based on the job history of Oomph's "Setup Archiver" job, the last build that > still had access to /home/data/httpd/download.eclipse.org/* was dated Jun 21, > 2018 10:55 PM. > > With this problem I cannot publish EMF's update site for the Photon release > and I cannot publish Oomph's product catalog for the Photon release, so the > Eclipse Installer will not be able to install the Photon release's packages. > > I expect this affects all Jenkins jobs, but perhaps it's dependent on the > machine on which the job runs... > > Regards, > Ed > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Photon RC3 is available
Hi, The photon RC3 repository is now visible to p2 clients from the http://download.eclipse.org/releases/photon/ <http://download.eclipse.org/releases/photon/> URL. The EPP packages will be available from https://www.eclipse.org/downloads/index-developer.php <https://www.eclipse.org/downloads/index-developer.php> The validation job is now active again for RC4 contributions. Thanks everyone for making RC3 available. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Photon RC3 stating is complete
Hi, I declare the staging repository for Photon RC3 complete. It can be found here: http://download.eclipse.org/staging/photon/ SimRel aggregation builds are disabled until Friday after the release. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Photon RC2 is available
Hi, The photon RC2 repository is now visible to p2 clients from the http://download.eclipse.org/releases/photon/ URL. The EPP packages will be available from https://www.eclipse.org/downloads/index-developer.php The validation job is now active again for RC3 contributions. Thanks everyone for making RC2 available. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Photon RC2 stating is complete
of course, the topic of the email should bee "Photon RC2 staging is complete" > Le 31 mai 2018 à 11:32, Mikaël Barbero > a écrit : > > Hi, > > I declare the staging repository for Photon RC2 complete. > > It can be found here: > > http://download.eclipse.org/staging/photon/ > <http://download.eclipse.org/staging/photon/> > > SimRel aggregation builds are disabled until Friday after the release. > > Cheers, > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > 🐦 @mikbarbero > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Photon RC2 is available
Hi, I declare the staging repository for Photon RC2 complete. It can be found here: http://download.eclipse.org/staging/photon/ SimRel aggregation builds are disabled until Friday after the release. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Deprecating the command line JAR signing service (aka /usr/bin/sign) - read if you use Buckminster
The jarsigner plugins does not do anything on update sites. It must be run on eclipse-bundle and eclipse-feature packaging types. It must run in a maven step after the jar of the plugin/feature is build, and it will send it to the signing service, and replace the existing jar with a signed version. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 30 mai 2018 à 01:53, Sam Davis a écrit : > > I have seen that page. The relevant part seems to be "Signs project main and > attached artifacts using the Eclipse jarsigner webservice. Only artifacts > with .jar extension are signed, other artifacts are not signed but a warning > message is logged." What does "project main and attached artifacts" mean? > > I have this in a pom, and the build creates an update site under that > directory and then runs the jarsigner plugin, but I am not seeing that > anything is signed. > > Sam > > > -- > Sam Davis > Senior Software Engineer, Tasktop > Committer, Eclipse Mylyn > http://tasktop.com <http://tasktop.com/> > > On Tue, May 29, 2018 at 3:32 PM, Matthias Sohn <mailto:matthias.s...@gmail.com>> wrote: > On Tue, May 29, 2018 at 11:55 PM, Sam Davis <mailto:sam.da...@tasktop.com>> wrote: > Thanks very much for the replies, but I'm still missing something very basic: > what does the sign goal of eclipse-jarsigner-plugin actually do? What are its > inputs and outputs? > > maybe [1] helps ? > > [1] > https://www.eclipse.org/cbi/sitedocs/eclipse-jarsigner-plugin/sign-mojo.html > <https://www.eclipse.org/cbi/sitedocs/eclipse-jarsigner-plugin/sign-mojo.html> > > -Matthias > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > <mailto:cross-project-issues-dev@eclipse.org> > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Photon RC1 is available
Hi, The photon RC1 repository is now visible to p2 clients from the http://download.eclipse.org/releases/photon/ <http://download.eclipse.org/releases/photon/> URL. The EPP packages will be available from https://www.eclipse.org/downloads/index-developer.php <https://www.eclipse.org/downloads/index-developer.php> The validation job is now active again for RC2 contributions. Thanks everyone for making RC1 available. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] HIPP5 is down
HIPP5 machine is back online as well as all Jenkins instances running on it. Thanks for your patience. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 24 mai 2018 à 10:46, Mikaël Barbero > a écrit : > > Hi, > > For several days now, the HIPP5 machine have been flaky. We're now > experiencing a complete outage. Jenkins instances running on it (listed > below) are all affected. I've created > https://bugs.eclipse.org/bugs/show_bug.cgi?id=535057 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=535057> to track the > investigation. Feel free to cc yourself on this bug. Only full remediation > announcement will be posted on this mailing list. > > We're doing our best to restore the services. Thanks for your patience. > > cdt > golo > drone > collections > ls > emfservices > microprofile > tm4e > time4sys > reddeer > sensinact > bpel > tigerstripe > gemoc > openj9 > tea > osbp > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > <mailto:mikael.barb...@eclipse-foundation.org> > 🐦 @mikbarbero > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] HIPP5 is down
Hi, For several days now, the HIPP5 machine have been flaky. We're now experiencing a complete outage. Jenkins instances running on it (listed below) are all affected. I've created https://bugs.eclipse.org/bugs/show_bug.cgi?id=535057 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=535057> to track the investigation. Feel free to cc yourself on this bug. Only full remediation announcement will be posted on this mailing list. We're doing our best to restore the services. Thanks for your patience. cdt golo drone collections ls emfservices microprofile tm4e time4sys reddeer sensinact bpel tigerstripe gemoc openj9 tea osbp -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Photon RC1 staging is complete
Hi, I declare the staging repository for Photon RC1 complete. It can be found here: http://download.eclipse.org/staging/photon/ <http://download.eclipse.org/staging/photon/> SimRel aggregation builds are disabled until Friday after the release. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Photon M7 is now available
And I've re-activated the validate job. Contributions are open for RC1. > Le 19 mai 2018 à 19:36, Mikaël Barbero > a écrit : > > Hi, > > The Photon M7 repository is now "visible" since 10:00am EDT. It's 24h late > due to an aggregator bug (see > https://bugs.eclipse.org/bugs/show_bug.cgi?id=534867 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=534867> for details). > > => http://download.eclipse.org/releases/photon/ > <http://download.eclipse.org/releases/photon/> (contains M5, M6 and M7) > => http://download.eclipse.org/releases/photon/201805191000 > <http://download.eclipse.org/releases/photon/201805191000> (M7 only) > > The M7 EPP packages are *not* yet available from > > => https://www.eclipse.org/downloads/index-developer.php > <https://www.eclipse.org/downloads/index-developer.php> > > but will be on Monday. Thus, EPP update site > (http://download.eclipse.org/technology/epp/packages/photon/ > <http://download.eclipse.org/technology/epp/packages/photon/>) referenced by > http://download.eclipse.org/releases/photon/ > <http://download.eclipse.org/releases/photon/> is M6 only for now (see > https://dev.eclipse.org/mhonarc/lists/epp-dev/msg05017.html > <https://dev.eclipse.org/mhonarc/lists/epp-dev/msg05017.html> for details). > > Thank you all for your contributions. > > Cheers, > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > <mailto:mikael.barb...@eclipse-foundation.org> > 🐦 @mikbarbero > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Photon M7 is now available
Hi, The Photon M7 repository is now "visible" since 10:00am EDT. It's 24h late due to an aggregator bug (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=534867 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=534867> for details). => http://download.eclipse.org/releases/photon/ <http://download.eclipse.org/releases/photon/> (contains M5, M6 and M7) => http://download.eclipse.org/releases/photon/201805191000 <http://download.eclipse.org/releases/photon/201805191000> (M7 only) The M7 EPP packages are *not* yet available from => https://www.eclipse.org/downloads/index-developer.php <https://www.eclipse.org/downloads/index-developer.php> but will be on Monday. Thus, EPP update site (http://download.eclipse.org/technology/epp/packages/photon/ <http://download.eclipse.org/technology/epp/packages/photon/>) referenced by http://download.eclipse.org/releases/photon/ <http://download.eclipse.org/releases/photon/> is M6 only for now (see https://dev.eclipse.org/mhonarc/lists/epp-dev/msg05017.html <https://dev.eclipse.org/mhonarc/lists/epp-dev/msg05017.html> for details). Thank you all for your contributions. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] [epp-dev] Photon aggregation jobsare stuck
Photon M7 is back on track. Staging repo is complete without any incorrect checksum (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=534867 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=534867> for details). EPP is currently building. To give a bit of time to EPP, official repo of Photon M7 is scheduled to be promoted tomorrow at 10:00am EDT, exactly 24h late. I'll re-activate the simrel build jobs shortly after. Thanks to Alex and Nick for their precious help. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] [epp-dev] Photon aggregation jobs are stuck
I've created https://bugs.eclipse.org/bugs/show_bug.cgi?id=534867 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=534867> to discuss solution about this issue. Add yourself to the cc list if you're interested in this issue. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] [epp-dev] Photon aggregation jobs are stuck
New build is no better. It seems that simrel is processing jars from platform in some ways. The sums of plugins from platform don't match those from contributed repository. I have no idea why the aggregator is doing that. I'm still investigating. I guess we won't be able to release M7 @ 10am EDT. See below the debug info I gathered. == artifacts p2 repo excerpt from platform == $ md5sum eclipse/updates/4.8milestones/S-4.8M7-201805092000/plugins/org.eclipse.compare_* 40b1b4bdae832096e9e4e4ce7cdfe95e eclipse/updates/4.8milestones/S-4.8M7-201805092000/plugins/org.eclipse.compare_3.7.200.v20180418-1233.jar 4a014f90877bc58a7336e0a6d863b4bd eclipse/updates/4.8milestones/S-4.8M7-201805092000/plugins/org.eclipse.compare_3.7.200.v20180418-1233.jar.pack.gz $ sha256sum eclipse/updates/4.8milestones/S-4.8M7-201805092000/plugins/org.eclipse.compare_* b769fd9464f64c6cc777f4d339a23cc415acdcef5a01b27711aae9b70ea76e09 eclipse/updates/4.8milestones/S-4.8M7-201805092000/plugins/org.eclipse.compare_3.7.200.v20180418-1233.jar 6bf838a9064adb86f20a1ced5fc953014ce72f68f6b9eb71ecd28d711e42cdc7 eclipse/updates/4.8milestones/S-4.8M7-201805092000/plugins/org.eclipse.compare_3.7.200.v20180418-1233.jar.pack.gz == artifacts p2 repo excerpt from simrel staging == $ md5sum staging/photon/plugins/org.eclipse.compare_* 6a4e388f9578dbb66d0dc8128097ad77 staging/photon/plugins/org.eclipse.compare_3.7.200.v20180418-1233.jar 4a014f90877bc58a7336e0a6d863b4bd staging/photon/plugins/org.eclipse.compare_3.7.200.v20180418-1233.jar.pack.gz $ sha256sum staging/photon/plugins/org.eclipse.compare_* 3ea05da118160a8aa1be2c98c43d8868495a95bca1a5d6a3980fbdc653773f02 staging/photon/plugins/org.eclipse.compare_3.7.200.v20180418-1233.jar 6bf838a9064adb86f20a1ced5fc953014ce72f68f6b9eb71ecd28d711e42cdc7 staging/photon/plugins/org.eclipse.compare_3.7.200.v20180418-1233.jar.pack.gz > Le 18 mai 2018 à 10:09, Mikaël Barbero > a écrit : > > A new aggregation build is running with the latest version of the aggregator > (incl Alex's patch). > > We need to talk about the future of the Eclipse Desktop IDE simrel tooling, > but let's build M7 first ;) > > Thanks. > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > <mailto:mikael.barb...@eclipse-foundation.org> > 🐦 @mikbarbero > >> Le 18 mai 2018 à 09:57, Mickael Istria > <mailto:mist...@redhat.com>> a écrit : >> >> I cannot resist to mention that this kind of bugs shows how obsolete and >> not-so-well maintained and regularly erroneous in its understanding of p2 is >> the SimRel aggregator compared to Tycho; and that building the Simultaneous >> Release on top of such bugged and unpopular software is a major risk for our >> community, and causes always the same individual (fortunately often courtesy >> of the Foundation mostly, but not only) to spend major efforts in cutting >> the fire. >> The only sustainable path for SimRel is to move away from CBI aggregator and >> a lot of related Ant scripts and start building on state of art and well >> used and maintained Maven and Tycho. >> Driven by my concerns about CBI aggregator, I've provided several related >> usable pieces of work on this topic: >> * a pom.xml can already be used to build simrel with a plain `mvn clean >> verify` (delegating to CBI aggregator so far) >> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=500769 >> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=500769> contains proposals of >> a migration to Tycho and some discussions. >> I'd gladly welcome help to move forward with it. >> >> In the meantime, good luck to those who still have the patience to fix the >> CBI aggregator ;) >> ___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] [epp-dev] Photon aggregation jobs are stuck
A new aggregation build is running with the latest version of the aggregator (incl Alex's patch). We need to talk about the future of the Eclipse Desktop IDE simrel tooling, but let's build M7 first ;) Thanks. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 18 mai 2018 à 09:57, Mickael Istria a écrit : > > I cannot resist to mention that this kind of bugs shows how obsolete and > not-so-well maintained and regularly erroneous in its understanding of p2 is > the SimRel aggregator compared to Tycho; and that building the Simultaneous > Release on top of such bugged and unpopular software is a major risk for our > community, and causes always the same individual (fortunately often courtesy > of the Foundation mostly, but not only) to spend major efforts in cutting the > fire. > The only sustainable path for SimRel is to move away from CBI aggregator and > a lot of related Ant scripts and start building on state of art and well used > and maintained Maven and Tycho. > Driven by my concerns about CBI aggregator, I've provided several related > usable pieces of work on this topic: > * a pom.xml can already be used to build simrel with a plain `mvn clean > verify` (delegating to CBI aggregator so far) > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=500769 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=500769> contains proposals of > a migration to Tycho and some discussions. > I'd gladly welcome help to move forward with it. > > In the meantime, good luck to those who still have the patience to fix the > CBI aggregator ;) > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] [epp-dev] Photon aggregation jobs are stuck
As platform is now building with Tycho 1.2.0-snapshot, the issues we see in the p2 repo files probably come from the different versions of p2. As suggested by Alexander, I'm currently building a new version of the aggregator with the latest p2 from platform M8 (https://git.eclipse.org/r/#/c/122911/) I'll start an aggregation build with this new version of the aggregator (https://git.eclipse.org/r/#/c/122913/) shortly after. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 18 mai 2018 à 09:18, Mickael Istria a écrit : > > > > On Fri, May 18, 2018 at 8:01 AM, Mikaël Barbero > <mailto:mikael.barb...@eclipse-foundation.org>> wrote: > Any idea how it could be fixed? > > Nope, but I think you should file a bug and link it to > https://bugs.eclipse.org/bugs/show_bug.cgi?id=423715 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=423715> . > Comparing with the Platform M7 repo, It looks like that aggregator does > create a new artifact, with a new md5 checksum (which is already questionable > as the idea behind p2 is more to reuse artifacts and metadata) and has copied > the download.checksum.* metadata from Platform (which is strange too, as > other hash says it's apparently a different artifact) and moreover, those are > metadata from the packed artifact while the artifact here is not packed! > > > -- > Mickael Istria > Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/> developer, > for Red Hat Developers > <https://developers.redhat.com/>___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Photon aggregation jobs are stuck
It seems that there is a bug with the aggregator and the way it computes download.checksum.* Here are the actual checksums of org.eclipse.compare_3.7.200.v20180418-1233.jar 6a4e388f9578dbb66d0dc8128097ad77 org.eclipse.compare_3.7.200.v20180418-1233.jar 3ea05da118160a8aa1be2c98c43d8868495a95bca1a5d6a3980fbdc653773f02 org.eclipse.compare_3.7.200.v20180418-1233.jar and here an excerpt of the p2 artifacts repository: As you can see download.md5 is correct, while download.checksum.md5 and download.checksum.sha-256 are not. Any idea how it could be fixed? Should keep the complete staging repo as is, and build EPP in order to release M7 later today? -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 17 mai 2018 à 15:35, Nick Boldt a écrit : > > There appears to be a problem with the simrel photon staging site. When I > attempt to use p2.mirror to make a copy of the site, I get this error: > > 09:00:15 [p2.mirror] Messages while mirroring artifact descriptors. > 09:00:15 [p2.mirror] Problems downloading artifact: > osgi.bundle,org.eclipse.compare,3.7.200.v20180418-1233. > 09:00:15 [p2.mirror] SHA-256 hash is not as expected. Expected: > 6bf838a9064adb86f20a1ced5fc953014ce72f68f6b9eb71ecd28d711e42cdc7 and found > 3ea05da118160a8aa1be2c98c43d8868495a95bca1a5d6a3980fbdc653773f02. > > Here's the command I'm running: > > 09:00:15 Command-line arguments: -consoleLog -data > /mnt/hudson_workspace/workspace/jbosstoolstargetplatformrequirements-mirror-matrix/a4e6db81/tmp > -application org.eclipse.ant.core.antRunner -f build.xml > -Dversion=201805161906-Photon.0.M7 > -DURL=http://download.eclipse.org/staging/photon > <http://download.eclipse.org/staging/photon> > And here's the script: > > http://download.jboss.org/jbosstools/updates/requirements/photon/build.xml > <http://download.jboss.org/jbosstools/updates/requirements/photon/build.xml> > http://download.jboss.org/jbosstools/updates/requirements/generic/build.xml > <http://download.jboss.org/jbosstools/updates/requirements/generic/build.xml> > > I can work around this with -DignoreErrors=true, but that seems potentially a > bad idea. > > Should the staging site be rebuilt to fix this SHA/metadata problem? > > > > Nick > > On Thu, May 17, 2018 at 7:10 AM, Daniel Megert <mailto:daniel_meg...@ch.ibm.com>> wrote: > The change was in the wrong Gerrit change but is still valid. This was > announced on May 10: > https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15529.html > <https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15529.html>and > Markus said, he will take care of this, see > ttps://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15530.html > <https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15530.html> > > Dani > > > > From:Mickael Istria mailto:mist...@redhat.com>> > To:Cross project issues <mailto:cross-project-issues-dev@eclipse.org>> > Date:17.05.2018 12:46 > Subject:Re: [cross-project-issues-dev] Photon aggregation jobs are > stuck > Sent by:cross-project-issues-dev-boun...@eclipse.org > <mailto:cross-project-issues-dev-boun...@eclipse.org> > > > > > > On Thu, May 17, 2018 at 12:39 PM, Arthur van Dorp > mailto:arthur.vand...@bsi-software.com>> > wrote: > Sorry. I’m looking at the latest EPP-Build: > https://ci.eclipse.org/packaging/job/photon.epp-tycho-build/ > <https://ci.eclipse.org/packaging/job/photon.epp-tycho-build/>I’m not sure, > what code will be pulled there after the SimRel part is done. > > > Please bring this to the epp-dev mailing-list. The contribution of RAP tools > was disabled by > http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/rap-tools.aggrcon?id=d298c990d67b7ee4cd2e1232a41f1bee636507fa > > <http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/rap-tools.aggrcon?id=d298c990d67b7ee4cd2e1232a41f1bee636507fa>(which > seems not related and erroneous to me). If this was not intentional, then it > would IMO be better to respin SimRel than to add workload on RAP which didn't > do anything wrong here. > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > <mailto:cross-project-issues-dev@eclipse.org> > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit >
Re: [cross-project-issues-dev] [egit-dev] Photon aggregation jobs are stuck
Thanks Matthias! I won't start another aggregation build yet. More of that in a couple of minutes. > Le 17 mai 2018 à 23:51, Sohn, Matthias a écrit : > > Hi Mikael, > > I have restored the lost staging repository which was overwritten by a > misconfigured build job from Nexus > https://repo.eclipse.org/content/groups/releases/org/eclipse/mylyn/github/github-updatesite/5.0.0.201805151920-m7/ > > <https://repo.eclipse.org/content/groups/releases/org/eclipse/mylyn/github/github-updatesite/5.0.0.201805151920-m7/> > and pushed a change reenabling the github plugin contribution > https://git.eclipse.org/r/#/c/122905/ <https://git.eclipse.org/r/#/c/122905/> > I submitted this change, maybe you include that ? > Otherwise will have it in RC1 > > -Matthias > > From: on behalf of Mikaël Barbero > > Date: Thursday, 17. May 2018 at 21:27 > To: Cross project issues > Cc: EGit developer discussion , Eclipse Packaging > Project > Subject: Re: [egit-dev] [cross-project-issues-dev] Photon aggregation jobs > are stuck > > I've deactivated the EGit/Github contrib > (https://git.eclipse.org/r/#/c/122893/ > <https://git.eclipse.org/r/#/c/122893/>) and the validate job is green. > > I've started a new aggregation build > https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.BUILD__CLEAN/248 > > <https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.BUILD__CLEAN/248> > > >> Le 17 mai 2018 à 19:42, Mikaël Barbero >> > <mailto:mikael.barb...@eclipse-foundation.org>> a écrit : >> >> Something is wrong with >> download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7 >> <http://download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7> >> features. In the complete staging repo, I properly have >> >> ./plugins/org.eclipse.mylyn.github.core_5.0.0.201805151920-m7.jar >> ./plugins/org.eclipse.mylyn.github.core_5.0.0.201805151920-m7.jar.pack.gz >> ./plugins/org.eclipse.mylyn.github.doc_5.0.0.201805151920-m7.jar >> ./plugins/org.eclipse.mylyn.github.doc_5.0.0.201805151920-m7.jar.pack.gz >> ./plugins/org.eclipse.mylyn.github.ui_5.0.0.201805151920-m7.jar >> ./plugins/org.eclipse.mylyn.github.ui_5.0.0.201805151920-m7.jar.pack.gz >> >> They have disappear since yesterday. >> >> Matthias, I am going to deactivate these contributions if I don't hear from >> you in the next hour. >> >> Thanks. >> >> -- >> Mikaël Barbero - Eclipse Foundation >> IT Services - Release Engineering >> 📱 (+33) 642 028 039 >> 📧 mikael.barb...@eclipse-foundation.org >> <mailto:mikael.barb...@eclipse-foundation.org> >> 🐦 @mikbarbero >> >> >>> Le 17 mai 2018 à 17:34, Mikaël Barbero >>> >> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit : >>> >>> Aggregation file is looking for feature >>> org.eclipse.mylyn.github.feature.feature.group version >>> 5.0.0.201805151920-m7 while it contains 5.0.0.201805170916. >>> >>> >>>> Le 17 mai 2018 à 17:25, Mikaël Barbero >>>> >>> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit : >>>> >>>> I've facing a validation error >>>> >>>> Missing requirement: >>>> mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 >>>> 1.0.0 requires 'org.eclipse.mylyn.github.feature.feature.group >>>> [5.0.0.201805151920-m7]' but it could not be found >>>> >>>> 11:20:40 [exec] Build failed! Exception was >>>> org.eclipse.core.runtime.CoreException: Cannot complete the install >>>> because one or more required items could not be found. Software being >>>> installed: validationSet_main 1.0.0 Missing requirement: >>>> mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 >>>> 1.0.0 requires 'org.eclipse.mylyn.github.feature.feature.group >>>> [5.0.0.201805151920-m7]' but it could not be found Cannot satisfy >>>> dependency: validationSet_main 1.0.0 depends on: >>>> mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 >>>> [1.0.0] >>>> >>>> It is weird, it should have failed during previous build except if the >>>> Egit repo (download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7 >>>> <http://download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7>) >>>> has changed since last build. signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Photon aggregation jobs are stuck
Build is green. Nick, can you try again your script against http://download.eclipse.org/staging/photon? <http://download.eclipse.org/staging/photon?> Thanks. PS: FYI $ diff -qr staging/photon/ releases/photon/201805181000/ Les fichiers staging/photon//artifacts.jar et releases/photon/201805181000//artifacts.jar sont différents. Les fichiers staging/photon//artifacts.xml.xz et releases/photon/201805181000//artifacts.xml.xz sont différents. Les fichiers staging/photon//content.jar et releases/photon/201805181000//content.jar sont différents. Les fichiers staging/photon//content.xml.xz et releases/photon/201805181000//content.xml.xz sont différents. Seulement dans releases/photon/201805181000//features: org.eclipse.mylyn.github.feature_5.0.0.201805151920-m7.jar Seulement dans releases/photon/201805181000//plugins: org.eclipse.egit.github.core_5.0.0.201805151920-m7.jar Seulement dans releases/photon/201805181000//plugins: org.eclipse.egit.github.core_5.0.0.201805151920-m7.jar.pack.gz Seulement dans releases/photon/201805181000//plugins: org.eclipse.lsp4e_0.6.0.201805160707.jar Seulement dans releases/photon/201805181000//plugins: org.eclipse.lsp4e_0.6.0.201805160707.jar.pack.gz Seulement dans staging/photon//plugins: org.eclipse.lsp4e_0.6.0.201805171449.jar Seulement dans staging/photon//plugins: org.eclipse.lsp4e_0.6.0.201805171449.jar.pack.gz Seulement dans releases/photon/201805181000//plugins: org.eclipse.mylyn.github.core_5.0.0.201805151920-m7.jar Seulement dans releases/photon/201805181000//plugins: org.eclipse.mylyn.github.core_5.0.0.201805151920-m7.jar.pack.gz Seulement dans releases/photon/201805181000//plugins: org.eclipse.mylyn.github.doc_5.0.0.201805151920-m7.jar Seulement dans releases/photon/201805181000//plugins: org.eclipse.mylyn.github.doc_5.0.0.201805151920-m7.jar.pack.gz Seulement dans releases/photon/201805181000//plugins: org.eclipse.mylyn.github.ui_5.0.0.201805151920-m7.jar Seulement dans releases/photon/201805181000//plugins: org.eclipse.mylyn.github.ui_5.0.0.201805151920-m7.jar.pack.gz > Le 17 mai 2018 à 21:20, Mikaël Barbero > a écrit : > > I've deactivated the EGit/Github contrib > (https://git.eclipse.org/r/#/c/122893/ > <https://git.eclipse.org/r/#/c/122893/>) and the validate job is green. > > I've started a new aggregation build > https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.BUILD__CLEAN/248 > > <https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.BUILD__CLEAN/248> > >> Le 17 mai 2018 à 19:42, Mikaël Barbero >> > <mailto:mikael.barb...@eclipse-foundation.org>> a écrit : >> >> Something is wrong with >> download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7 >> <http://download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7> >> features. In the complete staging repo, I properly have >> >> ./plugins/org.eclipse.mylyn.github.core_5.0.0.201805151920-m7.jar >> ./plugins/org.eclipse.mylyn.github.core_5.0.0.201805151920-m7.jar.pack.gz >> ./plugins/org.eclipse.mylyn.github.doc_5.0.0.201805151920-m7.jar >> ./plugins/org.eclipse.mylyn.github.doc_5.0.0.201805151920-m7.jar.pack.gz >> ./plugins/org.eclipse.mylyn.github.ui_5.0.0.201805151920-m7.jar >> ./plugins/org.eclipse.mylyn.github.ui_5.0.0.201805151920-m7.jar.pack.gz >> >> They have disappear since yesterday. >> >> Matthias, I am going to deactivate these contributions if I don't hear from >> you in the next hour. >> >> Thanks. >> >> -- >> Mikaël Barbero - Eclipse Foundation >> IT Services - Release Engineering >> 📱 (+33) 642 028 039 >> 📧 mikael.barb...@eclipse-foundation.org >> <mailto:mikael.barb...@eclipse-foundation.org> >> 🐦 @mikbarbero >> >>> Le 17 mai 2018 à 17:34, Mikaël Barbero >>> >> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit : >>> >>> Aggregation file is looking for feature >>> org.eclipse.mylyn.github.feature.feature.group version >>> 5.0.0.201805151920-m7 while it contains 5.0.0.201805170916. >>> >>>> Le 17 mai 2018 à 17:25, Mikaël Barbero >>>> >>> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit : >>>> >>>> I've facing a validation error >>>> >>>> Missing requirement: >>>> mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 >>>> 1.0.0 requires 'org.eclipse.mylyn.github.feature.feature.group >>>> [5.0.0.201805151920-m7]' but it could not be found >>>> >>>> 11:20:40 [exec] Build failed! Ex
Re: [cross-project-issues-dev] Photon aggregation jobs are stuck
I've deactivated the EGit/Github contrib (https://git.eclipse.org/r/#/c/122893/) and the validate job is green. I've started a new aggregation build https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.BUILD__CLEAN/248 > Le 17 mai 2018 à 19:42, Mikaël Barbero > a écrit : > > Something is wrong with > download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7 > <http://download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7> > features. In the complete staging repo, I properly have > > ./plugins/org.eclipse.mylyn.github.core_5.0.0.201805151920-m7.jar > ./plugins/org.eclipse.mylyn.github.core_5.0.0.201805151920-m7.jar.pack.gz > ./plugins/org.eclipse.mylyn.github.doc_5.0.0.201805151920-m7.jar > ./plugins/org.eclipse.mylyn.github.doc_5.0.0.201805151920-m7.jar.pack.gz > ./plugins/org.eclipse.mylyn.github.ui_5.0.0.201805151920-m7.jar > ./plugins/org.eclipse.mylyn.github.ui_5.0.0.201805151920-m7.jar.pack.gz > > They have disappear since yesterday. > > Matthias, I am going to deactivate these contributions if I don't hear from > you in the next hour. > > Thanks. > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > <mailto:mikael.barb...@eclipse-foundation.org> > 🐦 @mikbarbero > >> Le 17 mai 2018 à 17:34, Mikaël Barbero >> > <mailto:mikael.barb...@eclipse-foundation.org>> a écrit : >> >> Aggregation file is looking for feature >> org.eclipse.mylyn.github.feature.feature.group version 5.0.0.201805151920-m7 >> while it contains 5.0.0.201805170916. >> >>> Le 17 mai 2018 à 17:25, Mikaël Barbero >>> >> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit : >>> >>> I've facing a validation error >>> >>> Missing requirement: >>> mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 >>> 1.0.0 requires 'org.eclipse.mylyn.github.feature.feature.group >>> [5.0.0.201805151920-m7]' but it could not be found >>> >>> 11:20:40 [exec] Build failed! Exception was >>> org.eclipse.core.runtime.CoreException: Cannot complete the install because >>> one or more required items could not be found. Software being installed: >>> validationSet_main 1.0.0 Missing requirement: >>> mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 >>> 1.0.0 requires 'org.eclipse.mylyn.github.feature.feature.group >>> [5.0.0.201805151920-m7]' but it could not be found Cannot satisfy >>> dependency: validationSet_main 1.0.0 depends on: >>> mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 >>> [1.0.0] >>> >>> It is weird, it should have failed during previous build except if the Egit >>> repo (download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7 >>> <http://download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7>) >>> has changed since last build. >>> >>> >> > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Photon aggregation jobs are stuck
Something is wrong with download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7 <http://download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7> features. In the complete staging repo, I properly have ./plugins/org.eclipse.mylyn.github.core_5.0.0.201805151920-m7.jar ./plugins/org.eclipse.mylyn.github.core_5.0.0.201805151920-m7.jar.pack.gz ./plugins/org.eclipse.mylyn.github.doc_5.0.0.201805151920-m7.jar ./plugins/org.eclipse.mylyn.github.doc_5.0.0.201805151920-m7.jar.pack.gz ./plugins/org.eclipse.mylyn.github.ui_5.0.0.201805151920-m7.jar ./plugins/org.eclipse.mylyn.github.ui_5.0.0.201805151920-m7.jar.pack.gz They have disappear since yesterday. Matthias, I am going to deactivate these contributions if I don't hear from you in the next hour. Thanks. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 17 mai 2018 à 17:34, Mikaël Barbero > a écrit : > > Aggregation file is looking for feature > org.eclipse.mylyn.github.feature.feature.group version 5.0.0.201805151920-m7 > while it contains 5.0.0.201805170916. > >> Le 17 mai 2018 à 17:25, Mikaël Barbero >> > <mailto:mikael.barb...@eclipse-foundation.org>> a écrit : >> >> I've facing a validation error >> >> Missing requirement: >> mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 >> 1.0.0 requires 'org.eclipse.mylyn.github.feature.feature.group >> [5.0.0.201805151920-m7]' but it could not be found >> >> 11:20:40 [exec] Build failed! Exception was >> org.eclipse.core.runtime.CoreException: Cannot complete the install because >> one or more required items could not be found. Software being installed: >> validationSet_main 1.0.0 Missing requirement: >> mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 >> 1.0.0 requires 'org.eclipse.mylyn.github.feature.feature.group >> [5.0.0.201805151920-m7]' but it could not be found Cannot satisfy >> dependency: validationSet_main 1.0.0 depends on: >> mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 >> [1.0.0] >> >> It is weird, it should have failed during previous build except if the Egit >> repo (download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7 >> <http://download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7>) >> has changed since last build. >> >> > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Photon aggregation jobs are stuck
Aggregation file is looking for feature org.eclipse.mylyn.github.feature.feature.group version 5.0.0.201805151920-m7 while it contains 5.0.0.201805170916. > Le 17 mai 2018 à 17:25, Mikaël Barbero > a écrit : > > I've facing a validation error > > Missing requirement: > mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 > 1.0.0 requires 'org.eclipse.mylyn.github.feature.feature.group > [5.0.0.201805151920-m7]' but it could not be found > > 11:20:40 [exec] Build failed! Exception was > org.eclipse.core.runtime.CoreException: Cannot complete the install because > one or more required items could not be found. Software being installed: > validationSet_main 1.0.0 Missing requirement: > mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 > 1.0.0 requires 'org.eclipse.mylyn.github.feature.feature.group > [5.0.0.201805151920-m7]' but it could not be found Cannot satisfy dependency: > validationSet_main 1.0.0 depends on: > mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 > [1.0.0] > > It is weird, it should have failed during previous build except if the Egit > repo (download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7 > <http://download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7>) has > changed since last build. > > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Photon aggregation jobs are stuck
I've facing a validation error Missing requirement: mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 1.0.0 requires 'org.eclipse.mylyn.github.feature.feature.group [5.0.0.201805151920-m7]' but it could not be found 11:20:40 [exec] Build failed! Exception was org.eclipse.core.runtime.CoreException: Cannot complete the install because one or more required items could not be found. Software being installed: validationSet_main 1.0.0 Missing requirement: mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 1.0.0 requires 'org.eclipse.mylyn.github.feature.feature.group [5.0.0.201805151920-m7]' but it could not be found Cannot satisfy dependency: validationSet_main 1.0.0 depends on: mappedRepo_home_data_httpd_download.eclipse.org_egit_github_staging_v5.0.0.201805151920-m7 [1.0.0] It is weird, it should have failed during previous build except if the Egit repo (download.eclipse.org/egit/github/staging/v5.0.0.201805151920-m7) has changed since last build. signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Photon aggregation jobs are stuck
I've started a new aggregation build. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 17 mai 2018 à 17:12, Nick Boldt a écrit : > > After attempting to mirror with the ignoreErrors=true flag, I found 762 more > SHA warnings! > > Here's the list: > > https://gist.github.com/nickboldt/077e517c64e9750d07a385ae586f4b0b > <https://gist.github.com/nickboldt/077e517c64e9750d07a385ae586f4b0b> > > So, yeah, a respin is definitely a good idea. :D > > Nick > > On Thu, May 17, 2018 at 11:02 AM, Markus Knauer <mailto:mkna...@eclipsesource.com>> wrote: > No problem for EPP... we've had other issues that are "fixed" now and will > need another EPP package build anyway. > > (The best case would be if we could fix the RAP Tools contribution problem > with the rebuild, too. I'll see what I can do in the next minutes) > > Thanks, > Markus > > > On 17 May 2018 at 16:18, Mikaël Barbero > <mailto:mikael.barb...@eclipse-foundation.org>> wrote: > I'm willing to give it a try, but EPP would need to rebuild as well after > that. > > EPP, is it ok with you? > > Cheers, > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > <mailto:mikael.barb...@eclipse-foundation.org> > 🐦 @mikbarbero > >> Le 17 mai 2018 à 15:35, Nick Boldt > <mailto:nbo...@redhat.com>> a écrit : >> >> There appears to be a problem with the simrel photon staging site. When I >> attempt to use p2.mirror to make a copy of the site, I get this error: >> >> 09:00:15 [p2.mirror] Messages while mirroring artifact descriptors. >> 09:00:15 [p2.mirror] Problems downloading artifact: >> osgi.bundle,org.eclipse.compare,3.7.200.v20180418-1233. >> 09:00:15 [p2.mirror] SHA-256 hash is not as expected. Expected: >> 6bf838a9064adb86f20a1ced5fc953014ce72f68f6b9eb71ecd28d711e42cdc7 and found >> 3ea05da118160a8aa1be2c98c43d8868495a95bca1a5d6a3980fbdc653773f02. >> >> Here's the command I'm running: >> >> 09:00:15 Command-line arguments: -consoleLog -data >> /mnt/hudson_workspace/workspace/jbosstoolstargetplatformrequirements-mirror-matrix/a4e6db81/tmp >> -application org.eclipse.ant.core.antRunner -f build.xml >> -Dversion=201805161906-Photon.0.M7 >> -DURL=http://download.eclipse.org/staging/photon >> <http://download.eclipse.org/staging/photon> >> And here's the script: >> >> http://download.jboss.org/jbosstools/updates/requirements/photon/build.xml >> <http://download.jboss.org/jbosstools/updates/requirements/photon/build.xml> >> http://download.jboss.org/jbosstools/updates/requirements/generic/build.xml >> <http://download.jboss.org/jbosstools/updates/requirements/generic/build.xml> >> >> I can work around this with -DignoreErrors=true, but that seems potentially >> a bad idea. >> >> Should the staging site be rebuilt to fix this SHA/metadata problem? >> >> >> >> Nick >> >> On Thu, May 17, 2018 at 7:10 AM, Daniel Megert > <mailto:daniel_meg...@ch.ibm.com>> wrote: >> The change was in the wrong Gerrit change but is still valid. This was >> announced on May 10: >> https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15529.html >> <https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15529.html>and >> Markus said, he will take care of this, see >> ttps://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15530.html >> <https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15530.html> >> >> Dani >> >> >> >> From:Mickael Istria mailto:mist...@redhat.com>> >> To:Cross project issues > <mailto:cross-project-issues-dev@eclipse.org>> >> Date:17.05.2018 12:46 >> Subject:Re: [cross-project-issues-dev] Photon aggregation jobs are >> stuck >> Sent by:cross-project-issues-dev-boun...@eclipse.org >> <mailto:cross-project-issues-dev-boun...@eclipse.org> >> >> >> >> >> >> On Thu, May 17, 2018 at 12:39 PM, Arthur van Dorp >> mailto:arthur.vand...@bsi-software.com>> >> wrote: >> Sorry. I’m looking at the latest EPP-Build: >> https://ci.eclipse.org/packaging/job/photon.epp-tycho-build/ >> <https://ci.eclipse.org/
Re: [cross-project-issues-dev] Photon aggregation jobs are stuck
I'm willing to give it a try, but EPP would need to rebuild as well after that. EPP, is it ok with you? Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 17 mai 2018 à 15:35, Nick Boldt a écrit : > > There appears to be a problem with the simrel photon staging site. When I > attempt to use p2.mirror to make a copy of the site, I get this error: > > 09:00:15 [p2.mirror] Messages while mirroring artifact descriptors. > 09:00:15 [p2.mirror] Problems downloading artifact: > osgi.bundle,org.eclipse.compare,3.7.200.v20180418-1233. > 09:00:15 [p2.mirror] SHA-256 hash is not as expected. Expected: > 6bf838a9064adb86f20a1ced5fc953014ce72f68f6b9eb71ecd28d711e42cdc7 and found > 3ea05da118160a8aa1be2c98c43d8868495a95bca1a5d6a3980fbdc653773f02. > > Here's the command I'm running: > > 09:00:15 Command-line arguments: -consoleLog -data > /mnt/hudson_workspace/workspace/jbosstoolstargetplatformrequirements-mirror-matrix/a4e6db81/tmp > -application org.eclipse.ant.core.antRunner -f build.xml > -Dversion=201805161906-Photon.0.M7 > -DURL=http://download.eclipse.org/staging/photon > <http://download.eclipse.org/staging/photon> > And here's the script: > > http://download.jboss.org/jbosstools/updates/requirements/photon/build.xml > <http://download.jboss.org/jbosstools/updates/requirements/photon/build.xml> > http://download.jboss.org/jbosstools/updates/requirements/generic/build.xml > <http://download.jboss.org/jbosstools/updates/requirements/generic/build.xml> > > I can work around this with -DignoreErrors=true, but that seems potentially a > bad idea. > > Should the staging site be rebuilt to fix this SHA/metadata problem? > > > > Nick > > On Thu, May 17, 2018 at 7:10 AM, Daniel Megert <mailto:daniel_meg...@ch.ibm.com>> wrote: > The change was in the wrong Gerrit change but is still valid. This was > announced on May 10: > https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15529.html > <https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15529.html>and > Markus said, he will take care of this, see > ttps://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15530.html > <https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15530.html> > > Dani > > > > From:Mickael Istria mailto:mist...@redhat.com>> > To:Cross project issues <mailto:cross-project-issues-dev@eclipse.org>> > Date:17.05.2018 12:46 > Subject:Re: [cross-project-issues-dev] Photon aggregation jobs are > stuck > Sent by:cross-project-issues-dev-boun...@eclipse.org > <mailto:cross-project-issues-dev-boun...@eclipse.org> > > > > > > On Thu, May 17, 2018 at 12:39 PM, Arthur van Dorp > mailto:arthur.vand...@bsi-software.com>> > wrote: > Sorry. I’m looking at the latest EPP-Build: > https://ci.eclipse.org/packaging/job/photon.epp-tycho-build/ > <https://ci.eclipse.org/packaging/job/photon.epp-tycho-build/>I’m not sure, > what code will be pulled there after the SimRel part is done. > > > Please bring this to the epp-dev mailing-list. The contribution of RAP tools > was disabled by > http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/rap-tools.aggrcon?id=d298c990d67b7ee4cd2e1232a41f1bee636507fa > > <http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/rap-tools.aggrcon?id=d298c990d67b7ee4cd2e1232a41f1bee636507fa>(which > seems not related and erroneous to me). If this was not intentional, then it > would IMO be better to respin SimRel than to add workload on RAP which didn't > do anything wrong here. > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > <mailto:cross-project-issues-dev@eclipse.org> > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> > > > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > <mailto:cross-project-issues-dev@eclipse.org> > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> > > > > -- > Nick Boldt &g
Re: [cross-project-issues-dev] Photon aggregation jobs are stuck
EPP build should run again today against the completed staging repo. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 17 mai 2018 à 08:38, Arthur van Dorp a > écrit : > > Hi, > > With the staging repo complete: Will there be another epp build triggered > automatically or will it have to be done manually? It hasn't run for some > time now and is still red. > > Regards, > Arthur > > -Ursprüngliche Nachricht- > Von: cross-project-issues-dev-boun...@eclipse.org > [mailto:cross-project-issues-dev-boun...@eclipse.org] Im Auftrag von > Pierre-Charles David > Gesendet: Mittwoch, 16. Mai 2018 14:44 > An: Cross project issues > Betreff: [cross-project-issues-dev] Photon aggregation jobs are stuck > > Hi all, > > There a Photon aggregation build that have been stuck for about 22 > hours, with 7 (at this time) other builds pending in the queue: > https://hudson.eclipse.org/simrel/job/simrel.photon.runaggregator.BUILD__CLEAN/227/ > > Could someone with the appropriate rights kill it please? > > Thanks. > > -- > > *Pierre-Charles David* > +33 2 51 13 52 18 > > <http://www.obeo.fr/> > > 7 Boulevard Ampère - Carquefou - France > *obeo.fr* <http://www.obeo.fr/> | *twitter* > <https://twitter.com/obeo_corp> | *linkedin* > <https://www.linkedin.com/company/obeo> > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Photon M7 staging is complete
Hi, Since there were no requests for extension, I declare the staging repository for Photon M7 complete. It can be found here: http://download.eclipse.org/staging/photon/ <http://download.eclipse.org/staging/photon/> SimRel aggregation builds are disabled until Friday after the release. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Photon aggregation jobs are stuck
> > Could you restart the WTP JIPP? I would but it never comes back to life for > me [1]. Done signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Photon M7 build is failing
Hi, It seems that the corrosion project is failing the build. Could you please check your contribution? Mirroring artifacts from file:///home/data/httpd/download.eclipse.org/corrosion/snapshots 11:43:32 [exec] - mirroring artifact osgi.bundle,org.eclipse.corrosion,0.1.0.201805151243 11:43:32 [exec] doing copy of canonical artifact 11:43:32 [exec] - mirroring artifact org.eclipse.update.feature,org.eclipse.corrosion.feature,0.1.0.201805151243 11:43:32 [exec] doing copy of canonical artifact (https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.BUILD__CLEAN/238/console <https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.BUILD__CLEAN/238/console>) Thanks. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Photon aggregation jobs are stuck
I've killed it. Thanks. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 16 mai 2018 à 14:44, Pierre-Charles David a > écrit : > > Hi all, > > There a Photon aggregation build that have been stuck for about 22 hours, > with 7 (at this time) other builds pending in the queue: > https://hudson.eclipse.org/simrel/job/simrel.photon.runaggregator.BUILD__CLEAN/227/ > > Could someone with the appropriate rights kill it please? > > Thanks. > > -- > > *Pierre-Charles David* > +33 2 51 13 52 18 > > <http://www.obeo.fr/> > > 7 Boulevard Ampère - Carquefou - France > *obeo.fr* <http://www.obeo.fr/> | *twitter* <https://twitter.com/obeo_corp> | > *linkedin* <https://www.linkedin.com/company/obeo> > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Is SimRel final for M7?
Staging will be complete on Wed night as Nick said. However, tip of the day is (IIRC) part of Eclipse platform and their contribution is already done as +0 deadline is on Friday. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 14 mai 2018 à 17:21, Nick Boldt a écrit : > > I imagine there will be several more respins since it's only +1 day today. > > Last build is likely Wed night / Thurs morning, per the Photon calendar. > > https://calendar.google.com/calendar/embed?src=gchs7nm4nvpm837469ddj9t...@group.calendar.google.com > > <https://calendar.google.com/calendar/embed?src=gchs7nm4nvpm837469ddj9t...@group.calendar.google.com> > > On Mon, May 14, 2018 at 11:06 AM, Wim Jongman <mailto:wim.jong...@gmail.com>> wrote: > Hi, > > Is there going to be another SimRel build? I would like to update it with the > latest Tip of the Day feature version. > > Cheers, > > Wim > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > <mailto:cross-project-issues-dev@eclipse.org> > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> > > > > -- > Nick Boldt > Senior Software Engineer, RHCSA > Productization Lead :: JBoss Tools & Dev Studio > IM: @nickboldt / @nboldt / http://nick.divbyzero.com > <http://nick.divbyzero.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > @ @redhatnews <https://twitter.com/redhatnews> Red Hat > <https://www.facebook.com/RedHatInc> > <https://www.facebook.com/RedHatInc> > > > “The Only Thing That Is Constant Is Change” - Heraclitus > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] CBI Maven plugins version 1.1.5 have been released
Hi, A new version of CBI maven plugins have been published. Details are available on release page https://projects.eclipse.org/projects/technology.cbi/releases/maven-plugins-1.1.5 <https://projects.eclipse.org/projects/technology.cbi/releases/maven-plugins-1.1.5> Think about updating your pom to use this greatest and latest version. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Deprecating the command line JAR signing service (aka /usr/bin/sign) - read if you use Buckminster
Hi, A quick update about the termination date of the command line Jar signing service (aka /usr/bin/sign). With Oxygen.3a GA being available since yesterday, a grace period of 4 weeks is now starting before shutdown. The termination date is set to May 9th. Cheers, Mikael -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 22 août 2017 à 17:01, Mikaël Barbero > a écrit : > > Hi, > > Effective immediately, we are deprecating the usage the command line signing > service (aka /usr/bin/sign). > > Most certainly, this will only affect you if you use Buckminster as a build > system (because Buckminster can only sign jars via /usr/bin/sign service). If > you use Tycho, you're not concerned. > > There are two strategies for Buckminster users: > > 1- Migrate to a modern / maintained build plugin system (see Buckminster's > activity - https://projects.eclipse.org/projects/tools.buckminster > <https://projects.eclipse.org/projects/tools.buckminster>). See Tycho > documentation (https://wiki.eclipse.org/Tycho/Pack200#Pack200_and_Signing > <https://wiki.eclipse.org/Tycho/Pack200#Pack200_and_Signing>) and CBI > Jarsigner Maven plugin > (https://www.eclipse.org/cbi/maven-plugins/documentation/latest/eclipse-jarsigner-plugin/sign-mojo.html > > <https://www.eclipse.org/cbi/maven-plugins/documentation/latest/eclipse-jarsigner-plugin/sign-mojo.html>) > for how to add jar signing to a Tycho build. > > 2- Deactivate signing in Buckminster and do the repacking and the signing > phase as a post build step. You will need to do some shell scripting (in your > CI instance) to browse all the jars, pack200/unpack200 them (aka repack) and > then sign them. To sign a jar, you can use the webservice that the CBI maven > plugin uses in the background (see the Jar signing web service documentation > for details - > https://wiki.eclipse.org/IT_Infrastructure_Doc#Web_service_.28Instant.29 > <https://wiki.eclipse.org/IT_Infrastructure_Doc#Web_service_.28Instant.29>). > > If option 2 is chosen and highly motivated, we can provide some assistance > with the shell script (fill a bug under CBI/Signing-Service > https://bugs.eclipse.org/bugs/enter_bug.cgi?product=CBI&component=signing-service > > <https://bugs.eclipse.org/bugs/enter_bug.cgi?product=CBI&component=signing-service>). > > I've updated our documentation > (https://wiki.eclipse.org/IT_Infrastructure_Doc#Deprecated_-_ZIP_and_JAR_files_from_the_command_line_.28queued_or_not.29 > > <https://wiki.eclipse.org/IT_Infrastructure_Doc#Deprecated_-_ZIP_and_JAR_files_from_the_command_line_.28queued_or_not.29>) > to mention the deprecation. A bug has been created to keep track of the > termination (https://bugs.eclipse.org/bugs/show_bug.cgi?id=521263 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=521263>). > > Cheers, > Mikael > > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > <mailto:mikael.barb...@eclipse-foundation.org> > 🐦 @mikbarbero > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Gerrit and Jenkins, tips and news
Simply open a bug against Community > CI Jenkins (https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=CI-Jenkins) asking for specific plugin to be installed. You will have to configure your jobs to use the plugin though. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 20 mars 2018 à 10:49, Lars Vogel a écrit : > > Hi Mikael, > > what is the process if we want additional plug-ins for Jenkins? > > For example, the Warnings-Plugin looks useful to me to validate via Gerrit > verification builds, that the number of compiler warnings do not increase. > > References: > https://wiki.jenkins.io/display/JENKINS/Warnings+Plugin > <https://wiki.jenkins.io/display/JENKINS/Warnings+Plugin> > https://stackoverflow.com/questions/38308496/how-do-i-fail-a-build-in-jenkins-if-the-number-of-compiler-warnings-increases > > <https://stackoverflow.com/questions/38308496/how-do-i-fail-a-build-in-jenkins-if-the-number-of-compiler-warnings-increases> > > Best regards, Lars > > > > On Wed, Mar 14, 2018 at 9:43 AM, Mikaël Barbero > <mailto:mikael.barb...@eclipse-foundation.org>> wrote: > >> I would argue that the more tedious problem is having tests that sometimes >> fail. I've been waging a war against intermittent test failures in JBoss >> Tools for years. Some have been fixed by rewriting, some removed, and some >> fixed by upgrading the infrastructure (eg., giving slave nodes more RAM or >> more disk). > > I can't agree more that flaky tests should be addressed at all costs. But > it's a reality today, and having to re-trigger build of gerrit patchsets from > Jenkins can be tedious. This is just a little help (that shall not hinder the > effort to eradicate flaky tests) > >> >> Another way to manage this problem is to install the Naginator plugin to >> your JIPP: "Naginator is a plugin that schedules a new build immediately >> following a build failure, thereby nagging the project members that the >> build is failing." Can be configured to define number of rebuilds, frequency >> of rebuilds, etc. > > It is probably perfectly reasonable to run this plugin on the RedHat build > infra, but I must forbid this plugin on the Eclipse infra for the foreseeable > future. Some projects are already experiencing huge variation on their build > time during peak hours, such a plugin would just make it worse for everybody. > > We are working on isolating projects one from each other. Until then, thank > you for not using Naginator or similar plugin. > > Thanks. > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > <mailto:mikael.barb...@eclipse-foundation.org> > 🐦 @mikbarbero > >> >> >> >> >> On Mon, Mar 12, 2018 at 9:25 AM, Mikaël Barbero >> > <mailto:mikael.barb...@eclipse-foundation.org>> wrote: >> Hi, >> >> For those of you who use a JIPP to build Gerrit patch sets, you may have >> noticed that the user "Hudson CI" has been renamed to "CI Bot". This is >> purely cosmetic. >> >> Also, the documentation about how to setup the Gerrit trigger Jenkins plugin >> has been revamped and is now available here >> https://wiki.eclipse.org/Jenkins#Gerrit_Trigger_Plugin >> <https://wiki.eclipse.org/Jenkins#Gerrit_Trigger_Plugin> >> >> I would like to draw you attention to the possible triggers you can setup >> (https://wiki.eclipse.org/Jenkins#Configuration_of_Build_Triggers >> <https://wiki.eclipse.org/Jenkins#Configuration_of_Build_Triggers>). Many of >> you want to re-trigger a build when it fails (e.g., because of flaky tests). >> It can be tedious to have to go to Jenkins just to do that. The Gerrit >> trigger Jenkins plugin is not only able to trigger a build on a new patch >> set. It lets you define triggers on comment values (e.g., if a comment >> contains "run CI"). Have a look at the previous link for an example. >> >> Cheers, >> >> >> -- >> Mikaël Barbero - Eclipse Foundation >> IT Services - Release Engineering >> 📱 (+33) 642 028 039 >> 📧 mikael.barb...@eclipse-foundation.org >> <mailto:mikael.barb...@eclipse-foundation.org> >> 🐦 @mikbarbero >> >> >> ___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse
Re: [cross-project-issues-dev] Migration from Hudson to Jenkins is complete
We are about to submit a talk proposal to Eclipse Con France covering some of these topics ;) Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 15 mars 2018 à 12:59, Patrick Bänziger > a écrit : > > Thanks Frederic (and everyone who worked on this)! > > Wow, that is an amazing amount of Jenkins instances. > Maybe you could share some of your and the Foundations experience setting up > and operating such an enormous fleet of Jenkins? > I'm sure not only I and my colleagues, but also many others could profit of > your knowledge on how to run (setup, upgrade, monitoring, orchestration, ...) > so many Jenkins instances. > This would make a great blog post or series of posts! > > Regards, > Patrick > > > > -Original Message- > From: cross-project-issues-dev-boun...@eclipse.org > [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Frederic > Gurr > Sent: Donnerstag, 15. März 2018 12:25 > To: Cross project issues > Subject: [cross-project-issues-dev] Migration from Hudson to Jenkins is > complete > > Hi, > > As of March 1st, 2018, all 180 Hudson instances (HIPPs) have been > migrated to a recent LTS version of Jenkins. There were a few minor (and > expected) hiccups, but in general it went pretty smoothly. > > If you still find an issue that might be related to the migration, > please file a Bugzilla issue. > > We are currently in the process of bringing the build infrastructure to > the next level, to better utilize the available hardware and reduce > maintenance efforts. Expect to hear more details about this in the near > future. > > Thanks for your patience. > > > Regards, > > Fred > > -- > Frederic Gurr > > Release Engineer > Eclipse Foundation > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Gerrit and Jenkins, tips and news
> I would argue that the more tedious problem is having tests that sometimes > fail. I've been waging a war against intermittent test failures in JBoss > Tools for years. Some have been fixed by rewriting, some removed, and some > fixed by upgrading the infrastructure (eg., giving slave nodes more RAM or > more disk). I can't agree more that flaky tests should be addressed at all costs. But it's a reality today, and having to re-trigger build of gerrit patchsets from Jenkins can be tedious. This is just a little help (that shall not hinder the effort to eradicate flaky tests) > > Another way to manage this problem is to install the Naginator plugin to your > JIPP: "Naginator is a plugin that schedules a new build immediately following > a build failure, thereby nagging the project members that the build is > failing." Can be configured to define number of rebuilds, frequency of > rebuilds, etc. It is probably perfectly reasonable to run this plugin on the RedHat build infra, but I must forbid this plugin on the Eclipse infra for the foreseeable future. Some projects are already experiencing huge variation on their build time during peak hours, such a plugin would just make it worse for everybody. We are working on isolating projects one from each other. Until then, thank you for not using Naginator or similar plugin. Thanks. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > > > > > On Mon, Mar 12, 2018 at 9:25 AM, Mikaël Barbero > <mailto:mikael.barb...@eclipse-foundation.org>> wrote: > Hi, > > For those of you who use a JIPP to build Gerrit patch sets, you may have > noticed that the user "Hudson CI" has been renamed to "CI Bot". This is > purely cosmetic. > > Also, the documentation about how to setup the Gerrit trigger Jenkins plugin > has been revamped and is now available here > https://wiki.eclipse.org/Jenkins#Gerrit_Trigger_Plugin > <https://wiki.eclipse.org/Jenkins#Gerrit_Trigger_Plugin> > > I would like to draw you attention to the possible triggers you can setup > (https://wiki.eclipse.org/Jenkins#Configuration_of_Build_Triggers > <https://wiki.eclipse.org/Jenkins#Configuration_of_Build_Triggers>). Many of > you want to re-trigger a build when it fails (e.g., because of flaky tests). > It can be tedious to have to go to Jenkins just to do that. The Gerrit > trigger Jenkins plugin is not only able to trigger a build on a new patch > set. It lets you define triggers on comment values (e.g., if a comment > contains "run CI"). Have a look at the previous link for an example. > > Cheers, > > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > <mailto:mikael.barb...@eclipse-foundation.org> > 🐦 @mikbarbero > > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > <mailto:cross-project-issues-dev@eclipse.org> > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> > > > > -- > Nick Boldt > Senior Software Engineer, RHCSA > Productization Lead :: JBoss Tools & Dev Studio > IM: @nickboldt / @nboldt / http://nick.divbyzero.com > <http://nick.divbyzero.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > @ @redhatnews <https://twitter.com/redhatnews> Red Hat > <https://www.facebook.com/RedHatInc> > <https://www.facebook.com/RedHatInc> > > > “The Only Thing That Is Constant Is Change” - Heraclitus > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Gerrit and Jenkins, tips and news
Hi, For those of you who use a JIPP to build Gerrit patch sets, you may have noticed that the user "Hudson CI" has been renamed to "CI Bot". This is purely cosmetic. Also, the documentation about how to setup the Gerrit trigger Jenkins plugin has been revamped and is now available here https://wiki.eclipse.org/Jenkins#Gerrit_Trigger_Plugin <https://wiki.eclipse.org/Jenkins#Gerrit_Trigger_Plugin> I would like to draw you attention to the possible triggers you can setup (https://wiki.eclipse.org/Jenkins#Configuration_of_Build_Triggers <https://wiki.eclipse.org/Jenkins#Configuration_of_Build_Triggers>). Many of you want to re-trigger a build when it fails (e.g., because of flaky tests). It can be tedious to have to go to Jenkins just to do that. The Gerrit trigger Jenkins plugin is not only able to trigger a build on a new patch set. It lets you define triggers on comment values (e.g., if a comment contains "run CI"). Have a look at the previous link for an example. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] EPL-2.0 feature license available from CBI repository
There is no "in time" notion here. Updating from EPL-1.0 to EPL-2.0 is not compelled by any process ;) > Le 26 févr. 2018 à 15:56, Ed Willink a écrit : > > Hi > > Perhaps the helpful copyright tooling that I use every year at about RC2 will > be updated in time to offer EPL 2.0 upgrading. > > Regards > > Ed Willink > > On 26/02/2018 14:46, Mikaël Barbero wrote: >> Note that changing the license feature from 1.0 to 2.0 will not enough >> either. You will need to update your notice and license files, and also your >> files headers. The FAQ https://www.eclipse.org/legal/epl-2.0/faq.php >> <https://www.eclipse.org/legal/epl-2.0/faq.php> and the handbook >> http://www.eclipse.org/projects/handbook/#legaldoc >> <http://www.eclipse.org/projects/handbook/#legaldoc> are authoritative >> sources for those issues. >> >> Cheers, >> >> -- >> Mikaël Barbero - Eclipse Foundation >> IT Services - Release Engineering >> 📱 (+33) 642 028 039 >> 📧 mikael.barb...@eclipse-foundation.org >> <mailto:mikael.barb...@eclipse-foundation.org> >> 🐦 @mikbarbero >> >>> Le 26 févr. 2018 à 14:29, Ed Willink >> <mailto:e...@willink.me.uk>> a écrit : >>> >>> Hi >>> >>> Thanks. Not reading carefully enough. The license is forking from EPL 1.0 to >>> >>> EPL 2.0 (without Secondary License) >>> EPL 2.0 With Secondary License >>> >>> The former, 3.1 in the FAQ, is easy. The latter is hard. >>> >>> Regards >>> >>> Ed Willink >>> >>> On 26/02/2018 13:06, Zoltán Ujhelyi wrote: >>>> Hi, >>>> >>>> according to 3.1. How Do I Re-license from EPL-1.0 to EPL-2.0? [1] you >>>> don’t need to ask every contributor to allow relicensing to EPL 2.0; but >>>> it is a good idea to consult with your current contributors and notify >>>> your users. >>>> >>>> Best regards, >>>> Zoltán >>>> >>>> [1] https://www.eclipse.org/legal/epl-2.0/faq.php#h.tci84nlsqpgw >>>> <https://www.eclipse.org/legal/epl-2.0/faq.php#h.tci84nlsqpgw> >>>> -- Zoltán Ujhelyi >>>> >>>> Eclipse Technologies Expert >>>> IncQueryLabs Ltd. >>>> >>>>> On 2018. Feb 26., at 14:02, Ed Willink >>>> <mailto:e...@willink.me.uk>> wrote: >>>>> >>>>> Hi >>>>> >>>>> Since my builds pull the license directly from >>>>> http://download.eclipse.org/cbi/updates/license/ >>>>> <http://download.eclipse.org/cbi/updates/license/> I thought this should >>>>> be really easy, but then I started reading >>>>> https://www.eclipse.org/legal/epl-2.0/faq.php >>>>> <https://www.eclipse.org/legal/epl-2.0/faq.php> >>>>> >>>>> For Eclipse OCL, the IP log lists 20 authors some of whom are no longer >>>>> active Eclipse users. Am I right in thinking that until I have a >>>>> re-licensing approval from all 20 out of 20 authors, Eclipse OCL must >>>>> remain at EPL 1.0? >>>>> >>>>> Regards >>>>> >>>>> Ed Willink >>>>> >>>>> On 26/02/2018 12:39, Mikaël Barbero wrote: >>>>>> Hi, >>>>>> >>>>>> A feature license for EPL-2.0 is now available from the following p2 >>>>>> repositories >>>>>> >>>>>> http://download.eclipse.org/cbi/updates/license/ >>>>>> <http://download.eclipse.org/cbi/updates/license/> (aggregated) >>>>>> >>>>>> and directly from >>>>>> >>>>>> http://download.eclipse.org/cbi/updates/license/2.0.0.v20180130-0820 >>>>>> <http://download.eclipse.org/cbi/updates/license/2.0.0.v20180130-0820> >>>>>> >>>>>> See https://www.eclipse.org/legal/epl-2.0/ >>>>>> <https://www.eclipse.org/legal/epl-2.0/> and >>>>>> https://www.eclipse.org/legal/epl-2.0/faq.php >>>>>> <https://www.eclipse.org/legal/epl-2.0/faq.php> for details about EPL >>>>>> 2.0. >>>>>> >>>>>> Cheers, >>>>>> >>>>>> -- >>>>>> Mikaël Barbero - Eclipse Foundation >>&
Re: [cross-project-issues-dev] EPL-2.0 feature license available from CBI repository
Note that changing the license feature from 1.0 to 2.0 will not enough either. You will need to update your notice and license files, and also your files headers. The FAQ https://www.eclipse.org/legal/epl-2.0/faq.php <https://www.eclipse.org/legal/epl-2.0/faq.php> and the handbook http://www.eclipse.org/projects/handbook/#legaldoc <http://www.eclipse.org/projects/handbook/#legaldoc> are authoritative sources for those issues. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 26 févr. 2018 à 14:29, Ed Willink a écrit : > > Hi > > Thanks. Not reading carefully enough. The license is forking from EPL 1.0 to > > EPL 2.0 (without Secondary License) > EPL 2.0 With Secondary License > > The former, 3.1 in the FAQ, is easy. The latter is hard. > > Regards > > Ed Willink > > On 26/02/2018 13:06, Zoltán Ujhelyi wrote: >> Hi, >> >> according to 3.1. How Do I Re-license from EPL-1.0 to EPL-2.0? [1] you don’t >> need to ask every contributor to allow relicensing to EPL 2.0; but it is a >> good idea to consult with your current contributors and notify your users. >> >> Best regards, >> Zoltán >> >> [1] https://www.eclipse.org/legal/epl-2.0/faq.php#h.tci84nlsqpgw >> -- Zoltán Ujhelyi >> >> Eclipse Technologies Expert >> IncQueryLabs Ltd. >> >>> On 2018. Feb 26., at 14:02, Ed Willink wrote: >>> >>> Hi >>> >>> Since my builds pull the license directly from >>> http://download.eclipse.org/cbi/updates/license/ I thought this should be >>> really easy, but then I started reading >>> https://www.eclipse.org/legal/epl-2.0/faq.php >>> >>> For Eclipse OCL, the IP log lists 20 authors some of whom are no longer >>> active Eclipse users. Am I right in thinking that until I have a >>> re-licensing approval from all 20 out of 20 authors, Eclipse OCL must >>> remain at EPL 1.0? >>> >>> Regards >>> >>> Ed Willink >>> >>> On 26/02/2018 12:39, Mikaël Barbero wrote: >>>> Hi, >>>> >>>> A feature license for EPL-2.0 is now available from the following p2 >>>> repositories >>>> >>>> http://download.eclipse.org/cbi/updates/license/ (aggregated) >>>> >>>> and directly from >>>> >>>> http://download.eclipse.org/cbi/updates/license/2.0.0.v20180130-0820 >>>> >>>> See https://www.eclipse.org/legal/epl-2.0/ and >>>> https://www.eclipse.org/legal/epl-2.0/faq.php for details about EPL 2.0. >>>> >>>> Cheers, >>>> >>>> -- >>>> Mikaël Barbero - Eclipse Foundation >>>> IT Services - Release Engineering >>>> 📱 (+33) 642 028 039 >>>> 📧 mikael.barb...@eclipse-foundation.org >>>> 🐦 @mikbarbero >>>> >>>> >>>> >>>> ___ >>>> cross-project-issues-dev mailing list >>>> >>>> cross-project-issues-dev@eclipse.org >>>> >>>> To change your delivery options, retrieve your password, or unsubscribe >>>> from this list, visit >>>> >>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >>> >>> Virus-free. www.avast.com >>> ___ >>> cross-project-issues-dev mailing list >>> cross-project-issues-dev@eclipse.org >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> ___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] EPL-2.0 feature license available from CBI repository
Hi, A feature license for EPL-2.0 is now available from the following p2 repositories http://download.eclipse.org/cbi/updates/license/ <http://download.eclipse.org/cbi/updates/license/> (aggregated) and directly from http://download.eclipse.org/cbi/updates/license/2.0.0.v20180130-0820 <http://download.eclipse.org/cbi/updates/license/2.0.0.v20180130-0820> See https://www.eclipse.org/legal/epl-2.0/ <https://www.eclipse.org/legal/epl-2.0/> and https://www.eclipse.org/legal/epl-2.0/faq.php <https://www.eclipse.org/legal/epl-2.0/faq.php> for details about EPL 2.0. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Issues with windows7tests slave on Shared JIPP
We're working There is no ETA yet. Thanks for your patience. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 21 févr. 2018 à 10:46, Sravan K Lakkimsetti a > écrit : > > Hi Fred, > > We have issue with Mac machine also. The Xvnc utility is not getting invoked > anymore. Raised Bug 531436 - Xvnc failure on shared hipp > > Thanks > Sravan > > -Original Message- > From: Frederic Gurr [mailto:frederic.g...@eclipse-foundation.org > <mailto:frederic.g...@eclipse-foundation.org>] > Sent: Wednesday, February 21, 2018 4:14 AM > To: Cross project issues > Subject: [cross-project-issues-dev] Issues with windows7tests slave on Shared > JIPP > > Hi, > > After migrating the Shared Hudson instance > (https://urldefense.proofpoint.com/v2/url?u=https-3A__ci.eclipse.org_shared&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=BbJ1i82pNJnkXoEbqK7sZDkJsrJ7wkY_no7y0H4rMzE&m=bAp6atU0ZyHeDA8S8oonh72YTE2PIGToLDQD0mROSRA&s=7suQTRu4LFxcyD5OqQG0qQ05r3nilc8YDWi4sayGtkc&e= > > <https://urldefense.proofpoint.com/v2/url?u=https-3A__ci.eclipse.org_shared&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=BbJ1i82pNJnkXoEbqK7sZDkJsrJ7wkY_no7y0H4rMzE&m=bAp6atU0ZyHeDA8S8oonh72YTE2PIGToLDQD0mROSRA&s=7suQTRu4LFxcyD5OqQG0qQ05r3nilc8YDWi4sayGtkc&e=>) > to Jenkins we are facing some connection problems between the windows7tests > slave and the Shared JIPP (master). > > Therefore the windows7tests slave is currently offline. > We will continue to investigate. > > > Regards, > > Fred > > > -- > Frederic Gurr > > Release Engineer > Eclipse Foundation > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_cross-2Dproject-2Dissues-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=BbJ1i82pNJnkXoEbqK7sZDkJsrJ7wkY_no7y0H4rMzE&m=bAp6atU0ZyHeDA8S8oonh72YTE2PIGToLDQD0mROSRA&s=0pUnrWJcGUZVFRo2GTvx0iBr8Nrbs2-DXda7At3vi0k&e= > > <https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_cross-2Dproject-2Dissues-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=BbJ1i82pNJnkXoEbqK7sZDkJsrJ7wkY_no7y0H4rMzE&m=bAp6atU0ZyHeDA8S8oonh72YTE2PIGToLDQD0mROSRA&s=0pUnrWJcGUZVFRo2GTvx0iBr8Nrbs2-DXda7At3vi0k&e=> > > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] New environment variables on CI instances
Hi, [TL;DR: no impact for 99.9% of projects] Yesterday, we've setup a couple of environment variables on all CI instances at Eclipse. It ensures that default values for max heap size and java temp dir are set to sensible values. The environment variables are the following: JAVA_TOOL_OPTIONS JAVA_OPTS MAVEN_OPTS ANT_OPTS The values of all these environment variables are the same: "-Xmx2G -Djava.io.tmpdir=/tmp/" For most of projects, it should not change anything. But for those who are parsing the output of the JVM at startup, it will introduce some new outputs (like JDT, see [1]). Indeed, when JAVA_TOOL_OPTIONS is defined, most JDKs (Oracle, OpenJDK, probably IBM's as well) print the following line to stderr: Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/ This is unavoidable except if you unset the environment variable. Please don't do that except very extraordinary cases. The reasoning for setting JAVA_TOOL_OPTIONS on the CI instances is to easily prevent java to define on its own the max heap size. By default on most JVM implementation, it's something like 25% of the machine RAM. CI instances at Eclipse currently runs on machines with 64GB or 128GB of RAM, making the default value way too high for a shared environment. Setting JAVA_TOOL_OPTIONS is our only way to make the default a more sensible one for every single Java process spawned by builds. Making sure that projects actually pass a sensible value is an impossible task otherwise. Of course, any project can decide to override the default values by specifying a different one on the command line. E.g., giving a different -Xmx on the command line will override the value from JAVA_TOOL_OPTIONS. Thanks [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=530634 -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Some CI services are unavailable (HIPP5)
All CI instances are up and running since 11am. The issue is detailed in https://bugs.eclipse.org/bugs/show_bug.cgi?id=530422 Thanks for your patience. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 29 janv. 2018 à 09:09, Mikaël Barbero > a écrit : > > We currently investigating an issue with the hipp5 machine. Projects on the > following list are affected: > > tools.cdt > technology.golo > technology.package-drone > technology.collections > eclipse.jdt.ls > modeling.emfservices > technology.microprofile > technology.tm4e > polarsys.polarsys.time4sys > technology.reddeer > technology.sensinact > soa.bpel > technology.tigerstripe > modeling.gemoc > technology.openj9 > technology.tea > technology.osbp > You can track the issue on > https://bugs.eclipse.org/bugs/show_bug.cgi?id=530422 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=530422> > > Thanks for your patience. > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > <mailto:mikael.barb...@eclipse-foundation.org> > 🐦 @mikbarbero > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Some CI services are unavailable (HIPP5)
We currently investigating an issue with the hipp5 machine. Projects on the following list are affected: tools.cdt technology.golo technology.package-drone technology.collections eclipse.jdt.ls modeling.emfservices technology.microprofile technology.tm4e polarsys.polarsys.time4sys technology.reddeer technology.sensinact soa.bpel technology.tigerstripe modeling.gemoc technology.openj9 technology.tea technology.osbp You can track the issue on https://bugs.eclipse.org/bugs/show_bug.cgi?id=530422 Thanks for your patience. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] HTMLPrinter is Broken
Ed, My answers below > I think that this is the path paved with good intentions. Sure it is. I wish for the peace in world (even if it is the road to Hell) :) > We'll need to start at the bottom, in the Equinox runtime. For example, > we'll need to change a great many things in p2 before PDE works again; we'll > also need to change many things in p2 so that Oomph works again, we'll need > to change a great many things in Oomph itself so that it works again, we'll > need to do a whole heck of a lot of in JDT (likely leaving no time to make > JDT better for the end-user) and so on, and so on, until everyone on the > entire end-to-end internal food chain is exhausted. Then we'll inflict this > pain on the bad, very bad external community, who will likely also become > exhausted negotiating API before using it. At that point we'll find out we > made mistakes at the start of the chain, and then we will ripple the > next set of API changes through the system. In a few years we'll arguably > have the world's most shining gem, the best in the world, of all possible > worlds. After all, with 20/20 hindsight we can make everything perfect. The > result will conform to all principles of greatness beyond impeach. But more > than likely we'll have little or no community left. The users won't care at > all, those that are left, using the tools that have migrated and still > actually work, because the users won't see the underlying greatness of the > shining gem we have created. And the developers, those that are left, will > wonder if the Eclipse desktop platform is really such a great place to target > for development. > Did I make you think that we should remove all current internal API and, as such change everything / everywhere? Sorry if that is the case. For existing internals that we don't want to change, everything should stay as is. I suggest to not export any new internal code to prevent the phenomenon in new code. And for existing internals, I suggest to have a lightweight deprecation policy. Finally, I suggest to have a well defined best practice about how to provide new "unstable/beta" APIs. The goal is to communicate that one can use it, but it can change anytime until they are "production ready". Currently, the best practice is to mix it up with internal code, but IMO it's a bad practice (as you said earlier, the migration from internal to API is too disruptive). Cheers, signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] HTMLPrinter is Broken
> Le 25 janv. 2018 à 10:22, Lars Vogel a écrit : > > > Should we change our policy and stop exporting new internal packages so > > that they really cannot be used? > > -2, we want to enable extenders to use and explore code before making it API. > IMHO a good way to provide new API is by having it already been explored by > users. Are internal packages really a way to provide not yet stabilized APIs? IMO it should be done with a new package and/or bundle with a low version number (like 0.x)? internal should be for internal (sic), i.e., for implementation details. Also, if you use internal to test new API, there are chances that if your new API is successful you will never move it outside the a.b.c.internal package because you will have too many unhappy users. Of course, I was only talking about new internal packages, as existing should stay exported, with the x-internal directive. > > > And for existing internal that one wants to change/remove, we should > > probably go with a deprecation policy like for "real" API. > > This may be a joke, but if that was a serious suggestion, -2 to that > proposal. Not being able to freely change internals is a horrible suggestion > as this would effectively prevent all new development activities. No, it is serious and qualifying it as a joke may be unnecessary. I guess that your -2 was enough to state that you strongly disagree with me. Let me rephrase it in case I've mis-explained myself: I don't suggest that we cannot and shouldn't be free to modify internals. I say that, as long as existing internals can be used, they are de facto API. When we want to do a breaking change to these internals, maybe we should have a rule to give clients a little time to move away from this code. I did not made it explicit in my previous mail, but the deprecation policy for such code should be much shorter than for real API. My guess is that it is exactly what you've done by reverting the change in HTMLPrinter for Ed M. So, why not making it a clear policy for existing internal code. Of course, this is annoying and it slows down development. But IMO if one wants more freedom in changing internals, one needs to protect it by not exporting it or do no evil to your user. So again, I suggest that new internal code should be placed in new packages which won't be exported in the first place (see explanation above). To sum up, my overall proposition would be to acknowledge that we have different categories of API, each with a associated deprecation policy: - public API: same deprecation policy as today - existing internal packages (those which are exported with the x-internal directives): lightweight deprecation/removal policy. e.g., deprecate it in version x (say the September release) and, if marked for removal, could be deleted in version x+1 (December release). I guess that with the new platform release schedule, it won't slow down development too much. - all new internal code should go to non exported packages: private code that can change anytime. - beta/testing/new APIs should go to new packages, exported as public API with version number < 1 and which can change anytime. WDYT? signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] HTMLPrinter is Broken
Very interesting thread, thanks to all for sharing your opinion. Changing existing internals could break clients because so far, they can use it. Should we change our policy and stop exporting new internal packages so that they really cannot be used? And for existing internal that one wants to change/remove, we should probably go with a deprecation policy like for "real" API. Maybe the deprecation period before change/deletion will not be as long as for "real" API, but I guess we would get best of both worlds with such a policy, isn't it? WDYT? Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 25 janv. 2018 à 07:37, Ed Merks a écrit : > > Leo, > > While I agree in principle, the principles lead down a path where I'm sure no > one really wants to go; it is the path paved with good intentions. > > Specific comments below. > > On 24.01.2018 18:24, Leo Ufimtsev wrote: >> Hello Ed, >> >> On Wed, Jan 24, 2018 at 7:27 AM, Ed Merks > <mailto:ed.me...@gmail.com>> wrote: >> I'm a more than little annoyed to see that this method >> >> org.eclipse.jface.internal.text.html.HTMLPrinter.insertPageProlog(StringBuffer, >> int, RGB, RGB, String) >> >> I understand your frustration, we sometimes have to deal with similar >> problems. >> E.g when Gtk makes changes to their methods, it breaks SWT and causes >> glitches in Eclipse. >> >> But: >> >> As the package suggests, it's an internal method: >> org.eclipse.jface.internal.text.html. >> 'Internal' means it's not suppose to be used by public. > Yes, the point of "internal" has been hammered upon, but it's a general > point, like human rights, and of course we all agree the humans should have > plenty of those. But it strays far and wide from the specific problem at > hand. The irony of the specific problem is apparent is when you look at the > call hierarchy of the methods in question. They're not used internally at > all, unless JDT is considered internal, which it clearly is not. As a result > of JDT's trending setting example, you'll find uses of this in any code that > tries to have really nice hover information like JDT does. Given there bugs > are open asking for it to be API, it's clear there are clients of this > specific code. Yes, they're all bad, very bad. > > Of course I empathize with Lars' efforts to make improvements, and I have in > fact helped him in part with those changes, so I more than resent arguments > that I personally stand in the way of the platform's great progress. Of > course I could have been less of a jerk in how I phrased my opinion on this > specific change. Sorry for that. >> >> If you wish to use internal api because it's useful to you, then you should >> first put in effort to make >> the api public and only then use it. Not use it and then complain about it's >> removal. > Yes, the human rights issue again. The Bugzilla record speaks for itself > though as does the call hierarchy of the methods, which makes it clear they > exist to be used outside of the project that provides them. Had this high > standard been applied to JDT, we'd not have this problem. There simple is a > double standard. Had we applied this standard when developing Oomph, there > would be no Oomph. So while it's a high and mighty principle that one cannot > argue against without the wrath of the human rights activists protesting at > your door, it's simply not pragmatic and has not been well applied by the > overall Eclipse PMC itself. > > And again, the specifics of the problem StringBuffer -> StringBuilder; of > course a trivial change, one that I can change in two minutes in EMF, but not > without maintaining my compatible version ranges in EMF. >> >> Because you chose to use internal api, and your suggestion to revert the >> code removal, you are slowing down platform >> development and by extension slowing down the whole Eclipse development >> process. > Yes, I see it's a significant human rights violation. But I thought I did my > part for human rights when I changed EMF's templates to generate > StringBuilder in places such as the generated toString() method of each > EClass. > > I know JDT, Dani and his team, are very careful with changing internals > because they know many clients use them, and they know that while making > rapid progress is great, if they behave disruptively because they have the > intrinsic righ
Re: [cross-project-issues-dev] Gerrit internal server errors
Secondary index seems to be corrupted. We may need to run reindex. Will keep you posted. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 17 déc. 2017 à 11:55, Mikaël Barbero > a écrit : > > Thanks for the heads up. > > I'm having a look. > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > <mailto:mikael.barb...@eclipse-foundation.org> > 🐦 @mikbarbero > >> Le 17 déc. 2017 à 11:44, Matthias Sohn > <mailto:matthias.s...@gmail.com>> a écrit : >> >> Gerrit seems to be in trouble, see >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=528863 >> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=528863> >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=528864 >> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=528864> >> >> -Matthias >> ___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Gerrit internal server errors
Thanks for the heads up. I'm having a look. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 17 déc. 2017 à 11:44, Matthias Sohn a écrit : > > Gerrit seems to be in trouble, see > https://bugs.eclipse.org/bugs/show_bug.cgi?id=528863 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=528863> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=528864 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=528864> > > -Matthias > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] [Resolved] Issue with signing services
Hi, The signing services have been flaky for the last couple of hours (issue with the reverse proxy which had to be restarted) They are now fully operational. Thanks. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Unplanned maintenance today at 11am EST of macOS signing and packaging services
Security update has been installed. All services are operational. Thanks. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 11 déc. 2017 à 15:17, Mikaël Barbero > a écrit : > > Hi, > > Due to security update and the associated reboot, the macOS signing and > packaging services will be down for a couple of minutes. > > No further disruption is expected. > > The maintenance will happen today at 11am EST. > > Thanks. > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > <mailto:mikael.barb...@eclipse-foundation.org> > 🐦 @mikbarbero > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Unplanned maintenance today at 11am EST of macOS signing and packaging services
Hi, Due to security update and the associated reboot, the macOS signing and packaging services will be down for a couple of minutes. No further disruption is expected. The maintenance will happen today at 11am EST. Thanks. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] macOS signing/dmg packaging services are down
All services are operating normally. Thanks for your patience. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 8 déc. 2017 à 09:24, Mikaël Barbero > a écrit : > > Hi, > > We're experiencing issues with the macOS signing and DMG packaging services. > > We're investigating. > > Thanks. > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > <mailto:mikael.barb...@eclipse-foundation.org> > 🐦 @mikbarbero > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] macOS signing/dmg packaging services are down
Hi, We're experiencing issues with the macOS signing and DMG packaging services. We're investigating. Thanks. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] HIPP7 is offline
All systems are back online. Thanks. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 7 déc. 2017 à 09:09, Mikaël Barbero > a écrit : > > Hi, > > We're experiencing an outage with the HIPP7 machine. All projects running on > it are affected (list below). We're investigating. > > technology.tycho > modeling.ecp > modeling.upr > technology.sisu > modeling.edapt > rt.gemini > technology.cbi > iot.smarthome > modeling.eatop > technology.handly > polarsys.polarsys.kitalpha > technology.n4js > science.texlipse > soa.winery > technology.elogbook > eclipse.pde > > -- > Mikaël Barbero - Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > <mailto:mikael.barb...@eclipse-foundation.org> > 🐦 @mikbarbero > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] HIPP7 is offline
Hi, We're experiencing an outage with the HIPP7 machine. All projects running on it are affected (list below). We're investigating. technology.tycho modeling.ecp modeling.upr technology.sisu modeling.edapt rt.gemini technology.cbi iot.smarthome modeling.eatop technology.handly polarsys.polarsys.kitalpha technology.n4js science.texlipse soa.winery technology.elogbook eclipse.pde -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Concurrent jobs @ Travis CI
Hi, The Eclipse Foundation is happy to announce that we raised the number of concurrent jobs that projects (within the Eclipse organization) could run @ Travis CI. We've added 10 concurrent jobs, raising it from 5 to 15. It should help diminish the length of the queue for projects building @ Travis CI (see https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg14306.html <https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg14306.html> for the original issue). Let us know what you think. Cheers, -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Spam bugs on all platform projects
Thanks. I should have said that we've blocked most of the spam traffic. > Le 26 sept. 2017 à 15:56, Eric Williams a écrit : > > Also: > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=422969#c12 > > Eric > > On 09/26/2017 09:11 AM, Daniel Megert wrote: >> There is still spam coming in! >> _Bug 524411_ <https://bugs.eclipse.org/524411>: Free-It!Watch Stephen King's >> It Online - 2017 Full Movie Free >> Dani >> From: Mikaël Barbero >> To: Cross project issues >> Date: 26.09.2017 14:50 >> Subject: Re: [cross-project-issues-dev] Spam bugs on all platform projects >> Sent by: cross-project-issues-dev-boun...@eclipse.org >> >> Bugzilla is on again, spammers should have been blocked. Clean up is ongoing. >> Le 26 sept. 2017 à 11:38, Mikaël Barbero >> <_mikael.barbero@eclipse-foundation.org_ >> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit : >> Bugzilla has been turned off while we are solving the spam issue. Thanks for >> your understanding. >> Le 26 sept. 2017 à 10:45, Kaloyan Raev <_kaloyan.r@zend.com_ >> <mailto:kaloya...@zend.com>> a écrit : >> It's a real flood going right now. >> Perhaps, it would be best to block the creation of new Eclipse accounts and >> then block all existing spam accounts. After stopping this flood something >> better can be done. >> *Kaloyan Raev**| Zend Studio Team Lead** >> Rogue Wave Software, Inc.*/ >> Innovate with Confidence/* >> M* +359 887 648 663_ >> __www.roguewave.com_ <http://www.roguewave.com/>/ >> _kaloyan.raev@roguewave.com_ <mailto:kaloyan.r...@roguewave.com> >> On 09/26/2017 09:57 AM, Lars Vogel wrote: >> In the past we marked such bugs as dup's of Bug 442999. >> HTH >> Am 26.09.2017 8:17 vorm. schrieb "Mikaël Barbero" >> <_mikael.barbero@eclipse-foundation.org_ >> <mailto:mikael.barb...@eclipse-foundation.org>>: >> We're looking into it and will mitigate the attack ASAP. >> Thanks. >> -- >> *Mikaël Barbero - *Eclipse Foundation >> IT Services - Release Engineering >> 📱 (+33) 642 028 039 >> 📧 _mikael.barbero@eclipse-foundation.org_ >> <mailto:mikael.barb...@eclipse-foundation.org> >> 🐦 @mikbarbero >> Le 26 sept. 2017 à 07:07, Ed Merks <_ed.merks@gmail.com_ >> <mailto:ed.me...@gmail.com>> a écrit : >> Yes, also using a different account _tllr@taglead.com_ >> <mailto:t...@taglead.com>, so they have multiple accounts: >> _https://bugs.eclipse.org/bugs/buglist.cgi?email1=tllr%40taglead.com&emailreporter1=1&emailtype1=substring&list_id=16795840&query_format=advanced_ >> On 26.09.2017 06:48, Sravan K Lakkimsetti wrote: >> Hi, >> We are getting SPAM bugs from _markv@watchmtv.co_ >> <mailto:ma...@watchmtv.co>on all platform projects. Please disable this ID. >> Thanks >> Sravan >> ___ >> cross-project-issues-dev mailing list >> _cross-project-issues-dev@eclipse.org_ >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> _https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_ >> ___ >> cross-project-issues-dev mailing list_ >> __cross-project-issues-dev@eclipse.org_ >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit_ >> __https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_ >> ___ >> cross-project-issues-dev mailing list_ >> __cross-project-issues-dev@eclipse.org_ >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit_ >> __https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_ >> ___ >> cross-project-issues-dev mailing list >> _cross-project-issues-dev@eclipse.org_ >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> _https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_ >> ___ >> cross-project-issues-dev mailing list_ >> __cros
Re: [cross-project-issues-dev] Spam bugs on all platform projects
Bugzilla is on again, spammers should have been blocked. Clean up is ongoing. > Le 26 sept. 2017 à 11:38, Mikaël Barbero > a écrit : > > Bugzilla has been turned off while we are solving the spam issue. Thanks for > your understanding. > > >> Le 26 sept. 2017 à 10:45, Kaloyan Raev > <mailto:kaloya...@zend.com>> a écrit : >> >> It's a real flood going right now. >> >> Perhaps, it would be best to block the creation of new Eclipse accounts and >> then block all existing spam accounts. After stopping this flood something >> better can be done. >> >> Kaloyan Raev | Zend Studio Team Lead >> Rogue Wave Software, Inc. >> Innovate with Confidence >> M +359 887 648 663 >> www.roguewave.com <http://www.roguewave.com/> / kaloyan.r...@roguewave.com >> <mailto:kaloyan.r...@roguewave.com> >> >> On 09/26/2017 09:57 AM, Lars Vogel wrote: >>> In the past we marked such bugs as dup's of Bug 442999. >>> >>> HTH >>> >>> Am 26.09.2017 8:17 vorm. schrieb "Mikaël Barbero" >>> >> <mailto:mikael.barb...@eclipse-foundation.org>>: >>> We're looking into it and will mitigate the attack ASAP. >>> >>> Thanks. >>> >>> -- >>> Mikaël Barbero - Eclipse Foundation >>> IT Services - Release Engineering >>> 📱 (+33) 642 028 039 >>> 📧 mikael.barb...@eclipse-foundation.org >>> <mailto:mikael.barb...@eclipse-foundation.org> >>> 🐦 @mikbarbero >>> >>>> Le 26 sept. 2017 à 07:07, Ed Merks >>> <mailto:ed.me...@gmail.com>> a écrit : >>>> >>>> Yes, also using a different account t...@taglead.com >>>> <mailto:t...@taglead.com>, so they have multiple accounts: >>>> https://bugs.eclipse.org/bugs/buglist.cgi?email1=tllr%40taglead.com&emailreporter1=1&emailtype1=substring&list_id=16795840&query_format=advanced >>>> >>>> <https://bugs.eclipse.org/bugs/buglist.cgi?email1=tllr%40taglead.com&emailreporter1=1&emailtype1=substring&list_id=16795840&query_format=advanced> >>>> >>>> On 26.09.2017 06:48, Sravan K Lakkimsetti wrote: >>>>> Hi, >>>>> >>>>> We are getting SPAM bugs from ma...@watchmtv.co >>>>> <mailto:ma...@watchmtv.co> on all platform projects. Please disable this >>>>> ID. >>>>> >>>>> Thanks >>>>> Sravan >>>>> >>>>> >>>>> >>>>> ___ >>>>> cross-project-issues-dev mailing list >>>>> cross-project-issues-dev@eclipse.org >>>>> <mailto:cross-project-issues-dev@eclipse.org> >>>>> To change your delivery options, retrieve your password, or unsubscribe >>>>> from this list, visit >>>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >>>>> <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> >>>> ___ >>>> cross-project-issues-dev mailing list >>>> cross-project-issues-dev@eclipse.org >>>> <mailto:cross-project-issues-dev@eclipse.org> >>>> To change your delivery options, retrieve your password, or unsubscribe >>>> from this list, visit >>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >>>> <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> >>> >>> ___ >>> cross-project-issues-dev mailing list >>> cross-project-issues-dev@eclipse.org >>> <mailto:cross-project-issues-dev@eclipse.org> >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >>> <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> >>> >>> >>> ___ >>> cross-project-issues-dev mailing list >>> cross-project-issues-dev@eclipse.org >>> <mailto:cross-project-issues-dev@eclipse.org> >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >>> <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> >> ___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Spam bugs on all platform projects
Bugzilla has been turned off while we are solving the spam issue. Thanks for your understanding. > Le 26 sept. 2017 à 10:45, Kaloyan Raev a écrit : > > It's a real flood going right now. > > Perhaps, it would be best to block the creation of new Eclipse accounts and > then block all existing spam accounts. After stopping this flood something > better can be done. > > Kaloyan Raev | Zend Studio Team Lead > Rogue Wave Software, Inc. > Innovate with Confidence > M +359 887 648 663 > www.roguewave.com <http://www.roguewave.com/> / kaloyan.r...@roguewave.com > <mailto:kaloyan.r...@roguewave.com> > > On 09/26/2017 09:57 AM, Lars Vogel wrote: >> In the past we marked such bugs as dup's of Bug 442999. >> >> HTH >> >> Am 26.09.2017 8:17 vorm. schrieb "Mikaël Barbero" >> > <mailto:mikael.barb...@eclipse-foundation.org>>: >> We're looking into it and will mitigate the attack ASAP. >> >> Thanks. >> >> -- >> Mikaël Barbero - Eclipse Foundation >> IT Services - Release Engineering >> 📱 (+33) 642 028 039 >> 📧 mikael.barb...@eclipse-foundation.org >> <mailto:mikael.barb...@eclipse-foundation.org> >> 🐦 @mikbarbero >> >>> Le 26 sept. 2017 à 07:07, Ed Merks >> <mailto:ed.me...@gmail.com>> a écrit : >>> >>> Yes, also using a different account t...@taglead.com >>> <mailto:t...@taglead.com>, so they have multiple accounts: >>> https://bugs.eclipse.org/bugs/buglist.cgi?email1=tllr%40taglead.com&emailreporter1=1&emailtype1=substring&list_id=16795840&query_format=advanced >>> >>> <https://bugs.eclipse.org/bugs/buglist.cgi?email1=tllr%40taglead.com&emailreporter1=1&emailtype1=substring&list_id=16795840&query_format=advanced> >>> >>> On 26.09.2017 06:48, Sravan K Lakkimsetti wrote: >>>> Hi, >>>> >>>> We are getting SPAM bugs from ma...@watchmtv.co <mailto:ma...@watchmtv.co> >>>> on all platform projects. Please disable this ID. >>>> >>>> Thanks >>>> Sravan >>>> >>>> >>>> >>>> ___ >>>> cross-project-issues-dev mailing list >>>> cross-project-issues-dev@eclipse.org >>>> <mailto:cross-project-issues-dev@eclipse.org> >>>> To change your delivery options, retrieve your password, or unsubscribe >>>> from this list, visit >>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >>>> <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> >>> ___ >>> cross-project-issues-dev mailing list >>> cross-project-issues-dev@eclipse.org >>> <mailto:cross-project-issues-dev@eclipse.org> >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >>> <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> >> >> ___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> >> >> >> ___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev signature.asc Description: Message signed with OpenPGP ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Spam bugs on all platform projects
We're looking into it and will mitigate the attack ASAP. Thanks. -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 26 sept. 2017 à 07:07, Ed Merks a écrit : > > Yes, also using a different account t...@taglead.com > <mailto:t...@taglead.com>, so they have multiple accounts: > > https://bugs.eclipse.org/bugs/buglist.cgi?email1=tllr%40taglead.com&emailreporter1=1&emailtype1=substring&list_id=16795840&query_format=advanced > > <https://bugs.eclipse.org/bugs/buglist.cgi?email1=tllr%40taglead.com&emailreporter1=1&emailtype1=substring&list_id=16795840&query_format=advanced> > > On 26.09.2017 06:48, Sravan K Lakkimsetti wrote: >> Hi, >> >> We are getting SPAM bugs from ma...@watchmtv.co <mailto:ma...@watchmtv.co> >> on all platform projects. Please disable this ID. >> >> Thanks >> Sravan >> >> >> >> ___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > <mailto:cross-project-issues-dev@eclipse.org> > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] [epp-dev] [platform-releng-dev] Issue with the macOS bundle signing, dmg packaging and signing
Hi, I'm glad to announced that the macOS services (.app signing, .dmg packaging and .dmg signing) have been restored on a new machine hosted within the Foundation VLAN. If you've disabled their usages, you can now re-enable them as it was before. The authentication layer I was talking about in my initial mail will be released later to possibly let us use resources outside of the Foundation VLAN. We will keep you posted. Thanks for your patience while we were resolving this issue. Cheers, Mikael -- Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 📧 mikael.barb...@eclipse-foundation.org 🐦 @mikbarbero > Le 11 sept. 2017 à 19:56, Denis Roy a > écrit : > > Hi Dani, > > Just a clarification -- the current (broken) Mac services are hosted on our > hardware. We are working on two fronts -- > 1. Provision a temporary new Mac to re-establish the current service > > 2. Provision managed/hosted Mac services to avoid these problems in the > future, as our in-house hardware is not redundant, and does not scale. > > > In the immediate terms, you can disable the signing parts in your build > scripts for basically no cost, as signing is likely not needed on I-builds, > nor to validate test results. > Mikael has offered to manually sign your the last release candidates so that > release deadlines can be met. > > > I apologize for the inconveniences this causes, and thank you for your > continued patience while we resolve this issue and make it better. > > > Denis > > > On 11/09/17 08:14 AM, Daniel Megert wrote: >> Can you explain why this critical/blocking hardware is hosted outside the >> Eclipse Foundation, creating more/new issues and delays? Our automated >> builds don't play well with filing bugs (for signing and DMG creation) and >> wait for resolution ;-). Ah, and BTW, our latest Photon M2 candidate build >> just failed again: >> http://download.eclipse.org/eclipse/downloads/drops4/I20170911-0405/ >> <http://download.eclipse.org/eclipse/downloads/drops4/I20170911-0405/> >> >> Dani >> >> >> >> From:Mikaël Barbero >> <mailto:mikael.barb...@eclipse-foundation.org> >> To:"Eclipse platform release engineering list." >> <mailto:platform-releng-...@eclipse.org>, >> Eclipse Packaging Project <mailto:epp-...@eclipse.org> >> Cc:Webmaster <mailto:webmas...@eclipse.org>, >> Cross project issues >> <mailto:cross-project-issues-dev@eclipse.org> >> Date:07.09.2017 14:07 >> Subject:[platform-releng-dev] Issue with the macOS bundle signing, >> dmg packaging and signing >> Sent by:platform-releng-dev-boun...@eclipse.org >> <mailto:platform-releng-dev-boun...@eclipse.org> >> >> >> >> (cross-posting to platform-releng, epp-dev and cross-projects) >> >> Hi, >> >> Recently, we've been facing a lot of issues with the services we provide for >> macOS: UI testing, macOS .app bundles signing and DMG files creation and >> signing. It has been a combination of hardware, software and network >> failures and these issues have already impacted some projects, delaying >> their milestones/releases and consuming a lot of time from their teams. >> >> Since the beginning of the week, we've setup a new machine to run UI tests >> from the Hudson shared instance (https://hudson.eclipse.org/shared/ >> <https://hudson.eclipse.org/shared/>). This machine is not hosted on our >> infra, and thus not everything that was possible can be done on the new >> machine (most notably, it's not possible to access machines inside the >> Eclipse VLAN). We still need to figure out if we want to make it possible, >> or if we want to set this fact as a restriction. >> >> We've also successfully deployed and tested the signing and dmg packaging >> services on a similar machine. Unfortunately, we can't switch the current >> unreliable services to these new ones as they are also hosted outside of the >> Eclipse VLAN. As you may know, the services are insecure webapps (read plain >> HTTP) without any sort of authentication. We were using the fact that the >> services were running inside the VLAN to "protect" them. Only Eclipse >> projects and committers were both trusted to use the service by having >> access to the VLAN via their Hudson/Jenkins instance. >> >> Opening the new services on a machine directly connected to the internet >> would let anyone sign a macOS application wit
