From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | buildfarm-members(at)postgresql(dot)org |
Cc: | buildfarm-admins(at)postgresql(dot)org |
Subject: | Moving to HTTPS |
Date: | 2017-01-07 21:37:47 |
Message-ID: | 89d566b4-58fb-c1e9-97ef-46d4d915b86c@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members |
In common with the rest of the PostgreSQL infrastructure, we will
shortly be moving the buildfarm server to supporting HTTPS, and
eventually will stop support for plain HTTP. Many installations on
buildfarm animals will not need any great adjustment, others will need
some extra modules installed. Here's a simple test that should help tell
if your animal needs some extra stuff installed. Run something like this
on your animal, making sure that the perl in your path is the one used
to run the buildfarm client:
perl -MLWP::Simple -e 'head(q{});
If this doesn't complain you should be good. If it does, you probably
need to install the LWP::Protocol::https module, and anything it depends
on (e.g. crypto libraries).
This isn't enabled yet, I'm just being proactive so you don't get caught
having to adjust in a hurry.
Windows users probably don't need to worry - this works on every
installation of AS perl I have.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2017-01-07 21:55:23 | Re: Moving to HTTPS |
Previous Message | Andrew Dunstan | 2017-01-04 13:43:13 | Re: git failures |