Re: [cdt-dev] Build artifacts for cdt-verify jobs?

[Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx>]

I would also be concerned about the amount of disk space that would be used to archive artifacts for every Gerrit build. We keep a lot of them so that if there is a failure, there is a reasonable time window for people to go look at the job to see what failed.

In the Trace Compass project we do what Elena proposed - to have a special job. But if you need special builds for several different bugs/people, it won't scale very well. In the past I have shared CDT p2 repositorys (zips) from Dropbox. Maybe that would be an easier solution for you.

Marc-Andre

---

From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Alena Laskavaia [elaskavaia.cdt@xxxxxxxxx]
Sent: Thursday, 02 April 2015 8:31 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] Build artifacts for cdt-verify jobs?

Creating artifacts takes time, we want to minimize verify job as much as possible because with current 40 min it is backed up already.

We can create a special job like a master job which produces artifacts but has a parameter of the branch (gerrit review) to pull, when you start it you would

have to provide this parameter manually

On Thu, Apr 2, 2015 at 2:37 AM, Nathan Ridge <zeratul976@xxxxxxxxxxx> wrote:

I notice that cdt-verify jobs (e.g. [1]) do not have build artifacts the way cdt-master jobs do (e.g. [2]). Why not?

Is there a way to get Hudson to build CDT with a patch that's not on master (or a release branch), for example for the purpose of sharing it with someone who is unable to build it themselves?

Thanks,
Nate

[1] https://hudson.eclipse.org/cdt/job/cdt-verify/2539/
[2] https://hudson.eclipse.org/cdt/job/cdt-master/503/

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