change "course" to "enablement"
| | |
|---|
| | | # Red Hat Open Innovation Labs Enablement Materials |
|---|
| | | This repo will house all the slides and lab exercises for the Enablement course. It will also be used to track issues, features and new additions to the course. |
|---|
| | | This repo will house all the slides and lab exercises for the Enablement. It will also be used to track issues, features and new additions to the Enablement. |
|---|
| | | |
|---|
| | | [Course Content](https://rht-labs.github.io/enablement-docs/#/) |
|---|
| | | |
|---|
| | |
|---|
| | | > _In this exercise we will link GitLab to Jenkins so that new build jobs are triggered on each push to the `develop` branch._ |
|---|
| | | |
|---|
| | | <p class="tip" > |
|---|
| | | NOTE - This section is optional! Git webhooks are useful but not needed for course completion. |
|---|
| | | NOTE - This section is optional! Git webhooks are useful but not needed for Enablement completion. |
|---|
| | | </p> |
|---|
| | | |
|---|
| | | 7. In order to allow GitLab trigger Jenkins (because of the OpenShift Auth Plugin), we need to allow the `Anonymous` user trigger builds. Head to your Jenkins Dashboard and click on `Manage Jenkins` on the left hand side. Then scroll down and click `Configure Global Security`. Alternatively, type in `https://jenkins-<YOUR_NAME>-ci-cd.apps.some.domain.com/configureSecurity/` . You should see a screen like so: |
|---|
| | |
|---|
| | | * LOTS of wall space (more than you could think.... we may need to supplement with "portable wall" boards) |
|---|
| | | * Projector that supports HDMI |
|---|
| | | * Ability to play sound from laptop |
|---|
| | | * Strong WiFi (all delegates will need to be connected throughout the course) |
|---|
| | | * Strong WiFi (all delegates will need to be connected throughout the Enablement) |
|---|
| | | * At least one break out area - ideally a small room near the main room |
|---|
| | | |
|---|
| | | |
|---|
