No more CI/CD builds since the repository has been renamed

[dduportal]

It looks like the repository has been renamed from docker-agent to docker-agents.
(I guess #749).

It was not announced and it broke the CI/CD builds:

• https://ci.jenkins.io/job/Packaging/job/docker-agent is not renamed (neither the job or its configuration) and is disabled
• https://trusted.ci.jenkins.io/job/Containers/job/Agents/job/docker-agent/ (neither the job or its configuration)

As such we don't have any builds (last build of the master branch was 14 days ago) and we can't validate PRs such as #1125, neither release the images.

[lemeurherve]

That's my mistake, looking into fixing it ASAP.

---

FWIW, it was announced in #749 (comment)

[lemeurherve]

• Fix job config on ci.jenkins.io: https://ci.jenkins.io/job/Packaging/job/docker-agents/

  • 

  • Rename job (implicitely done by the change above)
  • Delete previous https://ci.jenkins.io/job/Packaging/job/docker-agent/ job
    • Note: not sure about that one, to be kept for historical reason?

• Fix job config on trusted.ci.jenkins.io: https://trusted.ci.jenkins.io/job/Containers/job/Agents/job/docker-agents/

  • 

  • Rename job

• Check that no tag builds were triggered in trusted.ci.jenkins.io "Scan repository" logs

  

• Check that on ci.jenkins.io builds were running on the primary branch and on pull requests (trusted.ci.jenkins.io builds only on new tags)

• Check references in @jenkinsci & @jenkins-infra repositories

[lemeurherve]

FWIW, build on master currently in failure on ci.jenkins.io (haven't checked the details yet):

[dduportal]

Delete previous https://ci.jenkins.io/job/Packaging/job/docker-agent/ job

I'm not sure:

• On one hand, it ensures old GH checks do not respond with an HTTP/404
• On the other hand, if you land on a page of the old job, you don't see it's is disabled easily leading to confusion

I would vote for removing it bu I want other point of view

WDYT @timja @MarkEWaite ?

[dduportal]

(outside this: LGTM! Thanks for the quick fixes)

[dduportal]

Checks are good on the master branch and at least 1 PR. We can close (unless you want to keep open until we've decided what to do for #1126 (comment)).

[timja]

I vote for remove

[lemeurherve]

I vote for remove

FWIW, I did not find any obvious way of deleting docker-agent folder from this organisation job.

Does it has to be done on disk directly?

[MarkEWaite]

I vote for remove

FWIW, I did not find any obvious way of deleting docker-agent folder from this organisation job.

Does it has to be done on disk directly?

There are builds that are marked as "Keep forever"; The docker-agent folder can't be deleted while a job is marked as "Keep forever".

Those include:

• https://ci.jenkins.io/job/Packaging/job/docker-agent/job/master/1013/
• https://ci.jenkins.io/job/Packaging/job/docker-agent/job/master/1011/
• https://ci.jenkins.io/job/Packaging/job/docker-agent/job/master/986/
• https://ci.jenkins.io/job/Packaging/job/docker-agent/job/master/989/
• https://ci.jenkins.io/job/Packaging/job/docker-agent/job/master/990/
• https://ci.jenkins.io/job/Packaging/job/docker-agent/job/master/985/