[Buildbot-devel] problems uploading build artefacts in Buildbot 0.8.8

[Kenny Ho]

Hi Neil,

As mentioned in the document:
http://docs.buildbot.net/0.8.8/manual/cfg-buildsteps.html#step-FileUpload

The FileUpload "moves a file up to the master", so the path you specified in "masterdest" need to exist on the master.


If uploading file to the master is not what you want, you might want to extend a build step:
http://docs.buildbot.net/0.8.8/developer/cls-buildsteps.html

addURL(name, url)

You can check the FileUpload step for reference:

https://github.com/buildbot/buildbot/blob/7254932ce162b763dea9faa91e85f1e2d46df616/master/buildbot/steps/transfer.py

Kenny


________________________________
From: Neil Leathers [neil.r.leathers at gmail.com]
Sent: October 9, 2013 10:09 AM
To: buildbot-devel at lists.sourceforge.net
Subject: [Buildbot-devel] problems uploading build artefacts in Buildbot 0.8.8

I would like to upload my build artefacts to our release area and record the URL so people can down them. I used the following commands.

        buildFactory.addStep(ShellCommand(name="Create Release Area", workdir=buildFactory.workdir+"/source", command=Interpolate('mkdir -p %(prop:artifacts_dst_path)s;')))
        buildFactory.addStep(FileUpload(slavesrc=Interpolate("~/package/%(prop:platform)s/%(prop:platform)s-artefact-%(prop:build_num)s.zip"),
                                        masterdest=Interpolate("%(prop:artifacts_dst_path)s"),
                                        url=Interpolate("https://server/Daily-Releases/%(prop:build_id)s/%(prop:platform)s-artefact-%(prop:build_num)s.zip")))


The first command works and creates the directory %(prop:artifacts_dst_path)s (specifically /media/HAServer/Daily-Releases/3.0.0-181-gd884775). The second command throws and exception creating the same directories again incorrectly (at the mount point /media/HAServer). The documentation of FileUpload gives no indication that it attempts to create directories and this undocumented "feature" is clearly not implemented correctly. Furthermore, reading the details of the FileUpload I suspect this may not be the correct step to use to release build artefacts.

Is FileUpload the correct way to release build artefacts? If so, when will it be fixed? If not, what is the correct step to use to release build artefacts and register the URL for use on the build details page?

Neil Leathers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20131009/aed42035/attachment.html>