RE: Slave doesnt create output directory

> > # Create basic BuildFactory object to generate our steps for us
> > f1 = factory.BuildFactory()
> > # Tell the BuildFactory about the steps
> > f1.steps.append(s(step.ShellCommand, command="dir" ))
> 
> > it kacks because the "build" directory hasn't been created:
> 
> Ah, yes, all of the steps assume that the workdir was created by a
Source
> step of some sort.. a CVS checkout or the like. If you don't do that,
> you'll
> need to add a mkdir step yourself.

Ok.

> > Oh, also the buildbot slave command doesn't work. I have to use
mktap.
> > It seems to foul up the arguments and miss the password for some
reason.
> 
> Hrm. Sounds like the %1..%9 vs %* problem. How many arguments are you
> passing
> in? Does the 'buildbot' command you're using use '%*' or the old
numbered
> parameters?

Could be. I'm using %*. I've attached the batch file I've been using, it
does a load of other stuff like get cvs as well. You might want to put
it in contrib? 

Although it looks correct to me:

<<<<
Z:\Temp\slave>buildbot slave --force . localhost:8007 myslave pwd
BB: Running buildbot...
chdir Z:\Temp\slave
mktap buildbot slave --basedir Z:\Temp\slave --master localhost:8007
--name myslave --passwd pwd

<<whole load of depration errors removed>>

Option --passwd requires argument
mktap failed, bailing..
>>>>

> Also, I should probably change 'buildbot slave' to 'buildbot
create_slave'
> or
> 'buildbot make slave' or something, to make the command more clear.
I'll
> look
> into this (probably keeping the old command as an alias for a while)
when
> I
> fix it to make .tac files instead of .tap files.

It seems pretty clear how it is TBH. "slave" to create slave and
"master" for master, then "start" for either.

Nick

Quarantined Attachment.txt
Description: Quarantined Attachment Report