...
Worker Node | Account | Directory | Host | Comment | |||||
|---|---|---|---|---|---|---|---|---|---|
exo-build01 | exodata | /nfs/slac/g/exo/software/hudson/exo-build01 | scalnx01 |
| |||||
exo-build02 | exodata | ~/hudson | www.exo200.org |
| |||||
exo-build-noric32 | exodata | /nfs/slac/g/exo/software/hudson/ | noric32 | This agent is started on-demand via ssh | |||||
srs-build01 | srs | /nfs/slac/g/srs/hudson/srs-build01 | scalnx01 | cronjob ok | |||||
| srs-build02 | srs | /nfs/slac/g/srs/hudson/srs-build02 | scalnx-v02 | running lcsim and hps builds | |||||
lsst-build01 | srs | /nfs/slac/g/srs/hudson/lsst-build01 | scalnx01 | cronjob ok. Running java at 32 bits. | |||||
freehep-build01 | freehep | /nfs/slac/g/jas/hudson/freehep-build01 | scalnx01 |
| |||||
lcsim-build01 | lcdprod | /nfs/slac/g/lcd/mc/prj/sw/hudson | lcddata01 |
| |||||
fermi-build01 | glast | /nfs/slac/g/glast/ground/software/hudson/ | fermilnx-v03 |
| |||||
cta-build01 | ctadata | /nfs/slac/g/agis/repo/hudson/rhel5-64/ | scalnx01 |
| |||||
fermi-bldmac01 | glastrm | /u/gl/glastrm/jenkins/bldmac01 | bldmac01 | This is now started using launchd from ~glastrm/Library/LaunchDaemons/monitor-jenkins.plist | |||||
fermi-bldmac02 | glastrm | /u/gl/glastrm/jenkins/bldmac02 | bldmac02 | This is now started using launchd from ~glastrm/Library/LaunchDaemons/monitor-jenkins.plist | |||||
fermi-win04 | glast | d:\jenkins | glast-win04 | This has been configured to run as a windows service using the instructions here: | |||||
fermi-bldlnx06 | glastrm | /u/gl/glastrm/hudson/bldlnx06 | bldlnx06 |
| |||||
fermi-bldlnx11 | glastrm | /u/gl/glastrm/hudson/bldlnx11 | bldlnx11 |
| |||||
fermi-bldlnx12 | glastrm | /u/gl/glastrm/hudson/bldlnx12 | bldlnx12 |
| |||||
cdms-build-noric34 | cdmsdata | /u/dm/cdmsdata/jenkins | noric34 | hps-build01 | lcdprod | /nfs/slac/g/lcd/mc/prj/sw/hudson | lcddata01 |
Launching Jobs
Most jobs are configured to start on SCM changes by polling the repository with scheduled tasks. The SCM polling has been causing problems, so we have migrated to a different strategy: triggering the jobs remotely upon SCM changes.
...