Author: miguel
Date: 2005-04-28 18:50:52 -0400 (Thu, 28 Apr 2005)
New Revision: 43750

Added:
   trunk/release/buildbot/HOWTO
Removed:
   trunk/release/buildbot-howto
Modified:
   trunk/release/buildbot/config/g5-mono
   trunk/release/scripts/update-versions
Log:
Move howto

Copied: trunk/release/buildbot/HOWTO (from rev 43745, 
trunk/release/buildbot-howto)

Modified: trunk/release/buildbot/config/g5-mono
===================================================================
--- trunk/release/buildbot/config/g5-mono       2005-04-28 21:51:01 UTC (rev 
43749)
+++ trunk/release/buildbot/config/g5-mono       2005-04-28 22:50:52 UTC (rev 
43750)
@@ -2,5 +2,6 @@
 export ACLOCAL_FLAGS="-I 
/Library/Frameworks/Mono.framework/Versions/1.0.4/share/aclocal/"
 
 export 
PKG_CONFIG_PATH=/usr/lib/pkgconfig:/Library/Frameworks/Mono.framework/Versions/1.0.4/lib/pkgconfig:$PKG_CONFIG_PATH
+PATH=$PATH:/System/Library/Frameworks/Python.framework/Versions/2.3/bin
 prefix=/Users/nbuilder/install
 install=true

Deleted: trunk/release/buildbot-howto
===================================================================
--- trunk/release/buildbot-howto        2005-04-28 21:51:01 UTC (rev 43749)
+++ trunk/release/buildbot-howto        2005-04-28 22:50:52 UTC (rev 43750)
@@ -1,78 +0,0 @@
-Hosts:
-
-Architecture   Hostname        Responsible for         User / Pass
-============    ========        ===============
-
-x86            hardhat         Packaging
-               x86-mono        intel-1.0               builder2 / builder
-                               intel-head              builder / builder
-               cygwin-mono     cygwin-head lane        
-
-PPC            g5-mono         ppc-1.0                 builder / builder
-                               ppc-head                builder / builder       
 
-               macmono         
-
-Sparc          sparcmono       sparc-1.0               builder / builder
-                               sparc-head              builder / builder
-
-AMD64          amd-mono        amd-head lane           builder / builder
-
-
-Q.  How to reconnect a build node?
-
-A.  First, ssh into the node using the corresponding username and password.
-
-    On each of the build nodes, there is a ongoing screen session for
-each lane the node is responsible for: i.e. on x86-mono, the
-`intel-head' lane is running inside the `HEAD' screen session, and the
-`intel-1.0' lane inside the `1.0' screen session.
-
-    When a lane is offline, connect to the node responsible for that
-lane and reattach into the correct screen session (screen -r <name of
-session>). End the running `connect' process and start a new one again
-from the screen session. When you're done, disconnect from the screen
-session (C-a d).
-
-    If the machine had to be rebooted / was rebooted, then ssh into
-the node as the appropriate user (see table above) and start a new
-screen session again (screen -S <name of session>, etc etc), make sure
-you're in the correct directory (HEAD vs. 1.0), and run "sh connect".
-
-The scripts used in the nodes:
-
-On each machine, you'll find two directories, `1.0' and `HEAD' (except
-for AMD, because it's responsible for only one lane). Inside the
-directory, there are the following scripts:
-
-    o clean-up -  Clears out the previous checkout.
-    o checkout -  Checks out the latest revision from SVN.
-    o build    -  Runs the build.
-    o test     -  Runs the test suite.
-    o extras   -  Runs any additional tasks.
-
-    o connect  - The script that connects the node to the buildbot
-                server.
-
-On the cgywin box, the scripts are in c:\builder.
-
-Q.  How do I set up a new build node?
-
-A.  You need to have python 2.x, twisted 1.3.0 and buildbot 0.4.3
-installed.
-
-Go to one of the existing build nodes and grab an existing copy of the
-6 scripts used and tweak as appropriate.
-
-The `connect' script contains a key used to identify the build lane.
-When adding a new lane, you need to connect to the buildbot master
-(mono.ximian.com) as build-master and add a new entry inside
-`private.py' for identifying the lane. After that, log in as root on
-the master and run `restart-build-server'. The new lane will now
-appear on the main page and the node can be connected.
-
-By default the builds will be installed to /mono-1.0 and /mono. Make
-sure that these directories exist before starting a new build, also
-make sure that the builder user has read/write permission into the
-directories.
-
-

Modified: trunk/release/scripts/update-versions
===================================================================
--- trunk/release/scripts/update-versions       2005-04-28 21:51:01 UTC (rev 
43749)
+++ trunk/release/scripts/update-versions       2005-04-28 22:50:52 UTC (rev 
43750)
@@ -20,9 +20,10 @@
 fi
 
 echo Updating versions in $root/mono and $root/mcs
-
+echo $root/mono/configure.in has been updated.
 perl -pi -e "s/AM_INIT_AUTOMAKE.*(mono,.*)/AM_INIT_AUTOMAKE(mono,$version)/" 
$root/mono/configure.in
 
-for i in mcs/AssemblyInfo.cs; do
+for i in mcs/AssemblyInfo.cs ilasm/AssemblyInfo.cs; do
+       echo $root/mcs/$i has been updated
        perl -pi -e "s/\[assembly: AssemblyVersion(".*")\]/\[assembly: 
AssemblyVersion(\"$version\")\]/" $root/mcs/$i
 done

_______________________________________________
Mono-patches maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-patches

Reply via email to