[CI] test_env broken #316

New Issue

dachary · 2023-02-04T15:43:24Z

dachary commented

2023-02-04 15:43:24 +00:00

https://gitea.com/gitea/test-env was upgraded two days ago and breaks the Forgejo builds. The container image could not be pinned because only the latest version is published, the previous ones are discarded.

create forgejo/test_env as a fork of https://gitea.com/gitea/test-env
add .woodpecker.yml to publish test_env container images in https://codeberg.org/forgejo-experimental
modify the forgejo pipelines to use those container images instead of the one published by Gitea

https://gitea.com/gitea/test-env was upgraded two days ago and breaks the Forgejo builds. The container image could not be pinned because only the latest version is published, the previous ones are discarded. - [x] create `forgejo/test_env` as a fork of https://gitea.com/gitea/test-env - [x] add .woodpecker.yml to publish test_env container images in https://codeberg.org/forgejo-experimental - [x] modify the forgejo pipelines to use those container images instead of the one published by Gitea

dachary added the

bug

forgejo/ci

labels 2023-02-04 15:43:24 +00:00

dachary self-assigned this 2023-02-04 15:43:25 +00:00

dachary commented

2023-02-04 15:53:59 +00:00

Poster

To keep the CI working while this is being fixed, the Woodpecker host was reset with an older image docker tag sha256:33777b3348bed8dc6073215bef9120b88bb70e46aea50b7f395720294687c718 gitea/test_env:linux-amd64

It won't prune the images and the CI was made to not always pull. This is a hack and this fix must be completed sooner rather than later or it will break again.

To keep the CI working while this is being fixed, the Woodpecker host was reset with an older image `docker tag sha256:33777b3348bed8dc6073215bef9120b88bb70e46aea50b7f395720294687c718 gitea/test_env:linux-amd64` It won't prune the images and the CI was made to not always pull. This is a hack and this fix must be completed sooner rather than later or it will break again.

dachary commented

2023-02-04 16:25:10 +00:00

Poster

docker tag sha256:dd6560ae0a65 gitea/test_env:linux-amd64 is better (7 weeks ago).

`docker tag sha256:dd6560ae0a65 gitea/test_env:linux-amd64` is better (7 weeks ago).

crystal commented

2023-02-04 20:28:39 +00:00

fwiw I was able to get it working fine with the new test_env image without making any major changes, see 9ca75fac38

fwiw I was able to get it working fine with the new test_env image without making any major changes, see https://codeberg.org/crystal/forgejo/commit/9ca75fac38c4d651ae056d1a430f5a30a10bc522

👍 1

dachary commented

2023-02-04 21:27:41 +00:00

Poster

@crystal rebased on top of Gitea is on progress and is going fine as well.

#51 (comment)

@crystal rebased on top of Gitea is on progress and is going fine as well. https://codeberg.org/forgejo/forgejo/issues/51#issuecomment-791580

👍 1

dachary closed this issue

2023-02-04 21:28:06 +00:00

dachary reopened this issue

2023-02-04 22:28:00 +00:00

dachary commented

2023-02-04 22:29:46 +00:00

Poster

At the moment test_env works on the main branch but fails with v1.18. If used with no change it will use lots of RAM and either abort or exceed the resources allocated to the CI. If the lint version is bumped to 1.51.0 it will fail because the branch does not comply.

dachary commented

2023-02-04 22:31:56 +00:00

Poster

https://codeberg.org/forgejo/test-env is where the work to version the container images happens.

crystal commented

2023-02-04 22:39:54 +00:00

the commit I linked earlier fixes the release branch :)

dachary referenced this issue from a commit

2023-02-04 23:36:16 +00:00

[CI] use codeberg.org/forgejo/test_env:main

dachary referenced this issue

2023-02-04 23:38:09 +00:00

[CI] use codeberg.org/forgejo/test_env:main #318

dachary commented

2023-02-04 23:46:58 +00:00

Poster

fwiw I was able to get it working fine with the new test_env image without making any major changes, see 9ca75fac38

I was too focused and missed your commit, sorry about that: it would have worked fine.

> fwiw I was able to get it working fine with the new test_env image without making any major changes, see https://codeberg.org/crystal/forgejo/commit/9ca75fac38c4d651ae056d1a430f5a30a10bc522 I was too focused and missed your commit, sorry about that: it would have worked fine.

dachary commented

2023-02-04 23:49:40 +00:00

Poster

The solution I went for instead consists of pinning a test-env container image for v1.18 https://codeberg.org/forgejo/-/packages/container/test_env/1.18 and another for the main branch https://codeberg.org/forgejo/-/packages/container/test_env/main instead of assuming a single test environment will work for both, which breaks almost every time it is upgraded.

👍 1

crystal commented

2023-02-05 00:03:21 +00:00

That seems like a good idea. I was somewhat frustrated when I realized that the there was no versioned tag for the one from Gitea.

dachary commented

2023-02-05 11:22:06 +00:00

Poster

https://github.com/go-gitea/gitea/pull/22764/files someone noticed the Gitea v1.18 branch is broken. And still is broken with this change https://drone.gitea.io/go-gitea/gitea/66827/1/6

It won't be too long before a commit similar to yours is added to v1.18.

Having a tagged test env helps not break the builds at all.

All v1.18 & forgejo branches run the CI successfully using the tagged test environment, this issue can finally be closed.

https://github.com/go-gitea/gitea/pull/22764/files someone noticed the Gitea v1.18 branch is broken. And still is broken with this change https://drone.gitea.io/go-gitea/gitea/66827/1/6 It won't be too long before a commit [similar to yours](https://codeberg.org/crystal/forgejo/commit/9ca75fac38c4d651ae056d1a430f5a30a10bc522) is added to v1.18. Having a tagged test env helps not break the builds at all. All v1.18 & forgejo branches run the CI successfully using the tagged test environment, this issue can finally be closed.

👍 1

dachary closed this issue

2023-02-05 11:22:09 +00:00

dachary referenced this issue from a commit

2023-02-11 07:21:04 +00:00

[CI] implementation: Woodpecker based CI

dachary referenced this issue from a commit

2023-02-11 08:22:00 +00:00

[CI] implementation: Woodpecker based CI

dachary referenced this issue from a commit

2023-02-20 08:05:48 +00:00

[CI] implementation: Woodpecker based CI