infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (JIRA)" <>
Subject [jira] [Commented] (INFRA-15957) DockerHub: automated build for Apache Sling should be named 'sling'
Date Thu, 08 Feb 2018 09:56:00 GMT


Robert Munteanu commented on INFRA-15957:

[~cthistle] - now tags 9 and 10 work fine when triggered with the branch name, so thanks for

One item is missing ( let me know if you need a separate Jira ticket for it ). The default
build rule would map the 'master' git branch to the 'latest' docker tag ( see
, search for "A default build rule is set up for you" ) . Right now the 'master' git branch
is mapped to the 'master' docker tag, which means that we still don't get the 'latest' tag,
which is widely used.

> DockerHub: automated build for Apache Sling should be named 'sling'
> -------------------------------------------------------------------
>                 Key: INFRA-15957
>                 URL:
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Docker
>            Reporter: Robert Munteanu
>            Assignee: Chris Thistlethwaite
>            Priority: Major
>         Attachments: docker-hub-settings.png
> In INFRA-15916 you added an automated build for Apache Sling, so many thanks for that.
However, we'd like the name to be 'sling', not 'sling-org-apache-sling-starter-docker'.
> I investigated and it's possible to have different names for the dockerhub and github
repos - I tested this with , which is built from
> In that line, please rename our image to just 'sling'. Re-creating is fine if needed,
we have not announced this anywhere yet.

This message was sent by Atlassian JIRA

View raw message