1# Releasing to JCenter 2 3Creating a release on jcenter is done by invoking the binaryUpload task with a bintray user and API key. Your API key can be [found here](https://bintray.com/user/edit/tab/apikey). 4 5`gradle -PbintrayUser=myusername -PbintrayKey=123 clean bintrayUpload` 6 7Note that you'll need to be a member of the appium organization on jcenter before publishing. Existing members are able to invite new ones. 8 9Update 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. 10 11# Releasing snapshots to artifactory 12 13Snapshots of DroidDriver are released to `http://oss.jfrog.org/artifactory` in the oss-snapshot-local 14repository. 15 16`gradle -PbintrayUser=myusername -PbintrayKey=123 clean assemble artifactoryPublish` 17 18Note that resolving the snapshots requires adding the maven repo to the gradle build file: 19 20`maven { url 'http://oss.jfrog.org/artifactory/oss-snapshot-local' }` 21 22# Known Issues 23 24- `[buildinfo] Properties file path was not found! (Relevant only for builds running on a CI Server)` 25The missing properties warning can be safely ignored. We're populating the values in Gradle so 26the artifactory plugin doesn't know that they're already set. 27