Hey Abhishek,
On Thu, Jul 23, 2015 at 09:44:26AM +0000, ABHISHEK PANDEY wrote:
> I was under assumption that Jenkins build works under a new sand box every
> time and all temporary files generated during build (such as
> <iotivity>/tmp and ~/GBS-ROOT) are deleted by default before build. Is it
> not the case ?
>
By default gbs-build appears to use `~/GBS-ROOT` and `/var/tmp`. Neither
of these are good locations for builds as they are outside the workspace
and will cause conflicts for other builds on the same server. The
gbs-build documentation[1] lists `TIZEN_BUILD_ROOT` (or the -B flag) as
a way of setting the build directory.
I am going to add this environment variable to the build servers and
verify that builds do not go outside of their workspace.
As an added measure it would be nice if `--clean-repos` was added to
the call to gbs:
> Local repos in gbs build root ('~/GBS-ROOT' by default) will affect
> build results, so you must make sure that repos don't contains old or
> unnecessary RPM packages. While running gbs build, you can specify
> '--clean-repos' to clean up local repos, which gbs created, before
> building.
Regards,
Trevor Bramwell
[1]
https://source.tizen.org/development/reference/git-build-system/usage/gbs-build
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150723/7d2e3b92/attachment.sig>
