Skip to content

Prebuild on a branch failed when fetching additional repository that didn't have that branch #13512

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
david-bakin opened this issue Oct 2, 2022 · 1 comment · Fixed by #13549
Labels
feature: prebuilds team: webapp Issue belongs to the WebApp team type: bug Something isn't working

Comments

@david-bakin
Copy link

david-bakin commented Oct 2, 2022

Bug description

Pushed commits to a new branch lldb-attempts in GitLab repo, prebuild was triggered, it seemed to completely build the custom .gitpod.Dockerfile but then failed with

SYSTEM ERROR
Prebuild failed for system reasons. Please contact support. undefined

Log cut/pasted from prebuild window: https://gist.github.com/david-bakin/51c7240de342148f228133e57983c1bd

Oh wait a sec! When I reopened the prebuild window I see a different SYSTEM ERROR:

Prebuild failed for system reasons. Please contact support. cannot initialize workspace: cannot initialize workspace: git initializer clone: Remote branch lldb-attempts does not exist in https://github.com/lldb-tools/lldb-mi.git

And this is true! My main repo is trying to prebuild branch lldb-attempts but I expected the additional repo to pull its default branch!

Note that the documentation says it will do this!!

When the above configuration is defined then the following additional steps happen when Gitpod workspace is started:

  1. If you open a workspace on a branch, Gitpod will clone the same-named branch in all repositories. If such a branch doesn’t exist Gitpod checks out the default branch.

And by the way the "undefined" error on the first prebuild window I saw is bad - it is only by sheer chance, wanting to file an issue on the "SYSTEM ERROR", that I opened the window again from the prebuilds dashboard page and saw the real error.

Steps to reproduce

Set up a repo with an additional repo - any arbitrary one off of the web. Main repo needs a .gitpod.yml that triggers a prebuild when any new branch is pushed. Then push a new branch to the main repo making sure the new branch name is not one that is present in the additional repo. See if it fails this way.

Workspace affected

https://gitpod.io/projects/env-wrappers-cpp/e9acba92-0005-452d-8319-927c48f6db4e

Expected behavior

I expected either the additional repo to pull its default branch, or for there to be a way to specify which branch to pull for the additional repos.

Example repository

No response

Anything else?

No response

Front logo Front conversations

@david-bakin david-bakin added the type: bug Something isn't working label Oct 2, 2022
@jimmybrancaccio
Copy link

I can confirm this is replicable. I was just working on a support ticket where this was happening. Thanks @david-bakin for getting this issue in! 😁 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: prebuilds team: webapp Issue belongs to the WebApp team type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants