Skip to content

Commit 23ee181

Browse files
authored
Update repository path (#27)
1 parent e834acc commit 23ee181

34 files changed

+70
-70
lines changed

.github/workflows/parallel-robot-pipeline.yml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@ on:
44
branches:
55
- main
66
paths:
7-
- docs/examples/jenkins/parallel-robot-pipeline/**
7+
- docs/tutorials/jenkins/parallel-robot-pipeline/**
88
- .github/workflows/parallel-robot-pipeline.yml
99
pull_request:
1010
branches:
1111
- main
1212
paths:
13-
- docs/examples/jenkins/parallel-robot-pipeline/**
13+
- docs/tutorials/jenkins/parallel-robot-pipeline/**
1414
- .github/workflows/parallel-robot-pipeline.yml
1515

1616
jobs:
@@ -21,13 +21,13 @@ jobs:
2121
- name: Checkout
2222
uses: actions/checkout@v3
2323
- name: Build container image
24-
working-directory: docs/examples/jenkins/parallel-robot-pipeline/
24+
working-directory: docs/tutorials/jenkins/parallel-robot-pipeline/
2525
run: |
2626
docker build . --tag rf-screenshot
2727
- name: Test container image
2828
run: |
2929
for browser in chromium firefox; do
30-
docker run --rm -v $(pwd)/robot_output:/out -e BROWSER=$browser rf-screenshot -d /out -l none -r none -o $browser.xml -N $browser -v URL:https://kangasta.github.io/cicd-examples/
30+
docker run --rm -v $(pwd)/robot_output:/out -e BROWSER=$browser rf-screenshot -d /out -l none -r none -o $browser.xml -N $browser -v URL:https://cicd-tutorials.github.io/cicd-tutorials.net/
3131
done
3232
- name: Store logs
3333
if: always()
@@ -45,13 +45,13 @@ jobs:
4545
password: ${{ secrets.GITHUB_TOKEN }}
4646
- name: Push container image to GitHub Container Registry
4747
if: github.ref == 'refs/heads/main'
48-
working-directory: docs/examples/jenkins/parallel-robot-pipeline/
48+
working-directory: docs/tutorials/jenkins/parallel-robot-pipeline/
4949
run: |
5050
docker build . --target base -t base
5151
5252
for tag in ${{ github.run_number }} latest; do
53-
docker tag base ghcr.io/kangasta/robot-browser:$tag
54-
docker push ghcr.io/kangasta/robot-browser:$tag
53+
docker tag base ghcr.io/cicd-tutorials/robot-browser:$tag
54+
docker push ghcr.io/cicd-tutorials/robot-browser:$tag
5555
done
5656
process-logs:
5757
name: Process logs

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
# CI/CD Examples
1+
# CI/CD Tutorials
22

3-
Examples on how to develop CI/CD pipelines and how to configure development environment for working with CI/CD pipelines.
3+
Tutorials on how to develop CI/CD pipelines and how to configure development environment for working with CI/CD pipelines.
44

55
## Developing
66

@@ -18,5 +18,5 @@ mkdocs serve
1818

1919
## License
2020

21-
CI/CD Examples is licensed under
21+
CI/CD Tutorials is licensed under
2222
<a href="https://creativecommons.org/licenses/by-sa/4.0/" target="_blank" rel="license noopener noreferrer">CC BY-SA 4.0</a>

docs/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
# CI/CD Pipeline and Tooling Examples
1+
# CI/CD Pipeline and Tooling Tutorials
22

3-
This website contains examples on how to develop CI/CD pipelines and how to configure a development environment for working with CI/CD pipelines.
3+
This website contains tutorials on how to develop CI/CD pipelines and how to configure a development environment for working with CI/CD pipelines.
44

55
## What are CI/CD pipelines?
66

@@ -24,8 +24,8 @@ The CI and CD pipelines are often tightly integrated with each other. Delivery i
2424

2525
## Installing Docker
2626

27-
Many of the examples provided on this website require Docker and Docker Compose to be installed on your development environment.
27+
Many of the tutorials provided on this website require Docker and Docker Compose to be installed on your development environment.
2828

2929
See [Get Docker](https://docs.docker.com/get-docker/) for official installation instructions. If you use Docker a lot on a Mac or Windows system, the recommended Docker Desktop is likely a good option for you. Note that, since January 2022, it has required paid subscription, if used for commercial development.
3030

31-
Alternatively, Windows users can [install Docker on top of WSL2](./docker/docker-on-wsl/). For Mac users there are alternatives, such as [Colima](https://github.com/abiosoft/colima), available.
31+
Alternatively, Windows users can [install Docker on top of WSL2](./tutorials/docker/docker-on-wsl/). For Mac users there are alternatives, such as [Colima](https://github.com/abiosoft/colima), available.
File renamed without changes.

docs/examples/gitlab-ci/docker-hub-ratelimit/README.md renamed to docs/tutorials/gitlab-ci/docker-hub-ratelimit/README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ description: Tutorial on how to test if Docker-in-Docker service in GitLab CI ac
66

77
The recommended way of running Docker commands in a GitLab CI Kubernets runner is to use a service to run Docker-in-Docker container (`docker:dind`). By default the `docker:dind` container pulls container images from Docker Hub without caching. This can cause problems as pulls from Docker Hub are rate-limited.
88

9-
This example tests how `docker pull ubuntu:24.04` commands consume Docker Hub ratelimit and provides example on how to configure pull-through cache to an Kubernetes cluster working as a GitLab runner.
9+
This tutorial tests how `docker pull ubuntu:24.04` commands consume Docker Hub ratelimit and provides example on how to configure pull-through cache to an Kubernetes cluster working as a GitLab runner.
1010

1111
## How to check if `docker pull` commands are cached
1212

@@ -15,13 +15,13 @@ Create a new GitLab project with `.gitlab-ci.yml` and `scripts/check-docker-hub-
1515
The `scripts/check-docker-hub-ratelimit.sh` script prints current Docker Hub ratelimit and also writes the result to a file if filename is given as first parameter. See [Docker Hub usage and rate limits](https://docs.docker.com/docker-hub/download-rate-limit/#how-can-i-check-my-current-rate) article in Docker documentation for more details.
1616

1717
```yaml title="scripts/check-docker-hub-ratelimit.sh"
18-
---8<--- "docs/examples/gitlab-ci/docker-hub-ratelimit/scripts/check-docker-hub-ratelimit.sh"
18+
---8<--- "docs/tutorials/gitlab-ci/docker-hub-ratelimit/scripts/check-docker-hub-ratelimit.sh"
1919
```
2020

2121
The pipeline defined by `.gitlab-ci.yml` tries to pull the same Docker image twice and checks if the rate limit headers are different after first and second pull.
2222

2323
```yaml title=".gitlab-ci.yml"
24-
---8<--- "docs/examples/gitlab-ci/docker-hub-ratelimit/.gitlab-ci.yml"
24+
---8<--- "docs/tutorials/gitlab-ci/docker-hub-ratelimit/.gitlab-ci.yml"
2525
```
2626

2727
The pipeline should fail, if images are pulled directly from Docker Hub.
@@ -31,8 +31,8 @@ The pipeline should fail, if images are pulled directly from Docker Hub.
3131
Manifests for configuring pull-through cache and configmap are available in the repository that provides this website.
3232

3333
```sh
34-
git clone https://github.com/kangasta/cicd-examples.git
35-
cd docs/examples/gitlab-ci/docker-hub-ratelimit
34+
git clone https://github.com/cicd-tutorials/cicd-tutorials.net.git
35+
cd docs/tutorials/gitlab-ci/docker-hub-ratelimit
3636
```
3737

3838
Configure pull-through cache and configmap for GitLab runner by running `kubectl apply -f manifests/`.

0 commit comments

Comments
 (0)