Fix Docker image deployment in jenkins4eval (ci.jenkins.io build)

[lemeurherve]

https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/Infra/pipelines/plugin-health-scoring/branches/main/runs/18/nodes/86/log/?start=0

== Deploying jenkins4eval/plugin-health-scoring to jenkins4eval/plugin-health-scoring with docker:
docker tag jenkins4eval/plugin-health-scoring jenkins4eval/plugin-health-scoring
docker push jenkins4eval/plugin-health-scoring
Using default tag: latest
The push refers to repository [docker.io/jenkins4eval/plugin-health-scoring]
cb11713fb944: Preparing
b4e7e851ba8f: Preparing
e82ca8ef018b: Preparing
298fa7d08e9d: Preparing
3ab35f64ae29: Preparing
7c3410334f0e: Preparing
7f5cbd8cc787: Preparing
7c3410334f0e: Waiting
7f5cbd8cc787: Waiting
denied: requested access to the resource is denied

[alecharp]

@lemeurherve is this something we can fix or is it because of some configuration? I'm not sure to see how we can fix that at our level..

[alecharp]

Note: the image jenkins4eval/plugin-health-scoring was created in Docker Hub, so the problem is something else.

[lemeurherve]

Probably a credential issue in our shared pipeline library. Not enough bandwidth to check more now but I'll keep an eye on this.

[alecharp]

It's really only about the push of the Docker image. As the project is also built on the infra instance, which is the only one which can deploy the "official" jenkins/plugin-health-scoring image, how about simply deactivating the push when on ci.jenkins.io?

[lemeurherve]

I was missing the permission on this (docker) registry for the "members" group of this organisation.

Restarted a build which succeeded, closing this issue.