Permalink
Browse files

Fixed release bug, documentation

Released Shipkit from my local so that it can take the '--tags' bugfix. Documented how we can break the stalemate if Shipkit cannot be released due to some bug in Shipkit.
  • Loading branch information...
mockitoguy committed Oct 20, 2017
1 parent 0eb549d commit fa9b460401fa93f7d5f07a2a704fb839c3a92289
Showing with 13 additions and 2 deletions.
  1. +12 −1 CONTRIBUTING.md
  2. +1 −1 build.gradle
View
@@ -16,7 +16,7 @@ Be pragmatic, all rules have exceptions given good reasons.
## Local development
### Local development
### Building and testing
1. Clone shipkit repo, make your changes, then run ```./gradlew fastInstall```
This will install the artifacts in local maven repository for easy sharing.
@@ -41,6 +41,17 @@ It should use the same version that was built in the previous step.
Remember to switch it back when you finished.
- Clone "mockito/mockito" repository and make testing with a proper project :)
### Troubleshooting releases
Sometimes we cannot release new version Shipkit because there is a bug in Shipkit.
Since we cannot release, we cannot release a bugfix.
To break the stalemate, we need to release from local, for example:
```
./gradlew testRelease
./gradlew performRelease
```
## Dependencies on external libraries
Reuse is awesome but it comes with a cost.
View
@@ -5,7 +5,7 @@ buildscript {
maven { url "https://plugins.gradle.org/m2/" }
}
dependencies {
classpath 'org.shipkit:shipkit:0.9.114'
classpath 'org.shipkit:shipkit:0.9.116'
classpath 'ru.vyarus:gradle-animalsniffer-plugin:1.3.0'
}
}

0 comments on commit fa9b460

Please sign in to comment.