Open jglick opened 2 years ago
Done, ci.jenkins.io and trusted.ci.jenkins.io updated as well
I have already forgotten what exactly this repository was called last week, but could it be confused with https://github.com/jenkinsci/docker-inbound-agent?
I have already forgotten what exactly this repository was called last week, but could it be confused with https://github.com/jenkinsci/docker-inbound-agent?
yep it could be confused. the only important is the other one « docker-inbound-agent ». I want to propose a jep to group « docker-agent », « docker-inbound-agent » (singular) and « docker-ssh-agent » into one repository « docker-agent » as they depend on each other (or should). It means less naming confusion.
however, wdyt renaming here something like « docker-inbound-collection » or « docker-agent-tools » as they are aimed at providing « tools » ?
(I would personnally vote to stop maintenance of this assets and archive it given the compatibility matrix that we have to keep. Providing a nice documentation showing a Dockerfile example - eventually a generator- would make more sense)
group … into one repository
That would make sense.
something like « docker-inbound-collection » or « docker-agent-tools »
Sure. No particular opinion as I have little knowledge of this repo or who relies on it.
I want to propose a jep to group « docker-agent », « docker-inbound-agent » (singular) and « docker-ssh-agent » into one repository « docker-agent » as they depend on each other (or should).
Related:
renaming here something like « docker-inbound-collection » or « docker-agent-tools » as they are aimed at providing « tools » ?
+1, I would propose "docker-inbound-examples".
(I would personnally vote to stop maintenance of this assets and archive it given the compatibility matrix that we have to keep. Providing a nice documentation showing a Dockerfile example - eventually a generator- would make more sense)
+100
Do not use the term JNLP. Do you mean inbound agent?