[Buildbot-commits] [SPAM] [Buildbot] #865: buildbot try not working with mercurial
Buildbot
buildbot-devel at lists.sourceforge.net
Thu May 27 16:16:57 UTC 2010
#865: buildbot try not working with mercurial
----------------------+-----------------------------------------------------
Reporter: bgunnison | Owner:
Type: undecided | Status: new
Priority: blocker | Milestone: undecided
Version: 0.8.0 | Keywords:
----------------------+-----------------------------------------------------
Several issues, some may be in my misunderstanding how to use it.
.buildbot/options
try_connect = 'pb'
try_vc = 'hg'
try_master = '....'
try_username = '...'
try_password = '...'
try_builders = ['... Smoke Build']
1) try client calls "hg diff" in working repository. If there are no
uncommitted changes, there is no output. Should "try" fail at the client
if there are no changes? Or at least inform the user?
2) The build step that try invokes is:
hgUpdateStep = Mercurial(repourl = RepoURL)
RepoURL is the master repository that the working repository was cloned
from.
This fails at the buildslave at:
hg.exe update --clean --repository <build_slave_path>\build --rev
<workdir_revision_hash>
...
abort: unknown revision '<workdir_revision_hash>'!
IT seems we are not applying the patch as the hg command above expects the
build slave repository (which was cloned from the master repo) to be
update-able to the working directory. Something is missing or not working.
3) So if I have the use-case correct, only uncommitted changes get "tried"
in the above scenario. Our workflow is such that we clone from the master
repo and commit many times in the working repo. Then a "hg push" is done
from the working to the master after smoke test passes. I need "buildbot
try" to interrogate the master repo, then "hg diff -r master_rev -r
working_tip" to get the difference between the master and working repos.
Then try those changes. Is this possible?
Thanks,
Brian
--
Ticket URL: <http://buildbot.net/trac/ticket/865>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
More information about the Commits
mailing list