Closed jflan-dd closed 1 month ago
This is the motivation for using the posix format according to the original article
we will use posix notation for higher-resolution timestamps. This preserves various attributes used by xcodebuild.
Focusing on the discussion of DerivedData provided by Xcode, I am very interested in the bitrise-steplib/bitrise-step-save-xcodebuild-cache and bitrise-steplib/bitrise-step-restore-xcodebuild-cache are beginning development.
These have not yet been added to bitrise-io/bitrise-steplib, so it does not appear that we can use them from bitrise.io yet.
custom_tar_args
has been added https://github.com/bitrise-steplib/bitrise-step-save-cache?tab=readme-ov-file#%EF%B8%8F-configuration , thanks for your feedback .
Thanks!
Troubleshooting
Useful information
Issue description
I've been attempting to replicate the work from this article for our Bitrise builds.
Using the standard Save Cache and Restore Cache I wasn't able to have Xcode reuse any build artifacts, and it actually ended up taking more time than without the cache.
After going through the differences between the steps in the article and the Bitrise Save/Restore Cache steps I found that the important difference was passing
--format posix
to thetar
command in Save Cache.I was also able to validate this behavior locally without Bitrise in the loop at all by manually archiving a restoring the DerivedData folder and seeing that Xcode only reused artifacts when
--format posix
was supplied.Bitrise info
Build URL: This is the build that create the cache: https://app.bitrise.io/build/a5c7e56a-116f-44cb-8ae6-24846dcd032e This is the build that reused the cache: https://app.bitrise.io/build/12116908-0e79-4902-8ffb-6a6161f9919a
Bitrise Support enabled: YES
Log:
Steps to reproduce