-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Instead of having exercises in their own separate section, they are now part of the main topics sections. This should make the learning process easier to follow where users have both exercises and questions in the same place. In addition, added a couple of new questions & exercises and modified existing scripts accordingly.
- Loading branch information
abregman
committed
Jul 11, 2021
1 parent
dfbe979
commit e54648d
Showing
12 changed files
with
216 additions
and
81 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
## Git Commit 01 | ||
|
||
### Objective | ||
|
||
Learn how to work with Git Branches | ||
|
||
### Instructions | ||
|
||
1. Pick up a Git repository (or create a new one) with at least one commit | ||
2. Create a new branch called "dev" | ||
3. Modify one of the files in the repository | ||
4. Create a new commit | ||
5. Verify the commit you created is only in "dev" branch | ||
|
||
### After you complete the exercise | ||
|
||
Answer the following: | ||
|
||
1. Why branches are useful? Give an example of one real-world scenario for using branches |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
## Git Commit 01 | ||
|
||
### Objective | ||
|
||
Learn how to commit changes in Git repositories | ||
|
||
### Instructions | ||
|
||
1. Create a new directory | ||
2. Make it a git repository | ||
3. Create a new file called `file` with the content "hello commit" | ||
4. Commit your new file | ||
5. Run a git command to verify your commit was recorded | ||
|
||
### After you complete the exercise | ||
|
||
Answer the following: | ||
|
||
* What are the benefits of commits? | ||
* Is there another way to verify a commit was created? |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
## Branch 01 - Solution | ||
|
||
``` | ||
cd some_repository | ||
echo "master branch" > file1 | ||
git add file1 | ||
git commit -a -m "added file1" | ||
git checkout -b dev | ||
echo "dev branch" > file2 | ||
git add file2 | ||
git commit -a -m "added file2" | ||
``` | ||
|
||
Verify: | ||
|
||
``` | ||
git log (you should see two commits) | ||
git checkout master | ||
git log (you should see one commit) | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
## Git Commit 01 - Solution | ||
|
||
``` | ||
mkdir my_repo && cd my_repo | ||
git init | ||
echo "hello_commit" > file | ||
git add file | ||
git commit -a -m "It's my first commit. Exciting!" | ||
git log | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
### Jenkins - Remove Jobs | ||
|
||
#### Objective | ||
|
||
Learn how to write a Jenkins script that interacts with builds by removing builds older than X days. | ||
|
||
#### Instructions | ||
|
||
1. Pick up (or create) a job which has builds older than X days | ||
2. Write a script to remove only the builds that are older than X days | ||
|
||
#### Hints | ||
|
||
X can be anything. For example, remove builds that are older than 3 days. Just make sure that you don't simply remove all the builds (since that's different from the objective). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
### Jenkins - Remove Jobs | ||
|
||
#### Objective | ||
|
||
Learn how to write a Jenkins script to remove Jenkins jobs | ||
|
||
#### Instructions | ||
|
||
1. Create three jobs called: test-job, test2-job and prod-job | ||
2. Write a script to remove all the jobs that include the string "test" |
File renamed without changes.
2 changes: 1 addition & 1 deletion
2
...s/jenkins/scripts/jobs_with_string.groovy → ...ins/solutions/remove_jobs_solution.groovy
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters