Re: [cross-project-issues-dev] Please test your builds with maven 3.8.5 / Fwd: [VOTE] Release Apache Maven version 3.8.5

[Mikael Barbero]

Given that 3.8.5 is not released yet, I'm not keen on adding it to Foundation's 
Jenkins.

Also, as I guess it would be for a one shot test, it's just as easy for 
projects to test their build locally.

If you *really* want to test in your Jenkins pipeline, maven's .tar.gz can 
always be downloaded as part of your job and unarchived somewhere in your 
workspace:

$ curl -sSJOLf 
https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.5/binaries/apache-maven-3.8.5-bin.tar.gz
 

$ tar zxf apache-maven-3.8.5-bin.tar.gz
$ export PATH="$(pwd)/apache-maven-3.8.5/bin:${PATH}"
$ mvn -v
Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
...

which not much more than changing your pipeline to select a different version 
of the "maven" jenkins tooling.



Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 6 Mar 2022, at 11:04, Dietrich, Christian  
> wrote:
> 
> Can this be provided on Jenkins ?
> 
> Christoph Läubrich mailto:lae...@laeubi-soft.de>> 
> schrieb am So. 6. März 2022 um 10:24:
> Tycho will soon require 3.8.5 due to crucial enhancements in the maven API.
> 
> So I'd like to ask everyone to test their builds with the upcoming maven
> 3.8.5 what could be found here:
> 
> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.5/ 
> 
> 
> Please report any issue to the maven dev list or the JIRA as soon as
> possible.
> 
> 
>  Weitergeleitete Nachricht 
> Betreff: [VOTE] Release Apache Maven version 3.8.5
> Datum: Sat, 5 Mar 2022 17:47:12 +0100
> Von: Michael Osipov mailto:micha...@apache.org>>
> Antwort an: Maven Developers List  >
> An: Maven Developers List  >
> 
> Hi,
> 
> We solved 27 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12351105
>  
> 
> 
> There are still hundreds of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved
>  
> 
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1724/ 
> 
> 
> Dev dist directory:
> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.5/ 
> 
> 
> Source release checksums:
> apache-maven-3.8.5-src.zip sha512:
> 7edb6864834a81c11cf9d22a8110abc3f5f96360bdbc4bc33ec0c98dc389dd9fc71465253a87729dbe7b8a011b2ec38afa0e011172657c3a97ef96fb6f40292b
> apache-maven-3.8.5-src.tar.gz sha512:
> 1aa1b2dcba794b7e4cbc8e2ff9baf64283fb3883ae93efff26fe259578504b60a8b68404a074f4741922e462fa696cbbe71f9d74e4e6316ed0e389d25667
> 
> Binary release checksums:
> apache-maven-3.8.5-bin.zip sha512:
> f9f838b4adaf23db0204a6cafa52bf1125bd2d649fd676843fd05e82866b596ec19c4f3de60d5e3ff17f10a63d96c141311ff9bc2bfa816eade7a5cbff2bd925
> apache-maven-3.8.5-bin.tar.gz sha512:
> 89ab8ece99292476447ef6a6800d9842bbb60787b9b8a45c103aa61d2f205a971d8c3ddfb8b03e514455b4173602bd015e82958c0b3ddc1728a57126f773c743
> 
> Draft for release notes:
> https://github.com/apache/maven-site/pull/292 
> 
> 
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html 
> 
> 
> Vote open until 2021-03-13T12:00Z
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org 
> 
> For additional commands, e-mail: dev-h...@maven.apache.org 
> 
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org 
> 
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev 
> 
> --
> Christian Dietrich (Diplom-Informatiker (BA))
> Softwareentwickler / -Architekt
> Committer and Co-Lead for Eclipse Xtext
> 
> Tel.: +49 (0) 711 / 34 21 91-0
> Fax.: +49 (0) 711 / 34 21 91-29
> Mobil: +49 (0) 151 / 173969 17
> Mail: christian.dietr...@itemis.de 
> XING: https://www.xing.com/profile/Christian_Dietrich8 
> 
> Web: http://www.itemis.de 

Re: [cross-project-issues-dev] P2 site mirror for Eclipse builds

[Mikael Barbero]

I get it is frustrating that suddenly it stops working while you did not change 
anything but Git(hub) repositories are no files servers and should not be 
abused like so.

You should contact the original author and ask him to publish his p2 repository 
to a proper file service. It could be github releases or github pages. Those 
are not rate limited AFAICT.


Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 22 Feb 2022, at 09:24, Christian Pontesegger 
>  wrote:
> 
>> as long as you don't use raw.githubusercontent.com, you should have
>> no issue.
> 
> and now we are facing the same issue with exactly such a page:
> 
> "No repository found at
> https://github.com/bartdag/py4j-eclipse-udpate-site/raw/master;
> 
> curl
> https://github.com/bartdag/py4j-eclipse-udpate-site/raw/master/artifacts.jar
> 
> You are being  href="https://raw.githubusercontent.com/bartdag/py4j-eclipse-udpate-site/master/artifacts.jar
> ">redirected.
> 
> What do we do about that one?
> 
> Christian
> 
> 
> 
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] P2 site mirror for Eclipse builds

[Mikael Barbero]

> On 21 Feb 2022, at 15:41, Christian Pontesegger 
>  wrote:
> 
> Coming back to my original question:
> 
>> So the question is whether eclipse provides some means of buffering,
>> eg
>> through artifactory? If not: under which circomstances could we
>> mirror
>> the p2 and provide it as jenkins artifacts?
> 
> Do we have an artifactory at eclipse which could provide a mirror of
> the p2 site?

No.

> 
> If not, under which circumstances are we allowed to eg use a mirror
> script and keep a copy of the affected p2 site on our jenkins instance
> @ eclipse?

Jenkins is not a file server and should not be used as one. If you need

Please open a ticket on the helpdesk 
(https://gitlab.eclipse.org/eclipsefdn/helpdesk 
) about your original issue 
"Sometimes the external site cannot be queried" with some details as, as long 
as you don't use raw.githubusercontent.com , 
you should have no issue.

Thanks

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] P2 site mirror for Eclipse builds

[Mikael Barbero]

Released artifacts are not limited as repository contents could be 
https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases#storage-and-bandwidth-quotas

My earlier comment about raw.githubusercontent.com was red herring.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation 
and Collaboration

> On 21 Feb 2022, at 14:03, Frederic Gurr 
>  wrote:
> 
> Hi Jonah,
> 
> You are right. I completely forgot about how P2 works. 臘‍♂️
> 
> When I use wget to fetch
> https://github.com/fabioz/Pydev/releases/download/pydev_9_2_0/content.jar I
> see a redirect to
> https://objects.githubusercontent.com/[..].
> 
> Not sure if the same rules and restrictions apply for
> objects.githubusercontent.com as for raw.githubusercontent.com.
> 
> Regards,
> 
> Fred
> 
> 
> On 21.02.22 13:47, Jonah Graham wrote:
>> Hi Fred,
>> 
>> p2 doesn't try to fetch the root at all, it fetches, for e.g.
>> https://github.com/fabioz/Pydev/releases/download/pydev_9_2_0/content.jar
>> which does work.
>> 
>> HTH, Jonah
>> 
>> 
>> 
>> 
>> On Mon., Feb. 21, 2022, 07:40 Frederic Gurr,
>> > <mailto:frederic.g...@eclipse-foundation.org>> wrote:
>> 
>> Hi,
>> 
>> This seems to be unrelated to the issues with
>> raw.githubusercontent.com <http://raw.githubusercontent.com> and
>> probably won't be fixed with API access.
>> 
>> https://github.com/fabioz/Pydev/releases/download/pydev_9_2_0/
>> returns a plain 404 in my browser.
>> https://github.com/fabioz/Pydev/releases/download/pydev_9_1_0/ and
>> https://github.com/fabioz/Pydev/releases/download/pydev_9_0_1/ also
>> return 404s. At the same time
>> https://github.com/fabioz/Pydev/releases/download/pydev_9_2_0/PyDev.9.2.0.zip
>> 
>> 
> works fine. Same for the 9.1.0 and the 9.0.1 release.
>> 
>> Please get in touch with user https://github.com/fabioz to fix this.
>> I suspect that GitHub has changed the rules how release artifacts
>> are served (e.g. no more read permissions on the parent
>> directories).
>> 
>> Regards,
>> 
>> Fred
>> 
>> P.S.: The Ease project does not have it's own GitHub bot because we
>> usually add this for projects that have repos at GitHub only. If you
>> still want to request it, please open a ticket here:
>> https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues
>> 
>> 
>> On 21.02.22 12:23, Christian Pontesegger wrote:
>>> 
>>> Am Montag, dem 21.02.2022 um 10:33 +0100 schrieb Mikael Barbero:
>>>> I guess you're using raw.githubusercontent.com
>> <http://raw.githubusercontent.com>?
>>> 
>>> We are using following location:
>>> 
>>> "Unable to read repository at http://www.pydev.org/updates. No
>>> repository found at
>>> https://github.com/fabioz/Pydev/releases/download/pydev_9_2_0.;
>>> 
>>>> See
>>>> 
>> https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/912#note_570694
>> 
>> 
>>> for some infos.
>>> 
>>> Can give it a try if api.github.com <http://api.github.com> is
>> able to deliver p2 site content.
>>> How can I register for an API token using my eclipse build bot?
>>> FYI: project is hosted on Eclipse Gerrit!
>>> https://ci.eclipse.org/ease/
>>> 
>>> thanks Christian
>>> 
>>> 
>>> ___
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@eclipse.org
>> <mailto:cross-project-issues-dev@eclipse.org>
>>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>> 
>> 
>> -- Frederic Gurr Release Engineer | Eclipse Foundation Europe GmbH
>> 
>> Berliner Allee 47, D-64295 Darmstadt Handelsregister: Darmstadt HRB
>> 92821 Managing Directors: Gaël Blondelle, Mike Milinkovich
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> <mailto:cross-project-issues-dev@eclipse.org> To unsubscribe from
>> this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>> 
>> 
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org To unsubscribe from this list,
>> visit
&g

Re: [cross-project-issues-dev] P2 site mirror for Eclipse builds

[Mikael Barbero]

I guess you're using raw.githubusercontent.com 
? See 
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/912#note_570694 
 for 
some infos.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 21 Feb 2022, at 10:18, Andrey Loskutov  wrote:
> 
> Same for platform builds, they fail on regular base trying to read some 
> (checked in) files from github repository and fail with zero data received.
> 
> See for example
> https://ci.eclipse.org/releng/view/Automated%20tests/job/ep423I-unit-cen64-gtk3-java11/121/console
> https://ci.eclipse.org/releng/view/Automated%20tests/job/ep423I-unit-cen64-gtk3-java17/121/console
> 
> Not sure if our webmaster can do here anything, or is this just a generic 
> github reliability issue?
> 
> Kind regards,
> Andrey Loskutov
> 
> Спасение утопающих - дело рук самих утопающих
> 
> https://www.eclipse.org/user/aloskutov
> 
> 
>> Gesendet: Montag, 21. Februar 2022 um 10:12 Uhr
>> Von: "Christian Pontesegger" 
>> An: "Cross project issues" 
>> Betreff: [cross-project-issues-dev] P2 site mirror for Eclipse builds
>> 
>> Hi,
>> 
>> we are facing some build issues with EASE and Tracecompass projects:
>> both depend on an external p2 site hosted on github. Sometimes the
>> external site cannot be queried, probably due to quota issues on
>> github?
>> 
>> So the question is whether eclipse provides some means of buffering, eg
>> through artifactory? If not: under which circomstances could we mirror
>> the p2 and provide it as jenkins artifacts?
>> 
>> thanks
>> Christian
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Travis CI deprecation and removal notice

[Mikael Barbero]

Dear committers, dear community,

With a 1 month grace period, we have removed the Travis CI app(s) from all 
GitHub organizations that the Eclipse Foundation manages. We also denied those 
apps access to organizations data.

Note that we also activated "access restrictions 
<https://docs.github.com/en/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions>"
 on a few organizations that had no restriction. It only concerns old 
organizations as access restrictions are enabled by default for new 
organizations for a long time now. It may lead to misbehaviors of some apps. 
Feel free to request permissions for those via GitHub 
<https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps>
 or just open tickets at https://gitlab.eclipse.org/eclipsefdn/helpdesk 
<https://gitlab.eclipse.org/eclipsefdn/helpdesk> to get support.

Thanks.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation 
and Collaboration

> On 21 Sep 2021, at 15:36, Mikael Barbero 
>  wrote:
> 
> Dear committers, dear community,
> 
> Since its acquisition by a private equity firm [1], Travis CI’s quality of 
> service has decreased drastically.
> 
> Recently, Travis CI suffered from a flaw that exposed secrets of thousands of 
> open source projects [2]. The way the incident has been handled is 
> unacceptable and supports the idea that Travis CI is in very low maintenance 
> mode. We are currently scanning our organizations / repositories and we will 
> reach out to projects that could have been affected by this flaw.
> 
> In addition to this security issue, Travis CI has lowered its free OSS 
> offering: while ceasing travis-ci.org <http://travis-ci.org/> in favor of 
> travis-ci.com <http://travis-ci.com/>, they changed their pricing model [3, 
> 4] and now only offer a fixed, one time amount of free credits for open 
> source. Once consumed, one needs to beg for more. This causes issues in many 
> OSS projects [5]. Projects hosted by the Eclipse Foundation are also 
> concerned, and bug 574335 [6] is one example of the issue. We expect many 
> more similar ones.
> 
> When we asked for renewable credits, we got the following answer:
> 
> > Thanks for your reply, at the current moment our OSS credit grants are a 
> > manual
> > process. When your credits begin running low again, please reach back out 
> > to the
> > Support team.
> 
> That would not be too much of a bummer if the credits were allocated to all 
> the organizations we manage, but this is on a per organization basis. It 
> means we would need to follow credits evolution and send those requests for 
> each organization running low on credits. This does not scale.
> 
> Due to the issues mentioned above, the Eclipse Foundation will stop 
> supporting Travis CI on GitHub organizations it manages. From now on, we 
> won't configure any new repository / organization and we plan on removing the 
> TravisCI GitHub app from all organizations we manage on October 20th. If you 
> still rely on Travis CI to build your projects, feel free to reach out to us, 
> we can help you migrate to our in-house Jenkins farm 
> https://wiki.eclipse.org/Jenkins <https://wiki.eclipse.org/Jenkins>.
> 
> Thanks.
> 
> [1] https://blog.travis-ci.com/2019-01-23-travis-ci-joins-idera-inc 
> <https://blog.travis-ci.com/2019-01-23-travis-ci-joins-idera-inc>
> [2] 
> https://arstechnica.com/information-technology/2021/09/travis-ci-flaw-exposed-secrets-for-thousands-of-open-source-projects/
>  
> <https://arstechnica.com/information-technology/2021/09/travis-ci-flaw-exposed-secrets-for-thousands-of-open-source-projects/>
> [3] https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing 
> <https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing>
> [4] https://blog.travis-ci.com/oss-announcement 
> <https://blog.travis-ci.com/oss-announcement>
> [5] 
> https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works
>  
> <https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works>
> [6] https://bugs.eclipse.org/bugs/show_bug.cgi?id=574335 
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=574335>
> 
> 
> 
> Mikaël Barbero
> Manager — Release Engineering and Technology | Eclipse Foundation
>  @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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Travis CI deprecation and removal notice

[Mikael Barbero]

Dear committers, dear community,

Since its acquisition by a private equity firm [1], Travis CI’s quality of 
service has decreased drastically.

Recently, Travis CI suffered from a flaw that exposed secrets of thousands of 
open source projects [2]. The way the incident has been handled is unacceptable 
and supports the idea that Travis CI is in very low maintenance mode. We are 
currently scanning our organizations / repositories and we will reach out to 
projects that could have been affected by this flaw.

In addition to this security issue, Travis CI has lowered its free OSS 
offering: while ceasing travis-ci.org in favor of travis-ci.com, they changed 
their pricing model [3, 4] and now only offer a fixed, one time amount of free 
credits for open source. Once consumed, one needs to beg for more. This causes 
issues in many OSS projects [5]. Projects hosted by the Eclipse Foundation are 
also concerned, and bug 574335 [6] is one example of the issue. We expect many 
more similar ones.

When we asked for renewable credits, we got the following answer:

> Thanks for your reply, at the current moment our OSS credit grants are a 
> manual
> process. When your credits begin running low again, please reach back out to 
> the
> Support team.

That would not be too much of a bummer if the credits were allocated to all the 
organizations we manage, but this is on a per organization basis. It means we 
would need to follow credits evolution and send those requests for each 
organization running low on credits. This does not scale.

Due to the issues mentioned above, the Eclipse Foundation will stop supporting 
Travis CI on GitHub organizations it manages. From now on, we won't configure 
any new repository / organization and we plan on removing the TravisCI GitHub 
app from all organizations we manage on October 20th. If you still rely on 
Travis CI to build your projects, feel free to reach out to us, we can help you 
migrate to our in-house Jenkins farm https://wiki.eclipse.org/Jenkins.

Thanks.

[1] https://blog.travis-ci.com/2019-01-23-travis-ci-joins-idera-inc 

[2] 
https://arstechnica.com/information-technology/2021/09/travis-ci-flaw-exposed-secrets-for-thousands-of-open-source-projects/
 

[3] https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing 

[4] https://blog.travis-ci.com/oss-announcement 

[5] 
https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works
 

[6] https://bugs.eclipse.org/bugs/show_bug.cgi?id=574335 




Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] download.eclipse.org unavailable

[Mikael Barbero]

Most fallout from last weekend outage have been resolved. If you still 
experience issues, feel free to (re-)open tickets about said issues.

Thanks for your patience while those issues were worked out.

Please be assured that a postmortem about this major incident will be posted 
once the summer break is over (next week).

Regards,

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 4 Aug 2021, at 12:31, Frederic Gurr  
> wrote:
> 
> Hi,
> Eclipse Foundation staff is on summer break this week and therefore 
> connectivity is limited for some of us, including the IT team.
> I currently cannot asses which issues are still the aftermath of the outage 
> on Sunday. I will be able to take a look in a few hours.
> 
> Obviously the timing of the outage, M2 week and the EF summer break is very 
> unfortunate. We will try to asses and hopefully fix the issues as soon as we 
> can.
> 
> Regards,
> Fred
> 
> 
> On Wed, 4 Aug 2021, 10:26 Sebastian Zarnekow,  > wrote:
> Given that Wayne announced on the committer mailing list last Friday that
> 
> FYI, the Eclipse Foundation will be shut down for the entire first week of 
> August (2-6). During this time period, the EMO IP Team will not process CQs 
> and responses to email requests to the EMO, EMO IP Team, and EMO Records 
> teams will be delayed.
> 
> I suspect that people are really not reachable even in case of an 
> infrastructure disaster.
> 
> I think the best we can do right now is to learn from the post-mortem and 
> implement mitigations afterwards.
> 
> Best
> Sebastian
> 
> 
> On Wed, Aug 4, 2021 at 9:54 AM Ed Merks  > wrote:
> Christoph ,
> 
> I  can only speculate about what's going on but speculation will get us 
> nowhere.  Suffice to say that I am deeply and fundamentally concerned both by 
> the state of our infrastructure and even more so by the complete silence from 
> the Foundation.
> 
> I have tried to reach out yesterday to gain more information, and to suggest 
> that information be posted to the community, but so far without success...
> 
> It would appear to me that we will not be able to get m2 completed today 
> because I'm not sure any of us can do a build and promote the results right 
> now.  Certainly I cannot, at this point, do any of my usual activities for 
> m2, no new version of Oomph, no new installers, no product catalog updates...
> 
> Regards,
> Ed
> 
> 
> On 04.08.2021 08:52, Christoph Läubrich wrote:
>> > but I guess there is still a major problem with eclipse.org 
>> >  infrastructure.
>> 
>> It would be good to have at least some more information, the status page 
>> says 'A fix has been implemented and we are monitoring the results' but this 
>> is two days old and still we see massive outages, updatesites are broken, CI 
>> builds are even not running, we get bug reports about broken functionality, 
>> that's really annoying and frustrating.
>> 
>> Am 03.08.21 um 18:17 schrieb Andrey Loskutov:
>>> See https://www.eclipsestatus.io/ 
>>> 
>>> Some basic website functionality seem to be restored, but mailing lists / 
>>> message sending seem to be still broken across different services.
>>> I received few random (I guess not all) mails from bugzilla, but I guess 
>>> there is still a major problem with eclipse.org  
>>> infrastructure.
>>> 
>>> 
>>> Am 2. August 2021 14:02:03 MESZ schrieb Laurent Goubet 
>>>  :
 Hello,
 
 All builds we started this morning (5 hours ago CEST) have failed with
 issues trying to reach download.eclipse.org  
 in one way or another, two
 examples of which are:
 
 - |Caused by: java.io.FileNotFoundException:
 https://download.eclipse.org/releases/2019-09/compositeContent.jar| 
 
 -|||java.io.FileNotFoundException: Neither
 https://download.eclipse.org/tools/orbit/downloads/drops/R20190602212107/repository/compositeContent.jar
  
 
 nor
 https://download.eclipse.org/tools/orbit/downloads/drops/R20190602212107/repository/compositeContent.xml|
  
 
 
 When we tried to access these repositories through a browser, we
 initially got a 403 error.
 |https://download.eclipse.org/releases/2019-09| 
  now seems to partially
 load (all icons are broken) but
 

Re: [cross-project-issues-dev] Linux Tools build cannot write to standard output location

[Mikael Barbero]

There is an ongoing outage of the infra. Please see http://eclipsestatus.io

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 3 Aug 2021, at 20:36, Jeff Johnston  wrote:
> 
> Hello,
> 
> Something has changed in the build infrastructure since last week and our 
> Linux Tools master build pipeline is failing when it tries to write to the 
> standard updates-nightly output directory we use.
> 
> Is there something we can do or is this a new infrastructure issue?  I didn't 
> see any posting about anything other than the removal of git protocol which I 
> had fixed last week and the jar signer plug-in version which we exceed.
> 
> -- Jeff J.
> 
> [Pipeline] // stage
> [Pipeline] stage
> [Pipeline] { (Deploy)
> [Pipeline] sshagent
> [ssh-agent] Using credentials genie.linuxtools 
> (ssh://genie.linuxto...@projects-storage.eclipse.org 
> )
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Exec ssh-agent (binary ssh-agent on a remote machine)
> $ ssh-agent
> SSH_AUTH_SOCK=/tmp/ssh-JKaxH65G7Ffd/agent.1134
> SSH_AGENT_PID=1136
> Running ssh-add (command line suppressed)
> Identity added: 
> /home/jenkins/agent/workspace/linuxtools-master@tmp/private_key_13458881067364320014.key
>  
> (/home/jenkins/agent/workspace/linuxtools-master@tmp/private_key_13458881067364320014.key)
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> + ssh genie.linuxto...@projects-storage.eclipse.org 
>  rm -rf 
> '/home/data/httpd/download.eclipse.org/linuxtools/updates-nightly/* 
> '
> Permission denied, please try again.
> Permission denied, please try again.
> genie.linuxto...@projects-storage.eclipse.org 
> : Permission denied 
> (publickey,password).
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] git rollback?

[Mikael Barbero]

The last weekend's outage was on our primary backend storage (where repos 
hosted at git.eclipse.org  are stored). The outage 
started at 9:20pm/9:30pm EDT on July 31st.

Since then, live replicas have been rsync'd back. What you see is apparent data 
loss. I don't have any information whether this is due to how the storage has 
been restored. I cannot tell you if we have more up-to-date data that could be 
restored for your git repo.

