I went to check docs, and the build was last run on Oct 30th.
Manually scheduling a build fails with:
> git fetch --no-tags --force --progress --depth=3 -- git@github.com:geoserver/geoserver.git +refs/heads/*:refs/remotes/origin/* # timeout=10
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from git@github.com:geoserver/geoserver.git
...
Caused by: hudson.plugins.git.GitException: Command "git fetch --no-tags --force --progress --depth=3 -- git@github.com:geoserver/geoserver.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout:
stderr: error: refs/remotes/origin/GEOS-11430 does not point to a valid object!
error: refs/remotes/origin/backport-7250-to-2.24.x does not point to a valid object!
error: refs/remotes/origin/backport-7312-to-2.24.x does not point to a valid object!
Checking against Geoserver-main build:
-
git check out settings is similar
-
geoserver-main-docs has additional section for:
shallow clone depth: 3
path of repo to use use during clone: /var/lib/jenkins/workspace/geoserver-main/.git
I guess it is trying to clone from geoserver-main workspace on local disk.
Mitigation taken:
- Remove geoserver-main-docs workspace, in the hopes it will do a fresh checkout
- Success: build restored
Please keep an eye out for any other affected builds.