infra-issues mailing list archives

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


Robert Munteanu updated INFRA-15957:
    Status: Waiting for Infra  (was: Closed)

I have sent multiple build requests using the provided API token but no builds were triggered.
At least 8 hours have passed, in the passed that was more than enough for builds to be triggered.

I have used both the 'full' build and the 'source tag' build, e.g.

curl -H "Content-Type: application/json" --data '{"build": true}' -X POST${TOKEN}

curl -H "Content-Type:application/json" --data '{"source_type": "Tag", "source_name":"9"}'

I see no builds and have no access to the builds logs. Can you please check if there are any
errors on the docker hub side?

> 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