Hopefully, the date/time of the outage given above should help you gather the 
required clues to bring back a working git repo.


Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 4 Aug 2021, at 10:23, Andrey Loskutov  wrote:
> 
> For SDK work coordination I've created
> 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=575230
> 
> 
> Kind regards,
> Andrey Loskutov
> 
> Спасение утопающих - дело рук самих утопающих
> 
> https://www.eclipse.org/user/aloskutov
> 
> 
> Gesendet: Mittwoch, 04. August 2021 um 10:06 Uhr
> Von: "Stephan Herrmann" 
> An: cross-project-issues-dev@eclipse.org
> Betreff: Re: [cross-project-issues-dev] git rollback?
> I think affected teams should now safe guard all clones on individual 
> machines, and wait until the IT team signals that systems are back to stable, 
> really.
> 
> At that time we may need to re-push lost commits from our local clones. 
> Perhaps even some lost tags are available from local clones.
> 
> For that task of re-pushing, teams may need to coordinate, which commits in 
> which order need to be re-played. A good indicator is the "Tested-by" line in 
> commit messages, which signals a commit that has once gone through the gerrit 
> exercise and thus should be seen as part of the "official" history. A 
> bugzilla query for recently resolved bugs would be helpful - if bugzilla 
> queries are reliable again.
> 
> For now, waiting and not pushing anything seems to be the best strategy, 
> right?
> 
> Stephan
> 
> On 04.08.21 08:38, Ed Willink wrote:
> Hi Sravan
> 
> In the absence of any clues from the IT team can you please identify the time 
> to which GIT / downloads have been rolled back so that we can all be aware of 
> what is, at least currently, lost at the EF.
> 
> Regards
> 
> Ed Willink
> 
> On 04/08/2021 06:36, Sravan K Lakkimsetti wrote:
> Platform I-build from July 31(last successful build for platform) has gone 
> missing https://download.eclipse.org/eclipse/downloads/drops4/I20210731-1800/ 
>  also 
> related git tags gone missing from the repository.
> 
> Thanks and Regards,
> Sravan
> 
> Sravan Kumar Lakkimsetti
> IBM India Pvt Ltd,
> Embassy Golf Links Business Park, C Block,
> Off Indiranagar-Kormangla Inner Ring Road,
> Bangalore - 560071, India
> 
> "Ed Willink" ---04-08-2021 10:00:35---Hi Same for OCL.
> 
> From: "Ed Willink"  
> To: cross-project-issues-dev@eclipse.org 
> 
> Date: 04-08-2021 10:00
> Subject: [EXTERNAL] Re: [cross-project-issues-dev] git rollback?
> Sent by: "cross-project-issues-dev" 
>  
> 
> 
> 
> 
> Hi
> Same for OCL.
> 
> I pushed a branch commit that successfully refreshed everything on the branch 
> with the result that the IT team now need to resolve a merge of the rolled 
> back copy, the incremental backed up history and the post 'no-outage' changes.
> 
> Regards
> 
> Ed Willink
> 
> On 04/08/2021 02:34, Jonah Graham wrote:
> 
> 
> On Tue, 3 Aug 2021 at 18:25, Stephan Herrmann  > wrote:
> Has the jdt.core git been rolled back?
> 
> I don't know - it certainly looks like it. AFAIK the git URL links you posted 
> are mirrors of the gerrit repos. The gerrit repos are the primary IIUC. In 
> gerrit the referenced review is still active - 
> https://git.eclipse.org/r/c/jdt/eclipse.jdt.core/+/183569 
>  - so it looks 
> like gerrit took a step backwards, rather than just git by itself. For the 
> latter commit, the gerrit entry is "broken" 
> https://git.eclipse.org/r/c/jdt/eclipse.jdt.core/+/183573 
> 
> 
> Locally pulling doesn't provide anything newer than 2021-07-26.
> 
> Same for me.
> 
> 
> Is this an effect of the recent incident?
> 
> Probably, but I don't know. @Webmaster will have to comment.
> 
> 
> Any other project seeing similar effects?
> 
> Yes. CDT has at least one gerrit from July 31st that has lost a patchset and 
> associated comments. I have them in my email, but they are missing from 
> gerrit:
> 
> https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/183568 
> 
> 
> The 

Re: [cross-project-issues-dev] Cannot login into ci.eclipse.org

[Mikael Barbero via cross-project-issues-dev]

I've created https://www.eclipsestatus.io/incidents/yd3qyk7g0xj3 
 with the reported issues. 
We will provide update. over there (and on tweeter @Eclipse_Status 
)

Thanks for your patience.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 22 Jul 2021, at 08:58, Ed Merks  wrote:
> 
> I think it's hit or miss because it works for this:
> 
> https://ci.eclipse.org/oomph/ 
> But for these I get an error:
> 
> https://ci.eclipse.org/justj/loginError 
> 
> https://ci.eclipse.org/emf/loginError 
> And this "staging" instance doesn't seem to be able to launch any jobs:
> 
> https://ci-staging.eclipse.org/oomph/ 
> So I think something is wrong.
> 
> I also saw that https://bugs.eclipse.org/bugs/show_bug.cgi?id=573903 
>  got reopened so maybe 
> there's a more general problem with credentials and accounts...
> 
> Regards,
> Ed
> 
> On 22.07.2021 08:51, Ondrej Dockal wrote:
>> Hey everybody,
>> 
>> Do you happen to share the same issue as I do? I cannot log into 
>> ci.eclipse.org/myProject  Jenkins instance. 
>> Just simply throwing "Invalid username or password".
>> 
>> Is it something global?
>> 
>> Thanks.
>> 
>> Ondrej Dockal
>> RedDeer project lead
>> 
>> 
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org 
>> 
>> To unsubscribe from this list, visit 
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev 
>> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Signed down

[Mikael Barbero]

Fixed. Details at https://bugs.eclipse.org/bugs/show_bug.cgi?id=574482#c1 


Cheers,

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 27 Jun 2021, at 09:32, Ed Willink  wrote:
> 
> Hi
> 
> The signer is down
> 
> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=574482
> 
> Regards
> 
> Ed Willink
> 
> 
> --
> 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 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Apache Maven 3.8.1 is now available on Jenkins instances

[Mikael Barbero]

In addition to the desirable change about non secured access to repositories, 
3.8.1 has a bug that cause random build failure (see 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=574316).

As such, we've reverted the change: apache-maven-latest points to version 3.6.3.

Apache Maven 3.8.1 stays available for the more adventurous of you ;)

See https://wiki.eclipse.org/Jenkins#Apache_Maven for all available versions.

Cheers,


Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation 
and Collaboration

> On 21 Jun 2021, at 17:47, Andrey Loskutov  wrote:
> 
> Hi Mickael,
> 
> thanks for heads up!
> 
> Interesting, this could be the cause for other, random build failures we've 
> started to observe on friday on both gerrit / SDK build machines:
> 
> Internal error: java.lang.IllegalArgumentException: Malformed \u encoding
> 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=574316
> 
> Kind regards,
> Andrey Loskutov
> 
> Спасение утопающих - дело рук самих утопающих
> 
> https://www.eclipse.org/user/aloskutov
> 
> 
> Gesendet: Montag, 21. Juni 2021 um 17:23 Uhr
> Von: "Mikael Barbero" 
> An: "Common-build Developers discussion" 
> Cc: "Cross project issues" 
> Betreff: Re: [cross-project-issues-dev] Apache Maven 3.8.1 is now available 
> on Jenkins instances
> (cross posted to cross-projects issues).
> 
> There is a breaking change in Maven 3.8.1: it blocks non TLS repositories. If 
> you have plain http URL in your pom.xml to reference external repositories, 
> you may see errors like
> 
> 
> Could not transfer artifact 
> org.jboss.tools.tycho-plugins:repository-utils:pom:1.7.0 from/to 
> maven-default-http-blocker (http://0.0.0.0/ <http://0.0.0.0/>): Blocked 
> mirror for repositories: [jboss-public-repository-group 
> (http://repository.jboss.org/nexus/content/groups/public/ 
> <http://repository.jboss.org/nexus/content/groups/public/>, default, 
> releases+snapshots)]
> (from https://bugs.eclipse.org/bugs/show_bug.cgi?id=574364 
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=574364>)
> The solution is easy: switch to https:// scheme in your pom.xml, most public 
> maven repositories are available via TLS.
> 
> Thanks.
> Mikaël Barbero
> Manager — Release Engineering and Technology | Eclipse Foundation
>  @mikbarbero
> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
> Innovation and Collaboration
> 
> On 18 Jun 2021, at 08:53, Mikael Barbero 
>  <mailto:mikael.barb...@eclipse-foundation.org>> wrote:
> 
> As announced last month, apache-maven-latest has been upgraded to 3.8.1.
> 
> Thanks.
> 
> Mikaël Barbero
> Manager — Release Engineering and Technology | Eclipse Foundation
>  @mikbarbero
> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
> Innovation and Collaboration
> 
> On 21 May 2021, at 10:19, Mikael Barbero 
>  <mailto:mikael.barb...@eclipse-foundation.org>> wrote:
> 
> Hi
> 
> Maven 3.8.1 has been deployed to all Jenkins instances.
> 
> Note that apache-maven-latest stays at 3.6.3 for now. We will do the the 
> change once upcoming 2021.06 release is done to avoid any issue with build 
> script relying on latest.
> 
> Version details are available at 
> https://wiki.eclipse.org/Jenkins#Apache_Maven 
> <https://wiki.eclipse.org/Jenkins#Apache_Maven>
> 
> Cheers,
> 
> Mikaël Barbero
> Manager — Release Engineering and Technology | Eclipse Foundation
>  @mikbarbero
> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
> Innovation and Collaboration
> ___ cross-project-issues-dev 
> mailing list cross-project-issues-dev@eclipse.org To 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 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Apache Maven 3.8.1 is now available on Jenkins instances

[Mikael Barbero]

(cross posted to cross-projects issues).

There is a breaking change in Maven 3.8.1: it blocks non TLS repositories. If 
you have plain http URL in your pom.xml to reference external repositories, you 
may see errors like

Could not transfer artifact 
org.jboss.tools.tycho-plugins:repository-utils:pom:1.7.0 from/to 
maven-default-http-blocker (http://0.0.0.0/ <http://0.0.0.0/>): Blocked mirror 
for repositories: [jboss-public-repository-group 
(http://repository.jboss.org/nexus/content/groups/public/ 
<http://repository.jboss.org/nexus/content/groups/public/>, default, 
releases+snapshots)]
(from https://bugs.eclipse.org/bugs/show_bug.cgi?id=574364)
The solution is easy: switch to https:// scheme in your pom.xml, most public 
maven repositories are available via TLS.

Thanks.
Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation 
and Collaboration

> On 18 Jun 2021, at 08:53, Mikael Barbero 
>  wrote:
> 
> As announced last month, apache-maven-latest has been upgraded to 3.8.1.
> 
> Thanks.
> 
> Mikaël Barbero
> Manager — Release Engineering and Technology | Eclipse Foundation
>  @mikbarbero
> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
> Innovation and Collaboration
> 
>> On 21 May 2021, at 10:19, Mikael Barbero 
>> > <mailto:mikael.barb...@eclipse-foundation.org>> wrote:
>> 
>> Hi
>> 
>> Maven 3.8.1 has been deployed to all Jenkins instances.
>> 
>> Note that apache-maven-latest stays at 3.6.3 for now. We will do the the 
>> change once upcoming 2021.06 release is done to avoid any issue with build 
>> script relying on latest.
>> 
>> Version details are available at 
>> https://wiki.eclipse.org/Jenkins#Apache_Maven 
>> <https://wiki.eclipse.org/Jenkins#Apache_Maven>
>> 
>> Cheers,
>> 
>> Mikaël Barbero
>> Manager — Release Engineering and Technology | Eclipse Foundation
>>  @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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] gerrit permissions "unstable"

[Mikael Barbero]

We've had an issue with the LDAP cluster earlier today.

It has been fixed around 5am EDT.

Thanks.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 15 Jun 2021, at 05:51, Jonah Graham  wrote:
> 
> Hi folks,
> 
> I am getting weird errors when using gerrit that I share with you all in case 
> the problem isn't only me.
> 
> For example, intermediary "Authentication unavailable at this time" 
> (screenshot ) and 
> "You don't have permission to edit this label" (screenshot 
> ) on projects that I 
> should have permission for.
> 
> See Bug 574193  for 
> more info.
> 
> Regards,
> Jonah
> 
> 
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Emergency maintenance of repo.eclipse.org

[Mikael Barbero]

Hi,

https://repo.eclipse.org  has experienced short 
outages in the last 3 days (as you can see on our status page 
https://www.eclipsestatus.io/ ).

To avoid any further issue, we need to proceed with an emergency maintenance 
which require to take it down for about 2 hours.

We will do that today, starting at 1pm EDT (7pm CEST). Please follow 
https://www.eclipsestatus.io/incidents/mj5k74wx3cf7 
 in order to get updates 
about the maintenance.

Thank you.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Problems with signing service

[Mikael Barbero]

The time stamping server was unreachable for a couple of minutes which lead to 
the error you've had. It's now back online and the service is working properly.

Note that the time stamping service is not (and cannot be) provided by the 
Eclipse Foundation and we are not a time stamping authority (TSA), so we have 
to rely on external service.

Thanks.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation 
and Collaboration

> On 11 May 2021, at 09:26, Mikael Barbero 
>  wrote:
> 
> I'll have a look.
> 
> Mikaël Barbero
> Manager — Release Engineering and Technology | Eclipse Foundation
>  @mikbarbero
> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
> Innovation and Collaboration
> 
>> On 11 May 2021, at 06:57, Christian Dietrich > <mailto:christian.dietr...@itemis.de>> wrote:
>> 
>> Hi,
>> our curls to
>> 
>> https://cbi.eclipse.org/jarsigner/sign 
>> <https://cbi.eclipse.org/jarsigner/sign>
>> 
>> fail with error code 92 today.
>> https://ci.eclipse.org/xtext/job/releng/job/sign-and-deploy/983/console 
>> <https://ci.eclipse.org/xtext/job/releng/job/sign-and-deploy/983/console>
>> 
>> anybody else having problems with the signing service?
>> 
>> Thanks and Regards
>> Christian
>> 
>> Vorstand/Board: Jens Wagener (Vors./chairman), Dr. Stephan Eberle, 
>> Abdelghani El-Kacimi, Wolfgang Neuhaus, Franz-Josef Schuermann
>> Aufsichtsrat/Supervisory Board: Michael Neuhaus (Vors./chairman), Harald 
>> Goertz, Stephan Grollmann
>> Sitz der Gesellschaft/Registered Office: Am Brambusch 15-24, 44536 Lünen 
>> (Germany)
>> Registergericht/Registry Court: Amtsgericht Dortmund | HRB 20621
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org 
>> <mailto:cross-project-issues-dev@eclipse.org>
>> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Problems with signing service

[Mikael Barbero]

I'll have a look.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 11 May 2021, at 06:57, Christian Dietrich  
> wrote:
> 
> Hi,
> our curls to
> 
> https://cbi.eclipse.org/jarsigner/sign 
> 
> 
> fail with error code 92 today.
> https://ci.eclipse.org/xtext/job/releng/job/sign-and-deploy/983/console 
> 
> 
> anybody else having problems with the signing service?
> 
> Thanks and Regards
> Christian
> 
> Vorstand/Board: Jens Wagener (Vors./chairman), Dr. Stephan Eberle, Abdelghani 
> El-Kacimi, Wolfgang Neuhaus, Franz-Josef Schuermann
> Aufsichtsrat/Supervisory Board: Michael Neuhaus (Vors./chairman), Harald 
> Goertz, Stephan Grollmann
> Sitz der Gesellschaft/Registered Office: Am Brambusch 15-24, 44536 Lünen 
> (Germany)
> Registergericht/Registry Court: Amtsgericht Dortmund | HRB 20621
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Scheduled upgrade of a build cluster

[Mikael Barbero]

Hi,

We will be doing an upgrade of the new build cluster on April 30th (tomorrow) 
at 13:00 EDT.

We will be doing an upgrade of the new build cluster. Some Jenkins instances 
(the ones labelled as "okd" on https://ci.eclipse.org 
) will be restarted at least twice during that period.

Watch https://www.eclipsestatus.io/incidents/dpsds2qsnt45 
 for 
details during the maintenance.

Go to https://www.eclipsestatus.io  or follow 
https://twitter.com/Eclipse_Status  to know 
about infrastructure maintenance and issues.

Thanks.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] New signing services URLs and new releases of the cbi-maven-plugins

[Mikael Barbero]

Hi,

(cross posted to cbi-dev and cross-projects mailing lists)

The various signing services URLs have changed:

Java Jarsigner http://build.eclipse.org:31338/sign -> 
https://cbi.eclipse.org/jarsigner/sign 
Windows portable executable signing http://build.eclipse.org:31338/winsign.php 
-> https://cbi.eclipse.org/authenticode/sign 

macOS bundle (.app, .pkg...) signing http://build.eclipse.org:31338/macsign.php 
-> https://cbi.eclipse.org/macos/codesign/sign 

macOS DMG package creator http://build.eclipse.org:31338/dmg-packager -> 
https://cbi.eclipse.org/macos/packager/dmg/create 

macOS notarization direct IP -> https://cbi.eclipse.org/macos/xcrun 


Remember, those URLs are only available from within the Eclipse Foundation 
infrastructure. The old URLs are still available but this will change at some 
point (follow bug 565644  
for updates).

A new version of the maven plugins (v1.3.0 
) have been 
released where the default URLs are now the new values. Using the new URLs is 
then as easy as just upgrading the plugins version in your pom.xml.

A another release (v1.3.1 
) just adds 
support for .dll signing and reinstate .msi signing on windows.

If you don't use the maven plugins but curl (or any other http client) to call 
the signing services, you should update the URLs in your scripts manually. We 
will issue some reminders and will do some brownouts as part of 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=565644 
 before turning off the 
URLs, but the sooner the better ;)

Cheers,

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] [eclipse.org-committers] DockerHub starts enforcing limits in organization membership

