infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joan Touzet (JIRA)" <>
Subject [jira] [Commented] (INFRA-13670) Set Up Apache CouchDB Jenkins Slaves
Date Thu, 16 Mar 2017 22:46:41 GMT


Joan Touzet commented on INFRA-13670:

Had another chat with [~pono] on HipChat today. He stated that our "slaves" can just use the
JNLP launch method as described here:

rather than provide direct ssh access. This eases things a lot, making the Jenkins scripts
easier to write and removes the need for me to allocate public IPv4 addresses to each guest
(of which I have painfully few).

Infra: Can you provide me the URLs that I will need to do this? Specifically:

* Confirm {{}} is the right URL for slave.jar
(it seems to be), and
* Confirm {{$ java -jar slave.jar -jnlpUrl<slave-name>/slave-agent.jnlp}}
is the right invocation for JNLP startup on each of my slaves.

> Set Up Apache CouchDB Jenkins Slaves
> ------------------------------------
>                 Key: INFRA-13670
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins
>            Reporter: Joan Touzet
> I chatted today with Infra on Hipchat and they recommended I open this ticket now to
memorialize our conversation. We're not ready for action *today* on this ticket :)
> CouchDB needs to run builds on platforms not supported by ASF Infra - various BSDs, macOS,
Illumos/Solaris, etc. We discussed various options and it sounds like registering our own
Jenkins build nodes ("slaves") with the ASF "master" will be the best approach.
> Our intent is to provide 2 machines - one macOS for macOS builds, and one Debian machine
with VirtualBox, for running the other OSes. It's unlikely we'll have IP space to expose all
the guest OSes directly, so we will probably need to craft our Jenkins jobs to connect directly
to the VirtualBox host and jump through it to guests via ssh.
> We'll need a "couchdb" label to ensure only our builds hit these machines, and probably
a "virtualbox" label so that vbox-driven builds can target the correct node.
> We've read and will comply with everything
it asks for.
> In a week or two I will ping this ticket again when we're ready to go. Please set this
to "Waiting on user" for now.

This message was sent by Atlassian JIRA

View raw message