spotify / XCRemoteCache

Other
827 stars 50 forks source link

The xcprepare check encoding url mismatch the cache link #124

Closed Serena1993 closed 2 years ago

Serena1993 commented 2 years ago

My integration setup

  1. Automatic integrate
  2. write .rcinfo

primary_repo: https://my-private-repo.git cache_addresses:

And I always get the error: error: (XXX_Example) Postbuild step failed unsuccessfulResponse(status: 413)

Could you help me find the problem? Thanks

polac24 commented 2 years ago

413 HTTP response means Payload Too Large

The example docker file instructs setting http://localhost:8080/cache as a cache_address (docs) - it sets 1GB max file size there. Otherwise, the max upload size is 1MB. Please switch to /cache or configure nginx.conf accordingly so it has bigger client_max_body_size for your /newcache.

Serena1993 commented 2 years ago

A new problem, when I use the cocoapods-plugin integration method, I can't get the correct cache link detection in the consumer mode, so I can't get the actual cache that already exists.

iShot2022-04-25 22 54 59

It seems that the URL checked and the cache are not the same.

frome xcprepare console log: http://localhost:8080/cache/marker/015f9205f102f4f1bb12571b035ac334bcf63285-%5BDevDebug%5D-iphonesimulator-13C100-5

file real download link: http://localhost:8080/cache/marker/015f9205f102f4f1bb12571b035ac334bcf63285-DevDebug-iphonesimulator-13C100-5

polac24 commented 2 years ago

Hello again,

  1. Is your current commit 015f9? if not, specify primary_branch to the branch name (on a remote repo) against which the producer built artifacts
  2. Consumer, to validate if artifacts are ready, checks /marker paths, not /meta. /meta files specify if an artifact of a given target is available (and what is its filename), while /meta says if artifacts for all targets are available for the sha
  3. If you still have troubles, can you close this issue and open new one? The problem seems unrelated to the original one.
polac24 commented 2 years ago

You edited you comment so now have more context. Please try

'check_build_configuration' => 'DevDebug',

it seems to be a string, not an array.

polac24 commented 2 years ago

The original problem seems to be resolved