You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Some debug log
* new user input: verbose_log
* Using warning instead of error if there is any error during the Cachefile check/compare.
* add more debug log
* add `Cartfile.resolved` to the `BITRISE_CACHE_INCLUDE_PATHS` env, so the `Cache push` step will push it automatically. With that, the user does not need to do it manually 🎉
* update readme: removed the `./Carthage -> ./Carthage/Cachefile` step, because it will be handled by the `Carthage` step itself.
* clean
* Revert "add `Cartfile.resolved` to the `BITRISE_CACHE_INCLUDE_PATHS` env, so the `Cache push` step will push it automatically. With that, the user does not need to do it manually 🎉"
This reverts commit b08d51b.
* Update warnings about cache process
* temporary branch change for the sample app to test the cache mechanism on CI
* Revert "temporary branch change for the sample app to test the cache mechanism on CI"
This reverts commit 0f74976.
* PR clean - fix
* clean + path fix
* PR: log ifxes
* dep -update github.com/bitrise-io/go-steputils
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,8 @@ Plain simple build step for setting up your project with [Carthage](https://gith
6
6
7
7
You can cache the result of `carthage bootstrap` to make Bitrise faster when building unchanged dependencies. For that you'll have to [set up caching](http://devcenter.bitrise.io/caching/about-caching/) in your Bitrise workflow.
8
8
9
-
1. add a cache pull step before your Carthage step,
10
-
2.set up a cache push step after your Carthage step and make sure to add `./Carthage -> ./Carthage/Cachefile`.
9
+
1. add a `Cache pull` step **before** your `Carthage` step,
10
+
2.add a `Cache push` step **after** your `Carthage` step,
11
11
12
12
The `Cachefile` stores a Swift version you ran `carthage bootstrap` the last time and the content of your `Cartfile.resolved`. Until either of these information is not changed between builds, Bitrise will ignore the `bootstrap` call and use the cached content of your `Carthage/Build` directory for building your project. If you have changes in your `Cartfile.resolved`, or changed the stack to one with a different Swift version, it will run `carthage bootstrap` to make sure the cache is only used when it's 100% compatible.
// Print the warning about the missing Cachefile only if the other required file (Cartfile.resolved) is available.
155
+
// If the Cartfile.resolved is not found, then we don't want to mislead the user with this warning.
156
+
if!cacheFileAvailable&&resolvedFileAvailable {
157
+
fmt.Println()
158
+
log.Warnf("The "+cacheFileName+" is generated by the step. Probably cache not initialised yet (first cache push initialises the cache), nothing to worry about ;)")
159
+
160
+
}
161
+
162
+
if!resolvedFileAvailable {
163
+
fmt.Println()
164
+
log.Warnf("No "+resolvedFileName+" found at: %s", resolvedFilePath)
165
+
log.Warnf("Make sure it's committed into your repository!")
166
+
log.Warnf(resolvedFileName+" presence ensures that Bitrise will use exactly the same versions of dependencies as you in your local environment. ")
167
+
log.Warnf("The dependencies will not be cached until the "+resolvedFileName+" file presents in the repository.")
0 commit comments