diff options
| -rw-r--r-- | INSTALL | 23 | ||||
| -rw-r--r-- | README | 25 |
2 files changed, 25 insertions, 23 deletions
@@ -114,26 +114,3 @@ Currently only the configuration is backed up, but neither the jenkins results n I've cloned these two git repos on my desktop and manually run `git pull`. This is certainly not ideal but good enough to re-setup the system anytime, which is something. -== Debugging jobs without jenkins - -*FIXME*: To debug certain jobs, a jenkins setup is actually not needed. Make this easy and describe here. - -*This is work in progress too and is not done yet!* - -FIXME: Describe which packages need to be installed, too. No, don't. Package it properly. update_jdn.sh is a hack and needs to die. -FIXME: svn/git using test-scripts need to learn checkout out - currently this is always done by jenkins. - -=== Debugging g-i-installation jobs - -as user run: - ----- -mkdir workspace ; cd workspace # test-script should check if they are in a directory called workspace and if not, mkdir it and cd into it. -/srv/jenkins/bin/cd_tester.sh 2 squeeze-test-debian-edu-standalone 20 http://ftp.skolelinux.org/cd-squeeze-test-amd64-i386-netinst/debian-edu-amd64-i386-NETINST-1.iso - ----- -See the *fourth line* on *any* log to find out how to debug any job. Point this out at the end of any log. - -When packaging this, two packages should be created: -- jenkins.debian.net - turn a machine into jenkins.$localdomain (not policy complient package), probably jenkins.d.n-seteup or such is a better package name -- jenkins.d.n-debug - or such to set an environment to run specific jobs easily @@ -18,6 +18,8 @@ Virtual hardware sponsored by http://www.profitbricks.com - currently it's just Some stats are available using link:http://jenkins.debian.net/munin/jenkins-month.html[munin-plugins for jenkins]. +If you notice some jobs has problems and you want to find out why, read <<debug,debug certain jobs>> to learn how to do this locally. + === Feedback I love to get feedback on this! Please join #debian-qa on irc.debian.org to report bugs or give other feedback! Or send an email to debian-qa@lists.debian.org if you prefer mail. @@ -102,6 +104,29 @@ These jobs are only run on the first day of each month. These are jobs for making sure jenkins.debian.net is running smoothly. +[[debug]] +== Debugging certain jobs + +*FIXME*: To debug certain jobs, a jenkins setup is actually not needed. Make this easy and describe here. + +*This is work in progress too and is not full done yet!* + +Build this source as a debian package and install the jenkins.d.n-debug package and all it's recommends. + +=== Debugging g-i-installation jobs + +as user run: + +---- +mkdir workspace ; cd workspace # test-script should check if they are in a directory called workspace and if not, mkdir it and cd into it. +/srv/jenkins/bin/cd_tester.sh 2 squeeze-test-debian-edu-standalone 20 http://ftp.skolelinux.org/cd-squeeze-test-amd64-i386-netinst/debian-edu-amd64-i386-NETINST-1.iso + +---- +See the *fourth line* on *any* log to find out how to debug any job. Point this out at the end of any log. + + +TODO: Currently as easy: svn/git using test-scripts need to learn checkout out - currently this is always done by jenkins. + == License * See link:http://anonscm.debian.org/gitweb/?p=users/holger/jenkins.debian.net.git;a=blob;f=LICENSE[LICENSE]. |