blob: eaeb815a8a5dbf406748a260926584b2835f2173 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
# Releasing to JCenter
Add the following credentials to `bintray.properties` Your API key can be [found here](https://bintray.com/user/edit/tab/apikey).
```
bintray.user=USERNAME
bintray.key=APIKEY
```
Creating a release on jcenter is done by invoking the binaryUpload task. Note that you'll need to be a member of the appium organization on jcenter before publishing. Existing members are able to invite new ones.
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.
|
