use alpinelinux/build-base:latest #3

sertonix commented 2023年12月03日 20:01:23 +01:00

I think alpinelinux/build-base:latest is the correct docker image for building alpine packages. alpinelinux/docker-abuild:latest seems to be intended for testing abuild itself (and seems pretty old).

If I understand the docker files correctly the use should already be buildozer

I more or less guessed the change in this pull request. I don't have access to any woodpecker CI instance to test it.

I think `alpinelinux/build-base:latest` is the correct docker image for building alpine packages. `alpinelinux/docker-abuild:latest` seems to be intended for testing abuild itself (and seems pretty old). If I understand the docker files correctly the use should already be `buildozer` I more or less guessed the change in this pull request. I don't have access to any woodpecker CI instance to test it.

Ghost commented 2023年12月06日 20:55:43 +01:00

Somewhere in the git history I used docker-abuild but there is nearly no documentation except for the dockerbuild file. But I would not use it, as it hasn't been updated for over 2 years. https://hub.docker.com/r/alpinelinux/docker-abuild

build-base seams to be the right one as it's frequently updated and there is more documentation. https://hub.docker.com/r/alpinelinux/build-base

Somewhere in the git history I used docker-abuild but there is nearly no documentation except for the dockerbuild file. But I would not use it, as it hasn't been updated for over 2 years. https://hub.docker.com/r/alpinelinux/docker-abuild build-base seams to be the right one as it's frequently updated and there is more documentation. https://hub.docker.com/r/alpinelinux/build-base

Ghost commented 2023年12月06日 21:34:20 +01:00

Also. buildozer is being used on actions. It works (see https://codeberg.org/librewolf/alpine/actions/runs/46) but for some reason woodpecker ci uses a different user and directory. Then I tried using gitlab ci to push the artifacts directly to gitlab. But the timelimit can not be changed and more than 3 hours are needed as their ci is slower than my machine. (See https://gitlab.com/librewolf-community/browser/alpine/-/jobs/5613514217) After all of that I had to pause for a bit.

The plan now is to build the package on woodpecker and push the artifacts "auto magically" to gitlab without their ci. But for that I need to read deep into both documentations and test how to integrate those two systems. (Maybe https://woodpecker-ci.org/docs/administration/forges/gitlab) And I didn't really wanted to do that after realizing in what kind of dependency hell I managed to get myself lost in. I will work an it again but for now I'll pause. If you have some idea to make everything more simple please let me know.

Also. buildozer is being used on actions. It works (see https://codeberg.org/librewolf/alpine/actions/runs/46) but for some reason woodpecker ci uses a different user and directory. Then I tried using gitlab ci to push the artifacts directly to gitlab. But the timelimit can not be changed and more than 3 hours are needed as their ci is slower than my machine. (See https://gitlab.com/librewolf-community/browser/alpine/-/jobs/5613514217) After all of that I had to pause for a bit. The plan now is to build the package on woodpecker and push the artifacts "auto magically" to gitlab without their ci. But for that I need to read deep into both documentations and test how to integrate those two systems. (Maybe https://woodpecker-ci.org/docs/administration/forges/gitlab) And I didn't really wanted to do that after realizing in what kind of dependency hell I managed to get myself lost in. I will work an it again but for now I'll pause. If you have some idea to make everything more simple please let me know.

Ghost commented 2023年12月12日 20:57:32 +01:00

Just yesterday I realized that I actually have the wrong image in the woodpecker ci. I now changed that.

Just yesterday I realized that I actually have the wrong image in the woodpecker ci. I now changed that.