Developer On-/Offboarding

First of all, we'll create a ticket for setting up the new developer's access.

Steps to be covered (add to ticket description).

1. Access to Git repositories:
   • Default repo: kieker.git
   • Developer must attach public SSH key (learn more) to ticket
2. LDAP user(name):
   • For CAU students: e-mail short name
   • Others: firstname.<middlename.>lastname
   • further required information:
     
     • email:
     • duration: e.g. end of SS 14
     • function: e.g. student assistant
     • advisor/contact person: e.g. avh
     • project: e.g. kieker
3. Access to Confluence and Jira
4. Access to Jenkins:
   • LDAP account required
   • Default jobs:
     1.  kieker
     2.  kieker-nightly-release
   • Default job permissions: read, build, workspace
5. Add to public mailing lists?
6. Add to internal mailing list

Change settings (to be completed)

1. Password change:  https://build.se.informatik.uni-kiel.de/LdapPasswd/

Password change will have an effect on Trac and Jenkins

1. ...

Workflow for Removing Access from Kieker Infrastructure for Developers Leaving the Project

Steps to be covered.

1. Remove GitLab access and remove account if necessary
2. Access to Trac:
   • Remove from permission group: 'basic'
   • Remove from Trac database
3. Access to Jenkins:
   • Remove job permissions:
     1.  kieker
     2.  kieker-nightly-release
4. Re- or unassign tickets assigned to the account
5. Remove the account from the CC of non-closed tickets.
6. Remove from public mailing lists? if the developer wants this
7. Remove from internal mailing list if the developer wants this