Buildduty/day 1 checklist: Difference between revisions

Jump to navigation Jump to search
m
Update BuildDuty to CiDuty. Renaming project
(edit jumphost ssh config to digest more hosts using star globs)
m (Update BuildDuty to CiDuty. Renaming project)
Line 1: Line 1:
__TOC__
__TOC__


Welcome to Buildduty!  
Welcome to CiDuty!  


This page is meant to serve as a resource for new Buildduty people getting up to speed and ensuring they have access to the appropriate systems that they are expected to use.
This page is meant to serve as a resource for new CiDuty people getting up to speed and ensuring they have access to the appropriate systems that they are expected to use.


= Buildduty and the Manifesto =
= CiDuty and the Manifesto =


* Before you start it would be a good idea to make sure you know what Buildduty is all about. Please have a read through of [[ReleaseEngineering/Buildduty_manifesto|the manifesto]]
* Before you start it would be a good idea to make sure you know what CiDuty is all about. Please have a read through of [[ReleaseEngineering/Buildduty_manifesto|the manifesto]]


= Access =
= Access =
Line 25: Line 25:
=== SSH ===
=== SSH ===


Upload your public ssh key. It is a good idea to generate a separate ssh keypair from your personal one or any other that you have created in the past and use that explicitly for Buildduty and upload that. Follow this [[Security/Guidelines/OpenSSH#OpenSSH_client|SSH guidelines doc]] on how to generate, configure, and use your ssh key.
Upload your public ssh key. It is a good idea to generate a separate ssh keypair from your personal one or any other that you have created in the past and use that explicitly for CiDuty and upload that. Follow this [[Security/Guidelines/OpenSSH#OpenSSH_client|SSH guidelines doc]] on how to generate, configure, and use your ssh key.


note: example ssh config for accessing our systems given below in Jumphost section
note: example ssh config for accessing our systems given below in Jumphost section
Line 93: Line 93:
     ProxyJump rejh1.srv.releng.scl3.mozilla.com
     ProxyJump rejh1.srv.releng.scl3.mozilla.com
</source>
</source>
== Buildduty LDAP groups ==
== CiDuty LDAP groups ==


You may have access to the [https://ldapadmin1.private.scl3.mozilla.com/manage/ ldap admin page] and see your own groups that you have on your record. This page is behind vpn and auth0.
You may have access to the [https://ldapadmin1.private.scl3.mozilla.com/manage/ ldap admin page] and see your own groups that you have on your record. This page is behind vpn and auth0.


Although you can read your current groups, you will not be able to modify them. To extend with Buildduty groups that you need. You and your manager will need to file a ticket for them under "MOC: Service Requests"
Although you can read your current groups, you will not be able to modify them. To extend with CiDuty groups that you need. You and your manager will need to file a ticket for them under "MOC: Service Requests"


example ldap groups they may have by default:
example ldap groups they may have by default:
Line 179: Line 179:
Special [https://mana.mozilla.org/wiki/display/~gene@mozilla.com/How+to+get+Vidyo+working+on+Ubuntu+16.04+and+newer Ubuntu instructions] that may help
Special [https://mana.mozilla.org/wiki/display/~gene@mozilla.com/How+to+get+Vidyo+working+on+Ubuntu+16.04+and+newer Ubuntu instructions] that may help


TODO: create a Buildduty room
Add to your contact list the CiDuty room


== IRC ==
== IRC ==
Line 186: Line 186:


Useful channels
Useful channels
* #buildduty, #releng, #taskcluster, #developers, #mobile, #ateam, #moc
* #ci, #taskcluster, #developers, #mobile, #ateam, #moc


Protected channels
Protected channels
Line 239: Line 239:
= Secrets =
= Secrets =


Releng and Relops have a shared repo of secrets. Please reach out to jlund or another manager for instructions on how to access and ask to be add yourself as a recipient to every secret that the rest of the buildduty team (users/buildduty-fingerprints) has access to
Releng and Relops have a shared repo of secrets. Please reach out to jlund or another manager for instructions on how to access and ask to be add yourself as a recipient to every secret that the rest of the CiDuty team (users/buildduty-fingerprints) has access to


= Releng AWS account =
= Releng AWS account =


File a release engineering "general" ticket and needinfo jlund or another releng manager to create a user account and add you to the Buildduty group
File a release engineering "general" ticket and needinfo jlund or another releng manager to create a user account and add you to the CiDuty group


= Other Services =
= Other Services =
Confirmed users
67

edits

Navigation menu