end-to-end

STACKITGit/end-to-end

Fork 0

Commit graph

Author	SHA1	Message	Date
Earl Warren	74b8bebbe8	actions: parallel LXC jobs (#1149 ) This is not guaranteed to fail if parallel jobs is broken, but it is likely to. That could create transient errors detecting race conditions similar to https://code.forgejo.org/forgejo/lxc-helpers/issues/50. Reviewed-on: https://code.forgejo.org/forgejo/end-to-end/pulls/1149 Reviewed-by: Mathieu Fenniak <mfenniak@noreply.code.forgejo.org> Co-authored-by: Earl Warren <contact@earl-warren.org> Co-committed-by: Earl Warren <contact@earl-warren.org>	2025-12-01 15:25:21 +00:00
Earl Warren	c29e1e64e7	feat: actions: verify LXC backend can checkout (#522 ) ACT is expected to provide an LXC backend with node pre-installed by default to allow for running commonly used actions written in JS. It also includes an upgrade to setup-forgejo 2.0.8 which contains a fix to teardown the runner properly even in the event where it contains files owned by root. This happens when running a workflow within a LXC container. Reviewed-on: https://code.forgejo.org/forgejo/end-to-end/pulls/522 Reviewed-by: Michael Kriese <michael.kriese@gmx.de> Co-authored-by: Earl Warren <contact@earl-warren.org> Co-committed-by: Earl Warren <contact@earl-warren.org>	2025-01-29 06:57:27 +00:00
Earl Warren	429d5584e1	feat: actions: add LXC backend example (#520 ) Without such an example, there is no test that would verify a modification of the ACT LXC backend is working when running a cascading pull request. Trace of the run at: https://code.forgejo.org/forgejo/end-to-end/actions/runs/2433/jobs/2#jobstep-4-28 Reviewed-on: https://code.forgejo.org/forgejo/end-to-end/pulls/520 Reviewed-by: Michael Kriese <michael.kriese@gmx.de> Co-authored-by: Earl Warren <contact@earl-warren.org> Co-committed-by: Earl Warren <contact@earl-warren.org>	2025-01-28 17:16:51 +00:00

Author

SHA1

Message

Date

Earl Warren

74b8bebbe8

actions: parallel LXC jobs (#1149 )

This is not guaranteed to fail if parallel jobs is broken, but it is likely to. That could create transient errors detecting race conditions similar to https://code.forgejo.org/forgejo/lxc-helpers/issues/50.

Reviewed-on: https://code.forgejo.org/forgejo/end-to-end/pulls/1149
Reviewed-by: Mathieu Fenniak <mfenniak@noreply.code.forgejo.org>
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>

2025-12-01 15:25:21 +00:00

Earl Warren

c29e1e64e7

feat: actions: verify LXC backend can checkout (#522 )

ACT is expected to provide an LXC backend with node pre-installed by default to allow for running commonly used actions written in JS.

It also includes an upgrade to setup-forgejo 2.0.8 which contains a fix to teardown the runner properly even in the event where it contains files owned by root. This happens when running a workflow within a LXC container.

Reviewed-on: https://code.forgejo.org/forgejo/end-to-end/pulls/522
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>

2025-01-29 06:57:27 +00:00

Earl Warren

429d5584e1

feat: actions: add LXC backend example (#520 )

Without such an example, there is no test that would verify a modification of the ACT LXC backend is working when running a cascading pull request.

Trace of the run at: https://code.forgejo.org/forgejo/end-to-end/actions/runs/2433/jobs/2#jobstep-4-28

Reviewed-on: https://code.forgejo.org/forgejo/end-to-end/pulls/520
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>

2025-01-28 17:16:51 +00:00

3 commits