Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Guidance on how long to keep Jenkins jobs on around for (e.g. forever, a certain number of years, a few years worth of releases)...

Hi Scott,

The releng team doest not have any guidance for how long a particular release of an Eclipse project could/should be serviceable. It's up to you and depends on the kind of "contract" your project want to set with its users base / consumers. To have some guidances, as Denis said, it may be worthwhile to reach out to the greater community on the other mailing-list. 

Note that we strive for a stable Jenkins infra. However, we don't provide any guarantee for a long term support of the said infra that would let give you the ability to rebuild your project in 10 years from now.

As such, to be able to have a long term support of some versions and keep the ability to build/release/test a release for 20 years, you will need to do regular maintenance on build pipelineof the said release in order to keep it up to date and serviceable.


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

On 1 Feb 2021, at 19:27, Denis Roy <denis.roy@xxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi Scott,

I'm not sure if you've seen a response to this, but you could also consider the cross-project-issues mailing list, as you would get a much wider audience:


On 2021-01-28 11:34 a.m., Scott Marlow wrote:


In the Jakarta EE Platform TCK environment [1], we are required to service our old releases.  We do not yet have a limit defined on how far back we go.  Our current Jakarta EE releases are { 8, 9 } and further releases are expected this year.  So, we could have a request in 20 years for service release of our Jakarta EE Platform TCK 8.0.x software which requires running the corresponding build/release/test jobs for Jakarta EE 8. 

My question for this mailing list is whether Eclipse has any guidance for how long (either in years or number of major releases) a particular Eclipse release could/should be serviceable with regard to future service releases being possible?



cbi-dev mailing list
To unsubscribe from this list, visit
Denis Roy
Director, IT Services | Eclipse Foundation
Eclipse Foundation: The Community for Open Innovation and Collaboration
Twitter: @droy_eclipse
cbi-dev mailing list
To unsubscribe from this list, visit

Attachment: signature.asc
Description: Message signed with OpenPGP

Back to the top