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

Should we have a 'test' jenkins server for experiments? #3027

Open
sxa opened this issue Apr 13, 2023 · 0 comments
Open

Should we have a 'test' jenkins server for experiments? #3027

sxa opened this issue Apr 13, 2023 · 0 comments

Comments

@sxa
Copy link
Member

sxa commented Apr 13, 2023

I need to request a new machine:

  • New machine operating system (e.g. linux/windows/macos/solaris/aix): Probably linux
  • New machine architecture (e.g. x64/aarch32/arm32/ppc64/ppc64le/sparc): Doesn't matter
  • Provider (leave blank if it does not matter):
  • Desired usage: Test jenkins server
  • Any unusual specification/setup required: jenkins :-)
  • How many of them are required: 1

Please explain what this machine is needed for:

  • Initially proposed in Secure the public Jenkins server #2108 it would be useful to have a second server for people to experiment with before deploying to our production one. This may also allow us to restrict the access controls on the production server a bit more.

We would need to give careful consideration to:

  • How many of the jobs are "live" on the test server (We would probably not want them triggering full build pipelines every day)
  • Which nodes to attach to them (We don't want it to conflict with the production server)
  • Which secrets will be available to jobs running on the server
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

1 participant