Skip to content

Commit 2e18bde

Browse files
update images path for woodpecker blog
Signed-off-by: prashant-gurung899 <prasantgrg777@gmail.com>
1 parent 0b18d0b commit 2e18bde

File tree

1 file changed

+11
-10
lines changed

1 file changed

+11
-10
lines changed

src/assets/woodpeckerCI/woodpeckerCI.md

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,8 @@ 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://raw.githubusercontent.com/JankariTech/blog/woodpecker-ci-starlark/src/assets/woodpeckerCI/images/cover.png
9+
banner: https://blog.jankaritech.com/src/assets/woodpeckerCI/images/cover.png
910
---
1011

1112
## Background
@@ -151,15 +152,15 @@ To connect GitHub with Woodpecker:
151152
152153
2. In your GitHub OAuth App, set the authorization callback URL to `https://<your-ci-server>/authorize`
153154

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

156157
3. Copy the generated Client ID and Secret.
157158

158159
4. Use these values in the `WOODPECKER_GITHUB_CLIENT` and `WOODPECKER_GITHUB_SECRET` env vars.
159160

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

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

164165
## Enabling a Repository
165166
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 +169,11 @@ From the Woodpecker UI:
168169

169170
- Click on Add Repository.
170171

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

173174
- 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).
174175

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

177178
Woodpecker will automatically add the necessary webhooks to the repo.
178179

@@ -199,7 +200,7 @@ steps:
199200
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`.
200201
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.
201202

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

204205
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.
205206

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

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

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

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

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

271272
## Add a Simple Starlark Pipeline
272273
Here's a simple starlark pipeline configuration example that you can add in your project.
@@ -296,9 +297,9 @@ def main(ctx):
296297
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.
297298
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.
298299

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

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

303304

304305
## Conclusion

0 commit comments

Comments
 (0)