Buildbot continuous integration for CPS

Hi there,

a big plus on he quality side : we started buildboting CPS (again) a few
days ago, see http://buildbot.cps-cms.org/waterfall.
The tests are triggered by pushes on the reference repositories hosted
at http://hg.cps-cms.org.

Email notifications of failures aren't configured yet, but we'll send
them either to this list or to code@... (opinions welcome).

If any of you are interested in setting up slaves, please check the
setup instructions at
http://hg.cps-cms.org/buildbot/cps-config/file/tip/README.txt .
In that repository you'll also find a template configuration and
instructions to buildbot hgbundler-tracked custom projects.

Regards,

--

-- 
Georges Racinet, http://www.racinet.fr
Zope/CPS expertise, assistance & development
GPG: 0x4862FFF7 identi.ca & twitter: gracinet

_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel

Changes in CPS mailing-lists hosting

Dear all,

the four mailing lists related to CPS have just moved to the
lists.cps-cms.org
domain, including all membership options and archives. Everything should
therefore
be about the same for you, apart from the addresses.

From now on, the addresses at lists.nuxeo.com are obsolete. We can't
guarantee that
you'll be read if you post on them.

Many thanks to our friends at Nuxeo for their help on this operation,
that will
allow us to manage them directly according to our needs.

To make a bit more sense of this cross-posting, let me take the
opportunity to
try and clarify the purposes of the different lists a bit (advices welcome).

 - cps-devel is focused on the development of CPS itself. Discussions
should be about
   design decisions and changes in the standard distributions
(CPS-3-base to CPS-3-full). We
   also often make announcements of releases that are not considered as
ready for a wider
   public there.

 - cps-users and cps-users-fr are for... users ! In practice, that
should mean mostly questions

Real-time update of CPS documentation

Hello again,

thanks to our recent continuous integration efforts, the RST
documentation of the CPS products is now converted to HTML and put
online in real time on http://doc.cps-cms.org. There still are quite a
few obsolete parts, though, but at least this gives developers more
incentive to update the documentation.

We currently maintain two lines : CPS-3.5-head is the latest in the 3.5
series ; CPS-head is the latest of the latest (currently 3.6).

In case of doubt, here's the link to watch the building process :
http://buildbot.cps-cms.org/waterfall?builder=CPS-3.5-doc&builder=CPS-3.6-doc

Cheers,

--

-- 
Georges Racinet, http://www.racinet.fr
Zope/CPS expertise, assistance & development
GPG: 0x4862FFF7 identi.ca & twitter: gracinet

_______________________________________________
cps-devel mailing list
http://lists.cps-cms.org/listinfo/cps-devel

Buildbot notifications

Dear CPS developers,

as of now, the buildbot will notify this list of builders status changes
(typically from success to failure and back).
This way, developers will be informed of current problems that may
impact their work or bleeding-edge based deployments, and get a notice
when situation is back to normal.
I'll do a voluntary failure and fix in a few minutes to test the
notification itself.

Of course, this also serves the purpose of fixing the problems as soon
as they occur. That's usually easier than a month later.

We considered also sending these notifications to the code mailing list,
but decided that they would be unnoticed among the changesets and trac
notifications. Build failures are supposed not to happen that often, but
of course the purpose of using a tool such as buildbot is to perform the
extensive testing that would not be realistic in the typical developer
workflow, so they will happen.

All of this is still in progress and a bit experimental, we'll see what
to do if people here find that this generates too much traffic.

Regards,

--

-- 
Georges Racinet, http://www.racinet.fr
Zope/CPS expertise, assistance & development
GPG: 0x4862FFF7 identi.ca & twitter: gracinet

buildbot failure in CPS Generic on CPS-3.6-full

The Buildbot has detected a new failure on builder CPS-3.6-full while building CPS Generic.
Full details are available at:
 http://buildbot.cps-cms.org/builders/CPS-3.6-full/builds/10

Buildbot URL: http://buildbot.cps-cms.org/

Buildslave for this Build: purity.racinet.fr

