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

Bug 481904

Summary:	No staging repo for EGit breaks N20151110-2000
Product:	[Eclipse Project] Platform	Reporter:	David Williams <david_williams>
Component:	Releng	Assignee:	David Williams <david_williams>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	bsd, Lars.Vogel, nobody
Version:	4.6
Target Milestone:	4.6 M4
Hardware:	PC
OS:	Linux
Whiteboard:

Description David Williams

2015-11-11 01:27:23 EST

At some point, for some reason, we used a "staging" repo to get EGit/JGit. Namely, 

http://download.eclipse.org/egit/staging/v4.0.0.201505260635-rc2

We have a very small test dependency on JGit. I will update to whatever the latest is. 

We use the same version in our M-builds, so will fix there too. 

(It is not often a nightly build can be used as an early warning to fix the next day's M-build!)

Comment 1 David Williams

2015-11-11 01:54:01 EST

FWIW, the test that needs jgit and egit.core to compile, is 

/org.eclipse.releng.tests/src/org/eclipse/releng/tests/GitCopyrightAdapterTest.java

And, it does still compile in my workbench, using JGit and EGit.core at version 4.1.0.201509280440-r. The manifest for that test bundle specifies the two bundle optionally, at a version 3.0 minimum. 

There is one "discouraged access" method we use. (And, always have, I think). 

The dependencies are listed as "optional" and we do not actually run these tests in our production tests.

Comment 2 David Williams

2015-11-11 02:10:30 EST

http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=0b0d50f1df859c05688c748b3ad4e19ade36b8d2

Fixed in both streams.

Comment 3 Lars Vogel

2015-11-11 03:00:02 EST

(In reply to David Williams from comment #2)
> http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/
> commit/?id=0b0d50f1df859c05688c748b3ad4e19ade36b8d2
> 
> Fixed in both streams.

Our Gerrit build trigger will fails. 

prereqs-4.6.0-SNAPSHOT.target: Failed to load p2 metadata repository from location http://download.eclipse.org/egit/staging/v4.0.0.201505260635-rc2
[DEBUG] Closing connection to remote
[ERROR] Failed to resolve target definition /home/hudson/genie.platform/.hudson/jobs/eclipse.platform.ui-Gerrit/workspace/.maven/repo/org/eclipse/eclipse-sdk-prereqs/4.6.0-SNAPSHOT/eclipse-sdk-prereqs-4.6.0-SNAPSHOT.target: Failed to load p2 metadata repository from location http://download.eclipse.org/egit/staging/v4.0.0.201505260635-rc2: No repository found at http://download.eclipse.org/egit/staging/v4.0.0.201505260635-rc2. -> [Help 1]

Comment 4 David Williams

2015-11-11 07:55:47 EST

Remember ... the Gerrit jobs need a day or so to get anything new from "parent pom" or "prereqs" ... if you go by the once-a-day schedule. So I do not think there is a "bug" here or reason to re-open. If anything, please open one for yourself to "... learn to hit "deploy" deploy button on Hudson" :)

Comment 5 Lars Vogel

2015-11-11 08:34:04 EST

(In reply to David Williams from comment #4)
> Remember ... the Gerrit jobs need a day or so to get anything new from
> "parent pom" or "prereqs" ... if you go by the once-a-day schedule. So I do
> not think there is a "bug" here or reason to re-open. If anything, please
> open one for yourself to "... learn to hit "deploy" deploy button on Hudson"
> :)

Not sure what the last sentence means, I send a clarification question to the releng mailing list. I'm not aware of this deploy button but would be happy to learn about it. If there is no easy way to fix that on our side today, could you re-run the aggregator build to fix our Gerrit validation build?

Comment 6 Lars Vogel

2015-11-11 08:47:54 EST

I think I found the answer, releng please correct me if I'm wrong. We
have Gerrit jobs for the deployment of the parent pom, e.g.,
https://hudson.eclipse.org/platform/job/deploy-eclipse-platform-parent-pom-4.6/

Re-running them should fix the problem, I guess. Currently only releng
seems to have the permission to run these jobs, I will request
permission to run them also.

Comment 7 David Williams

2015-11-11 11:47:29 EST

(In reply to Lars Vogel from comment #6)
> I think I found the answer, releng please correct me if I'm wrong. We
> have Gerrit jobs for the deployment of the parent pom, e.g.,
> https://hudson.eclipse.org/platform/job/deploy-eclipse-platform-parent-pom-4.
> 6/
> 
> Re-running them should fix the problem, I guess. Currently only releng
> seems to have the permission to run these jobs, I will request
> permission to run them also.

I assumed you already had that, Lars, since this has come up before. 

While the "manual deploy" is not bad, I have also opened bug 481941. 
Perhaps, someday, someone will want to improve the automation for those "deploy" jobs. 

Thanks,

Comment 8 Lars Vogel

2015-11-11 14:25:31 EST

(In reply to David Williams from comment #7)
> (In reply to Lars Vogel from comment #6)
> > I think I found the answer, releng please correct me if I'm wrong. We
> > have Gerrit jobs for the deployment of the parent pom, e.g.,
> > https://hudson.eclipse.org/platform/job/deploy-eclipse-platform-parent-pom-4.
> > 6/
> > 
> > Re-running them should fix the problem, I guess. Currently only releng
> > seems to have the permission to run these jobs, I will request
> > permission to run them also.
> 
> I assumed you already had that, Lars, since this has come up before. 

Paul gave me the permission to trigger the job. Thanks for pushing me in the right direction. Sorry for not knowing about these jobs before your gentle push. :-)