Re: [platform-releng-dev] Trigger test integration build

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

> I
would prefer the I-build to be controlled.

+1. We also want to avoid scheduling
too many builds and make sure we avoid to compete with more important builds
being scheduled, e.g. an M-build.

And in most cases, one build per day
is enough.

Dani



From:      
 "Sravan K Lakkimsetti"
<sravankumarl@xxxxxxxxxx>
To:      
 "Eclipse platform
release engineering list." <platform-releng-dev@xxxxxxxxxxx>
Date:      
 10.02.2017 11:43
Subject:    
   Re: [platform-releng-dev]
Trigger test integration build
Sent by:    
   platform-releng-dev-bounces@xxxxxxxxxxx

---

Hi,
 
I would prefer the I-build to be controlled.
But there is a job on Hudson which can be used to verify integration builds.
https://hudson.eclipse.org/platform/view/My%20Jobs/job/eclipse-aggregator-master/
 
This available for platform ui committers.
If any other team is interested. I will add them
 
From: Mickael Istria [mailto:mistria@xxxxxxxxxx]
Sent: Friday, February 10, 2017 4:03 PM
To: platform-releng-dev@xxxxxxxxxxx
Subject: Re: [platform-releng-dev] Trigger test integration build
 
Hi,

On the initial topic, would it make sense to give permissions to run a
build on Hudson to all Platform committers, so if one needs an extra build
ASAP, they can trigger it by themselves? That would allow to better share
the work.

Cheers,
-- 
Mickael Istria
Eclipse developer for Red
Hat Developers
My
blog - My
Tweets

_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev