Skip to content

Latest commit

 

History

History
65 lines (51 loc) · 2.52 KB

manual_config.md

File metadata and controls

65 lines (51 loc) · 2.52 KB
Raw

Manual configuration

The following steps need to be done by hand.

Access control

  1. Follow the Role-Based Strategy guide.
  2. Create a developer role with all but the Agent and SCM options.
  3. Assign the role by adding a group called authenticated, selecting the developer checkbox.

Audit trail

  1. Click Manage Jenkins.
  2. Click Configure System.
  3. Under Audit Trail, click Add Logger, then Log file.
  4. For Log Location, enter /var/log/jenkins/audit.log.
  5. For Log File Size, enter 50 MB.
  6. For Log File Count, enter 10.
  7. Click Save.

Credentials

  1. Visit https://JENKINS_EXTERNAL_HOSTNAME/credentials/store/system/domain/_/newCredentials
  2. Fill in the form:
    1. Kind: SSH Username with private key
    2. Scope: Global (Jenkins, nodes, items, all child items, etc)
    3. Username: jenkins
    4. Private Key: From the Jenkins master ~/.ssh
    5. Passphrase: the value from vault_jenkins_ssh_key_passphrase
    6. ID: jenkins-ssh-key
    7. Description: (empty)
  3. Click OK.
  4. Use these Credentials from your Jobs.

Adding users

For each user:

  1. Generate a password. Here's an easy way on Linux:

    cat /dev/urandom | LC_ALL=C tr -dc 'a-zA-Z0-9!@#\$%^&\*\(\)\+=_' | head -c 64

  2. View the people list.

    1. Click Manage Jenkins.
    2. Click Manage Users.
    3. If they exist already:
      1. Click their username.
      2. Click Configure.
      3. Correct their Full Name.
      4. Set their password.
    4. If they don't, create a user for them.
      1. Click Create User.
      2. For the Username, use the first part of their GSA email. This will ensure that it matches up to their commits.

  3. Send the password via Fugacious.

Other