[Mikael Barbero]

Hi Kevin,

This is not related to github, just to Docker Hub. And yes, we are working on a 
solution via https://bugs.eclipse.org/559659 <https://bugs.eclipse.org/559659>

Thanks.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation 
and Collaboration

> On 23 Mar 2021, at 14:05, Kevin Herron  wrote:
> 
> Miakael,
> 
> Some time back on this list I read that it was now possible for your project 
> to request to be its own top-level organization, which would mean you are not 
> subject to the shared org-wide limitations.
> 
> I think you just need to open a bug against Community/GitHub and ask for 
> assistance.
> 
> Maybe there is an easier solution in the works, though...
> 
> 
> Kevin
> 
> On Mon, Mar 22, 2021 at 6:44 AM Mikael Barbero 
>  <mailto:mikael.barb...@eclipse-foundation.org>> wrote:
> Hi everyone,
> 
> (cross posted to cbi-dev and eclipse.org <http://eclipse.org/>-committer).
> 
> Until now, we've been managing DockerHub hosting request as per the following 
> gules (copied from https://wiki.eclipse.org/CBI#Docker_Hub 
> <https://wiki.eclipse.org/CBI#Docker_Hub>):
> 
> ---
> The Eclipse Foundation owns the eclipse organization and a couple of other 
> project specific organizations at https://hub.docker.com 
> <https://hub.docker.com/>. You can ask to get a repository being created on 
> one of these organizations. We will set permissions so that committers have 
> write access to this repo (you will need to share your Docker Hub ID with us).
> 
> You can also ask us to create a project specific organization. The 
> organization name needs to follow the pattern eclipse.
> 
> Note that we don't grant admin permissions on any Eclipse Foundation owned 
> organization. We recognize that this means that you will have to go through 
> us for all new repo creation, but we can't grant organizations-wide admin 
> permission assigned to committers for security reasons.
> ---
> 
> When we add people (and bots) to teams (in order to grant them write 
> permissions on repositories), they are automatically added to the 
> corresponding organization as member. Until now, we were able to add as many 
> members as we wanted to. But 10 days ago we discovered via bug 571598 
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=571598> that the number of 
> (free) members is now limited to 3. See 
> https://docs.docker.com/docker-hub/billing/ 
> <https://docs.docker.com/docker-hub/billing/>, 
> https://www.docker.com/pricing/faq <https://www.docker.com/pricing/faq> and 
> https://www.docker.com/pricing <https://www.docker.com/pricing> for details.
> 
> We are largely surpassing this number on all the organizations we manage (see 
> below a screenshot of the eclipse organization members counter for example). 
> As such and effective immediately, we cannot grant access to anyone new to 
> our existing managed organizations and for new organizations. We can only 
> grant write access to a single committer (we keep one seat for webmaster and 
> one seat for a bot user). We are also expecting DockerHub to start removing 
> member from the various organization. If you lose your write permissions on 
> some repository, please open a ticket 
> <https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community=Outside%20Services>.
> 
> We are quite surprised by this change as we did not read or heard about such 
> policy change at docker hub. You may remember about the pull rate policy 
> change announced back in August 
> (https://www.docker.com/blog/scaling-docker-to-serve-millions-more-developers-network-egress/
>  
> <https://www.docker.com/blog/scaling-docker-to-serve-millions-more-developers-network-egress/>)
>  and enforced last October 
> (https://www.docker.com/blog/what-you-need-to-know-about-upcoming-docker-hub-rate-limiting/
>  
> <https://www.docker.com/blog/what-you-need-to-know-about-upcoming-docker-hub-rate-limiting/>),
>  but we did not see any message similar about Free Teams.
> 
> We need to find a solution moving forward. Some time ago, we opened bug 
> 559659 to start discussing better integration with a container registry 
> provider. I propose we continue discussing over there about how to move 
> forward on that topic.
> 
> Thanks.
> 
> 
> 
> Mikaël Barbero
> Manager — Release Engineering and Technology | Eclipse Foundation
>  @mikbarbero
> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
> Innovation and Collaboration
> 
> ___

[cross-project-issues-dev] DockerHub starts enforcing limits in organization membership

[Mikael Barbero]

Hi everyone,

(cross posted to cbi-dev and eclipse.org -committer).

Until now, we've been managing DockerHub hosting request as per the following 
gules (copied from https://wiki.eclipse.org/CBI#Docker_Hub):

---
The Eclipse Foundation owns the eclipse organization and a couple of other 
project specific organizations at https://hub.docker.com. You can ask to get a 
repository being created on one of these organizations. We will set permissions 
so that committers have write access to this repo (you will need to share your 
Docker Hub ID with us).

You can also ask us to create a project specific organization. The organization 
name needs to follow the pattern eclipse.

Note that we don't grant admin permissions on any Eclipse Foundation owned 
organization. We recognize that this means that you will have to go through us 
for all new repo creation, but we can't grant organizations-wide admin 
permission assigned to committers for security reasons.
---

When we add people (and bots) to teams (in order to grant them write 
permissions on repositories), they are automatically added to the corresponding 
organization as member. Until now, we were able to add as many members as we 
wanted to. But 10 days ago we discovered via bug 571598 
 that the number of 
(free) members is now limited to 3. See 
https://docs.docker.com/docker-hub/billing/ 
, 
https://www.docker.com/pricing/faq  and 
https://www.docker.com/pricing  for details.

We are largely surpassing this number on all the organizations we manage (see 
below a screenshot of the eclipse organization members counter for example). As 
such and effective immediately, we cannot grant access to anyone new to our 
existing managed organizations and for new organizations. We can only grant 
write access to a single committer (we keep one seat for webmaster and one seat 
for a bot user). We are also expecting DockerHub to start removing member from 
the various organization. If you lose your write permissions on some 
repository, please open a ticket 
.

We are quite surprised by this change as we did not read or heard about such 
policy change at docker hub. You may remember about the pull rate policy change 
announced back in August 
(https://www.docker.com/blog/scaling-docker-to-serve-millions-more-developers-network-egress/)
 and enforced last October 
(https://www.docker.com/blog/what-you-need-to-know-about-upcoming-docker-hub-rate-limiting/),
 but we did not see any message similar about Free Teams.

We need to find a solution moving forward. Some time ago, we opened bug 559659 
to start discussing better integration with a container registry provider. I 
propose we continue discussing over there about how to move forward on that 
topic.

Thanks.



Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] JDK 16 is GA (and available on Jenkins instances)

[Mikael Barbero]

Hi,

JDK16 is GA and we've installed it on all Jenkins instances (see 
https://wiki.eclipse.org/Jenkins#JDK  for 
details).

Cheers,

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] ci-staging is down?

[Mikael Barbero]

Should be back now.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 22 Feb 2021, at 08:16, Simon Skoczylas  wrote:
> 
> Hi there,
> 
> same here. I cannot reach https://ci-staging.eclipse.org/mdmbl 
> 
> 
> Regards
> Simon
> 
> Von: cross-project-issues-dev  > im Auftrag von Wim 
> Jongman mailto:wim.jong...@gmail.com>>
> Antworten an: Cross project issues  >
> Datum: Sonntag, 21. Februar 2021 um 15:08
> An: Cross project issues 
> Betreff: [cross-project-issues-dev] ci-staging is down?
> 
> Hi,
> 
> I can't contact ci-staging. Is it just me?
> 
> https://ci-staging.eclipse.org/windowbuilder/ 
> 
> 
> Cheers,
> 
> Wim
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] publishing and maintaining a composite update site from JIRO

[Mikael Barbero]

FYI, I've just posted an update on 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=558735#c18

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 5 Feb 2021, at 11:40, Lorenzo Bettini  wrote:
> 
> Hi
> 
> for my Eclipse projects built on and released from Hudson, and then JIPP, I 
> was using a working releng mechanism to publish and update composite p2 sites 
> for my Eclipse projects, EMF Parsley and Xsemantics (completely automated 
> from the Maven/Tycho build).
> 
> JIRO completely broke this mechanism since there's no direct access to the 
> download area. Looks like I'm not the only one complaining about that 
> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=558735) and looks like 
> "mounted download folders" are not yet available.
> 
> Of course, I can come up with a different strategy, copying some metadata 
> locally in the JIRO runner, update it, then put it back, but it'll surely 
> take me some time (especially because I seem to understand that in JIRO 
> workspaces are completely ephemeral so everything is lost, making debugging a 
> nightmare I guess), which I'd rather save at the moment.
> 
> So I'm wondering if anyone else has a working solution that can be easily 
> reused?
> I'm also taking the chance to ask (once again) if "mounted download folders" 
> can be provided (now that a year has passed).
> 
> Of course I'd be OK with other solutions, from other supported CIs, but I 
> guess it's only possible to publish p2 sites from JIRO, is it?
> 
> thanks in advance
>   Lorenzo
> 
> --
> Prof. Lorenzo Bettini, Computer Science, DISIA, Univ. Firenze
> HOME: http://www.lorenzobettini.it
> TDD Book: https://leanpub.com/tdd-buildautomation-ci
> Xtext Book: 
> https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Scheduled upgrade of a build cluster

[Mikael Barbero]

Hi,

We will be doing an upgrade of the new build cluster on January 29th at 13:00 
EST.

Some Jenkins instances will be restarted (the ones labelled as "okd" on 
https://ci.eclipse.org).

Watch https://www.eclipsestatus.io/incidents/nwc167whsskz?u=jj3b62dj4xzk 
 for 
details during the maintenance.

Go to https://www.eclipsestatus.io  or follow 
https://twitter.com/Eclipse_Status  to know 
about infrastructure maintenance and issues.

Thanks.


Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Planned upgrade of repo.eclipse.org

[Mikael Barbero]

Upgrade is complete.

Thanks.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation 
and Collaboration

> On 6 Jan 2021, at 10:49, Mikael Barbero 
>  wrote:
> 
> Hi,
> 
> A planned upgrade of repo.eclipse.org <http://repo.eclipse.org/> is scheduled 
> for Jan 8, 13:00 - 14:00 EST.
> 
> The service will be unavailable for a couple of minutes during restart. You 
> builds may fail as a result of this unavailability.
> 
> See https://www.eclipsestatus.io/incidents/fxd0njl0gjs4 
> <https://www.eclipsestatus.io/incidents/fxd0njl0gjs4> and 
> https://www.eclipsestatus.io <https://www.eclipsestatus.io/> (along with 
> https://twitter.com/Eclipse_Status <https://twitter.com/Eclipse_Status>) to 
> get updates on this maintenance.
> 
> Thanks.
> 
> Mikaël Barbero
> Manager — Release Engineering and Technology | Eclipse Foundation
>  @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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Planned upgrade of repo.eclipse.org

[Mikael Barbero]

Hi,

A planned upgrade of repo.eclipse.org  is scheduled 
for Jan 8, 13:00 - 14:00 EST.

The service will be unavailable for a couple of minutes during restart. You 
builds may fail as a result of this unavailability.

See https://www.eclipsestatus.io/incidents/fxd0njl0gjs4 
 and 
https://www.eclipsestatus.io  (along with 
https://twitter.com/Eclipse_Status ) to get 
updates on this maintenance.

Thanks.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Travis CI Docker Integration

[Mikael Barbero]

At the Foundation, we switched to a pro account for our bots, it was the 
solution that was making the most sense. There is also quay.io (by RedHat) that 
offers free hosting for public repositories. Maybe you can switch to this 
service.

HTH

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 27 Nov 2020, at 18:33, Mezzasalma, Claudio 
>  wrote:
> 
> Hello all,
> In Eclipse Kapua we're trying to understand how to better use Docker in our 
> integration tests running on Travis. Currently, the generation of the Docker 
> images is done in the main build job, while integration tests are run in 
> different test jobs; this means we need to find a way to share images across 
> the various steps in Travis. According the Travis docs [1], the only way to 
> share Docker images is by using an external Docker registry, but as you may 
> know, Docker recently introduced a quota on how many pulls can be done from a 
> free account, which is 200 pulls in 6 hours [2]. So, I was wondering if 
> someone already faced a similar issue, and how did you worked around it.
> 
> Thanks anyone!
> 
> [1] https://docs.travis-ci.com/user/build-stages/share-docker-image/
> [2] https://www.docker.com/pricing
> --
> Claudio Mezzaslma | Eurotech
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Travis CI waiting queue and new pricing options

[Mikael Barbero]

Indeed, a dedicated organization could work around the issue. Note that given 
the way Travis is changing, I would advise to prepare to switch to another 
build system now rather than waiting to be forced to do so on the next policy 
change (which seems to happen frequently).

The Eclipse Foundation offers a Jenkins based CI, which integrates seamlessly 
with GH (build on commit push, PR builds etc..). See 
https://wiki.eclipse.org/CBI#CI_Environment_.28Jenkins.29 
 and 
https://wiki.eclipse.org/Jenkins 

Cheers,

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 27 Nov 2020, at 18:45, Jonah Graham  wrote:
> 
> In the past there was a similar issue and IIRC the solution was to have a new 
> github organization so that not everything was shared together. There are 
> already a number of Eclipse organizations (in addition to the main eclipse 
> one).
> 
> HTH,
> Jonah
> 
> On Fri., Nov. 27, 2020, 12:33 Mezzasalma, Claudio, 
> mailto:claudio.mezzasa...@eurotech.com>> 
> wrote:
> Hello all,
> In Eclipse Kapua we're using Travis as our CI server. However, it looks like 
> in the past few weeks the queue in the Eclipse account increased 
> significantly, leading to very long waiting time (the average waiting time 
> for today, November 27th, 2020 is 2392 minutes while yesterday was 2248 
> minutes -- data from [1]). Moreover, Travis announced they're moving to a 
> different usage policy for free account (announcement [2] and follow up [3]) 
> that is basically preventing us, as single committers, to use our personal 
> forks to do CI on pull requests before merging the code in the main branch, 
> something we were doing to reduce the amount of jobs in the whole Eclipse 
> account on Travis.
> So, while we wait for a reply from the Travis staff who could offer some free 
> credits for our personal forks, I would like to ask for any suggestion from 
> our community on how we could approach this issue.
> 
> Thanks everyone!
> 
> [1] https://travis-ci.org/github/eclipse?tab=insights 
> 
> [2] https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing 
> 
> [3] https://blog.travis-ci.com/oss-announcement 
> 
> --
> Claudio Mezzaslma | Eurotech
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org 
> 
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev 
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] JustJ JREs and download.eclipse.org Browsing

[Mikael Barbero]

> It's a little odd that https://archive.eclipse.org 
>  redirects to 
> https://archive.eclipse.org/eclipse/downloads/ 
>  as if the platform project 
> owns everything. :-P

I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=568020 
 to fix that.

Cheers,
Mikael


signature.asc
Description: Message signed with OpenPGP
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Upgrade repo.eclipse.org today

[Mikael Barbero]

Upgrade is completed. Service is back online fully operational.

This was an emergency upgrade after security advisory  
https://support.sonatype.com/hc/en-us/articles/360051068253 
<https://support.sonatype.com/hc/en-us/articles/360051068253>

Thanks for your patience.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation 
and Collaboration

> On 8 Oct 2020, at 16:46, Mikael Barbero 
>  wrote:
> 
> Hi,
> 
> We will upgrade Sonatype Nexus (repo.eclipse.org <http://repo.eclipse.org/>) 
> today @ 11am EDT.
> 
> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=567719 
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=567719> and 
> https://status.eclipse.org/incidents/wzgkp9jjs5x6 
> <https://status.eclipse.org/incidents/wzgkp9jjs5x6> to stay informed.
> 
> Thanks.
> 
> Mikaël Barbero
> Manager — Release Engineering and Technology | Eclipse Foundation
>  @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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Upgrade repo.eclipse.org today

[Mikael Barbero]

Hi,

We will upgrade Sonatype Nexus (repo.eclipse.org ) 
today @ 11am EDT.

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=567719 
 and 
https://status.eclipse.org/incidents/wzgkp9jjs5x6 
 to stay informed.

Thanks.

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Problem with gerrit?

[Mikael Barbero]

Yes. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=558957 
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=558957> which tracks this 
feature for Jenkins on the new infra.


Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 @mikbarbero
Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation 
and Collaboration

> On 18 Aug 2020, at 10:28, Laurent Redor  wrote:
> 
> Hi,
> 
> Thank you, the problem is solved.
> 
> By the way, is it expected to no longer have the restart button on the 
> profile page?
> 
> 
> We've thinked to restart the Jenkins to see if it solved the problem but we 
> couldn't.
> 
> Regards,
> 
> Laurent Redor
> DELIVERY MANAGER
> +33 2 51 13 52 18 | +33 6 89 99 85 29
> 
>  <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>
> Le 18/08/2020 à 10:03, Mikael Barbero a écrit :
>> Hi Laurent,
>> 
>> I did not hear any issue from other projects. It seems to be only affecting 
>> Sirius' Jenkins. The gerrit connection was broken. I've restarted your 
>> Jenkins and it's now in good shape (I did not manage to restore the 
>> connection to gerrit without a Jenkins restart).
>> 
>> Cheers,
>> 
>> Mikaël Barbero
>> Team Lead - Release Engineering | Eclipse Foundation
>>  @mikbarbero
>> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
>> Innovation and Collaboration
>> 
>>> On 18 Aug 2020, at 09:18, Laurent Redor >> <mailto:laurent.re...@obeo.fr>> wrote:
>>> 
>>> Hi,
>>> 
>>> For Sirius project, the gerrit jobs have not been launched since yesterday. 
>>> Does this problem occurs only for Sirius project or is it the same for 
>>> others?
>>> 
>>> Sample of issues:
>>> 
>>> https://git.eclipse.org/r/c/sirius/org.eclipse.sirius/+/167835/1 
>>> <https://git.eclipse.org/r/c/sirius/org.eclipse.sirius/+/167835/1>
>>> https://git.eclipse.org/r/c/sirius/org.eclipse.sirius/+/167696/3 
>>> <https://git.eclipse.org/r/c/sirius/org.eclipse.sirius/+/167696/3>
>>> OK for previous patch set 1 and 2 (but created the 14th of august)
>>> https://git.eclipse.org/r/c/sirius/org.eclipse.sirius/+/167713 
>>> <https://git.eclipse.org/r/c/sirius/org.eclipse.sirius/+/167713>
>>> OK for previous patch set 1 (but created the 14th of august)
>>> This problem is maybe linked to 
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=566080 
>>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=566080>?
>>> 
>>> Regards,
>>> 
>>> --
>>> Laurent Redor
>>> 
>>>  <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 
>>> <mailto:cross-project-issues-dev@eclipse.org>
>>> To 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 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 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Problem with gerrit?

[Mikael Barbero]

Hi Laurent,

I did not hear any issue from other projects. It seems to be only affecting 
Sirius' Jenkins. The gerrit connection was broken. I've restarted your Jenkins 
and it's now in good shape (I did not manage to restore the connection to 
gerrit without a Jenkins restart).

Cheers,

Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> On 18 Aug 2020, at 09:18, Laurent Redor  wrote:
> 
> Hi,
> 
> For Sirius project, the gerrit jobs have not been launched since yesterday. 
> Does this problem occurs only for Sirius project or is it the same for others?
> 
> Sample of issues:
> 
> https://git.eclipse.org/r/c/sirius/org.eclipse.sirius/+/167835/1 
> 
> https://git.eclipse.org/r/c/sirius/org.eclipse.sirius/+/167696/3 
> 
> OK for previous patch set 1 and 2 (but created the 14th of august)
> https://git.eclipse.org/r/c/sirius/org.eclipse.sirius/+/167713 
> 
> OK for previous patch set 1 (but created the 14th of august)
> This problem is maybe linked to 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=566080 
> ?
> 
> Regards,
> 
> --
> Laurent Redor
> 
>  
> 7 Boulevard Ampère - Carquefou - France
> obeo.fr  | twitter  | 
> linkedin 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Upgrade to latest Jenkins LTS version during CW 21 (May 18-22)

[Mikael Barbero]

Hi Michael,

Yes, please share if you could. We have quite a different setup from you (as 
upgrade are done by deploying new docker images rather than updating the 
instances with jenkins builtin feature and modifying $JENKINS_HOME from within 
the instance), but we could still learn some tricks to make the process 
smoother.

Thanks.

Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> Le 9 mai 2020 à 16:12, Michael Keppler  a écrit :
> 
> On 06.05.2020 18:53, Frederic Gurr wrote:
>> To
>> spread the load and wait for running builds to finish, we distribute the
>> upgrade over several days.
> 
> At work I have created a pipeline which automatically restarts Jenkins
> whenever it is necessary and no jobs are running _without_ using the
> "cannot take any further jobs" mode. I upgrade Jenkins plugins every
> other day, but _never_ restart manually, since that pipeline takes care
> of everything.
> 
> Would you be interested in that, and if so, is there any bugzilla to
> continue such discussion?
> 
> 
> Ciao, Michael
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Infrastructure Problems

[Mikael Barbero]

It is fixed.

Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> Le 6 avr. 2020 à 06:57, Ed Merks  a écrit :
> 
> FYI,
> 
> I don't know if others are affected but the Oomph CI instance is not usable 
> right now because of signing service failures and gateway errors:
> 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=561793
> 
> This started happening yesterday morning (Sunday).
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Is Git dead?

[Mikael Barbero]

Works for me.

git clone ssh://mbarb...@git.eclipse.org:29418/cdo/cdo.git
Cloning into 'cdo'...
remote: Counting objects: 13486, done
remote: Finding sources: 100% (505/505)
Receiving objects:  63% (291090/461199), 94.66 MiB | 1.19 MiB/s

While the server is under substantial load 
(https://accounts.eclipse.org/committertools/infra-status 
) it should not be 
something it cannot handle.


Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> Le 12 mars 2020 à 11:20, Eike Stepper  a écrit :
> 
> Hi,
> 
> Is Git dead? I can't push or fetch within the 30s timeouts:
> 
> Can't connect to any repository: 
> ssh://estep...@git.eclipse.org:29418/cdo/cdo (Read timed out after 30.000 ms)
> 
> Cheers
> /Eike
> 
> 
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
> 
> 
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To 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 unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] git.eclipse.org seems down

[Mikael Barbero]

I've escalated the issue. Thanks for your patience.

Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 @mikbarbero
Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation 
and Collaboration

> Le 18 févr. 2020 à 13:53, Aleksandar Kurtakov  a écrit :
> 
> I can't push to gerrit Can't connect to any repository: 
> ssh://akurta...@git.eclipse.org:29418/cdt/org.eclipse.cdt.git 
> <http://akurta...@git.eclipse.org:29418/cdt/org.eclipse.cdt.git> (Read timed 
> out after 30,000 ms).
> 
> On Tue, Feb 18, 2020 at 12:42 PM Mikael Barbero 
>  <mailto:mikael.barb...@eclipse-foundation.org>> wrote:
> I can't see anything bad in the gerrit logs. It may be network congestion, 
> but AFAICT no equipment in the infra is under an unusual load.
> 
> Is this blocking anyone at the moment?
> 
> Mikaël Barbero
> Team Lead - Release Engineering | Eclipse Foundation
>  @mikbarbero
> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
> Innovation and Collaboration
> 
>> Le 18 févr. 2020 à 11:00, Andrey Loskutov > <mailto:losku...@gmx.de>> a écrit :
>> 
>> Yep, I see many random timeouts today on pulling from different platform git 
>> repositories.
>> 
>> Kind regards,
>> Andrey Loskutov
>> 
>> Спасение утопающих - дело рук самих утопающих
>> 
>> https://www.eclipse.org/user/aloskutov 
>> <https://www.eclipse.org/user/aloskutov>
>> 
>> 
>> Gesendet: Dienstag, 18. Februar 2020 um 10:58 Uhr
>> Von: "LORENZO Vincent" > <mailto:vincent.lore...@cea.fr>>
>> An: " (cross-project-issues-dev@eclipse.org 
>> <mailto:cross-project-issues-dev@eclipse.org>)" 
>> > <mailto:cross-project-issues-dev@eclipse.org>>
>> Betreff: [cross-project-issues-dev] git.eclipse.org 
>> <http://git.eclipse.org/> seems down
>> Hello everybody,
>> 
>>   I can’t  patches on gerrit and locally I can’t make a git pull 
>> (Connection to git.eclipse.org <http://git.eclipse.org/> closed by remote 
>> host.)
>> 
>> The server service seems spotty.
>> 
>> 
>> Does someone have the same trouble ?
>> 
>> 
>> 
>> Regards,
>> 
>> --
>> 
>> Vincent LORENZO
>> 
>> 01-69-08-17-24
>> 
>> CEA Saclay Nano-INNOV
>> 
>> Institut CARNOT CEA LIST
>> 
>> Point Courrier n° 174
>> 
>> 91 191 Gif sur Yvette CEDEX
>> 
>> 
>> ___ 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>
> ___
> 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>
> 
> --
> Alexander Kurtakov
> Red Hat Eclipse Team
> ___
> 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] git.eclipse.org seems down

