Docker Community Forums

Share and learn in the Docker community.

AUTOMATED not show 'OK' after successful automated build

I successfully build a docker image using docker hub automated build. But when I search my image by ‘docker search’ command, it doesn’t showed “OK” beneath the ‘Automated’ section. Any help will be appreciated.

My image name is fnjn/cs1.6

1 Like

Hi.

Not working for me either. I triggered an automated build and it worked, but the “AUTOMATED” indicator was not set for my image. I’ll ping the Docker Hub team.

It is happening to me too.

When “git push origin” to GitHub, the automated build runs and ends successfully. But no “[OK]” appears in “AUTOMATED” column in docker search results.

I also added a “docker-compose.test.yml” in the GitHub repo. It also successfully ends but still I don’t get a “[OK]” status in “AUTOMATED”.

[F.Y.I.] Here are my build configurations in “Configure Automated Builds”:

  • SOURCE REPOSITORY: KEINOS/Dockerfile_of_CoreOS_Transpile @ GitHub
  • BUILD LOCATION: Build on Docker Hub's infrastructure
  • AUTOTEST: Internal and External Pull Requests
  • REPOSITORY LINKS: Off
  • BUILD RULES:
    • Source Type: Branch
    • Source: master
    • Docker Tag: latest
    • Dockerfile location: Dockerfile
    • Build Context: /
    • Autobuild: active
    • Build Caching: active

Image: keinos/coreos-transpiler @ Docker Hub

This “not-showing-OK-in-AUTOMATED” thing is happening not only in GitHub but in BitBucket also.

I created a simple “Hello World” repo with a test in both GitHub and BitBucket with the settings below:

  • SOURCE REPOSITORY: KEINOS / hello_dockerhub @ GitHub and @BitBucket
  • BUILD LOCATION: Build on Docker Hub's infrastructure
  • AUTOTEST: Internal and External Pull Requests
  • REPOSITORY LINKS: On Enable for Base Image
  • BUILD RULES:
    • Source Type: Branch
    • Source: master
    • Docker Tag: latest
    • Dockerfile location: Dockerfile
    • Build Context: /
    • Autobuild: active
    • Build Caching: active
    • BUILD ENVIRONMENT VARIABLES: None

They both pass the tests and the build status is in “SUCCESS” state.

Source code repositories:

This also happens on all my projects too.
e.g., https://hub.docker.com/r/bluet/cronicle-docker

Anyone got it fixed or any idea why? :cry: