THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Since the Sling 8 release we also provide a docker image. The Dockerfile can be found in the sling-org-apache-sling-starter-docker repo. Images are deployed by tagging the repository with the version of Sling they correspond to, for instance:
| Code Block | ||
|---|---|---|
| ||
git tag -a 11
git push --tags |
After the tags are pushed the DockerHub build can be triggered. We since we trigger builds based on Github tags, the type of build we use is source_type: Tag . For more details , see the /repos/private/pmc/sling SVN repository. The build status for ongoing builds can be verified at https://hub.docker.com/r/apache/sling/builds/ .
As of the Sling Starter 12 release, the process is automated using DockerHub automated builds . Pushing a tag of the form org.apache.sling.starter-$VERSION will result in a DockerHub tag of $VERSION and also in the latest tag being updated.
There is no direct access to the DockerHub UI. If needed, a set of credentials that can be used to trigger builds are stored in the private Sling PMC area in SVN.
The automated builds setup was configured in
| Jira | ||||||
|---|---|---|---|---|---|---|
|
sling-org-apache-sling-starter-docker module must be released before deploying binaries (like the Docker image) to public places .Update local references to the old starter
...