[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [gef-dev] Multi-branch build for GEF Classic
|
Hi Patrick,
everything that makes our build better is good. The only thing that I'm
concerned of is that the old build created promoted to
https://download.eclipse.org/tools/gef/classic/latest/
Do we want that for every PR? Or would we do this in a new separate
build job that would only run at midnight?
BR,
Alois
PS: I noticed a branch with my name. Should this one be deleted?
On Tue, 2023-12-12 at 20:29 +0100, Patrick Ziegler via gef-dev wrote:
> Hello everyone,
>
> I've set up a new multi-branch pipeline on the Jenkins to deprecate
> the
> old job.
>
> New: https://ci.eclipse.org/gef/job/build-classic/
>
> Old: https://ci.eclipse.org/gef/job/gef-classic-latest/
>
>
> Main motivation being that the new job has a built-in GitHub
> integration, meaning the build is also triggered for each
> pull-request/branch
>
> and (more importantly) is also included in the automatic checks that
> shown in the browser.
>
> I've disabled the old job and -if there are no objections- plan to
> delete it within the next few days.
>
>
> Many regards,
>
> Patrick
>
> _______________________________________________
> gef-dev mailing list
> gef-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/gef-dev
