Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 366849

Summary:	[releng] Review the hudson tests-job
Product:	[Modeling] OCL	Reporter:	Adolfo Sanchez-Barbudo Herrera <adolfosbh>
Component:	Core	Assignee:	OCL Inbox <mdt-ocl-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	ed
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Adolfo Sanchez-Barbudo Herrera

2011-12-15 12:55:35 EST

With the new core-tools layout, the tests job need reviewing.

We will probably keep (renamed) the all-in-one stuff (bukminster files, scripts,etc) to check this.

P.S: Ed my idea is having the test-job purely for testing (without signing neither publishing artifacts). Let me know if you want constructing, signing, and publishing artifacts .. Perhaps only the constructing artifacts so they may be checked directly from hudson.

Regards,
Adolfo.

Comment 1 Adolfo Sanchez-Barbudo Herrera

2011-12-19 08:38:21 EST

Well,

I've reconsidered this. Keeping old files for the test job, means duplication of the repositories defined in the rmap files. Not very maintainable.

Conceptually, what we want for the tools job is a tools build in which we want to download the OCL Core sources in the buckminster workspace instead of feeding the buckminster target platform with the OCL Core jars taken from a Core build.

I think I could sort out this with some tunning of the rmap (plus a configuration property).

Working on this.

Comment 2 Adolfo Sanchez-Barbudo Herrera

2011-12-22 13:59:20 EST

Still waiting for a functional tools build to verify the currently tests job. If Xtext doesn't get fixed tomorrow, I'll create an experimental branch, fix compiling errors in my own, and build against such a branch.

Regards,
Adolfo

Comment 3 Ed Willink

2011-12-22 14:34:49 EST

(In reply to comment #2)
> I'll create an experimental branch, fix
> compiling errors in my own, and build against such a branch.

Try bug/366849

Comment 4 Adolfo Sanchez-Barbudo Herrera

2011-12-23 07:14:09 EST

Oh dear,

I didn't realize the branch you mentioned was related to this bug >.<.... I thought it was a branch you were working on. I didn't want to contaminate it with releng changes, and I was doing it directly to master.

Anyway, the currently running tests-job looks like it's properly running test cases, let's see what happens with the the p2 repository building.

Cheers,
Adolfo.

Comment 5 Adolfo Sanchez-Barbudo Herrera

2011-12-23 07:20:27 EST

Build failed ;P

New fixes arriving...  I'll directly work on bug/366849 to avoid rebasing/merging between master an this bug branch. When finished, I'll only cherry pick the relevant commits.

Cheers,
Adolfo.

Comment 6 Ed Willink

2011-12-23 07:30:56 EST

(In reply to comment #5)
> New fixes arriving...  I'll directly work on bug/366849 to avoid

That branch is all yours. If there's anything that I should be aware of please communicate the problem here.

Comment 7 Adolfo Sanchez-Barbudo Herrera

2011-12-23 08:18:20 EST

Well,

I only needed to do some minor fixes in the tests-job hudson configuration, so no extra committs needed.. Now we have functional tests-job  (remember to merge the current master, before running the job on a bug branch).

I'll remove old buckminster files and resolve the bug.

Comment 8 Adolfo Sanchez-Barbudo Herrera

2011-12-23 08:25:41 EST

Resolving as fixed

Comment 9 Ed Willink

2012-01-04 16:27:34 EST

Fantastic. I can now do preliminary full builds.

Comment 10 Ed Willink

2013-05-20 11:35:24 EDT

CLOSED after a year in the RESOLVED state.