[Mikael Barbero]

I can't see anything bad in the gerrit logs. It may be network congestion, but 
AFAICT no equipment in the infra is under an unusual load.

Is this blocking anyone at the moment?

Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> Le 18 févr. 2020 à 11:00, Andrey Loskutov  a écrit :
> 
> Yep, I see many random timeouts today on pulling from different platform git 
> repositories.
> 
> Kind regards,
> Andrey Loskutov
> 
> Спасение утопающих - дело рук самих утопающих
> 
> https://www.eclipse.org/user/aloskutov
> 
> 
> Gesendet: Dienstag, 18. Februar 2020 um 10:58 Uhr
> Von: "LORENZO Vincent" 
> An: " (cross-project-issues-dev@eclipse.org)" 
> 
> Betreff: [cross-project-issues-dev] git.eclipse.org seems down
> Hello everybody,
> 
>   I can’t  patches on gerrit and locally I can’t make a git pull 
> (Connection to git.eclipse.org closed by remote host.)
> 
> The server service seems spotty.
> 
> 
> Does someone have the same trouble ?
> 
> 
> 
> Regards,
> 
> --
> 
> Vincent LORENZO
> 
> 01-69-08-17-24
> 
> CEA Saclay Nano-INNOV
> 
> Institut CARNOT CEA LIST
> 
> Point Courrier n° 174
> 
> 91 191 Gif sur Yvette CEDEX
> 
> 
> ___ 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 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] Issues with git/gerrit and sometimes bugzilla

[Mikael Barbero]

Some of you are still unable to log into services like git/gerrit, bugzilla or 
jenkins.

Webmasters are currently looking into it and will keep you posted as soon as 
it's fixed.

Thanks for your patience.

Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> Le 7 févr. 2020 à 20:42, Matthew Ward  a 
> écrit :
> 
> One of our backend storage nodes fell over which has impacted service 
> availability.  We've cut over to our standby and are restarting services as 
> required to bring everything back up.
> 
> -Matt.
> 
> On Fri, Feb 7, 2020 at 2:03 PM Thomas Watson  > wrote:
> I've been getting 502 errors access the eclipse servers, bug 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=559928 
>  opened.
> 
> 
> Tom
> 
> 
> ___
> 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 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] Maintenance of the macOS notarization service

[Mikael Barbero]

Maintenance is over. Services are all up and running.

Thanks.

> Le 21 janv. 2020 à 16:05, Mikael Barbero 
>  a écrit :
> 
> Hi,
> 
> We have to do some maintenance on the macOS notarization service tomorrow Jan 
> 22 between 1pm and 3pm CET (7am and 9am EST). The service will be 
> un-available for all users reaching out directly to the machine IP ending 
> with "146". The service should be unavailable first for about 30min and once 
> again later for about 10min.
> 
> No other macOS services (signing, dmg packaging) will be affected.
> 
> Maintenance operation details can be tracked in 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=559372 
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=559372>
> 
> Thanks for your understanding.
> 
> 
> Mikaël Barbero
> Team Lead - Release Engineering | Eclipse Foundation
>  @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 of the macOS notarization service

[Mikael Barbero]

Hi,

We have to do some maintenance on the macOS notarization service tomorrow Jan 
22 between 1pm and 3pm CET (7am and 9am EST). The service will be un-available 
for all users reaching out directly to the machine IP ending with "146". The 
service should be unavailable first for about 30min and once again later for 
about 10min.

No other macOS services (signing, dmg packaging) will be affected.

Maintenance operation details can be tracked in 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=559372 


Thanks for your understanding.


Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : 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] repo.eclipse.org maintenance on January 19th

[Mikael Barbero]

Please try again by restarting your job from scratch (ie not just a module, 
some bad caching could be involved, e.g., see 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=559326#c7).

If you still face an issue, please open a separate ticket so we can investigate 
without spamming everyone on this list.

Thanks.

> Le 20 janv. 2020 à 10:41, Ed Willink  a écrit :
> 
> Hi
> 
> The 'old' ci.eclipse.org seems to have gone down.
> 
> While trying to investigate weird failures that started yesterday [1], I now 
> get catastrophic start up [2].
> 
> Regards
> 
> Ed Willink
> 
> [1] 
> https://ci.eclipse.org/ocl/job/ocl-compatibility-2019-03/org.eclipse.ocl$org.eclipse.ocl.compatibility.tests/45/
>  
> <https://ci.eclipse.org/ocl/job/ocl-compatibility-2019-03/org.eclipse.ocl$org.eclipse.ocl.compatibility.tests/45/>
> [2] 
> https://ci.eclipse.org/ocl/job/ocl-compatibility-2019-03/org.eclipse.ocl$org.eclipse.ocl.compatibility.tests/48/
>  
> <https://ci.eclipse.org/ocl/job/ocl-compatibility-2019-03/org.eclipse.ocl$org.eclipse.ocl.compatibility.tests/48/>
> On 20/01/2020 09:25, Mikael Barbero wrote:
>> As note on the associated ticket, and unrelated to the repo.eclipse.org 
>> <http://repo.eclipse.org/> maintenance, we've been having a failing proxy 
>> node in our reverse proxy pool for the last 2 days. This node has not been 
>> automatically removed from the pool for some reasons. As such, 1/3 of the 
>> requests directed to the cluster were timing out. It was mostly affecting 
>> Jenkins instances on the new infra and help.eclipse.org 
>> <http://help.eclipse.org/>.
>> 
>> Everything should be back on track. We're now working on preventing such 
>> proxy node failure from impacting projects as much as it did this week end.
>> 
>> Thanks for your patience.
>> 
>> Mikaël Barbero
>> Team Lead - Release Engineering | Eclipse Foundation
>>  @mikbarbero
>> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
>> Innovation and Collaboration
>> 
>>> Le 19 janv. 2020 à 16:52, Mikael Barbero 
>>> >> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit :
>>> 
>>> Internal DNS are note yet updated, so builds on Jenkins are still seeing 
>>> 503 while https://repo.eclipse.org <https://repo.eclipse.org/> is up and 
>>> running.
>>> 
>>> Will keep you posted once everything is back to normal.
>>> 
>>>> Le 19 janv. 2020 à 16:22, Mikael Barbero 
>>>> >>> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit :
>>>> 
>>>> Note that DNS had to be changed, so depending on the caching level of your 
>>>> setup, you may have to wait until the change is fully propagated.
>>>> 
>>>>> Le 19 janv. 2020 à 16:15, Mikael Barbero 
>>>>> >>>> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit :
>>>>> 
>>>>> Maintenance is over.
>>>>> 
>>>>> Thanks for your patience.
>>>>> 
>>>>> Mikaël Barbero
>>>>> Team Lead - Release Engineering | Eclipse Foundation
>>>>>  @mikbarbero
>>>>> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
>>>>> Innovation and Collaboration
>>>>> 
>>>>>> Le 14 janv. 2020 à 15:37, Mikael Barbero 
>>>>>> >>>>> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit :
>>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> We will do some maintenance of the Nexus instance servicing 
>>>>>> repo.eclipse.org <http://repo.eclipse.org/>. The maintenance is 
>>>>>> scheduled for Jan 19. @ 12 noon CET following our maintenance window for 
>>>>>> Tier II services (https://wiki.eclipse.org/IT_SLA#Maintenance 
>>>>>> <https://wiki.eclipse.org/IT_SLA#Maintenance>).
>>>>>> 
>>>>>> The repositories will set to readonly (no deploy will work) for about 3 
>>>>>> hours and the service will be unavailable for about 15 min.
>>>>>> 
>>>>>> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=551775 
>>>>>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=551775> for details.
>>>>>> 
>>>>>> Thanks for your understanding.
>>>>>> 
>>>>>> 
>>>>>> Mikaël Barbero
>>>>>> Team 

Re: [cross-project-issues-dev] repo.eclipse.org maintenance on January 19th

[Mikael Barbero]

As note on the associated ticket, and unrelated to the repo.eclipse.org 
<http://repo.eclipse.org/> maintenance, we've been having a failing proxy node 
in our reverse proxy pool for the last 2 days. This node has not been 
automatically removed from the pool for some reasons. As such, 1/3 of the 
requests directed to the cluster were timing out. It was mostly affecting 
Jenkins instances on the new infra and help.eclipse.org 
<http://help.eclipse.org/>.

Everything should be back on track. We're now working on preventing such proxy 
node failure from impacting projects as much as it did this week end.

Thanks for your patience.

Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 @mikbarbero
Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation 
and Collaboration

> Le 19 janv. 2020 à 16:52, Mikael Barbero 
>  a écrit :
> 
> Internal DNS are note yet updated, so builds on Jenkins are still seeing 503 
> while https://repo.eclipse.org <https://repo.eclipse.org/> is up and running.
> 
> Will keep you posted once everything is back to normal.
> 
>> Le 19 janv. 2020 à 16:22, Mikael Barbero 
>> > <mailto:mikael.barb...@eclipse-foundation.org>> a écrit :
>> 
>> Note that DNS had to be changed, so depending on the caching level of your 
>> setup, you may have to wait until the change is fully propagated.
>> 
>>> Le 19 janv. 2020 à 16:15, Mikael Barbero 
>>> >> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit :
>>> 
>>> Maintenance is over.
>>> 
>>> Thanks for your patience.
>>> 
>>> Mikaël Barbero
>>> Team Lead - Release Engineering | Eclipse Foundation
>>>  @mikbarbero
>>> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
>>> Innovation and Collaboration
>>> 
>>>> Le 14 janv. 2020 à 15:37, Mikael Barbero 
>>>> >>> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit :
>>>> 
>>>> Hi,
>>>> 
>>>> We will do some maintenance of the Nexus instance servicing 
>>>> repo.eclipse.org <http://repo.eclipse.org/>. The maintenance is scheduled 
>>>> for Jan 19. @ 12 noon CET following our maintenance window for Tier II 
>>>> services (https://wiki.eclipse.org/IT_SLA#Maintenance 
>>>> <https://wiki.eclipse.org/IT_SLA#Maintenance>).
>>>> 
>>>> The repositories will set to readonly (no deploy will work) for about 3 
>>>> hours and the service will be unavailable for about 15 min.
>>>> 
>>>> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=551775 
>>>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=551775> for details.
>>>> 
>>>> Thanks for your understanding.
>>>> 
>>>> 
>>>> Mikaël Barbero
>>>> Team Lead - Release Engineering | Eclipse Foundation
>>>>  @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] Is the help.eclipse.org not working properly

[Mikael Barbero]

This has been caused by a failing reverse proxy node in the infra. It has 
caused troubles for the migration of repo.eclipse.org as well. See 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=551775#c22
.
With the removal of the failing proxy node, everything is back to normal.


Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> Le 20 janv. 2020 à 09:26, Daniel Megert  a écrit :
> 
> Looks like it is back, but e.g. JDT and PDE are still missing. However, this 
> seems t be the case for a while (filed https://bugs.eclipse.org/559328 
> ).
> 
> Dani
> 
> 
> 
> From:Andrey Loskutov 
> To:cross-project-issues-dev@eclipse.org, webmas...@eclipse.org
> Date:19.01.2020 09:35
> Subject:[EXTERNAL] Re: [cross-project-issues-dev] Is the 
> help.eclipse.org not working properly
> Sent by:cross-project-issues-dev-boun...@eclipse.org
> 
> 
> 
> Lucky you!
> 
> I don't even see CDT tools, I only get 400 error for
> https://help.eclipse.org/2019-12 , while 
> https://help.eclipse.org/2019-09 
> is working as expected.
> 
> So I assume https://help.eclipse.org/2019-12 
> is broken.
> I've filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=559322 
> .
> 
> HTTP ERROR 400 Duplicate valid session cookies:
> node0cxbgaawhg39m6glkonadnsqn5773743.node0,node0j1re79n6gd5n1swbb8j2ljy1g5773470.node0
> URI: /help/advanced/views.jsp
> STATUS: 400
> MESSAGE: Duplicate valid session cookies:
> node0cxbgaawhg39m6glkonadnsqn5773743.node0,node0j1re79n6gd5n1swbb8j2ljy1g5773470.node0
> SERVLET: -
> CAUSED BY: org.eclipse.jetty.http.BadMessageException: 400: 
> Duplicate
> valid session cookies:
> node0cxbgaawhg39m6glkonadnsqn5773743.node0,node0j1re79n6gd5n1swbb8j2ljy1g5773470.node0
> Caused by:
> org.eclipse.jetty.http.BadMessageException: 400: Duplicate valid session
> cookies:
> node0cxbgaawhg39m6glkonadnsqn5773743.node0,node0j1re79n6gd5n1swbb8j2ljy1g5773470.node0
> at
> org.eclipse.jetty.server.session.SessionHandler.checkRequestedSessionId(SessionHandler.java:1675)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1526)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1212)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at org.eclipse.jetty.server.Server.handle(Server.java:500)
> at
> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:383)
> at 
> org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:547)
> at 
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:375)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:270)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
> at 
> org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
> at 
> org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129)
> at
> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:388)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938)
> at java.lang.Thread.run(Thread.java:748)
> 
> On 19.01.2020 03:31, Jonah Graham wrote:
> > When I visit https://help.eclipse.org/2019-12/index.jsp 
> > all I see is the
> > C/C++ Development User Guide - I tried in multiple browsers. I
> > screenshoted what I see, attached.
> >
> > Is this just me - or is it broken?
> >
> > Thanks for your time.
> >
> > Jonah
> >
> > ~~~
> > Jonah Graham
> > Kichwa Coders
> > www.kichwacoders.com 
> > 

Re: [cross-project-issues-dev] repo.eclipse.org maintenance on January 19th

[Mikael Barbero]

Internal DNS are note yet updated, so builds on Jenkins are still seeing 503 
while https://repo.eclipse.org <https://repo.eclipse.org/> is up and running.

Will keep you posted once everything is back to normal.

> Le 19 janv. 2020 à 16:22, Mikael Barbero 
>  a écrit :
> 
> Note that DNS had to be changed, so depending on the caching level of your 
> setup, you may have to wait until the change is fully propagated.
> 
>> Le 19 janv. 2020 à 16:15, Mikael Barbero 
>> > <mailto:mikael.barb...@eclipse-foundation.org>> a écrit :
>> 
>> Maintenance is over.
>> 
>> Thanks for your patience.
>> 
>> Mikaël Barbero
>> Team Lead - Release Engineering | Eclipse Foundation
>>  @mikbarbero
>> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
>> Innovation and Collaboration
>> 
>>> Le 14 janv. 2020 à 15:37, Mikael Barbero 
>>> >> <mailto:mikael.barb...@eclipse-foundation.org>> a écrit :
>>> 
>>> Hi,
>>> 
>>> We will do some maintenance of the Nexus instance servicing 
>>> repo.eclipse.org <http://repo.eclipse.org/>. The maintenance is scheduled 
>>> for Jan 19. @ 12 noon CET following our maintenance window for Tier II 
>>> services (https://wiki.eclipse.org/IT_SLA#Maintenance 
>>> <https://wiki.eclipse.org/IT_SLA#Maintenance>).
>>> 
>>> The repositories will set to readonly (no deploy will work) for about 3 
>>> hours and the service will be unavailable for about 15 min.
>>> 
>>> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=551775 
>>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=551775> for details.
>>> 
>>> Thanks for your understanding.
>>> 
>>> 
>>> Mikaël Barbero
>>> Team Lead - Release Engineering | Eclipse Foundation
>>>  @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] repo.eclipse.org maintenance on January 19th

[Mikael Barbero]

Note that DNS had to be changed, so depending on the caching level of your 
setup, you may have to wait until the change is fully propagated.

> Le 19 janv. 2020 à 16:15, Mikael Barbero 
>  a écrit :
> 
> Maintenance is over.
> 
> Thanks for your patience.
> 
> Mikaël Barbero
> Team Lead - Release Engineering | Eclipse Foundation
>  @mikbarbero
> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
> Innovation and Collaboration
> 
>> Le 14 janv. 2020 à 15:37, Mikael Barbero 
>> > <mailto:mikael.barb...@eclipse-foundation.org>> a écrit :
>> 
>> Hi,
>> 
>> We will do some maintenance of the Nexus instance servicing repo.eclipse.org 
>> <http://repo.eclipse.org/>. The maintenance is scheduled for Jan 19. @ 12 
>> noon CET following our maintenance window for Tier II services 
>> (https://wiki.eclipse.org/IT_SLA#Maintenance 
>> <https://wiki.eclipse.org/IT_SLA#Maintenance>).
>> 
>> The repositories will set to readonly (no deploy will work) for about 3 
>> hours and the service will be unavailable for about 15 min.
>> 
>> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=551775 
>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=551775> for details.
>> 
>> Thanks for your understanding.
>> 
>> 
>> Mikaël Barbero
>> Team Lead - Release Engineering | Eclipse Foundation
>>  @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] repo.eclipse.org maintenance on January 19th

[Mikael Barbero]

Maintenance is over.

Thanks for your patience.

Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 @mikbarbero
Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation 
and Collaboration

> Le 14 janv. 2020 à 15:37, Mikael Barbero 
>  a écrit :
> 
> Hi,
> 
> We will do some maintenance of the Nexus instance servicing repo.eclipse.org 
> <http://repo.eclipse.org/>. The maintenance is scheduled for Jan 19. @ 12 
> noon CET following our maintenance window for Tier II services 
> (https://wiki.eclipse.org/IT_SLA#Maintenance 
> <https://wiki.eclipse.org/IT_SLA#Maintenance>).
> 
> The repositories will set to readonly (no deploy will work) for about 3 hours 
> and the service will be unavailable for about 15 min.
> 
> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=551775 
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=551775> for details.
> 
> Thanks for your understanding.
> 
> 
> Mikaël Barbero
> Team Lead - Release Engineering | Eclipse Foundation
>  @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] repo.eclipse.org maintenance on January 19th

[Mikael Barbero]

Hi,

We will do some maintenance of the Nexus instance servicing repo.eclipse.org 
. The maintenance is scheduled for Jan 19. @ 12 noon 
CET following our maintenance window for Tier II services 
(https://wiki.eclipse.org/IT_SLA#Maintenance 
).

The repositories will set to readonly (no deploy will work) for about 3 hours 
and the service will be unavailable for about 15 min.

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=551775 
 for details.

Thanks for your understanding.


Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 @mikbarbero
Eclipse Foundation : 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

[Mikael Barbero]

All Jenkins instances @ hipp6 are back online.

Thanks for your patience.

Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 (+33) 642 028 039 |  @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration

> Le 16 déc. 2019 à 08:45, Ed Merks  a écrit :
> 
> FYI,
> 
> CI instances on hipp6 have been down for the past 24 hours.  I opened 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=558331 yesterday.
> 
> 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://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] Can we please stop using composite repos?

[Mikael Barbero]

>> 
>> Can the composite only include the current/latest version, or can someone 
>> educate me as to the value of having multiple versions?
> It's a really good question.  It just seems to be a "habit" to compose 
> multiple children, usually with some restriction on the number of children, 
> e.g., the most recent n children.  But personally, just to make everything 
> faster for the client and less overhead for the download.eclipse.org 
>  server, I would prefer to use a repo with a 
> single child with the most recent version.
> 
> So what prompted everyone to have this habit?
> 
AFAIK, it comes from the simrel process of "making visible" the repository to 
the world (after the quiet / mirroring time). See code comment in  
https://git.eclipse.org/c/simrel/org.eclipse.simrel.tools.git/tree/promoteUtils/makeVisible.sh#n25
 


See also this FAQ entry 
https://wiki.eclipse.org/SimRel/Simultaneous_Release_Cycle_FAQ#Why_do_we_use_composites_anyway.2C_if_there_are_potential_problems_with_them.3F
 


Cheers,

Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 (+33) 642 028 039 |  @mikbarbero
Eclipse Foundation : 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-06 Release Candidate 1 (RC1) is available

[Mikael Barbero]

Hi,

The 2019-06 RC1 update repository is now available from:

=> http://download.eclipse.org/releases/2019-06/

The RC1 EPP packages will be available soon:

=> https://www.eclipse.org/downloads/packages/release/2019-06/rc1

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
___
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] CBI Maven Plugins 1.1.3 has been released

[Mikael Barbero]

I've released version 1.1.3 of the CBI maven plugins. You should only need to 
change the version from whatever you use to 1.1.3.

The release notes are on the release page: 
https://projects.eclipse.org/projects/technology.cbi/releases/maven-plugins-1.1.3
The documentation is here 
https://www.eclipse.org/cbi/maven-plugins/documentation/1.1.3/

Thanks.
Mikael


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
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] Apache Maven update

[Mikael Barbero]

Hi,

After https://bugs.eclipse.org/bugs/show_bug.cgi?id=484747, I've installed 
Apache Maven 3.3.9 on all build locations:

- /shared/common/apache-maven-latest -> /shared/common/apache-maven-3.3.9 (so 
it impacts all HIPPs & Linux slaves and build.eclipse.org)

On the shared instance (https://hudson.eclipse.org/shared/ 
), I've done the following changes:
- For the Windows slave, "apache-maven-latest" is now configured to be 
"c:\tools\apache-maven-3.3.9\"
- On the mac-tests2 slave, "apache-maven-latest" is now configured to 
"/shared/common/apache-maven-latest -> /shared/common/apache-maven-3.3.9" (note 
that /shared/common on mac-tests2 is not the same as /shared/common on HIPPs 
and build).

Cheers.
Mikael


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
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] Mac signing service issues -- plan for M4

[Mikael Barbero]

> Le 17 déc. 2015 à 14:13, Denis Roy  a écrit :
> *sigh*  The breakage coincided with system updates and a reboot.
> 
> How did you figure it out?  I couldn't get codesign to return an actual error 
> (other than, "1").

I don't send the full process output to the client (to avoid disclosing 
sensitive information) but everything is added to a local log file 
(~/webservice/eclipse.org/signing/log/ ).

> 
> Oh, and thank you for fixing this.

You're welcome.

Mikael

> 
> Denis
> 
> 
>> 
>> Cheers,
>> Mikael
>> 
>>> Le 16 déc. 2015 à 22:03, David M Williams < 
>>> david_willi...@us.ibm.com 
>>> > a écrit :
>>> 
>>> Given there is currently "no solution in sight" for this week, I think the 
>>> best course of action is to push ahead, and produce M4 as planned, with 
>>> affected projects disabling "Mac signing".
>>> 
>>> Once we have that build "in hand", a) if the user experience is "really 
>>> bad", we can reconsider (but as far as know, if they are doing fresh 
>>> install, then they have to do that "open" or "ctrl-open" trick we have used 
>>> in the past -- that is, in the past there has been milestones without a Mac 
>>> signature. b) if enough people are around next week, to redo contributions 
>>> with Mac signed, we can do an M4a deliverable.
>>> 
>>> But, in either case, since we are between a rock and a hard place, I think 
>>> best to try and produce one as planned. Otherwise, we might be well into 
>>> January before we could produce one, depending on everyone's holiday 
>>> schedules.
>>> 
>>> Thanks,
>>> 
>>> 
>>> 
>>> 
>>> 
>>> From:Denis Roy >> >
>>> To:Cross project issues >> >,
>>> Date:12/16/2015 01:36 PM
>>> Subject:[cross-project-issues-dev] Mac signing service issues
>>> Sent by: 
>>> cross-project-issues-dev-boun...@eclipse.org
>>>  
>>> 
>>> 
>>> 
>>> Folks,
>>> 
>>> The Mac signing service is currently broken. We're tracking the issue in :
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=484438 
>>> 
>>> 
>>> Denis
>>> 
> 
> ___
> 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 using GPGMail
___
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] Mac signing service issues -- plan for M4

