[Buildbot-devel] Manual Scheduler trigger?

[Stephen Milner]

Hello Ian,

The way I do manual builds with our dev teams is with the IRC bots. When a dev lead is ready to have something built they fire it off in IRC and it goes through whatever build/test/package/etc.. steps that are defined.

Why not have two build targets .... one for internal team building (builds on all check ins and/or when developers say build) and one for cutting a release that pushes it up to the company wide repository? That way your not adding in build related data to check-ins.

As of right now I believe there is only an XMLRPC interface to see status, but not to kick off new builds and things like that ... but that sounds like a good addition that could be done.

----- Original Message -----
From: "Ian Peters-Campbell" <mahatmamanic at gmail.com>
To: Buildbot-devel at lists.sourceforge.net
Sent: Friday, January 30, 2009 4:01:58 PM GMT -05:00 US/Canada Eastern
Subject: [Buildbot-devel] Manual Scheduler trigger?


Does anyone have any advice regarding setting up manual triggers for Schedulers/Builders? During setup I would really like to get the kinks worked out of the system without spamming check-ins to our SVN repository, so if there was a good quick way to order the Buildmaster to fire off a particular Builder at will it would help. I guess I could swap in a PeriodicScheduler with a short period to test with, but if there's an easy way to trigger from the command line that would be preferable. 

On a related note, my final goal is to have continuous integration builds put together after each check-in, but for those to only be published to the development team for the particular project. I would then like a way to specify a "published" build that is packaged and placed on a company-wide server, and that notifies a wider portion of the dev team including PM and QA. My "best" ideas so far were to have either an SVN commit message tag which tagged the build as public, or a README/release notes file that was watched by a scheduler for the public release. I assume that others have dealt with similar issues, and I am wondering if anyone has suggestions as to the cleanest way to manage this? 

Thanks 
Ian 


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Buildbot-devel mailing list
Buildbot-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/buildbot-devel