How does "validating repository" work?

#1

Bitrise Build Issue Report template

Description of the issue

  1. add a new app at https://app.bitrise.io/apps/add

  2. add repo: https://github.com/torvalds/linux

  3. see “validating repository” spin

Agent version: 1.9.9

Start time: 2020-04-23T14:53:02Z

$ docker “run” “-v” “/var/run/docker.sock:/var/run/docker.sock” “-v” “/bitrise:/bitrise” “-v” “/tmp/bitrise-agent022676468:/.bitrise-config” “–privileged” “–network=host” “–name=bitrise-main-container” “bitriseio/android:pinned” “bitrise” “run” “–config” “/.bitrise-config/bitrise.yml” “–inventory” “/.bitrise-config/bitrise.secrets.yml” “–json-params-base64” “eyJ3b3JrZmxvdyI6InZhbGlkYXRpb25fd29ya2Zsb3dfbm9fc3NoIn0=”

Environment:

Where did the issue happen?

If on Bitrise.io: which stack? If not on Bitrise.io: on what operating system? (Plus any other information you can share)

Which build Step causes the issue and which version of the step?

E.g.: Git Clone v3.6.0

Reproducibility

  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : YES/NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : YES/NO
  • Does the issue happen sporadically, or every time? :
  • Does upgrading the build Step to the latest version help? : YES/NO
  • When did the issue start? :

Local reproduction

Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what bitrise.io will get when it does a git clone in the clean environment! If possible please note which sections you tried.

Local reproduction: Linux / Android (docker based) stack builds

Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( https://www.bitrise.io/cli )? If no, can it be reproduced with Docker (using the same docker images / environment we use on bitrise.io)? Related guide: http://devcenter.bitrise.io/docker/run-your-build-locally-in-docker/ .

Build log

Please copy paste the build’s bitrise.io URL here (or if the issue happens somewhere else then the full logs), or if you can’t share the url / log here then send the url or full log through a private channel (e.g. email - https://www.bitrise.io/contact ), with a link to the related Discuss issue.

still spinning

0 Likes

#2

bump

is still spinning

0 Likes

#3

Hi @Ql1!

The process of validating your repository is our project scanner cloning it and parsing through it’s files, to find something that would signify the repository being an iOS, Android app or was built with Flutter, React Native, Xamarin, Ionic or Cordova frameworks.

Of course, the scanner was not mean to recognize the Linux kernel, it also shouldn’t hang forever. It takes an unusually long time compared to other projects for sure, due to the size of the repository, but I could not recreate this, I forked the repo and the validation failed as expected. Is it persistent if you try again?

0 Likes

closed #4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

0 Likes