[Mikael Barbero]

The signing issue is due to too much difference between the system clock and 
the time stamping authority (and for some reason, NTP does not work the mac 
signing machine). I manually synched the time on the machine and the signing 
now works properly.

Cheers,
Mikael

> Le 16 déc. 2015 à 22:03, David M Williams  a écrit 
> :
> 
> Given there is currently "no solution in sight" for this week, I think the 
> best course of action is to push ahead, and produce M4 as planned, with 
> affected projects disabling "Mac signing".
> 
> Once we have that build "in hand", a) if the user experience is "really bad", 
> we can reconsider (but as far as know, if they are doing fresh install, then 
> they have to do that "open" or "ctrl-open" trick we have used in the past -- 
> that is, in the past there has been milestones without a Mac signature. b) if 
> enough people are around next week, to redo contributions with Mac signed, we 
> can do an M4a deliverable.
> 
> But, in either case, since we are between a rock and a hard place, I think 
> best to try and produce one as planned. Otherwise, we might be well into 
> January before we could produce one, depending on everyone's holiday 
> schedules.
> 
> Thanks,
> 
> 
> 
> 
> 
> From:Denis Roy 
> To:Cross project issues ,
> Date:12/16/2015 01:36 PM
> Subject:[cross-project-issues-dev] Mac signing service issues
> Sent by:cross-project-issues-dev-boun...@eclipse.org
> 
> 
> 
> Folks,
> 
> The Mac signing service is currently broken. We're tracking the issue in :
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=484438 
> 
> 
> Denis
> 
> ___
> 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 using GPGMail
___
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] Update of /shared/common/apache-maven-latest

[Mikael Barbero]

Hi,

I have updated the symlink /shared/common/apache-maven-latest to Maven 3.3.3. 
It uses to point to v3.3.1. The release note is here 
https://maven.apache.org/docs/3.3.3/release-notes.html.

Every single HIPPs using a Maven task with a maven runtime named 
"apache-maven-latest" or similar rely on this symlink, so they will see the 
update.

Cheers,
Mikael


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
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] unable to connect to build.eclipse.org via http

[Mikael Barbero]

Yes, I just fixed it ;) (https://bugs.eclipse.org/bugs/show_bug.cgi?id=476936 
)

Cheers,
Mikael

> Le 9 sept. 2015 à 09:49, Lars Vogel  a écrit :
> 
> Seems fixed, website reports now: It's just you. http://build.eclipse.org is 
> up.
> 
> On Wed, Sep 9, 2015 at 9:29 AM, Daniel Megert  
> wrote:
>> It's not just you, see
>> http://www.downforeveryoneorjustme.com/http://build.eclipse.org/
>> 
>> Dani
>> 
>> 
>> 
>> From:Markus Knauer 
>> To:Eclipse Cross Project Issues
>> 
>> Date:09.09.2015 09:14
>> Subject:[cross-project-issues-dev] unable to connect to
>> build.eclipse.orgvia http
>> Sent by:cross-project-issues-dev-boun...@eclipse.org
>> 
>> 
>> 
>> 
>> Hi everyone,
>> 
>> anyone else having problems to connect to build.eclipse.org via http?
>> 
>>  Bug 476936 - Can't connect to build.eclipse.org via http
>>  https://bugs.eclipse.org/bugs/show_bug.cgi?id=476936
>> 
>> At the moment this prevents me from building our RAP Mars.1 RC3
>> contribution. If it cannot be fixed within the next two hours I'll try to
>> workaround this issue.
>> 
>> Thanks,
>> Markus___
>> 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
> 
> 
> 
> -- 
> Eclipse Platform UI and e4 project co-lead
> CEO vogella GmbH
> 
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Fax (032) 221739404, Email: lars.vo...@vogella.com, Web: 
> http://www.vogella.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

Re: [cross-project-issues-dev] Remote debug on a HIPP

[Mikael Barbero]

Hi Axel,

For security reasons, HIPP servers are running behind our firewall so you won't 
be able to remote debug something on it.

Cheers,
Mikael

 Le 8 juil. 2015 à 10:09, Axel RICHARD axel.rich...@obeo.fr a écrit :
 
 Hi,
 
 I want to remotely debug a test on one of our HIPP's job 
 (https://hudson.eclipse.org/emfcompare/view/logical%20model%20builds/job/master-build-on-egit-logical-nighlty/).
  
 I don't found how to do that on a HIPP. Is anybody already succeed in ? Is 
 anybody can tell me the procedure to do that ?
 
 Regards,
 
 -- 
 Axel RICHARD
 Eclipse Consultant
 EMF Compare committer
 Obeo
 
 axel_richard.vcf___
 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] Windows7-test slave disconnected from the Hudson shared instance for the day

[Mikael Barbero]

In order to test the new Hudson shared instance 
(https://hudson.eclipse.org/shared), I need to disconnect the windows slave 
from the current shared instance (https://hudson.eclipse.org/hudson 
https://hudson.eclipse.org/hudson). I will reconnect it by 1pm EDT.

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=412933#c24 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=412933#c24 for the migration 
plan.

Thanks,
Mikael___
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] [cbi-dev] Windows7-test slave disconnected from the Hudson shared instance for the day

[Mikael Barbero]

The following jobs run well on the new shared instance:

https://hudson.eclipse.org/shared/job/jgit-windows-test/ 
https://hudson.eclipse.org/shared/job/jgit-windows-test/
https://hudson.eclipse.org/shared/job/tracecompass-windows-nightly/ 
https://hudson.eclipse.org/shared/job/tracecompass-windows-nightly/

I just started https://hudson.eclipse.org/shared/job/ep46N-unit-win32 
https://hudson.eclipse.org/shared/job/ep46N-unit-win32. I will reconnect the 
Windows slave to the current shared instance (https://hudson.eclipse.org/hudson 
https://hudson.eclipse.org/hudson) once it is finished. Usually it takes ~5h. 
So if it does not fail before the end, the windows slave will then be 
reconnected around 3pm EDT. 

If anyone need it before, please say it, I will stop the job and and will 
reconnect the slave quickly.

Thanks.
Mikael


 Le 7 juil. 2015 à 10:14, Mikael Barbero mik...@eclipse.org a écrit :
 
 In order to test the new Hudson shared instance 
 (https://hudson.eclipse.org/shared https://hudson.eclipse.org/shared), I 
 need to disconnect the windows slave from the current shared instance 
 (https://hudson.eclipse.org/hudson https://hudson.eclipse.org/hudson). I 
 will reconnect it by 1pm EDT.
 
 See https://bugs.eclipse.org/bugs/show_bug.cgi?id=412933#c24 
 https://bugs.eclipse.org/bugs/show_bug.cgi?id=412933#c24 for the migration 
 plan.
 
 Thanks,
 Mikael
 ___
 cbi-dev mailing list
 cbi-...@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe from 
 this list, visit
 https://dev.eclipse.org/mailman/listinfo/cbi-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] Hudson shared instance migration: volunteers needed!

[Mikael Barbero]

(cross-posted on cross-project and cbi-dev)

After a lot of waiting (https://bugs.eclipse.org/bugs/show_bug.cgi?id=412933 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=412933), we now have a new 
upgraded version of the Hudson shared instance 
(https://hudson.eclipse.org/shared/ https://hudson.eclipse.org/shared/). It 
runs on the same infrastructure as HIPPs so it will be easier for us to 
maintain this instance up-to-date.

No job has been migrated yet, we would like to start with some volunteer to 
check everything works fine before doing a massive migration. So, is there 
anyone who wants to migrate to this instance? Obviously, this will be non 
destructive and nothing from the current shared instance will be removed and/or 
modified until everything work properly on the new one.

Thanks for your help!

Mikael


___
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 v1.1.2 released (incl. jarsigner)

[Mikael Barbero]

Hi, 

The CBI Maven plugins have just been released to repo.eclipse.org 
http://repo.eclipse.org/. 

The most notable changes are a some changes to jarsigner, winsigner and 
macsigner to make them much more reliable than they were (because of issues 
with unclosed resources).

It also now requires Java 1.7, i.e.,  the VM that runs Maven Tycho must now be 
Java 1.7 or later.

Cheers,
Mikael___
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 moving to Java 7

[Mikael Barbero]

Greetings,

Before moving the CBI maven signer plugins (jarsigner, macsigner and winsigner) 
to Java 7, we would like to know if anyone in the community is using one or all 
of these signers plugins on Java 6 with Tycho 0.22 (and don't plan to move to 
Tycho 0.23 after it is released as it will require to run on Java 7 too). 

Thanks.

Mikael
___
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] Upgrade of Nexus to 2.11.2 and unzip plugin to 0.14

[Mikael Barbero]

Hi,

I plan to upgrade the Nexus instance to 2.11.2 today around 8am EDT. You should 
expect a short unavailability for about 20min.

Thanks.
Mikael
___
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] Hudson shared instance cleanup

[Mikael Barbero]

Hi,

As announced on https://bugs.eclipse.org/bugs/show_bug.cgi?id=460918 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=460918, several old inactive 
jobs has been removed and some has been deactivated before deletion on April 
7th. 

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=460918#c17 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=460918#c17 for the list of 
removed jobs and https://bugs.eclipse.org/bugs/show_bug.cgi?id=460918#c18 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=460918#c18 for the list of 
deactivated jobs to be removed on April 7th.

If one of your job is in the deactivated list and should not be removed, please 
add a comment on that bug. 

I will keep a backup of deleted jobs for some times. If you need some jobs to 
be restored, I still can do it but you have to add a comment on the bug 
quickly. I won't advertise the removal of the backup which should happen by the 
end of April.

Kind regards,
Mikael

 Le 26 févr. 2015 à 11:48, Mikael Barbero mik...@eclipse.org a écrit :
 
 Hi,
 
 I would like to start a discussion about the cleanup of the Hudson shared 
 instance. It is bloated with a lot of inactive jobs and it would be great if 
 we could clean it up a bit. I think that most of theses inactive jobs are 
 remains which pre-date HIPPs. I created the bug 460918 
 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=460918 
 https://bugs.eclipse.org/bugs/show_bug.cgi?id=460918) with the list of jobs 
 without any successful build in the last 12 months. There are 218 such jobs 
 on the 360 current jobs in the shared instance. After the job name is the 
 duration since last time when a successful build has been seen!
 
 If you see one of your jobs and want it to be kept, please comment on the 
 bug. Speak now or forever hold your peace ;)
 
 Cheers,
 Mikaël
 ___
 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] HIPP upgrade capability to Hudson 3.2.2 is now online.

[Mikael Barbero]

Dear community,

I am glad to announce that Denis and I (based on Thanh's previous work) have 
finished the work on the HIPP upgrade facility (see 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=422507 for details). 

We are now offering the upgrade to Hudson 3.2.2 through your Eclipse account 
page (https://dev.eclipse.org/site_login/myaccount.php). On the right side of 
this page, you will find the usual control to start / stop / restart your HIPP 
and now also an Upgrade link (if you don't use the latest version already).

A full backup of your current HIPP environment is performed before the upgrade. 
If the upgrade fails or the upgraded HIPP performs erratically, please file a 
bug against Community  Hudson as soon as possible.

Cheers,
Mikael
___
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] Hudson shared instance cleanup

[Mikael Barbero]

Hi,

I would like to start a discussion about the cleanup of the Hudson shared 
instance. It is bloated with a lot of inactive jobs and it would be great if we 
could clean it up a bit. I think that most of theses inactive jobs are remains 
which pre-date HIPPs. I created the bug 460918 
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=460918 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=460918) with the list of jobs 
without any successful build in the last 12 months. There are 218 such jobs on 
the 360 current jobs in the shared instance. After the job name is the duration 
since last time when a successful build has been seen!

If you see one of your jobs and want it to be kept, please comment on the bug. 
Speak now or forever hold your peace ;)

Cheers,
Mikaël___
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 restart

[Mikael Barbero]

Hi,

I would like to let you know that the Gerrit server @ eclipse.org will be 
restarted at 4pm EDT for maintenance. You should notice that the git 
repositories (handled through Gerrit) will not reachable during this restart.

Mikael
___
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