finished vieter-0.3.0
ci/woodpecker/push/woodpecker Pipeline was successful Details

dev
Jef Roosens 2022-06-13 21:27:00 +02:00
parent 71ad9d2f18
commit e186363a07
Signed by: Jef Roosens
GPG Key ID: B75D4F293C7052DB
1 changed files with 32 additions and 4 deletions

View File

@ -1,13 +1,16 @@
--- ---
title: "Announcing Vieter 0.3.0" title: "Announcing Vieter 0.3.0"
date: 2022-06-03 date: 2022-06-13
draft: true
--- ---
When this post is live, Vieter 0.3.0 will have been released! This release When this post is live, Vieter 0.3.0 will have been released! This release
really does come with a lot of new features, including more reliable builds and really does come with a lot of new features, including more reliable builds and
a new cron implementation! a new cron implementation!
This release ended up taking me over two months, but I'm quite proud of it :)
It not only adds a lot of useful features, but also paves the way for a lot
more cool features down the road!
## What is Vieter? ## What is Vieter?
Vieter consists of two independents parts, namely an implementation of an Arch Vieter consists of two independents parts, namely an implementation of an Arch
@ -16,6 +19,9 @@ to remove the need for an AUR helper & move all builds to a remote server. Not
only does this greatly reduce update times on lower-end systems, it also only does this greatly reduce update times on lower-end systems, it also
prevents AUR packages from being built multiple times on different systems. prevents AUR packages from being built multiple times on different systems.
The repository can also be used independently, providing a convenient server
for publishing Arch packages from CI builds for example.
While I specifically mention Arch & the AUR, Vieter is compatible with any While I specifically mention Arch & the AUR, Vieter is compatible with any
Pacman-based distro & can build PKGBUILDs provided from any Git source. Pacman-based distro & can build PKGBUILDs provided from any Git source.
@ -36,6 +42,28 @@ more regularly than all the rest.
Often, a build would fail with exit code 8. This error indicates that makepkg Often, a build would fail with exit code 8. This error indicates that makepkg
wasn't able to install all dependencies, caused by the builder image not being wasn't able to install all dependencies, caused by the builder image not being
up to date enough. Due to this, each build now runs `pacman -Syu` before running the actual build. up to date enough. Due to this, each build now runs `pacman -Syu` before
running the actual build.
Another useful additions to builds is that packages from the target repository are now Builds can now also use dependencies that are part of the target repository.
This allows building packages with AUR dependencies, as long as all
dependencies are also being built for said repository.
### Build logs
The main server now stores the logs of each build, including the exit code.
This makes it a lot easier to debug why builds fail.
### Improved documentation
The [Vieter documentation](https://rustybever.be/docs/vieter/) has had a pretty
major re-write to get it up to date with this new release. Now there's also
[HTTP API docs](https://rustybever.be/docs/vieter/api/#introduction) & [man
pages](https://rustybever.be/man/vieter/vieter.1.html).
## Interested?
If you're interested in Vieter, considering joining
[#vieter:rustybever.be](https://matrix.to/#/#vieter:rustybever.be) on Matrix!
The source code can be found on my personal
[Gitea](https://git.rustybever.be/vieter/vieter).