[Buildbot-devel] Problem with buildbot configuration for building debian packages

joguerrero at cnti.gob.ve joguerrero at cnti.gob.ve
Fri Jul 3 13:17:27 UTC 2015

Hi Francesco, Charles, you were totally right, I changed the path for 
the lines which store the properties and the one which creates the tar 
and now it works as intended. It ended up like this:

f.addStep(SetPropertyFromCommand(command = "dpkg-parsechangelog | 
grep-dctrl -esSource . | awk -F' ' '{print $2}'", property = 
'packagename', workdir='build/'+package))
f.addStep(SetPropertyFromCommand(command = "dpkg-parsechangelog | 
grep-dctrl -esVersion . | awk -F' ' '{print $2}' | sed 's/-.*//g'", 
property = 'origver', workdir='build/'+package))
f.addStep(ShellCommand(command = WithProperties("tar --anchored 
--exclude-vcs --exclude './debian' -cvzf 
../%(packagename)s_%(origver)s.orig.tar.gz --directory=$(pwd) ./"), 
workdir='build/'+package ))

I'll be checking what Charles suggested about using the builddir 
property instead of "$(pwd)" and also what Dan mentioned about invoking 
the build steps from a script.

Thank you all for your help! A lot!

El 2015-07-02 22:26, Dan Kegel escribió:
> My usual advice is to write a shell script that does it,
> and then invoke the shell script from a build step.
> Less hassles with quoting that way, and less interlocking of
> your workflow with buildbot.  It's good to be able to invoke
> the build by hand, which is hard if it's encoded in buildbot steps.

More information about the devel mailing list