Jenkins: Difference between revisions

From Pumping Station One
No edit summary
Line 41: Line 41:
== Adding A Buildslave ==
== Adding A Buildslave ==


     sudo pacman -S libvirt qemu
     sudo pacman -S libvirt qemu jdk8-openjdk
     sudo useradd --home-dir /srv/jenkins --groups kvm --create-home --system jenkins
     sudo useradd --home-dir /srv/jenkins --groups kvm --create-home --system jenkins
     sudo -u jenkins mkdir ~jenkins/.ssh
     sudo -u jenkins mkdir ~jenkins/.ssh
     sudo chown jenkins:jenkins /srv/jenkins/.ssh/authorized_keys
     sudo chown jenkins:jenkins /srv/jenkins/.ssh/authorized_keys
     sudo chmod 700 /srv/jenkins/.ssh/authorized_keys
     sudo chmod 700 /srv/jenkins/.ssh/authorized_keys

Revision as of 13:48, 16 June 2015

General info

Jenkins is an automatic build server. It compiles code projects on change

Github Integration

Github integration requires an ouath token to create post commit callbacks to the jenkins server. You can either let jenkins manage all webhooks for all your projects, or configure each project yourself.

Option 1: Let Jenkis Manage Webhooks

Each github user only needs to do this once.

Option 2: Manually Manage Webhooks

You will have to do this for each github project you add to jenkins.

  • go to your project page on github.
  • Click "Settings" in the right sidebar
  • Click "Webhooks and Services"
  • Click "Add Service" and type "jenkins"
    • You should see "Jenkins (Git plugin)"
  • In the "Jenkins hook url" box, enter "https://jenkins.pumpingstationone.org/github-webhook/"
  • Click "Add Service"

Adding A Buildslave

   sudo pacman -S libvirt qemu jdk8-openjdk
   sudo useradd --home-dir /srv/jenkins --groups kvm --create-home --system jenkins
   sudo -u jenkins mkdir ~jenkins/.ssh
   sudo chown jenkins:jenkins /srv/jenkins/.ssh/authorized_keys
   sudo chmod 700 /srv/jenkins/.ssh/authorized_keys