User Tools

Site Tools


jenkins

AMPLab Jenkins

AMPLab Jenkins Introduction (presentation)

Access to Jenkins web UI

If you have a Berkeley EECS account, you can log in through the Jenkins UI using your EECS LDAP credentials.

If you do not have a Berkeley EECS LDAP account, please email Shane Knapp and request an account. Please be sure to include any reasons why you need a login. If you're approved, the account will be created and you will receive an email with instructions on how to log in to the unix shell and change your default password.

Creating Builds

Only people with an account on the Jenkins server, or people with EECS LDAP credentials can create new builds.

If the build fits under an existing project (Spark, Tachyon, etc), please add the item there. If it doesn't, then please create a new tab for your project, and put the new build in there.

For private github repos, please be sure to use the proper github credentials to allow jenkins access:

1) on github.com, add the “Jenkins Build” team to your repo as a Collaborator.

2) when setting up the build on jenkins itself, in the “Source Code Management” section, you'll need to enter the github url that points to your repo. directly under that will be a drop-down box labeled “Credentials”, and in there select “jenkins (private repo key)”.

You can use the velox testing build as a template (be sure to log in w/your LDAP creds before viewing):

For general build creation instructions, refer to the official Jenkins wiki for more detail. If you have any questions or issues, please feel free to reach out to Shane Knapp.

Shell access to the Jenkins cluster

People with EECS LDAP credentials automatically have shell accounts on the Jenkins master and workers. Otherwise, you will need to email Shane Knapp and request access to the master and workers.

To log in via SSH:

ssh <EECS LDAP username>@hadrian.ist.berkeley.edu

From the master, you can then log in workers using the same credentials:

ssh <EECS LDAP username>@amp-jenkins-worker-{01..08}

Operational Guide

Starting/Stopping/Restarting the Jenkins daemon:

service jenkins start|stop|restart

If you get a 503 Bad Gateway error when visiting the website, restart Apache HTTPD:

service httpd restart

If logins aren't working, restart sssd:

service sssd restart

Setting up a new worker (run as root from the master):

/root/tools/setup_jenkins_worker.sh <hostname>

Tools github repo (private, visible only to people in the AMPLab group):

https://github.com/amplab/amplab-infra

Architecture

Master:

  • 1 Intel® R2308GZ4GC Server System
    • 1 Intel® S2600GZ Server Board
    • 4x Intel® i350 Gigabit Ethernet
    • 2x Intel® 82599ES 10Gigabit Ethernet
    • 1x Intel® Intel Sandy Bridge E5-2670 2.6Ghz CPU (16 cores w/HT)
    • 1x Intel® Integrated RAID Module RMS25CB040
  • 4x Seagate Constellation ES.3 3TB SAS HDD as a 2×2 RAID 10
  • 128GB - 8x Samsung M393B2G70QH0-CK0 1600Mhz DDR3 16GB SDRAM DIMMs
  • CentOS 6.6

Workers:

  • 2 Intel® H2216JFQKR Server Systems (essentially 4-node blade systems)
  • Each contains 4 independent Intel® HNS2600JFQ Compute Modules
    • 1 Intel® S2600JFQ Server Board
    • 2x Intel® i350 Gigabit Ethernet
    • 1x Mellanox® ConnectX-3 40Gb/s Infiniband (can double as 10Gb/s Ethernet)
    • 2x Intel® Sandy Bridge E5-2670 2.6Ghz CPUs (32 cores w/HT)
  • 128GB - 8x Samsung M393B2G70BH0-CK0 1600Mhz DDR3 16GB SDRAM DIMMs
  • 1x Innodisk SATADOM-ML 3SE 16GB SSD - for boot/OS
  • 4x Seagate Constellation.2 ST91000640NS 1TB SATA HDD - for Data
  • CentOS 6.6
jenkins.txt · Last modified: 2016/04/04 11:24 by sknapp