Context

The purpose of this document is to instruct users/sponsors on how to grant access to our gred-ecdi GitHub organization, hosted on Roche’s GitHub Enterprise instance. For those of you familiar with the GitLab workflow - whereby users just logged in with SSO credentials and were provisioned in GitLab - this is a bit different due to the fact that, unlike GitLab, this is an enterprise solution with seat licenses. Don’t fret, though. There is a solution; it just requires one or two manual steps, which I’ll explain below.

Checking Access

Before getting into instructions for users who don’t have access, it’s important to confirm whether you have access. An unfortunate quirk with GitHub Enterprise is that unauthenticated users who click direct repo links with often get 404 responses rather than getting redirected to a login page where they can authenticate. Before you assume you don’t have access, you can click this Roche-EMU GitHub Enterprise link and try logging in with your UNIX ID and password. For some, this will yield a successful login, at which point you need to select the gRED ECDi organization or go back and retry the repo link, which should work.

If this does not work for you, please go to the section below that applies to your use case.

ECDi Members

For those users who are members of ECDi, you should have first-class access based on your affiliation with one of our ECDi GitHub groups.

If you’ve been around for a while and don’t have access, please get in touch with @Murali Movva in our #ecdi-ace-infra-support channel and request an addition to the appropriate ECDi groups.

If you’re new to ECDi and don’t have access, this is an indication of a problem with our CIDM workflow, a process that is designed to ensure that new users get automatically added to all requisite groups as part of new user onboarding. Please contact @Murali Movva in our #ecdi-ace-infra-support channel to:

1. request addition to the appropriate ECDi groups.
2. Let him know that CIDM failed you.

Once you’ve been added to the requisite groups, you’ll need to wait a maximum of 40 minutes for the group information to sync with GitHub. At that point, you can retry access by visiting the Roche-EMU GitHub Enterprise homepage and logging in with your UNIX ID and password. Once you’ve successfully logged in, you should be able to access any of our internal repositories.

Non-ECDi Members

For those users who are outside of ECDi and who don’t already have access to one of the many other orgs hosted on Roche’s GitHub Enterprise Instance (Roche-EMU), you can still get ReadOnly access to all of the internal gred-ecdi repositories by following these instructions:

1. Visit the GLOAZUGHAdmin_ReadOnly self-registration page. Please note that this is only accessible from the office or over the enterprise VPN.
2. Log in with your UNIX ID and password.
3. Click the subscribe button to register yourself with the GitHub ReadOnly user group.

After you complete these steps, you’ll need to wait a maximum of 40 minutes for the group information to sync with GitHub. At that point, you can retry access by visiting the Roche-EMU GitHub Enterprise homepage and logging in with your UNIX ID and password. Once you’ve successfully logged in you should be able to access any of our internal repositories.

More Information

Once you have access to GitHub please visit our Gitlab to GitHub Migration Wiki page for more information.