Build Reason: scheduler
Build Source Stamp: [branch default] 2ad7f470309ae22370579ebe4b37cb265b6643c0
Blamelist: Georges Racinet on ishtar.racinet.fr <georges@...>

BUILD FAILED: failed shell_2

sincerely,
 -The Buildbot

_______________________________________________
cps-devel mailing list
http://lists.cps-cms.org/listinfo/cps-devel

buildbot success in CPS Generic on CPS-3.6-full

The Buildbot has detected a restored build on builder CPS-3.6-full while building CPS Generic.
Full details are available at:
 http://buildbot.cps-cms.org/builders/CPS-3.6-full/builds/11

Buildbot URL: http://buildbot.cps-cms.org/

Buildslave for this Build: purity.racinet.fr

Build Reason: scheduler
Build Source Stamp: [branch default] 6f81f928cbd64144096cfc4151a7c64471abed30
Blamelist: Georges Racinet on ishtar.racinet.fr <georges@...>

Build succeeded!

sincerely,
 -The Buildbot

_______________________________________________
cps-devel mailing list
http://lists.cps-cms.org/listinfo/cps-devel

buildbot failure in CPS Generic on CPS-3.6-base

The Buildbot has detected a new failure on builder CPS-3.6-base while building CPS Generic.
Full details are available at:
 http://buildbot.cps-cms.org/builders/CPS-3.6-base/builds/6

Buildbot URL: http://buildbot.cps-cms.org/

Buildslave for this Build: purity.racinet.fr

Build Reason: The web-page 'force build' button was pressed by 'gracinet': Reinstalled slave

Build Source Stamp: HEAD
Blamelist: 

BUILD FAILED: failed shell_2

sincerely,
 -The Buildbot

_______________________________________________
cps-devel mailing list
http://lists.cps-cms.org/listinfo/cps-devel

buildbot success in CPS Generic on CPS-3.6-base

The Buildbot has detected a restored build on builder CPS-3.6-base while building CPS Generic.
Full details are available at:
 http://buildbot.cps-cms.org/builders/CPS-3.6-base/builds/7

Buildbot URL: http://buildbot.cps-cms.org/

Buildslave for this Build: purity.racinet.fr

Build Reason: The web-page 'rebuild' button was pressed by 'gracinet': Cleanup remnants of previous builds

Build Source Stamp: HEAD
Blamelist: 

Build succeeded!

sincerely,
 -The Buildbot

_______________________________________________
cps-devel mailing list
http://lists.cps-cms.org/listinfo/cps-devel

buildbot failure in CPS Generic on CPS Release

The Buildbot has detected a new failure on builder CPS Release while building CPS Generic.
Full details are available at:
 http://buildbot.cps-cms.org/builders/CPS%20Release/builds/10

Buildbot URL: http://buildbot.cps-cms.org/

Buildslave for this Build: dubber.racinet.fr

Build Reason: The web-page 'force build' button was pressed by 'gracinet': 

Build Source Stamp: HEAD
Blamelist: 

BUILD FAILED: failed shell_6

sincerely,
 -The Buildbot

_______________________________________________
cps-devel mailing list
http://lists.cps-cms.org/listinfo/cps-devel

Re: buildbot failure in CPS Generic on CPS Release

Sorry,

I simply forgot to deactivate the notifications while working on this
new builder.
It is currently able to produce and upload the tarballs for any version
tagged with hgbundler of the 3 distributions.
The ultimate goal will be to produce the Debian packages as well.

All of this will spare us the extra amount of time we currently don't
have right after tagging a release.

Regards,

Le 14/02/2012 22:38, buildbot@... a écrit :
> The Buildbot has detected a new failure on builder CPS Release while building CPS Generic.
> Full details are available at:
>  http://buildbot.cps-cms.org/builders/CPS%20Release/builds/10
>
> Buildbot URL: http://buildbot.cps-cms.org/
>
> Buildslave for this Build: dubber.racinet.fr
>
> Build Reason: The web-page 'force build' button was pressed by 'gracinet': 
>
> Build Source Stamp: HEAD
> Blamelist: 
>
> BUILD FAILED: failed shell_6
>
> sincerely,