I'm trying to write a job which reads from:
https://ci.centos.org/artifacts/sig-atomic/rdgo/centos-continuous/
However on the Duffy node:
# host ci.centos.org ci.centos.org has address 172.19.0.13 #
Which appears to be something entirely different, it's a Jetty server (Server: Jetty(winstone-2.9)).
I tried working around this by using the public IP:
``` curl http://66.187.224.197/artifacts/sig-atomic/rdgo/centos-continuous/build/repo... ```
But that just times out.
I can likely work around this by using rsync or some other way to get content from artifacts, but it'd be really a lot better if I could read them over HTTP.
On Jul 13 13:54, Colin Walters wrote:
I'm trying to write a job which reads from:
https://ci.centos.org/artifacts/sig-atomic/rdgo/centos-continuous/
However on the Duffy node:
# host ci.centos.org ci.centos.org has address 172.19.0.13 #
Which appears to be something entirely different, it's a Jetty server (Server: Jetty(winstone-2.9)).
I tried working around this by using the public IP:
curl http://66.187.224.197/artifacts/sig-atomic/rdgo/centos-continuous/build/repodata/But that just times out.
I can likely work around this by using rsync or some other way to get content from artifacts, but it'd be really a lot better if I could read them over HTTP.
You can use 'http://artifacts.ci.centos.org' both inside and outside the CI Infra.
Cheers! --Brian
On Wed, Jul 13, 2016, at 02:05 PM, Brian Stinson wrote:
You can use 'http://artifacts.ci.centos.org' both inside and outside the CI Infra.
Oh right, now I remember we talked about this before, and the problem I had with that was that it lacks (working) https://. I ended up working around that in the same way I did before, sed the baseurl just when working in the CI infra:
https://github.com/cgwalters/sig-atomic-buildscripts/blob/c5e06fab28a42aecc3...
It's OK for now, but it'd be nicer to have https:// by default there too.
On 13/07/16 20:54, Colin Walters wrote:
On Wed, Jul 13, 2016, at 02:05 PM, Brian Stinson wrote:
You can use 'http://artifacts.ci.centos.org' both inside and outside the CI Infra.
Oh right, now I remember we talked about this before, and the problem I had with that was that it lacks (working) https://. I ended up working around that in the same way I did before, sed the baseurl just when working in the CI infra:
https://github.com/cgwalters/sig-atomic-buildscripts/blob/c5e06fab28a42aecc3...
It's OK for now, but it'd be nicer to have https:// by default there too.
the challenge there might be that the same host has https://ci.centos.org on there. I wonder if we can use another ip there and setup the second host as well ?
-
Brian Stinson -
Colin Walters -
Karanbir Singh