Hi,
I do have problems connecting to the shared hudson instance:
https://hudson.eclipse.org/hudson
"This HIPP instance is currently unavailable…"
Is there something wrong?
Thanks
Jens
--
IBH SYSTEMS GmbH
D-85235 Pfaffenhofen an der Glonn
Läutenring 43
Geschäftsführer / CEO: Dr. Thomas
I believe that is the old instance.
The shared instance is now hipp-ified:
https://hudson.eclipse.org/shared/
Denis
On 11/01/16 08:54 AM, Jens Reimann wrote:
Hi,
I do have problems connecting to the shared hudson instance:
https://hudson.eclipse.org/hudson
"This HIPP instance is currently
Ok,
then there is a dead link at: https://hudson.eclipse.org/ which points
to https://hudson.eclipse.org/hudson
Thanks & sorry
Jens
On 01/11/2016 03:24 PM, Denis Roy wrote:
> I believe that is the old instance.
>
> The shared instance is now hipp-ified:
> https://hudson.eclipse.org/shared/
>
>
I just ran, repeatedly, into an "java.net.UnknownHostException:
eclipse.org" on our HIPP instance [1].
It worked a few hours ago.
Is there any known issue or change?
[1] https://hudson.eclipse.org/package-drone
--
IBH SYSTEMS GmbH
D-85235 Pfaffenhofen an der Glonn
Läutenring 43
You can call them being lazy, but I call it being understaffed/underfunded.
While I agree with the technicalities of your argument Mickael, we have
also been very careful on the planning council not to put too much burden
on the projects. Forcing them to update all the versions they have in the
Right, I will fix that.
Denis
On 11/01/16 09:29 AM, Jens Reimann wrote:
Ok,
then there is a dead link at: https://hudson.eclipse.org/ which points
to https://hudson.eclipse.org/hudson
Thanks & sorry
Jens
On 01/11/2016 03:24 PM, Denis Roy wrote:
I believe that is the old instance.
The
Hi
Or just cache the checksum.
Regards
Ed Willink
On 11/01/2016 18:55, Sam Davis wrote:
Even if fully-qualified versions are used, is there anything to stop
someone from rebuilding bundles with changed content but reusing the
same version and qualifier? This is bad practice but
Even if fully-qualified versions are used, is there anything to stop
someone from rebuilding bundles with changed content but reusing the same
version and qualifier? This is bad practice but I've heard of projects (not
at Eclipse) doing it and it would mean the only way to absolutely guarantee