| [eclipse.org-committers] Eclipse IT update |
Greetings committers and project leads,
I have a relatively long but useful update for you.
A decade ago [0], we began the discussion about what to do with the Eclipse Forums as, with time, the underlying software has become stale and is now a serious security liability for the Foundation. After a decade of reluctance, the Forums will be sunset December 31, 2024.
Please discuss with your community which
location is best for user-centric discussions for your project.
Some options include using the Eclipse Chat Service [1], GitHub
Discussions that can be enabled for your project, or the
creation of a user discussion mailing list. Please use a
HelpDesk ticket [5] to request any needed resources for your
project.
The Forums will be archived in
read-only, static html format. More information can be found in
the HelpDesk issue [0].
The deprecation of Git/Gerrit & Bugzilla is on schedule, and at this time, the vast majority of projects have migrated off those platforms. The plan can be found here [2]
The infra team will create a (very
large) static html copy of all Bugzilla bugs in the coming
months. Bugzilla sunset is slated for May 2025.
The Foundation's Releng team has been knee-deep in migrating Jenkins instances to a robust and scalable storage cluster (away from a single storage device operating beyond capacity) to help improve the service availability of the Common Build (CBI) Jenkins offering.
Although the migrations are not yet
complete, we're already observing much needed stability
improvements across all instances. You can follow the effort
here [3]
For more information on Eclipse Common
Build, please see: https://github.com/eclipse-cbi/cbi/wiki
As detailed here [4] RISC V agents are
available for builds in a very limited quantity for building
native code. If you'd like to use the agents, please file a
HelpDesk ticket [5].
Did you know that the Foundation hosts a Chat Service. You can check it out at https://chat.eclipse.org/ and your project can request a room by filing a HelpDesk ticket [5].
We encourage all project Release
Engineers to subscribe to, and monitor the
cross-project-issues-dev mailing list [6]. It is the primary
mechanism used by the EF Releng team to communicate about CBI
and build/releng issues in general.
The EF's IT Service Level Agreement (SLA) has been updated to reflect new realities in 2024, and has been renamed to Service Level Objectives. In short, we've removed Git/Gerrit/Bugzilla and other terminated (or deprecated services) and have added GitLab, the Eclipse Downloads area, the ECA and sync mechanisms as Critical or Best Effort Services. You can consult the new SLO document at [7].
The Foundation is committed to providing
a quality, robust and useful infrastructure and set of tools to
allow you to get things done.
The Infra team, known previously as
Webmasters, can now be reached at
infratructure@xxxxxxxxxxxxxxxxxxxxxx. The preferred way of
interacting with the EF IT team is through HelpDesk [5].
Many thanks for taking the time to read
this communication. We understand that migrations and
improvements can be disruptive, and we're sparing no effort
towards minimizing the downsides and helping your projects be
successful.
[0] https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/187
[3] https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5054
[4]
https://gitlab.eclipse.org/eclipsefdn/infrazilla/-/issues/1730
[5]
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/
[6]
https://accounts.eclipse.org/mailing-list/cross-project-issues-dev
[7]
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/IT-Service-Level-Objectives
Denis Roy
Director, IT Services | Eclipse Foundation
Eclipse Foundation: The Community for Open Innovation and Collaboration
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature