[Buildbot-devel] basic question

Richard Woods rwoods at tresys.com
Thu Aug 26 16:24:44 UTC 2010


Digging a little further, here's a snippet from the step's stdio (which
I just discovered) --

 

starting git operation

 

<snip>

 

/usr/bin/git reset --hard None

in dir
/home/buildbot/sidecar-protocol-library/full-report-coverage/build
(timeout 1200 secs)

watching logfiles {}

argv: ['/usr/bin/git', 'reset', '--hard', 'None']

environment:

    <snip>

closing stdin

using PTY: False

fatal: ambiguous argument 'None': unknown revision or path not in the
working tree.

Use '--' to separate paths from revisions

elapsedTime=0.006632

program finished with exit code 128

 

What would cause BuildBot to say `git reset --hard None`?

 

From: Richard Woods 
Sent: Thursday, August 26, 2010 10:08 AM
To: buildbot-devel at lists.sourceforge.net
Subject: RE: [Buildbot-devel] basic question

 

Of note:

 

When I do a manual `git clone ssh://machinename/path/to/repository`,
.git/config looks like:

 

[core]

                repositoryformatversion = 0

                filemode = true

                bare = false

                logallrefupdates = true

[remote "origin"]

                url = ssh://machinename/path/to/repository

                fetch = +refs/heads/*:refs/remotes/origin/*

[branch "master"]

                remote = origin

                merge = refs/heads/master

 

However, the .git/config file in the repository buildbot created is
missing the [remote "origin"] and [branch "master"] sections.

 

[ I'm also a git newbie or I'd have known to provide this information to
start with ]

 

From: Richard Woods 
Sent: Thursday, August 26, 2010 9:19 AM
To: buildbot-devel at lists.sourceforge.net
Subject: RE: [Buildbot-devel] basic question

 

Ah, thank you!  With that sorted out...

 

The builds fail at the Git step.  The step is defined by
`Git(repourl="ssh://machinename/path/to/repository"))` -- pretty simple.
If I do a `git pull` from the build directory, I get "unable to chdir or
not a git archive", however if I do `git pull
ssh://machinename/path/to/repository`, I get the updates correctly.

 

From: John Ford [mailto:jhford at mozilla.com] 
Sent: Wednesday, August 25, 2010 5:13 PM
To: Richard Woods
Cc: buildbot-devel at lists.sourceforge.net
Subject: Re: [Buildbot-devel] basic question

 

your scheduler is on branch 'master' but your sendchange doesn't have a
branch.  Try adding --branch master to your sendchange

 

John

 

 

On Aug 25, 2010, at 2:10 PM, Richard Woods wrote:

 

I had BuildBot set up to do periodic builds, and I'd like it to instead
receive change notifications from a git repository.

 

I have the post-receive hook set up in the repository to send the
changes to BuildBot.  I have changed the configuration file:

*         The change source is configured via `c['change_source'] =
PBChangeSource()`

*         The scheduler is defined by `Scheduler(name="all",
branch="master", treeStableTimer=0, buildernames=["buildbot-full"])` and
appended to c['schedulers']

But where my periodic builds were working before, I can't get these
builds to kick off.

 

I have done `buildbot sendchange --user=username --master=localhost:9989
Makefile`, and I see a change show up on the status Waterfall page, but
no builds kick off.  Where might I be missing something?

------------------------------------------------------------------------
------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users

worldwide. Take advantage of special opportunities to increase revenue
and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d______________________________________
_________
Buildbot-devel mailing list
Buildbot-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/buildbot-devel

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20100826/942319bd/attachment.html>


More information about the devel mailing list