This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
Neels Hofmeyr gerrit-no-reply at lists.osmocom.orgPatch Set 4: > > have you checked that the jenkins build job running this cleans > up the workspace? > > I've look through web-ui and it seems ok but I might have missed > smth. What would be the right way to do this? e.g. under 'Source Code Management' choose the 'Additional Behaviors' as 'Clean before checkout'. But then again, we build twice in the script, and the second build re-uses a git checkout that is already tainted by the first build. For example, if built-sources are placed in the source tree instead of the builddir or other side effects ... are unlikely and wrong, nevertheless, the best practice for jenkins builds is to start from a clean git repos every time. -- To view, visit https://gerrit.osmocom.org/3132 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I24e500e132f5c8e8133d35548cb7b4e4552331d0 Gerrit-PatchSet: 4 Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Owner: Max <msuraev at sysmocom.de> Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: Max <msuraev at sysmocom.de> Gerrit-Reviewer: Neels Hofmeyr <nhofmeyr at sysmocom.de> Gerrit-Reviewer: blobb <dr.blobb at gmail.com> Gerrit-Reviewer: lynxis lazus <lynxis at fe80.eu> Gerrit-Reviewer: neels <nhofmeyr at sysmocom.de> Gerrit-HasComments: No