4075d2c891
chore(ci): run merge conditions when a new commit is pushed
...
Otherwise the latest status of the PR may be skipped instead of fail
if the condition is not met.
2024-12-02 13:20:35 +01:00
8365133d6c
Update renovate to v39.42.4 (forgejo) ( #6115 )
...
Co-authored-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
Co-committed-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
2024-12-02 07:14:08 +00:00
5f0049bfea
Update renovate to v39.28.0 (forgejo) ( #6065 )
...
Co-authored-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
Co-committed-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
2024-11-25 00:33:00 +00:00
caea17ccb2
ci: use more `tmpfs` and `noatime` for faster CI
2024-11-22 11:13:04 +01:00
a69943085a
chore(ci): remove unused experimental DNS updates
2024-11-20 15:13:53 +00:00
cff7754735
Merge pull request 'ci: disable postgresql fsync' ( #5962 ) from viceice/ci/pg/fsync into forgejo
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5962
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
2024-11-18 21:43:15 +00:00
1806db31d1
chore(ci): merge jobs in issue-labels.yml in one workflow
...
Fixes : forgejo/forgejo#5999
2024-11-18 19:43:35 +01:00
7c1f3a7594
chore(ci): cat all issue labels workflows in issue-labels.yml
...
cat cascade-setup-end-to-end.yml backport.yml merge-requirements.yml release-notes-assistant.yml > issue-labels.yml
rm cascade-setup-end-to-end.yml backport.yml merge-requirements.yml release-notes-assistant.yml
2024-11-18 19:40:15 +01:00
73cb6c9204
chore(ci): make release-notes-assistant job copy/pastable (part two)
...
The event is pull_request_target
Refs: forgejo/forgejo#5999
2024-11-18 18:11:07 +01:00
18cecf124f
chore(ci): make release-notes-assistant job copy/pastable
...
Refs: forgejo/forgejo#5999
2024-11-18 17:23:33 +01:00
6cfaebf043
Merge pull request 'chore(ci): make backporting job copy/pastable' ( #6002 ) from earl-warren/forgejo:wip-ci-labels-backports into forgejo
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/6002
Reviewed-by: Otto <otto@codeberg.org>
2024-11-18 10:44:38 +00:00
6553148de9
Update renovate to v39.19.1 (forgejo) ( #6008 )
...
Co-authored-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
Co-committed-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
2024-11-18 05:52:58 +00:00
b6869d643e
chore(ci): make backporting job copy/pastable
...
Refs: forgejo/forgejo#5999
2024-11-17 19:17:11 +01:00
64a89c8d33
chore(ci): make merge-conditions job copy/pastable
...
Refs: forgejo/forgejo#5999
2024-11-17 17:57:40 +01:00
b5161325ef
chore(ci): make end-to-end job copy/pastable
...
Refs: forgejo/forgejo#5999
2024-11-17 13:33:21 +01:00
7f707b2a6f
ci: disable postgresql fsync
2024-11-15 15:29:06 +01:00
5406310f3e
ci: upload all e2e artifacts
2024-11-15 15:01:39 +01:00
c8d97e5594
ci: use oci mirror images
2024-11-15 08:19:50 +01:00
19c9e0a0c2
ci: proper job name
2024-11-15 00:48:45 +01:00
d1ad4dd561
Merge pull request 'Highlight user mention in comments and commit messages' ( #5899 ) from 0ko/forgejo:mention-highlight into forgejo
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5899
Reviewed-by: Otto <otto@codeberg.org>
2024-11-14 17:46:03 +00:00
8a4407ef72
ci: use tmpfs for service storage
2024-11-14 17:27:48 +01:00
eda83cc7ed
ci: disable mysql binlog
2024-11-14 16:39:34 +01:00
019e38a746
chore(ci): Upload screenshots on test failure
2024-11-14 14:12:31 +01:00
068558accd
chore(ci): ROLE forgejo-coding & forgejo-testing (part two)
...
When the CI vars.ROLE is forgejo-coding, it is assumed to be the
repository where collaborative coding happens,
i.e. https://codeberg.org/forgejo/forgejo
When the CI vars.ROLE is forgejo-testing, it is assumed that only codebase
testing is to be run and no other tests such as release build
integration, label constraints, backporting etc.
2024-11-13 23:04:47 +01:00
f82840f1ea
chore(ci): ROLE forgejo-coding & forgejo-testing
...
When the CI vars.ROLE is forgejo-coding, it is assumed to be the
repository where collaborative coding happens,
i.e. https://codeberg.org/forgejo/forgejo
When the CI vars.ROLE is forgejo-testing, it is assumed that only codebase
testing is to be run and no other tests such as release build
integration, label constraints, backporting etc.
2024-11-13 22:18:35 +01:00
7492330721
chore(ci): trigger a mirror when a release is publish
...
Notify https://code.forgejo.org/forgejo/forgejo that a new release was
published by setting the trigger label to
https://code.forgejo.org/forgejo/forgejo/issues/5 .
It is only ever useful when a stable release is published, the
experimental releases are not mirrored. But it is triggered in all
cases. This will waste a few mirror check daily, when experimental
releases are built. This is an improvement compared to the current
situation where mirrors are checked hourly:
* Instead of being checked 24 times per day it will be down to less
than 5
* The mirror happens immediately after the release is published
instead of waiting for the next run of the cron job.
If a mirror operation is in progress, as evidenced by the presence of
the trigger label on the issure, it means two releases are being
published. Wait up to 1h for the mirror to complete and remove the
trigger label.
2024-11-13 17:17:08 +01:00
ff1a084fa3
Update renovate to v39.9.0 (forgejo) ( #5907 )
...
Co-authored-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
Co-committed-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
2024-11-11 05:57:44 +00:00
2cfd59cb30
Merge pull request 'chore(ci): Enforce test label with CI check' ( #5886 ) from fnetx/test-label-test into forgejo
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5886
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
2024-11-10 12:21:08 +00:00
493175e6fd
fix(ci): only trigger end-to-end tests when the label is set
...
Use event.label instead of event.pull_request.labels.*.name
Prior to Forgejo v9.0.2 it was not set and that was the only workaround.
2024-11-10 11:44:59 +01:00
2483dbc694
chore(ci): Enforce test label with CI check
...
Re-add the test after bugfixes have been deployed to Codeberg
2024-11-10 02:16:21 +01:00
39f4018d87
fix(ci): slow runners may need more than 50 minutes for a test
2024-11-09 18:16:38 +01:00
2eeb2fcd35
chore(renovate): only run if renovate workflow changed
2024-11-08 13:05:43 +01:00
669b4b46e6
chore(renovate): pin to single actions runner
2024-11-08 12:18:29 +01:00
8b27dcb3b6
Update renovate to v39 (forgejo) (major) ( #5829 )
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5829
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
Co-committed-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
2024-11-06 14:39:53 +00:00
ece87d0569
chore(ci): deprecate legacy infrastructure supporting v*.next
...
https://code.forgejo.org/infrastructure/k8s/ was replaced with
https://code.forgejo.org/infrastructure/k8s-cluster/
2024-11-05 16:18:06 +01:00
fb1b3e2c6d
Update renovate to v38.142.5 (forgejo) ( #5802 )
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5802
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
Co-committed-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
2024-11-04 05:52:26 +00:00
c56c49adeb
Update actions/git-backporting action to v4.8.4
2024-11-03 00:03:53 +00:00
2f7f3834b6
Revert "chore(ci): Enforce test label with CI check"
...
This reverts commit 5da7f07fbehttps://codeberg.org/forgejo/forgejo/pulls/5769
2024-11-01 14:36:37 +01:00
ab936de02d
Update infrastructure/next-digest action to v1.1.0
2024-11-01 10:40:13 +00:00
5da7f07fbe
chore(ci): Enforce test label with CI check
...
- test label needs to be set and either present, not-needed or manual
- if manual test label is set, PR description needs to contain a heading
(defined by '#') starting with "Test" (e.g. "Test instructions",
"Testing" etc)
2024-10-31 16:39:53 +01:00
b087cdc002
chore(ci): use rootless for the container images sent to k8s
...
The input to the action is not image_suffix but tag_suffix. It finds
an image and does not error. But it is the root image and the k8s
cluster needs the rootless image.
2024-10-31 12:24:40 +01:00
dab156b452
chore(ci): notify the k8s cluster about experimental releases
...
This is in preparation of the migration of the v*.next.forgejo.org
instances currently managed at https://code.forgejo.org/infrastructure/k8s
The key difference is that the former system relies on ad-hoc scripts
and creates one k8s cluster for each instance, sharing nothing between
them.
The newer k8s cluster is used for all and requires significantly less
ad-hoc tooling.
See also:
* https://code.forgejo.org/infrastructure/next-digest
* https://code.forgejo.org/infrastructure/k8s-cluster/src/branch/main/k8s.md#updating-v-next-forgejo-org
2024-10-30 19:44:55 +01:00
f9a16f8be0
Update renovate to v38.133.0
2024-10-28 06:26:24 +00:00
511b213db2
tests(e2e): skip browser downloads
...
The browser versions are updated weekly in the cache, see https://code.forgejo.org/forgejo/playwright-image-builder
When they change between the runs, they are refreshed for each CI run (see https://codeberg.org/forgejo/forgejo/actions/runs/35651/jobs/3#jobstep-7-19 for an example).
Updating the browsers weekly is good enough, so skip the explicit update check here.
Related playwright documentation: https://playwright.dev/docs/library#browser-downloads
2024-10-24 22:42:21 +02:00
e0ea4e2de4
feat(ci): allow manual triggering of the test suite
...
When a skip ci label is added to the PR title, removing it won't
trigger the CI. There needs to be a way to manually trigger it.
2024-10-21 08:06:22 +02:00
13762759fd
Update renovate to v38.128.6
2024-10-21 00:03:17 +00:00
54c8ac3e39
vars.SKIP_END_TO_END optionally skip tests when building a release
...
The end-to-end tests will always fail when more than one release is
broken. When trying to fix one, the other will get in the way and vice
versa. The only way to get out of this deadlock is to replace all
broken releases but one by doing the following on forgejo-integration:
* set SKIP_END_TO_END to true in the actions vars tab
* pushing a commit to the corresponding branch, fixing the problem
2024-10-17 07:31:22 +02:00
1a7a9055e4
forgejo-cli is now a symlink and cannot be used for sanity checks
...
It could be used but then `cp --dereference` would need to be used instead in
the forgejo-build-publish action.
+ docker cp forgejo-amd64:/app/gitea/forgejo-cli forgejo-9.0-test-linux-amd64
+ chmod +x forgejo-9.0-test-linux-amd64
chmod: cannot operate on dangling symlink 'forgejo-9.0-test-linux-amd64'
2024-10-17 06:59:05 +02:00
7e805fa665
Update renovate to v38.121.0
2024-10-14 20:04:12 +00:00
80d41ee2e1
Update actions/cache action to v4.1.1 (forgejo) ( #5498 )
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5498
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
Co-committed-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
2024-10-09 04:54:02 +00:00
b23217fb3e
Update actions/git-backporting action to v4.8.2
2024-10-08 00:02:57 +00:00
c82e5d1a1a
Merge pull request 'chore(ci): update changed-files actions URL for consistency' ( #5485 ) from fnetx/changed-files-action-url into forgejo
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5485
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
2024-10-07 05:34:33 +00:00
36c384246c
chore(ci): update changed-files actions URL for consistency
...
mirrored actions are typically created under the name of the original author; additionally this moves the action to Forgejo's control
2024-10-07 03:21:45 +02:00
e9040fafec
Update renovate to v38.110.2
2024-10-07 00:03:30 +00:00
e4866d9c9a
Update actions/cache action to v4.1.0
2024-10-06 00:04:15 +00:00
72749bcf70
ci: (always|only) run e2e tests based on changes
...
- detect changed files for the run
- let e2e files specify which related files they "watch"
- only run e2e tests based on pattern matching or when generic files
change
- fallback to full runs if env not specified
2024-10-04 15:14:45 +02:00
f2a23c962a
ci: merge e2e workflow into testing.yml
...
ci: cache frontend build across jobs
ci: ensure caches are saved with zstd
work around https://github.com/actions/cache/issues/1169
ci: require unit tests for remote cacher
- prevents unnecessary runs in case the unit tests already fail
- starts the integration tests about 2 minutes earlier
- should give some overall speedup to the CI run, because the long integration tests are run and finish earlier, and the cacher tests should still usually finish in time
- does not save any computing resources, just provides quicker results when runners are not under high load
2024-10-04 15:14:28 +02:00
e6b84f9191
ci: move composite workflow location
...
otherwise, they unfortunately display in the Forgejo UI with an error message
2024-10-01 16:51:02 +02:00
be373e948e
Update actions/setup-go action to v5
2024-10-01 10:02:16 +00:00
9a7fc2e55e
Merge pull request 'Update actions/cache action to v4 (forgejo)' ( #5426 ) from renovate/forgejo-actions-cache-4.x into forgejo
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5426
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
2024-10-01 07:50:24 +00:00
e3eaa284bb
Update actions/checkout action to v4 (forgejo) ( #5427 )
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5427
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
Co-committed-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
2024-09-30 13:08:26 +00:00
92305933b1
Update actions/setup-node action to v4 (forgejo) ( #5428 )
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5428
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
Co-committed-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
2024-09-30 12:56:08 +00:00
502a6a4461
Update actions/cache action to v4
2024-09-30 12:06:49 +00:00
1b06287fe3
Update renovate to v38.101.1
2024-09-30 00:08:52 +00:00
a56c000f60
Replace setup-go with a custom action
...
To maximize the caching efficiency, all build jobs are executed as
forgejo user.
Hash is explicitly specified to avoid breaking changes.
2024-09-30 01:16:54 +02:00
1fa09d1621
Split Git package installation
2024-09-28 12:08:30 +02:00
c0b17a06ef
Split backend building boilerplate
2024-09-27 20:47:35 +02:00
5b84756137
Split env preparation boilerplate
2024-09-27 20:47:35 +02:00
15ec27e658
Update renovate to v38.93.2
2024-09-23 02:02:04 +00:00
4cff39c4d9
Update renovate to v38.80.0
2024-09-16 00:02:10 +00:00
6e02a6b422
Update renovate to v38.77.2
2024-09-12 16:02:09 +00:00
d14b17e08d
tests(e2e): use playwright image for dependency caching
2024-09-12 03:16:51 +02:00
2f49437608
Revert "fix: CI: temporarily disable redict tests"
...
This reverts commit 9d306bbec3
2024-09-11 15:45:07 +02:00
9d306bbec3
fix: CI: temporarily disable redict tests
...
Refs: https://codeberg.org/redict/redict-containers/issues/32
2024-09-11 07:33:57 +02:00
0f3ba99ff0
Add detailed instructions for e2e testing
...
- rewrite parts of and improve README
- simplify repo declaration
- list coverage in workflow path filter
2024-09-09 14:06:10 +02:00
d9893ed2b6
Update renovate to v38.59.2
2024-09-02 00:02:39 +00:00
293203cb64
Merge pull request 'chore(ci): Cache generated binary across jobs' ( #5130 ) from fnetx/runner-caching into forgejo
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5130
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
2024-08-30 05:47:01 +00:00
72408c7d68
Cache generated binary across jobs
...
- retrieved by the commit hash
- removes bindata tags from integration tests, because it does not seem
to be required
- due to the missing automatically generated data, the zstd tests fail
(they use repo data including node_modules (!) as input to the test,
there is no apparent reason for the size constants)
2024-08-26 23:43:09 +02:00
c856f77622
Merge pull request 'Update links affected by the renaming of 'developer' documentation sub-path into 'contributor'' ( #5129 ) from floss4good/forgejo__forgejo:contrib-doc into forgejo
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5129
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Reviewed-by: Otto <otto@codeberg.org>
2024-08-26 18:50:40 +00:00
d97e36f6d7
Playwright testing for commit diffs
...
includes:
- easier repo declaration for playwright tests by @Gusted
- full backend build for pushing Git repos by @Gusted
- playwright testing (which fails with the current diff algorithm, but
passes with the new)
- disable eslint rule for conditional expect, because it defeats the
purpose (working around it would result in much more complex test code
in our cases)
2024-08-26 13:57:42 +02:00
018aefe29f
Replace Developer Guide links with the new Contributor Guide one for PR template and release workflows comments.
2024-08-26 14:29:10 +03:00
fbe464309b
Update renovate to v38.52.3
2024-08-26 04:05:34 +00:00
74f08b5da0
Merge pull request 'feat: add forgejo-cli to the container images' ( #5012 ) from earl-warren/forgejo:wip-cli into forgejo
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5012
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
2024-08-19 08:47:57 +00:00
b6efebc237
feat: add forgejo-cli to the container images
...
When the Forgejo CLI binary is `forgejo-cli`, the `--verbose` or `--quiet`
arguments are available globally for all sub-commands. The same
sub-commands can be used with `forgejo forgejo-cli`, those flags are
not available.
2024-08-19 09:44:04 +02:00
1b9222f6e2
Update renovate to v38.39.6
2024-08-19 02:03:33 +00:00
2960f78adb
Update docker.io/bitnami/minio Docker tag to v2024.8.17
2024-08-18 00:02:17 +00:00
9b66710bf5
Merge pull request 'Update docker.io/bitnami/mysql Docker tag to v8.4 (forgejo)' ( #4961 ) from renovate/forgejo-docker.io-bitnami-mysql-8.x into forgejo
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/4961
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
2024-08-17 07:46:57 +00:00
7614efcaf6
Update docker.io/bitnami/mysql Docker tag to v8.4
2024-08-15 00:03:35 +00:00
da44a7c01b
Update docker.io/bitnami/minio Docker tag to v2024.8.3
2024-08-15 00:03:08 +00:00
696e0ff27e
ci: use mirror or bitnami images
...
This reduces chances of docker hub rate limiting.
Bitnami images are excluded from rate limiting.
2024-08-14 12:10:53 +02:00
395c10596e
chore(ci): use postgres image from mirror
2024-08-12 16:19:20 +02:00
53ca3d4e6c
chore(ci): Use mirrored container images for node
2024-08-12 16:11:35 +02:00
eb6afae1c0
Update renovate to v38.25.0
2024-08-12 00:04:22 +00:00
f250f89491
chore(ci): do not remove tags from forgejo-integration
...
If the tag of a stable release is removed from integration, it won't
be properly described when building the test release. It will be:
8.0.0-dev-1648-7b31a541c0+gitea-1.22.0
instead of:
8.0.1-5-7b31a541c0+gitea-1.22.0
2024-08-11 07:22:21 +02:00
6e94be527a
chore(ci): remove old releases from forgejo-integration
...
The releases are created when:
* a tag is pushed to the integration repository it will create a
vX.Y.Z release
* a new commit is pushed to a branch and mirrored to the integration
repository, it will create a vX.Y-test release named after the branch
When both vX.Y.Z and vX.Y-test release are present, the end-to-end
tests will use vX.Y.Z because it comes first in release sort
order. This ensures that a last round of end-to-end tests is run from
the release built in the integration repository, exactly as it will be
published and signed.
In between stable releases, the vX.Y-test releases are built daily and
must be used instead for end-to-end testing so that problems can be
detected as soon as possible. For that to happen, the stable release
must be removed from the integration repository and this is done 24h
after they were published.
The vX.Y-test releases are removed if they have not been updated in 18
months. As of August 2024 it is possible for a LTS to still be needed
in tests over a year after it was last updated, although it is
unlikely that such a lack of activity happens, there is no reason to
remove the test release before that.
2024-08-10 15:16:00 +02:00
8039240c26
Update module github.com/editorconfig-checker/editorconfig-checker/v2/cmd/editorconfig-checker to v3
2024-08-09 21:03:37 +02:00
52666d4a8a
Update renovate to v38.21.3
2024-08-08 08:05:32 +00:00
2e2a044493
Revert "Open telemetry integration ( #3972 )"
...
This reverts commit c738542201
2024-08-07 11:22:43 +02:00
4fb19da661
ci: add `workflow_dispatch` to renovate and mirror
2024-08-06 13:52:36 +02:00
c738542201
Open telemetry integration ( #3972 )
...
This PR adds opentelemetry and chi wrapper to have basic instrumentation
<!--start release-notes-assistant-->
## Draft release notes
<!--URL:https://codeberg.org/forgejo/forgejo-- >
- Features
- [PR](https://codeberg.org/forgejo/forgejo/pulls/3972 ): <!--number 3972 --><!--line 0 --><!--description YWRkIHN1cHBvcnQgZm9yIGJhc2ljIHJlcXVlc3QgdHJhY2luZyB3aXRoIG9wZW50ZWxlbWV0cnk=-->add support for basic request tracing with opentelemetry<!--description-->
<!--end release-notes-assistant-->
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/3972
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: TheFox0x7 <thefox0x7@gmail.com>
Co-committed-by: TheFox0x7 <thefox0x7@gmail.com>
2024-08-05 06:04:39 +00:00
Earl Warren