Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-10126

CI infrastructure for CouchDB

    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Fix Version/s: Mar 2016
    • Component/s: None
    • Labels:
      None

      Description

      The CouchDB project wants to up their CI game. Right now there is only an undermaintained Jenkins installation on a box in Jan Lehnhardt's flat. The goal is to build and test CouchDB on as many different OSes and Erlang versions as possible. In the end, this will probably a matrix of build slaves. I volunteered to help with that/take care of that. I already started to create an Ansible project that provisions a Jenkins server and several slaves for different OSes.

      But in the end this will probably need to run on some "official" ASF CI infrastructure.

      The two options I see are
      1) Integrate this into the existing Jenkins infrastructure?
      2) Run it on different VMs provided by the ASF infra team?

      I read some of the docs at https://cwiki.apache.org/confluence/display/REEF/Continuous+Integration+Setup and saw that the usual way is to maintain the job configs manually. This might be quite a lot of effort since we will need a large number of jobs (for the matrix of configurations). We plan to automate as much as possible, even the job configs and the slave configs etc. Of course, this might conflict with the existing Jenkins setup.

      Which of the two options is viable? What is the best way to proceed here?

      Kind regards

        Bastian

        Attachments

          Activity

            People

            • Assignee:
              abayer Andrew Bayer
              Reporter:
              bastian.krol Bastian
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: