[
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 https://ci.eclipse.org/jakartaee-tck around for (e.g. forever, a certain number of years, a few years worth of releases)...
|
Hi Mikael,
On 2/2/21 4:35 AM, Mikael Barbero
wrote:
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.
Thank you, that answers my initial question as to whether there
is any general guidance already. I think it is fine that there is
not any general guidance on this topic.
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.
IMO, I think it would be good to only maintain a limited set of
releases to keep costs down but that is something to be discussed
elsewhere regarding https://ci.eclipse.org/jakartaee-tck. Thank
you for helping!
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.
Thanks for pointing this out!
Cheers,
Scott
Cheers,
Mikaël Barbero
Manager —
Release Engineering and Technology | Eclipse Foundation
🐦 @mikbarbero
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:
https://accounts.eclipse.org/mailing-list/cross-project-issues-dev
Denis
On 2021-01-28 11:34 a.m.,
Scott Marlow wrote:
Hi,
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?
Scott
[1] https://ci.eclipse.org/jakartaee-tck/
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cbi-dev
--
Denis Roy
Director, IT Services | Eclipse Foundation
Twitter: @droy_eclipse
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cbi-dev
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cbi-dev