Merge branch 'jenkins-configure' of github.com:valet-customers/labs into jenkins-configure
This commit is contained in:
@@ -23,6 +23,9 @@ In this lab, you will use the Valet `configure` command to set up the required i
|
||||
- Under the `API token` section, click `Add new Token`.
|
||||
- Add a defaualt name to your token, then click `Generate`.
|
||||
- Copy the token that was generated and record token for a later step.
|
||||
|
||||

|
||||
|
||||
2. Create a GitHub personal access token (PAT).
|
||||
- Navigate to your GitHub `Settings` - click your profile photo and then click `Settings`.
|
||||
- Go to `Developer Settings`
|
||||
@@ -44,7 +47,7 @@ In this lab, you will use the Valet `configure` command to set up the required i
|
||||
- At the Jenkins url prompt enter `http://localhost:8080/` and press enter.
|
||||
- At the Personal access token to fetch source code in GitHub prompt, if any of your Jenkins pipelines have source code in a GitHub repository enter the GitHub PAT that would have acess to these files.
|
||||
4. If all went well you should see a similar output in your terminal:
|
||||

|
||||

|
||||
|
||||
## Verify Valet Works
|
||||
|
||||
@@ -68,8 +71,9 @@ To verify Valet works we are going to run a `update` and `dry-run` command. We
|
||||
```
|
||||
|
||||
4. In the terminal you should see the command was successful, if not it is a good time to practice the configure command again and make sure the access tokens values are correct and were generated with the correct permissions.
|
||||

|
||||

|
||||
|
||||
|
||||
### Next Lab
|
||||
|
||||
# TODO
|
||||
TODO
|
||||
|
||||
Reference in New Issue
Block a user