[Buildbot-devel] problems­ uploading build artefact­s in Buildbot 0.8.8

[vasslitvinov at pisem.net]

You seem to misunderstand what FileUpload does. It uploads a file to the *master*, and yours first command creates a directory on the *slave*.

Those are entirely different beasts.

Maybe what will suit you is something like ShellCommand(['cp', , Interpolate('%(prop:artifacts_dst_path)s')])

--

Vasily

Срд 09 Окт 2013 18:10:23 +0400, Neil Leathers  написал:
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/eca7c9b1/attachment.html>