diff options
| author | bootstraponline <code@bootstraponline.com> | 2015-02-20 14:25:26 -0500 |
|---|---|---|
| committer | bootstraponline <code@bootstraponline.com> | 2015-02-20 15:26:28 -0500 |
| commit | e891ed293a14adf751c58e47117212da25fc08e6 (patch) | |
| tree | d80ba42989a8a4e9f408e549101148f493b59fab /releasing_to_jcenter.md | |
| parent | 22a1bce4356564f66630054ae8c300cce8867488 (diff) | |
| download | droiddriver-e891ed293a14adf751c58e47117212da25fc08e6.tar.gz | |
Refactor build.gradle & add artifactory support
Artifactory enables publishing snapshots of droiddriver
jcenter is only for released artifacts and doesn't allow snapshots
Change-Id: Ifb5b5a6e5de081516ec8ffbb81190776aa0658c2
Diffstat (limited to 'releasing_to_jcenter.md')
| -rw-r--r-- | releasing_to_jcenter.md | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/releasing_to_jcenter.md b/releasing_to_jcenter.md index cb6be49..d8321db 100644 --- a/releasing_to_jcenter.md +++ b/releasing_to_jcenter.md @@ -12,3 +12,20 @@ Creating a release on jcenter is done by invoking the binaryUpload task. Note th Update the version number in `build.gradle` by modifying the value of `ddVersion`. Official releases should be made only after removing the `-SNAPSHOT` suffix. If the same version number is used as an existing release of droiddriver then jcenter will reject the upload. `gradle clean bintrayUpload` + +# Releasing snapshots to artifactory + +Snapshots of DroidDriver are released to `http://oss.jfrog.org/artifactory` in the oss-snapshot-local +repository. + +`gradle clean artifactoryPublish` + +Note that resolving the snapshots requires adding the maven repo to the gradle build file: + +`maven { url 'http://oss.jfrog.org/artifactory/oss-snapshot-local' }` + +# Known Issues + +- `[buildinfo] Properties file path was not found! (Relevant only for builds running on a CI Server)` +The missing properties warning can be safely ignored. We're populating the values in Gradle so +the artifactory plugin doesn't know that they're already set. |