Skip to content

Commit

Permalink
phase1: workaround gitverify 1st build failures on fresh workers
Browse files Browse the repository at this point in the history
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 <[email protected]>
  • Loading branch information
ynezz committed May 17, 2023
1 parent 6b145db commit d47fd60
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions phase1/master.cfg
Original file line number Diff line number Diff line change
Expand Up @@ -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",
Expand Down

0 comments on commit d47fd60

Please sign in to comment.