-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Support for carthage --cache-builds flag #47
Comments
Interesting, I will take a look at that. Notes to self:
|
@t089 Maybe I ask what the use case for this is? Usually the workflow with rome resembles the following:
So carthage is only triggered to build the frameworks that are currently missing from the cache. |
Very good questing. Let me explain: Say you have a dependency FrameworkA that itself depends on FrameworkB and FrameworkC. Now, FramworkA needs an update. In your example Rome would fail to download FramworkA from cache and would trigger a carthage build. Carthage would then build FrameworkA but would also build its dependencies FrameworkB and FrameworkC, although they did not change and are already present in the We are working a lot with internal frameworks that are included in the main app as carthage dependencies. Our frameworks also have some 3rd party dependencies and it's always painful to watch carthage build stuff that is already there waiting to be used... |
@t089 I understand. Thanks for explaining, I think we have the same issue but never noticed. Do you have any opinion on the implementation details I have made a note of to myself in the first comment? |
@t089 Please try pre-release https://github.com/blender/Rome/releases/tag/v0.10.0.21 Let me know if it works as expected and I will proceed with a full release. |
Awesome, that was quick, nice work. May I ask which route of implementing it you chose? I ran a quick test |
I implemented the following:
Seems to work for me, I'm running:
|
Oh, boy was probably too early in the morning 💤, of course I was using the pre-release version binary only for the upload but not for the download command. Ok, seems to work for me as well. Thank you 👍 |
Great, I will test a little more and hopefully promote the tag to full release :) @t089 Thanks for suggesting this feature. I look forward to hear more feedback. |
Looks like it's working. Full release it is! |
Hey,
carthage 0.20.0 introduced the
--cache-builds
flag, which generates.NAME.version
version files for each built framework. When building a dependency carthage will use these version files to check if a corresponding build artefact is already available and skip the build. Would be great if rome could store these version files alongside the frameworks in the S3 cache and restore them during arome download
.Thank you!
The text was updated successfully, but these errors were encountered: