[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [gef-dev] Multi-branch build for GEF Classic
|
- From: Patrick Ziegler <ziegler.patrick@xxxxxxxxxx>
- Date: Tue, 12 Dec 2023 20:46:15 +0100
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=KadLclYZyz+qZOrM1fW8QXrayPLui80GPus58BPaAaU=; b=VWtfzHWysTlgjGQTc/kEtzRwG2N3r2lCwBRD1u3dV3z2srp/At237jiYJaJOQFHJ8juY9dUYgUkSO5TbvSWt64zP2tKvGiUQ5UTeTGhky1mcRFYaVFSwoQt1Lkyw5AZg5216F+axtqB8anJPlFreRQKuMi8RVl83/hXLHGgMpLv0mIazA+bovbzYk8x60xNoyrRVpeENICyCoAlAjf5+fhTM1Q9KtxPtK1SOaynkndyqldl0ySa0Dawpv83/hGqV37MQpMzE1drGN6po+pwt1afDLeHaPgg0aSRoS+i6bGoFxzLQcgyGNsukZ/vmmhYtSeg8awrFvoGaSpUMpA2cJQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=g6j/l2XwCyqblgL/1TGfDJftXhChZOHn2NoB7Ci05Sp35moB+nZB0bZO9dErJhASQe+24GuV59l/xAQ/wOQGQ5BCPvte7fkMXASnQJ6n6sOnbit2OaTrsi54kIXzaG+66dHvV4BRdUr9LaEHsO0k2lo3wBvBFI0T7lzzNjj48v7k8EI7XgPOQJxHeEHfgOpZM5dn+YOESBTltC8KF5bOatPKIirTkmTE0xW4w/PyGi5/aBLfPIqixLjtpMLP9CGyF7pq+KcdNlMPehD0z0p2MhhxlBpFrZq4D6hxQpN2M4/1jGDU3vk5v8QvLBXLNT/gvQSGc0plRXvve/QsVLrOfQ==
- Delivered-to: gef-dev@xxxxxxxxxxx
- List-archive: <https://www.eclipse.org/mailman/private/gef-dev/>
- List-help: <mailto:gef-dev-request@eclipse.org?subject=help>
- List-subscribe: <https://www.eclipse.org/mailman/listinfo/gef-dev>, <mailto:gef-dev-request@eclipse.org?subject=subscribe>
- List-unsubscribe: <https://www.eclipse.org/mailman/options/gef-dev>, <mailto:gef-dev-request@eclipse.org?subject=unsubscribe>
- User-agent: Mozilla Thunderbird
Hi Alois,
yeah, that's something I noticed as well. My current plan is to
configure the Jenkinsfile to only promote when building on the
"master" branch.
But this is just a band-aid. In general, we should probably
consider cleanup up our build process. The only problem being that
I don't really know what the required steps are...
@Ed You did something similar for the WindowBuilder project. Do
you have some advice on how I could get started?
>
PS: I noticed a branch with my name. Should this one be deleted?
It's your branch. If you don't need it, just delete it ;D
Many regards,
Patrick
On 12.12.23 20:40, Alois Zoitl wrote:
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