Page MenuHomeSoftware Heritage

use CNAME for upcoming jenkins CI
Closed, ResolvedPublic

Description

Submitting this before it becomes to painful to change later: we should use abstract service names rather than hostnames for new services.
In particular the new ci should have a CNAME like "ci" or "jenkins" rather than http://thyssen.internal.softwareheritage.org:8080/ .

To be coordinated with @douardda as he is actively working on the Jenkins setup.

Event Timeline

zack created this task.Oct 3 2018, 3:40 PM
zack triaged this task as High priority.

I'm +1 for jenkins.softwareheritage.org

olasd added a subscriber: olasd.Oct 4 2018, 11:30 AM

JFTR, setting up a reverse proxy with https in front of this service was always the plan before this went further than the prototype stage :)

The only blocker is choosing which of our public-facing hosts should play the role of the reverse proxy. I'll be going with tate, which hosts phabricator and the wikis.

should the public facing (rev proxy) be a "web server" like nginx (or apache) or a varnish? (I like varnish, far from being an expert though. At Logilab, I usually put a varnish (or nginx) alone on a small VM.)

olasd claimed this task.Oct 4 2018, 11:49 AM
olasd changed the task status from Open to Work in Progress.

Varnish is indeed nice but that host (tate) already has an apache so I'll be configuring a vhost in that.