Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename repository #31

Open
jglick opened this issue Jun 10, 2022 · 5 comments
Open

Rename repository #31

jglick opened this issue Jun 10, 2022 · 5 comments

Comments

@jglick
Copy link
Member

jglick commented Jun 10, 2022

Do not use the term JNLP. Do you mean inbound agent?

@timja
Copy link
Member

timja commented Jun 12, 2022

Done, ci.jenkins.io and trusted.ci.jenkins.io updated as well

@timja timja closed this as completed Jun 12, 2022
@jglick
Copy link
Member Author

jglick commented Jun 13, 2022

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?

@dduportal
Copy link
Contributor

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)

@jglick
Copy link
Member Author

jglick commented Jun 13, 2022

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.

@timja timja reopened this Jun 13, 2022
@lemeurherveCB
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants