Fix publishing JavaDoc
MODIFY
.travis.yml
.travis.yml
@@ -18,7 +18,7 @@ jobs:
script: skip
deploy:
provider: script
- script: ./gradlew -s assemble bintrayUpload gitPublishPush
+ script: ./gradlew -s assemble bintrayUpload gitPublishPush -Dorg.ajoberstar.grgit.auth.username=bmuschko -Dorg.ajoberstar.grgit.auth.password=$GH_TOKEN
on:
tags: true

MODIFY
doc/RELEASE.md
doc/RELEASE.md
@@ -7,6 +7,9 @@ The release process uses some external libraries and services described in detai
## gradle-git
The [`gradle-git`](https://github.com/ajoberstar/gradle-git) Gradle plugin is used to automatically determine the project version. `org.ajoberstar.release-opinion` is applied in the main [build.gradle](build.gradle#L15) and configured in [gradle/release.gradle](gradle/release.gradle#L16). Please refer to the plugin [documentation](https://github.com/ajoberstar/gradle-git/wiki/Release%20Plugins#how-do-i-use-the-opinion-plugin) for more details.
+## gradle-git-publish
+The [`gradle-git-publish`](https://github.com/ajoberstar/gradle-git-publish) Gradle plugin is used to publish the documentation to `gh-pages` branch. It is applied and configured in the [gradle/documentation.gradle](gradle/documentation.gradle) file.
+
## Travis CI
[Travis CI](https://travis-ci.com) service is used as our current [CI/CD](https://en.wikipedia.org/wiki/CI/CD) server. Build and deploy jobs are configured in [.travis.yml](.travis.yml) file. Please refer its [documentation](https://docs.travis-ci.com/) for more details.
@@ -31,7 +34,7 @@ where `[SCOPE]` can be one of: `major`, `minor`, `patch`, and determines which p
5. When Gradle build is finished, developer's work is done and the rest of the release process is automated.
6. After push to the `origin`, Travis detects new tag and triggers a build.
7. Travis [is instructed](.travis.yml#L23) to execute [release stage](https://docs.travis-ci.com/user/build-stages/) when on Git tag.
-8. In this stage [Gradle script](.travis.yml#L21) assembles plugin binaries (with new version) and uploads them to Bintray (credentials are stored as [secure variables](https://docs.travis-ci.com/user/environment-variables/#Defining-Variables-in-Repository-Settings) in Travis). Also JavaDoc is published to `gh-pages` branch.
+8. In this stage [Gradle script](.travis.yml#L21) assembles plugin binaries (with new version) and uploads them to Bintray (credentials are stored as [secure variables](https://docs.travis-ci.com/user/environment-variables/#Defining-Variables-in-Repository-Settings) in Travis). Also JavaDoc is published to `gh-pages` branch (GitHub username and [access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) are also stored as secure variables).
# Useful links
* [Semantic Versioning](http://semver.org/)

MODIFY
gradle/documentation.gradle
gradle/documentation.gradle
@@ -11,7 +11,7 @@ buildscript {
apply plugin: org.ajoberstar.gradle.git.publish.GitPublishPlugin
gitPublish {
- repoUri = 'git@github.com:bmuschko/gradle-docker-plugin.git'
+ repoUri = 'https://github.com/bmuschko/gradle-docker-plugin.git'
branch = 'gh-pages'
contents {

MODIFY
gradle/release.gradle
gradle/release.gradle
@@ -11,10 +11,9 @@ buildscript {
}
}
-ext.repo = Grgit.open(rootDir)
+apply plugin: org.ajoberstar.gradle.git.base.GrgitPlugin
release {
- grgit = Grgit.open(rootDir)
versionStrategy Strategies.FINAL
defaultVersionStrategy = Strategies.FINAL
tagStrategy {

Fix publishing JavaDoc