[M3devel] hudson tasks m3cc vs. build vs. prebuilt cm3cg?

[Olaf Wagner]

Quoting Jay K <jay.krell at cornell.edu>:
I didn't notice this mail before... see below

> Olaf, I'm not sure Hudson works right in terms of using/copying the right
> prebuilt cm3cg at the right time.
>
> I see evidence of using out of date cm3cg.
>
> Given that we don't ever by default clean m3cc.
> And given that I adjusted stuff to use upgrade.sh and I believe
> install cm3cg and cm3 together at the right time.
>
> But given that I didn't look into or adjust how the pairs of tasks   
> (m3cc and build) interace.
>
> Given that I think build works on its own.
>
> I request that we stop all the m3cc tasks and remove or at least   
> disable the PREBUILD_CM3CG stuff.
> i.e. asking agreement/permission. I'm willing to do it.

I'm not against disabling all the m3cc tasks and just build m3cc
in the usual way in the build jobs. That was just a performance
optimization making sense we built release candiate after release
candidate again and again on many more platforms than now.

I suggest something like this:

% cvs diff -u scripts/regression/
Warning: untrusted X11 forwarding setup failed: xauth key data not generated
Warning: No xauth data; using fake authentication data for X11 forwarding.
cvs diff: Diffing scripts/regression
Index: scripts/regression/hudson_build_system.sh
===================================================================
RCS file: /usr/cvs/cm3/scripts/regression/hudson_build_system.sh,v
retrieving revision 1.21
diff -u -u -r1.21 hudson_build_system.sh
--- scripts/regression/hudson_build_system.sh   21 Nov 2010 13:00:38  
-0000     1.21
+++ scripts/regression/hudson_build_system.sh   21 Nov 2010 13:14:07 -0000
@@ -37,7 +37,7 @@
      ;;
    esac
  fi
-if [ "$CLEAN" = "false" ]; then
+if [ "$CLEAN" = "false" && "$USE_PREBUILT_CM3CG" = "true" ]; then
    if [ -x "${CM3CG}" ]; then
      echo "checking for working pre-built cm3cg in ${CM3CG}"
      cp -p "${CM3CG}" ${WS}/cm3cg

> Alternately stated:
>   I understand and can fix if needed upgrade.sh.
>     Though I do use upgrade.py myself, all the time. We should   
> consider it..but they are about the same.
>   Anyway, my point is, I understand, like, "a single workspace" setup.
>   Maybe Hudson should work that way?
>   Now, I understand there is granularity. You want to see some   
> Hudson tasks finish,
>   before others run. So, in the interest of that, I'm very willing   
> to leave m3cc first,
>   and if that succeeds, have build build its own cm3cg. That is wasteful, but
>   can be helpful. I mainly want to remove/disable the "prebuilt_cm3cg" thing.

Single build workspace setup should be OK now. Shall I disable all the
m3cc jobs?

We'll keep all the test jobs though...

Olaf

PS: The lastok and release installations on your Darwin machine are all
empty, see  
http://hudson.modula3.com:8080/job/cm3-current-build-AMD64_DARWIN/63/console.
-- 
Olaf Wagner -- elego Software Solutions GmbH
                Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
    http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194