What we're missing ATM is different documentation versions for different application versions. What this change does is that it's:
- finding out what is the current branch (e.g. 1.0.x)
- finding out out what is the name of the main adoc file (e.g. spring-cloud-sleuth)
- pulling the changes from gh-pages after checkout
- finding out what is the list of comma separated whitelisted branches (via the `docs.whitelisted.branches` prop)
- in gh-pages creating a folder with name of the branch (e.g. /1.0.x)
copying all the docs/target/generated-docs/ to that folder
- if the branch from which we're calling the script is NOT master then we're changing the ${main.adoc}.html to index.html so that it's easier to access the docs (e.g. http://cloud.spring.io/spring-cloud-sleuth/1.0.x/)
With the following configuration at `bootstrap.yaml`
```yaml
spring:
application.name: spring-cloud-hystrix-dashboard
profiles.active: prod
cloud:
config:
discovery:
enabled: true
serviceId: spring-cloud-server-config-with-eureka
server.port: 9003
turbine:
appConfig: some-service
clusterNameExpression: 'default'
```
I wasn't able to see why Turbine can't find the instance. The reason was related to SPEL:
```
org.springframework.expression.spel.SpelEvaluationException: EL1008E:(pos 0): Property or field 'default' cannot be found on object of type 'com.netflix.appinfo.InstanceInfo' - maybe not public?
```
Anyways there was nothing there in the logs so maybe it should not be silenced like right now?