On Sep 27, 2016, at 2:34 AM, Paulo Matos wrote: > On 27/09/16 09:14, Ryan Schmidt wrote: >> >> If builds from each branch don't need to be happening at the same time, can >> you use "svn switch" to switch a single working copy to the applicable >> branch for each build? >> > > Thanks Ryan, however I couldn't find an easy way to perform the switch. > I looked at svn.py from buildbot repo and maybe the easiest way is to > override startVC since it gets the branch argument and the revision > argument and then I should be able to trigger a svn switch to that > branch at that revision and call the parent startVC. Is this how you > thought about performing the switch?
I'm not familiar enough with Buildbot to be able to suggest a specific way to accomplish the switch. But I know Subversion very well, and that "svn switch" is the intended solution to the problem of wanting to work on different branches while only keeping a single working copy on disk. This may create some additional complications. Depending on how your branches differ from one another, there might be situations where switching from one branch to another does not leave your working copy in a clean state. Make sure you check the status code of "svn switch" to ensure it didn't have an error, and I'd probably also run "svn status --ignore-externals" on the working copy afterward, to make sure there are no modified or unversioned files present before building. _______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
