Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-1105

Slave to Agent Renaming: Rename Docker Agent images on DockerHub

    Details

    • Type: Task
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: etc
    • Labels:
      None
    • Similar Issues:

      Attachments

        Issue Links

          Activity

          Hide
          rtyler R. Tyler Croy added a comment -

          There are repositories prepared under the new namespace jenkins/agent which need to be published.

          Show
          rtyler R. Tyler Croy added a comment - There are repositories prepared under the new namespace jenkins/agent which need to be published.
          Hide
          csanchez Carlos Sanchez added a comment -

          jenkins/slave and jenkins/jnlp-slave are using auto build, do we want to change that ?

          https://github.com/jenkinsci/docker-slave and https://github.com/jenkinsci/docker-jnlp-slave git repos can be renamed

          Show
          csanchez Carlos Sanchez added a comment - jenkins/slave and jenkins/jnlp-slave are using auto build, do we want to change that ? https://github.com/jenkinsci/docker-slave and https://github.com/jenkinsci/docker-jnlp-slave git repos can be renamed
          Hide
          renescheibe René Scheibe added a comment -

          Is there anything I can help to get this done?

          Show
          renescheibe René Scheibe added a comment - Is there anything I can help to get this done?
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Not now, I'd guess. We need to migrate the agent image delivery frows to Trusted CI, and I believe we will be able to finalize this story after it. CC Alex Earl and Marky Jackson who were working on the foundation infra changes for it

           

          We could go ahead and implement this story for DockerHub, but it would be an effort overhead

          Show
          oleg_nenashev Oleg Nenashev added a comment - Not now, I'd guess. We need to migrate the agent image delivery frows to Trusted CI, and I believe we will be able to finalize this story after it. CC Alex Earl and Marky Jackson who were working on the foundation infra changes for it   We could go ahead and implement this story for DockerHub, but it would be an effort overhead
          Hide
          jequals5 Marky Jackson added a comment -

          Ack: Alex and should sync sometime this week

          Show
          jequals5 Marky Jackson added a comment - Ack: Alex and should sync sometime this week
          Hide
          jequals5 Marky Jackson added a comment -

          I am going to assign this to me

          Show
          jequals5 Marky Jackson added a comment - I am going to assign this to me
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          reassigned it to myself Marky Jackson. I am preparing the change

          Show
          oleg_nenashev Oleg Nenashev added a comment - reassigned it to myself Marky Jackson . I am preparing the change
          Hide
          slide_o_mix Alex Earl added a comment -

          Anything I can help with on Trusted.ci?

          Show
          slide_o_mix Alex Earl added a comment - Anything I can help with on Trusted.ci?
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Alex Earl thanks, we might need to do changes there later for experimental Windows agents and for others during the release flow migration. Here I rather target the current production images which are currently automated by DockerHub Autobuilds. Maybe we could move the experimental images to a separate story since we can easily do changes there without worrying about compatibility

           

           

          Show
          oleg_nenashev Oleg Nenashev added a comment - Alex Earl thanks, we might need to do changes there later for experimental Windows agents and for others during the release flow migration. Here I rather target the current production images which are currently automated by DockerHub Autobuilds. Maybe we could move the experimental images to a separate story since we can easily do changes there without worrying about compatibility    
          Hide
          slide_o_mix Alex Earl added a comment -

          Currently the Windows images are only being published to the jenkins4eval/*agent repo on Dockerhub. I am not publishing anything to any "slave" repo on dockerhub.

          Show
          slide_o_mix Alex Earl added a comment - Currently the Windows images are only being published to the jenkins4eval/*agent repo on Dockerhub. I am not publishing anything to any "slave" repo on dockerhub.
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Alex Earl Mark Waite Jeff Thompson Daniel Beck Marky Jackson Jesse Glick while we are here, would it make sense to rename "jenkins/jnlp-slave" to "jenkins/inbound-agent"? "JNLP" terminology is also deprecated, and with WebSockets support it creates even more confusion.  

          Show
          oleg_nenashev Oleg Nenashev added a comment - Alex Earl   Mark Waite Jeff Thompson Daniel Beck Marky Jackson Jesse Glick while we are here, would it make sense to rename "jenkins/jnlp-slave" to "jenkins/inbound-agent"? "JNLP" terminology is also deprecated, and with WebSockets support it creates even more confusion.  
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          INFRA-2570 caused unexpected errors. Both Trusted CI and ci.jenkins.io cannot provision Windows Docker agents, so we cannot deliver this story at the moment

          Show
          oleg_nenashev Oleg Nenashev added a comment - INFRA-2570  caused unexpected errors. Both Trusted CI and ci.jenkins.io cannot provision Windows Docker agents, so we cannot deliver this story at the moment
          Hide
          slide_o_mix Alex Earl added a comment -

          ci.j.io is fine now, let.me look at trusted

          Show
          slide_o_mix Alex Earl added a comment - ci.j.io is fine now, let.me look at trusted
          Hide
          slide_o_mix Alex Earl added a comment -

          What about "remoting-agent"?

          Show
          slide_o_mix Alex Earl added a comment - What about "remoting-agent"?
          Hide
          jglick Jesse Glick added a comment -

          jenkins/inbound-agent sounds good to me for https://github.com/jenkinsci/docker-inbound-agent, just like jenkins/agent gets built out of https://github.com/jenkinsci/docker-agent.

          (The JNLP terminology is deprecated, because it is very misleading. You can use JNLP to launch an inbound agent using WebSocket transport; and you can start an inbound agent using the TCP protocol named JNLP4-Connect without using JNLP.)

          Show
          jglick Jesse Glick added a comment - jenkins/inbound-agent sounds good to me for https://github.com/jenkinsci/docker-inbound-agent , just like jenkins/agent gets built out of https://github.com/jenkinsci/docker-agent . (The JNLP terminology is deprecated, because it is very misleading. You can use JNLP to launch an inbound agent using WebSocket transport; and you can start an inbound agent using the TCP protocol named JNLP4-Connect without using JNLP.)
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Renaming itself is completed. I am working on a blogpost and the SSH agents follow-up

          Show
          oleg_nenashev Oleg Nenashev added a comment - Renaming itself is completed. I am working on a blogpost and the SSH agents follow-up
          Show
          oleg_nenashev Oleg Nenashev added a comment - Blog:  https://www.jenkins.io/blog/2020/05/06/docker-agent-image-renaming/

            People

            • Assignee:
              oleg_nenashev Oleg Nenashev
              Reporter:
              oleg_nenashev Oleg Nenashev
            • Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: