Bug 337317

Comment 1 Chris Aniszczyk 2011-02-16 09:37:40 EST

Actually, Hallvard should have his committer id added to the job too but I don't know his committer id.

Comment 2 Eclipse Webmaster 2011-02-16 10:01:06 EST

Done.

-M.

Comment 3 Hallvard Traetteberg 2011-02-17 17:15:27 EST

(In reply to comment #1)
> Actually, Hallvard should have his committer id added to the job too but I
> don't know his committer id.

My id is htraetteb, I think.

Comment 4 Hallvard Traetteberg 2011-02-18 11:00:00 EST

(In reply to comment #2)
> Done.
> 
> -M.

Thanks!

I've tried to configure the build, using egit as the model (since I use Maven + Tycho). The SCM is git, with the repo at github. The manually schedules build fails with a timout when trying to clone from git://github.com/hallvard/js4emf.git. Does this mean I have to move to git @ eclipse.org?

Comment 5 Eclipse Webmaster 2011-02-18 11:39:02 EST

I suspect the issue is that the proxy/firewall isn't allowing your outbound git URI request.  If you use an http git URI it should be fine. You may need to make sure to pass the proxy configuration to git if it's not picking up the details from the environment.

-M.

Comment 6 Hallvard Traetteberg 2011-02-18 11:50:17 EST

(In reply to comment #5)
> I suspect the issue is that the proxy/firewall isn't allowing your outbound git
> URI request.  If you use an http git URI it should be fine. You may need to
> make sure to pass the proxy configuration to git if it's not picking up the
> details from the environment.

github gives me the following https URI: https://hallvard@github.com/hallvard/js4emf.git
However, the build fails with
fatal: Unable to find remote helper for 'https'

Perhaps I'm missing the point here?

Comment 7 Eclipse Webmaster 2011-02-18 15:53:46 EST

Sigh it looks like our git build can't find libcurl.  I'll have to work on producing a new git RPM and pushing it out to the hudson nodes.

If you need this 'now' your best bet is going to be using an Eclipse git URI.

-M.

Comment 8 Hallvard Traetteberg 2011-02-18 16:22:56 EST

(In reply to comment #7)
> Sigh it looks like our git build can't find libcurl.  I'll have to work on
> producing a new git RPM and pushing it out to the hudson nodes.
> 
> If you need this 'now' your best bet is going to be using an Eclipse git URI.
> 
> -M.

I've moved to git @ eclipse, now, and the build setup works. Thanks for your effort!

Comment 9 Eclipse Webmaster 2011-03-01 13:06:53 EST

I've built and installed a new git RPM with https support.

-M.