phase1: workaround gitverify 1st build failures on fresh workers v4
authorPetr Štetiar <ynezz@true.cz>
Tue, 16 May 2023 18:41:05 +0000 (20:41 +0200)
committerPetr Štetiar <ynezz@true.cz>
Wed, 17 May 2023 09:27:23 +0000 (11:27 +0200)
Currently every 1st build on ephemeral build worker results in the
failure of the `gitverify` build step as the stock buildbot Git() build
step for some reasons just clones the Git repository into detached HEAD
state.

On the 2nd build using the same build worker Git() checkouts the branch
and thus makes `gitverify` step happy and the builds then continues
normally.

This needs to be fixed properly, either by adjusting the `gitverify`
check or adding suitable `mode` into Git() build step, but this needs
more time and testing.

So for now, lets simply workaround that issue by running Git() step two
times.

References: #5
Signed-off-by: Petr Štetiar <ynezz@true.cz>
phase1/master.cfg

index c392c5f2185de2521b97c887db36222b997f7396..1658a91a380e7ec63cdcb0cd6e2e75939ee0d8a0 100644 (file)
@@ -725,6 +725,16 @@ for target in targets:
                haltOnFailure = True,
        ))
 
+       # workaround for https://github.com/openwrt/buildbot/issues/5
+       factory.addStep(Git(
+               name = "git me once more please",
+               repourl = repo_url,
+               mode = 'full',
+               method = 'fresh',
+               locks = NetLockDl,
+               haltOnFailure = True,
+       ))
+
        # update remote refs
        factory.addStep(ShellCommand(
                name = "fetchrefs",