Changes between Version 3 and Version 4 of NuWa_Slave

Timestamp:

08/26/10 16:12:03 (14 years ago)

Author:

blyth (IP: 140.112.102.77)

Comment:

--

NuWa_Slave

@@ -7 +7 @@
   * automatically updated and tested dybinst'allation
   * web interface to the status of the installation including history of build/test status
+
+
 
 
@@ -20 +22 @@
   ||  Caltech       ||  ?Dan               ||   ?                           ||  ?                                                  || 
   ||  LBNL          ||  ?                  ||   ?                           ||  ?                                                  || 
-
 
 
@@ -162 +163 @@
 
 
-
+= Getting the slave to do periodic builds =
+
+To zeroth order only a few steps are needed to convert a
+standard update-build bitten slave into a periodic (daily/weekly) builder.
+
+== Develop/Debug the cron commandline ==
+  
+Starting point ...  interactive trials with :
+{{{
+SLAVE_OPTS="--single --dry-run" ./dybinst -b singleshot_\\\${revision} -l /dev/stdout  trunk slave 
+}}}
+
+   ||  '''dybinst'''   options             ||                                                                  ||    
+   ||  '''-l /dev/stdout'''                || send logging to stdout, for debugging                            ||
+   ||  '''-b  singleshot_\\\${revision}''' || option propagated to bitten-slave '''--build-dir'''              || 
+   ||                                      ||   (variables evaluated in build context supplied by the master)  ||  
+
+The '''SLAVE_OPTS''' are incorporated into the bitten-slave commandline, 
+  * '''--dry-run''' is for debugging only : builds are performed but not reported to the master.
+  * '''--single'''  perform a single build before exiting
+
+=== Issues Forseen ===
+
+  * may need more escaping '''\\\${revision}''' of the '''build-dir'''
+  * the cron command might not get a build to perform within the period (if no qualifying commits), 
+    * process pile-up will occur ...   
+       * maybe avoid by exiting if existing slave process ? 
+       * perhaps add a first '''step''' that checks 
+
+  * will need some purging to avoid filling the disk with builds
+    * could add a build step to do this cleanup  
+
+=== Understanding how {{{./dybinst trunk slave}}} works ===
+
+'''dybinst''' invokes the below which construct and evaluate the bitten-slave commandline to talk to the master and perform builds 
+  * source:installation/trunk/dybinst/scripts/dybinst-slave
+  * source:installation/trunk/dybinst/scripts/slave.sh
+
+=== bitten-slave options ===
+
+{{{
+[blyth@belle7 dyb]$ bitten-slave --help
+Usage: bitten-slave [options] url
+
+Options:
+  --version             show program's version number and exit
+  -h, --help            show this help message and exit
+  --name=NAME           name of this slave (defaults to host name)
+  -f FILE, --config=FILE
+                        path to configuration file
+  -u USERNAME, --user=USERNAME
+                        the username to use for authentication
+  -p PASSWORD, --password=PASSWORD
+                        the password to use when authenticating
+
+  building:
+    -d DIR, --work-dir=DIR
+                        working directory for builds
+    --build-dir=BUILD_DIR
+                        name pattern for the build dir to use inside the
+                        working dir ["build_${config}_${build}"]
+    -k, --keep-files    don't delete files after builds
+    -s, --single        exit after completing a single build
+    -n, --dry-run       don't report results back to master
+    -i SECONDS, --interval=SECONDS
+                        time to wait between requesting builds
+
+  logging:
+    -l FILENAME, --log=FILENAME
+                        write log messages to FILENAME
+    -v, --verbose       print as much as possible
+    -q, --quiet         print as little as possible
+    --dump-reports      whether report data should be printed
+
+}}}
+
+