carthage_cache
carthage_cache copied to clipboard
Wolox
A tool that allows to cache Carthage/Build folder in Amazon S3.
aws-sdk v2.x is being deprecated. I also had a dependency clash with fastlane where [it now depends on v.3](https://github.com/fastlane/fastlane/commit/13e1b2a13a126d6e96c8c5f09020480a6fa617f1)
This plugin worked great up until about 6 weeks ago, in which it now only archives a single `.framework`, `.DSYM`, and 2 `.bcsymbolmap`s. Evidently, introducing some new dependency has broken...
Hi, As far as I can see, the Amazon's S3 endpoint URL is hardcoded in your code. It would be neat to be able to override it through configuration to...
I have begun implementing support for using ftps instead of aws. The branch can be found here: https://github.com/Lutzifer/carthage_cache/tree/ftps_support It is not quite ready yet for a PR, as host, username...
When I run `carthage_cache publish`, I get the following output: ``` error: . Use --trace to view backtrace /Library/Ruby/Gems/2.0.0/gems/aws-sdk-resources-2.9.17/lib/aws-sdk-resources/resource.rb:134:in `rescue in exists?': Aws::S3::Errors::Http301Error from /Library/Ruby/Gems/2.0.0/gems/aws-sdk-resources-2.9.17/lib/aws-sdk-resources/resource.rb:131:in `exists?' from /Library/Ruby/Gems/2.0.0/gems/carthage_cache-0.8.3/lib/carthage_cache/repository.rb:16:in `archive_exist?' from...
Hi @guidomb, cc: @mokagio , @Dschee I'd like to restart the discussion that was in issue #12 . My organization has multiple projects which share dependencies including in house dependencies....
If `carthage_cache` fails to download the full archive, it still tries to unzip it, and it ignores any errors reported by the unzip. The output of the tool includes ```...
Sometimes the build folder is quite big (~> 100 MB) and at least in these cases it would be very nice to see upload progress or at least the number...
could we add something like `carthage_cache nuke`? That would completely clear out all the archives? Maybe also deletes the local cache on the machine?
The current version crashes in any case there is invalid user input and the only way to differentiate this from an actual internal error or bug is to pass `--trace`...
