buildbot fails to fetch repo from private branch |
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: This is for libiota project that uses cbuildbot for build waterfall. https://uberchromegw.corp.google.com/i/internal.client.weave/console We wanted to enhance the builder to build and generate artifacts required for testing. This meant that we needed to make use of some proprietary tools for the build. So a new private manifest repo branch was created which will point to teams repo that had these proprietary tools. 1. When the buildbot change to point to the manifest file in private branch was added. 2. The builder started to fail as it cannot fetch the manifest repo anymore. Here is the detailed error message - Error messages: fatal: Couldn't find remote ref refs/heads/libiota-internal fatal: Couldn't find remote ref refs/heads/libiota-internal fatal: cannot obtain manifest https://weave.googlesource.com/weave/manifest @@@STEP_FAILURE@@@ 21:15:03: ERROR: Traceback (most recent call last): File "/mnt/data/b/cbuild/libiota/chromite/cbuildbot/stages/generic_stages.py", line 525, in Run self.PerformStage() File "/mnt/data/b/cbuild/libiota/chromite/config/builders/weave_builders.py", line 71, in PerformStage weave_repo.Initialize() File "/mnt/data/b/cbuild/libiota/chromite/cbuildbot/repository.py", line 331, in Initialize cros_build_lib.RunCommand(init_cmd, cwd=self.directory, input='\n\ny\n') File "/mnt/data/b/cbuild/libiota/chromite/lib/cros_build_lib.py", line 624, in RunCommand raise RunCommandError(msg, cmd_result) RunCommandError: return code: 1; command: repo init --repo-url https://chromium.googlesource.com/external/repo --manifest-url https://weave.googlesource.com/weave/manifest --manifest-name default.xml --manifest-branch libiota-internal cwd=/mnt/data/b/cbuild/libiota_weave Error log link: https://uberchromegw.corp.google.com/i/internal.client.weave/builders/libiota/builds/770/steps/WeaveSync/logs/stdio What is the expected behavior? Buildbot should fetch the manifest file from the private branch and continue the build process. What went wrong? Buildbot doesn't have access to fetch manifest from private branch. Did this work before? N/A Chrome version: Channel: n/a OS Version: Flash Version:
,
Feb 8 2017
,
Feb 10 2017
Adding 'TE-NeedsTriageHelp' label to the issue as it is out of scope from TE end to triage the issue.Requesting dev team for further investigation. Thanks.
,
Feb 10 2017
-trooper +git admins
,
Feb 10 2017
Newer builds (e.g., https://luci-milo.appspot.com/buildbot/internal.client.weave/libiota/805) seem to be succeeding in the WeaveSync step with this manifest branch. I didn't do anything. Is this working as intended now?
,
Feb 23 2017
Closing this bug as inactive. It seems to be working now.
,
Feb 23 2017
Sorry for the late response, I missed the previous comment. The newer builds are succeeding because I made the manifest branch public in order to get the build working. But I would be interested to understand why buildbot is not able to use manifest from private branch. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by andyb...@chromium.org
, Feb 7 2017