Skip to content
This repository has been archived by the owner on Nov 20, 2019. It is now read-only.

Create automated setup process for new CI instances #186

Open
mmitche opened this issue Feb 19, 2016 · 0 comments
Open

Create automated setup process for new CI instances #186

mmitche opened this issue Feb 19, 2016 · 0 comments
Labels

Comments

@mmitche
Copy link
Member

mmitche commented Feb 19, 2016

We should create an automated process for new CI instances. Here are the general steps. Some of this is already available:

  1. Create a new VM in Azure with correct cloud services, endpoints, etc. Endpoint scripting is already available in dotnet-ci-internal repo (management\master)
  2. Add disks to the VM for Jenkins data.
  3. Use Chef or some other automated way to install Jenkins upon the creation and boot up of the VM.
  4. Automate modification of the Jenkins setup (location of data, startup options etc.)
  5. Automate installation of the standard set of plugins (this could be restored from a backup, it is copyable)
  6. Start Jenkins
  7. Automate startup of basic settings, including security, setup of the azure cloud. etc.

Alternatively, it may be that key config files and directories could simply by identified, tarred up from the main installation and applied. For instance, if I took everything from the Jenkins directory except for the jobs and fingerprints, I believe I would have a full installation. It would slightly be tied to the server name, but that could be customized by editing afterwards.

Anyways, the really critical stuff here is:

  • creds
  • plugins
  • main system config
@mmitche mmitche added the Pri-2 label Jun 23, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant