Shields: Docker build shield show "manual" instead of "automated"?

Created on 14 Dec 2018  路  10Comments  路  Source: badges/shields

Are you experiencing an issue with...

  • [x] [shields.io](https://shields.io/#/)

:beetle: Description
I have this docker image being built automatically by Docker Hub Automated Builds but the badge displays "manual" instead of "automated".

:link: Link to the badge
https://github.com/rfgamaral/docker-alpine/tree/rfgamaral/alpine-base

bug needs-upstream-help service-badge

Most helpful comment

This was actually solved by @ldez in #1400. Fix your badges with:

Automated

-https://img.shields.io/docker/automated/{user}/{repo}.svg
+https://img.shields.io/docker/cloud/automated/{user}/{repo}.svg

Status

-https://img.shields.io/docker/build/{user}/{repo}.svg
+https://img.shields.io/docker/cloud/build/{user}/{repo}.svg

It worked for me 馃憤

All 10 comments

Hello @rfgamaral,

When querying the Docker Hub API, I get the following response:
{ "user": "rfgamaral", "name": "alpine-base", "namespace": "rfgamaral", "repository_type": "image", "status": 1, "description": "An Alpine Linux base image, featuring s6 process management to run just about anything! ", "is_private": false, "is_automated": false, "can_edit": false, "star_count": 0, "pull_count": 13, "last_updated": "2018-12-14T18:29:28.033625Z", "is_migrated": false, "has_starred": false, "full_description": "...", "affiliation": null, "permissions": { "read": true, "write": false, "admin": false } }

We are using the value of is_automated to derive what the badge is showing, as far as I can tell Shields is doing the right thing here. Have you set up the build automation properly? Might there be a consistency delay with the Docker API? Maybe you need to retrigger a build? Unfortunately, I'm not an expert about how Docker Hub works, I'm not going to be able to provide much more assistance. 馃槈

Cheers,

Pyves

Unfortunately, I'm not an expert about how Docker Hub works, I'm not going to be able to provide much more assistance.

Nor am I, just started playing with this today...

Have you set up the build automation properly?

As far as I can tell, yes... Every time I push a new tag a build is automatically triggered, it's working as expected. Why is_automated returns false, I don't know either.

image

Well, it might be a bug on Docker side because of this: https://blog.docker.com/2018/12/the-new-docker-hub/

New Automated Builds

  • Speed up builds using Build Caching
  • Add environment variables and run tests in your builds
  • Add automated builds to existing repositories

It's new stuff and maybe they are not updating the is_automated flag properly on this new build system.

I have no idea how can I contact Docker about reporting this issue, does anyone know the proper place/contact for things like this?

The Hub feedback repository seems to be the place where to report issues about the Docker Hub website itself. However, I _think_ the API lives in the Moby repository, so it may be useful to have a dig around there as well.

Thanks, will look into it.

Same issue here. Also getting repo not found for https://img.shields.io/docker/build/papaemmelab/toil_mutect.svg. Repo does exists.

I created this ticket at docker hub, feel free to complement https://github.com/docker/hub-feedback/issues/1733.

same here

Related to #1400

This was actually solved by @ldez in #1400. Fix your badges with:

Automated

-https://img.shields.io/docker/automated/{user}/{repo}.svg
+https://img.shields.io/docker/cloud/automated/{user}/{repo}.svg

Status

-https://img.shields.io/docker/build/{user}/{repo}.svg
+https://img.shields.io/docker/cloud/build/{user}/{repo}.svg

It worked for me 馃憤

Was this page helpful?
0 / 5 - 0 ratings

Related issues

calebcartwright picture calebcartwright  路  3Comments

najeeb-ur-rehman picture najeeb-ur-rehman  路  3Comments

kerolloz picture kerolloz  路  3Comments

paulmelnikow picture paulmelnikow  路  3Comments

Fazendaaa picture Fazendaaa  路  3Comments