Skip to content

Commit c5150fa

Browse files
update images path for woodpecker blog (#165)
Signed-off-by: prashant-gurung899 <prasantgrg777@gmail.com>
1 parent 0b18d0b commit c5150fa

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

src/assets/woodpeckerCI/woodpeckerCI.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ authorAvatar: https://avatars.githubusercontent.com/u/53248463?v=4
55
authorLink: https://github.com/prashant-gurung899
66
createdAt: September 11, 2025
77
tags: CI/CD, Woodpecker, starlark, docker-compose, Traefik, WCCS
8-
banner: https://raw.githubusercontent.com/JankariTech/blog/woodpecker-ci-starlark/src/assets/woodpeckerCI/images/cover.png
8+
banner: https://blog.jankaritech.com/src/assets/woodpeckerCI/images/cover.png
99
---
1010

1111
## Background
@@ -151,15 +151,15 @@ To connect GitHub with Woodpecker:
151151
152152
2. In your GitHub OAuth App, set the authorization callback URL to `https://<your-ci-server>/authorize`
153153

154-
![Callback URL](https://raw.githubusercontent.com/JankariTech/blog/woodpecker-ci-starlark/src/assets/woodpeckerCI/images/oauth.png)
154+
![Callback URL](/src/assets/woodpeckerCI/images/oauth.png)
155155

156156
3. Copy the generated Client ID and Secret.
157157

158158
4. Use these values in the `WOODPECKER_GITHUB_CLIENT` and `WOODPECKER_GITHUB_SECRET` env vars.
159159

160160
After that, you can log into the Woodpecker web UI using your GitHub account.
161161

162-
![GitHub Login](https://raw.githubusercontent.com/JankariTech/blog/woodpecker-ci-starlark/src/assets/woodpeckerCI/images/github.png)
162+
![GitHub Login](/src/assets/woodpeckerCI/images/github.png)
163163

164164
## Enabling a Repository
165165
Before enabling a repo in the Woodpecker CI server, make sure to have a GitHub repository ready. You can use an existing repo of your own or create a new empty one. We will be making a pull request to the repo to trigger CI later.
@@ -168,11 +168,11 @@ From the Woodpecker UI:
168168

169169
- Click on Add Repository.
170170

171-
![Add Repo](https://raw.githubusercontent.com/JankariTech/blog/woodpecker-ci-starlark/src/assets/woodpeckerCI/images/add.png)
171+
![Add Repo](/src/assets/woodpeckerCI/images/add.png)
172172

173173
- Enable it. For this blog, I am using an existing repo called `Drum-KIT` which has already been enabled (as you can see in the last row of the image below).
174174

175-
![Enable Repo](https://raw.githubusercontent.com/JankariTech/blog/woodpecker-ci-starlark/src/assets/woodpeckerCI/images/enable.png)
175+
![Enable Repo](/src/assets/woodpeckerCI/images/enable.png)
176176

177177
Woodpecker will automatically add the necessary webhooks to the repo.
178178

@@ -199,7 +199,7 @@ steps:
199199
Now that you have your `.woodpecker.yaml` file ready, you can commit and push it to your enabled GitHub repository and then, open a Pull Request from your branch <your-branch-name> to `master/main` according to you repo. GitHub's default branch is set to `main`.
200200
Once the PR is created, Woodpecker will automatically fetch the pipeline configuration, and start your first CI run. You can then head over to the Woodpecker UI to watch the build logs in real time.
201201

202-
![Yaml Pipleine](https://raw.githubusercontent.com/JankariTech/blog/woodpecker-ci-starlark/src/assets/woodpeckerCI/images/yaml.png)
202+
![Yaml Pipleine](/src/assets/woodpeckerCI/images/yaml.png)
203203

204204
Now that we have already set up the woodpecker server and triggered pipelines using the traditional `.yaml` configuration, let's now integrate WCCS to unlock flexibility and define our pipelines in Starlark.
205205

@@ -262,11 +262,11 @@ After conneting WCCS with the woodpecker server, there's one more thing that you
262262

263263
- From the settings of your Woodpecker server, go to `Repositories` and click on the enabled repo's settings icon as shown below:
264264

265-
![Settings](https://raw.githubusercontent.com/JankariTech/blog/woodpecker-ci-starlark/src/assets/woodpeckerCI/images/settings.png)
265+
![Settings](/src/assets/woodpeckerCI/images/settings.png)
266266

267267
- Then, add `.woodpecker.star` as pipeline config path and save it:
268268

269-
![Pipeline Config](https://raw.githubusercontent.com/JankariTech/blog/woodpecker-ci-starlark/src/assets/woodpeckerCI/images/path.png)
269+
![Pipeline Config](/src/assets/woodpeckerCI/images/path.png)
270270

271271
## Add a Simple Starlark Pipeline
272272
Here's a simple starlark pipeline configuration example that you can add in your project.
@@ -296,9 +296,9 @@ def main(ctx):
296296
Now that you have your `.woodpecker.star` file ready, commit and push it to your GitHub repository and then, open a new Pull Request from your branch <your-branch-name> to master/main.
297297
Once the PR is created, Woodpecker will automatically send a build request to WCCS, fetch the pipeline configuration, and start your first CI run. You can then head over to the Woodpecker UI to watch the build logs in real time.
298298

299-
![Converted Yaml](https://raw.githubusercontent.com/JankariTech/blog/woodpecker-ci-starlark/src/assets/woodpeckerCI/images/converted.png)
299+
![Converted Yaml](/src/assets/woodpeckerCI/images/converted.png)
300300

301-
![CI build](https://raw.githubusercontent.com/JankariTech/blog/woodpecker-ci-starlark/src/assets/woodpeckerCI/images/CI.png)
301+
![CI build](/src/assets/woodpeckerCI/images/CI.png)
302302

303303

304304
## Conclusion

0 commit comments

Comments
 (0)