actions/importer-labs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update valet-configure-lab.md

Browse Source
This commit is contained in:
Begona Guereca
2022-08-10 16:46:49 -07:00
committed by GitHub
parent e85034408a
commit 31c0776986
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
jenkins/valet-configure-lab.md
+7 -3
View File
@@ -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`. - Under the `API token` section, click `Add new Token`.
- Add a defaualt name to your token, then click `Generate`. - Add a defaualt name to your token, then click `Generate`.
- Copy the token that was generated and record token for a later step. - Copy the token that was generated and record token for a later step.
![configure-result](https://user-images.githubusercontent.com/19557880/184041667-d06cb7f2-a885-474e-b728-7567314aeaf3.png)
2. Create a GitHub personal access token (PAT). 2. Create a GitHub personal access token (PAT).
- Navigate to your GitHub `Settings` - click your profile photo and then click `Settings`. - Navigate to your GitHub `Settings` - click your profile photo and then click `Settings`.
- Go to `Developer 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 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. - 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: 4. If all went well you should see a similar output in your terminal:
![configure-result](https://user-images.githubusercontent.com/18723510/183990474-d0b2559c-d2bf-40d9-ac43-19af53e45329.png) ![configure-result](https://user-images.githubusercontent.com/19557880/184041328-ce54ea22-b0cd-4c84-b02c-10ad7b09ad89.png)
## Verify Valet Works ## 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. 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.
![configure-dry-run](https://user-images.githubusercontent.com/18723510/183989794-d51fa29d-b4c0-4074-8402-a55ffcea3a6b.png) ![configure-dry-run](https://user-images.githubusercontent.com/19557880/184041510-018d7a17-9966-4a0f-af3f-4092dfb90ac0.png)
### Next Lab ### Next Lab
# TODO TODO