mirror/gitea
1
1
Fork 1
mirror of https://github.com/go-gitea/gitea.git synced 2024-11-18 20:43:57 +01:00
Code Issues
15,028 Commits 17 Branches 213 Tags 610 MiB
96fb7506db
Commit Graph

263 Commits

Author SHA1 Message Date
silverwind
96fb7506db
Introduce lint-md and compliance-docs pipeline (#24021) 
- Add new Make target `lint-md`
- Add new Drone pipeline `compliance-docs`
- Add `*.md` to docs exclusion/inclusion
- Consistently quote `path.include` and `path.exclude` statements in
YAML
 2023-04-09 20:05:12 +02:00
silverwind
af4c178452
Update JS deps (#23853) 
- Update all JS dependencies
- Regenerate svgs
- Tested heatmap, swagger, citation
 2023-04-02 19:47:14 -04:00
silverwind
96be0cb6e3
Update JS dependencies, Require Node.js 16 (#23528) 
- Update all JS dependencies
- Require Node.js 16 as dictated by `esbuild-loader`
- Regenerate SVG
- Adapt to `esbuild-loader` breaking changes
- Minor refactor in `webpack.config.js`
- Tested build, monaco and swagger-ui

---------

Co-authored-by: techknowlogick <techknowlogick@gitea.io>
 2023-03-17 01:45:45 -04:00
techknowlogick
f42740cb2b
Use arm image for arm runner (#23503) 2023-03-15 15:56:02 -05:00
silverwind
ea1b92621b
Use gitea/test_env image instead of golang (#23455) 
The `safe.directory` setting was not executed for pull requests, which
made subsequent `deps-backend` target fail at `go mod download`. To fix
it, split thep and perform the git config unconditionally.

Example: https://drone.gitea.io/go-gitea/gitea/69477/4/3

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
 2023-03-14 21:53:14 -04:00
techknowlogick
f96eef872f
Skip DB tests duplicate runs on push to branches (#23476) 
This skips all testing-* pipelines on push to main or release/*
branches. This decreases the total build time on those, as in theory
they should already be run for PRs before merging.

Fixes https://github.com/go-gitea/gitea/issues/22011

---------

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
 2023-03-14 21:46:13 -04:00
techknowlogick
32204fcf8b
test_env: hardcode major go version in use (#23464) 
hardcode the version of test_env we use in docker, so that we can use
different major versions of golang between versions of Gitea

---------

Co-authored-by: Lauris BH <lauris@nix.lv>
 2023-03-14 16:09:01 -04:00
techknowlogick
ab5bcdf98f
Use buildkit for docker builds (#23415) 
This switches Docker builds to use build kit which is less prone to
error than legacy docker-in-docker building. It also switches back to
using the upstream docker image again now that it has been updated to a
version that supports alpine 3.14+

Co-authored-by: John Olheiser <john.olheiser@gmail.com>
 2023-03-11 23:08:56 +02:00
John Olheiser
f92e0a4018
Split CI pipelines (#23385) 
- This PR attempts to split our various DB tests into separate
pipelines.
- It splits up some of the extra feature-related tests rather than
having most of them in the MySQL test.
- It disables the race detector for some of the pipelines as well, as it
can cause slower runs and is mostly redundant when the pipelines just
swap DBs.
- It builds without SQLite support for any of the non-SQLite pipelines.
- It moves the e2e test to using SQLite rather than PG (partially
because I moved the minio tests to PG and that mucked up the test
config, and partially because it avoids another running service)
- It splits up the `go mod download` task in the Makefile from the tool
installation, as the tools are only needed in the compliance pipeline.
(Arguably even some of the tools aren't needed there, but that could be
a follow-up PR)
- SQLite is now the only arm64 pipeline, moving PG back to amd64 which
can leverage autoscaler

Should resolve #22010 - one thing that wasn't changed here but is
mentioned in that issue, unit tests are needed in the same pipeline as
an integration test in order to form a complete coverage report (at
least as far as I could tell), so for now it remains in a pipeline with
a DB integration test.

Please let me know if I've inadvertently changed something that was how
it was on purpose.

---

I will say sometimes it's hard to pin down the average time, as a
pipeline could be waiting for a runner for X minutes and that brings the
total up by X minutes as well, but overall this does seem to be faster
on average.

---------

Signed-off-by: jolheiser <john.olheiser@gmail.com>
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
 2023-03-10 01:13:17 -05:00
Lunny Xiao
725a97c6c9
Don't run unnecessary steps when only docs changed (#23103) 
Remove some unnecessary steps from drone when only docs changed.

ref: https://drone.gitea.io/go-gitea/gitea/68090/1/3
 2023-02-27 16:20:42 -06:00
Lunny Xiao
c3d9a70d0a
only trigger docs build and publish when docs changed (#22968) 
Since drone plugin
https://github.com/meltwater/drone-convert-pathschanged/ enabled, we can
filter event with path in drone.

Building docs will now only be triggered when documentations changed.

---------

Co-authored-by: Jason Song <i@wolfogre.com>
 2023-02-20 21:08:41 +08:00
zeripath
54d7435d28
Adjust manifest to prevent tagging latest on rcs (#22811) 2023-02-19 09:24:08 -05:00
techknowlogick
ff18d17442
use drone secrets for s3 config (#22770) 2023-02-05 16:42:48 -05:00
techknowlogick
cfb1cb1168
update to build with go1.20 (#22732) 
as title

---------

Co-authored-by: Lauris BH <lauris@nix.lv>
 2023-02-03 11:23:52 -05:00
silverwind
a1fcb1cfb8
Update JS dependencies (#22538) 
- Update all JS dependencies
- Add new eslint rules
- Rebuild SVGs
- Tested citation and build

SVG changes are because of https://github.com/primer/octicons/pull/883.

Co-authored-by: techknowlogick <techknowlogick@gitea.io>
 2023-01-21 10:42:13 +08:00
KN4CK3R
fc037b4b82
Add support for incoming emails (#22056) 
closes #13585
fixes #9067
fixes #2386
ref #6226
ref #6219
fixes #745

This PR adds support to process incoming emails to perform actions.
Currently I added handling of replies and unsubscribing from
issues/pulls. In contrast to #13585 the IMAP IDLE command is used
instead of polling which results (in my opinion 😉) in cleaner code.

Procedure:
- When sending an issue/pull reply email, a token is generated which is
present in the Reply-To and References header.
- IMAP IDLE waits until a new email arrives
- The token tells which action should be performed

A possible signature and/or reply gets stripped from the content.

I added a new service to the drone pipeline to test the receiving of
incoming mails. If we keep this in, we may test our outgoing emails too
in future.

Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
 2023-01-14 23:57:10 +08:00
silverwind
3affb02df5
Run hugo via go run and lock its version (#22206) 
- Don't rely on obscure docker images like `plugins/hugo`
- Lock down `hugo` to same version the image had used
- Remove unnecessary verbosity in `trans-copy`
- Rename `trans-copy` to `trans-copy.sh`

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: John Olheiser <john+github@jolheiser.com>
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
 2022-12-21 21:09:53 -05:00
John Olheiser
9914b21493
fix: update libcurl in docs pipeline (#22203) 
updating libcurl fixes the mismatch between curl and libcurl

Signed-off-by: jolheiser <john.olheiser@gmail.com>
Co-authored-by: silverwind <me@silverwind.io>
 2022-12-21 13:45:32 -06:00
silverwind
e767b3372a
Update JS dependencies and eslint (#22190) 
- Update all JS dependencies to latest version
- Enable unicorn/prefer-node-protocol and autofix issues
- Regenerate SVGs
- Add some comments to eslint rules
- Tested build, Mermaid and Katex rendering
 2022-12-20 17:15:47 -05:00
flynnnnnnnnnn
350bc83d00
Update to Alpine 3.17 (#21904) 
This pull request is for updating the base docker images to build with
the latest version of Alpine.
 2022-12-02 11:23:26 -05:00
silverwind
c8b217110b
Update JS dependencies (#21881) 
- Update all JS deps
- Regenerate SVGs
- Add new eslint rules, fix issues
- Tested Mermaid, Swagger, Vue, Webpack, Citation

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
 2022-11-22 08:58:55 +08:00
silverwind
9380bb6d0c
Consolidate security-check into checks-backend (#21882) 
Also, run it via exact version instead of relying on global binary.
 2022-11-21 10:39:00 +08:00
silverwind
b1dd1ba48f
Update JS dependencies and misc tweaks (#21583) 
- Update all JS dependencies to latest version
- Disable two redundant eslint rules
- Adapt stylelint config to codebase
- Regenerate SVGs
- Make file editor spinner "reserve" height so page does not shift
- Tested katex, swagger, monaco

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: 6543 <6543@obermui.de>
 2022-10-28 09:40:50 -04:00
Yarden Shoham
94d6d93cc2
Fix Drone pushing commits with wrong author info (#21450) 
I don't know how to test this so I'll explain my thought process:

After a discussion with @techknowlogick in
cda2c38f4a
I saw the CI config has this block:

cda2c38f4a/.drone.yml (L618-L630)

I don't know much about Drone but after looking at
[appleboy/drone-git-push](https://github.com/appleboy/drone-git-push)'s
source code, I think each setting becomes an environment variable (e.g.
`remote` to `PLUGIN_REMOTE`, `commit_message` to `PLUGIN_COMMIT_MESSAGE`
etc...). Take a look at the code block loading the author info:

a69878c006/main.go (L32-L42)

Two environment variables are listed for each setting. This PR forces
both to have the same value.

Signed-off-by: Yarden Shoham <hrsi88@gmail.com>
 2022-10-14 15:09:04 -04:00
silverwind
94037ada24
Hook go-licenses into tidy again (#21353) 
Running it as part of the build is really unnecessary because we have a
valid output file in the repo and assuming go dependencies do not change
unless go.mod also changes, tidy really is the best target to run the
license generation after.

Also, regenerate the file as I missed to do so during the chroma update,
and mark all json files in assets as generated.
 2022-10-10 20:45:02 +02:00
silverwind
7044d34ae5
Update JS dependencies and eslint config (#21388) 
- Update all JS dependencies and playwright image
- Add new eslint rules, enable a few more, fix issues
- Regenerate SVGs
- Tested Vue and Swagger

Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
 2022-10-10 20:02:20 +08:00
Kyle D
7bb12d7efa
Bump playwright to 1.26.1 (#21357) 2022-10-08 16:54:34 +08:00
zeripath
64073276c4
Update go to 1.19 (#21361) 
It appears that updating go to 1.19 for playwright was missed when we
updated to go 1.19 elsewhere.

Signed-off-by: Andrew Thornton <art27@cantab.net>
 2022-10-06 21:51:18 +01:00
Bo-Yi Wu
24b5a384d2
chore(security): Support Go Vulnerability Management (#21139) 
See https://go.dev/security/vuln/

Signed-off-by: Bo-Yi.Wu <appleboy.tw@gmail.com>

Signed-off-by: Bo-Yi.Wu <appleboy.tw@gmail.com>
 2022-09-11 15:02:18 +08:00
silverwind
b5d21c0adf
Generate go-licenses during tidy again (#21108) 
We can not have the `frontend` target depend on golang because of they
way drone is set up. Move the `go-licenses` generation back into `tidy`
where it will now also be checked for consistency during `tidy-check`.

(I assume all `main` branch builds should currently fail [like
this](https://drone.gitea.io/go-gitea/gitea/60244/1/11)).

The reasony why it shouldn't be treated the same as for example `go
generate` is because output files are checked in. tidy is imho the
optimal target to run this after.

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
 2022-09-09 11:33:01 -04:00
silverwind
52c2ef7902
Rewrite go license generator in go (#21078) 
This removes the JS dependency in the checks pipeline. JSON output is
different because the previous JS did indent the license data
differently and a JSON key was changed, but the end result is the same
as it gets re-indented by wepack.

Co-authored-by: 6543 <6543@obermui.de>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: zeripath <art27@cantab.net>
 2022-09-07 17:35:54 -04:00
Kyle D
6361b48b21
Bump playwright test image to match version in package.json (#21097) 
Bump the playwright test image to match version in package.json (so it
doesn't re-download browsers setup)
 2022-09-07 00:00:34 +01:00
silverwind
7f6306ccd1
Add missing volume to test-e2e (#21079) 
Without it, the deps-backend step before is useless as `go test` will not see the files in GOPATH and re-download them.
 2022-09-05 17:35:46 -04:00
silverwind
49efd1fb96
Add go licenses to licenses.txt (#21034) 
`make go-licenses` will generate `assets/go-licenses.json` which is then included in the webpack build. 

This step depends on both go and node being present, so unfortunately, I could not automate the generation by hooking it up to `tidy` as that target is triggered on CI where we do not have a docker image with both go an node.

It should be ran from time to time, ideally after each go mod update.
 2022-09-04 00:20:46 +02:00
Kyle D
c8ded77680
Kd/ci playwright go test (#20123) 
* Add initial playwright config

* Simplify Makefile

* Simplify Makefile

* Use correct config files

* Update playwright settings

* Fix package-lock file

* Don't use test logger for e2e tests

* fix frontend lint

* Allow passing TEST_LOGGER variable

* Init postgres database

* use standard gitea env variables

* Update playwright

* update drone

* Move empty env var to commands

* Cleanup

* Move integrations to subfolder

* tests integrations to tests integraton

* Run e2e tests with go test

* Fix linting

* install CI deps

* Add files to ESlint

* Fix drone typo

* Don't log to console in CI

* Use go test http server

* Add build step before tests

* Move shared init function to common package

* fix drone

* Clean up tests

* Fix linting

* Better mocking for page + version string

* Cleanup test generation

* Remove dependency on gitea binary

* Fix linting

* add initial support for running specific tests

* Add ACCEPT_VISUAL variable

* don't require git-lfs

* Add initial documentation

* Review feedback

* Add logged in session test

* Attempt fixing drone race

* Cleanup and bump version

* Bump deps

* Review feedback

* simplify installation

* Fix ci

* Update install docs
 2022-09-02 15:18:23 -04:00
techknowlogick
be824890e4
Switch to building with go1.19 (#20695) 2022-08-07 12:25:03 -04:00
silverwind
aec6b30e2a
Unbreak release pipeline (#20356) 
Downgrade release pipeline to node 16 until xgo updates its base OS to a
version with a compatible glibc.

Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
 2022-07-14 16:09:26 +08:00
silverwind
9cd1f38f70
Upgrade to Node 18 on CI (#20340) 
* Upgrade to Node 18 on CI

Should be pretty stable now.

* restart ci

Co-authored-by: 6543 <6543@obermui.de>
 2022-07-13 11:45:08 -04:00
wxiaoguang
5f618248a9
Use Golang 1.18 for Gitea 1.17 release (#19918) 
Use Golang 1.18 (as minimal requirement) for Gitea 1.17 release, make sure the Golang version is still actively supported during Gitea 1.17 lifecycle.

Co-authored-by: zeripath <art27@cantab.net>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: 6543 <6543@obermui.de>
 2022-06-10 05:34:41 +02:00
Lunny Xiao
48be5e77e5
Increment tests time out from 40m to 50m because sometimes the machine is slow (#19887) 2022-06-05 12:24:51 +08:00
techknowlogick
cab3a8b59d
Set safe dir for git operations in .drone.yml CI (#19641) 
Our drone by necessity runs on git repositories not owned by the drone process. Unfortunately this means that git operations and thence CI builds will fail without the `safe.directory` option being set. 

See: https://drone.gitea.io/go-gitea/gitea/54632/2/8
 2022-05-06 18:25:18 +01:00
Lunny Xiao
54961f3ac9
Use goproxy.io instead of goproxy.cn (#19242) 2022-03-28 20:01:07 +03:00
techknowlogick
ed1d95c55d
use go1.18 to build gitea (#19099) 
* use go1.18 to build gitea& update min go version to 1.17

* bump in a few more places

* add a few simple tests for isipprivate

* update go.mod

* update URL to https://go.dev/dl/

* golangci-lint

* attempt golangci-lint workaround

* change version

* bump fumpt version

* skip strings.title test

* go mod tidy

* update tests as some aren't private??

* update tests
 2022-03-16 00:08:31 -04:00
silverwind
fe9626af29
Use go run for tool dependencies, require go 1.17 (#18874) 
This ensures the tools only run in the versions we've tested and it also
does not polute PATH with those tools so they are truly isolated. This
syntax of `go run` requires go 1.17, so the minimum version is set
accordingly.

Fixes: https://github.com/go-gitea/gitea/issues/18867

Co-authored-by: techknowlogick <techknowlogick@gitea.io>
 2022-03-15 22:50:26 -04:00
6543
e800bc0cf4
allow overwrite artifacts for github releases (#18987) 2022-03-03 15:28:41 +01:00
silverwind
2ddff74a54
Reduce CI go module downloads, add make targets (#18708) 
The CI currently downloads all go modules in each pipeline step because
go modules reside outside the project directory. Fix this by introducing
a volume for the `/go` directory [1] so modules are only downloaded once per
pipeline using a new `deps-backend` make target.

For completeness, I also included new `deps` and `deps-frontend` targets
and the frontend one is also triggered explicitly on CI where needed.

[1] https://docs.drone.io/pipeline/kubernetes/examples/language/golang/#dependencies
 2022-02-12 07:08:53 +00:00
zeripath
9f9ca0aae4
Fix pushing to 1-x-dev docker tag (#18578) 
* Fix pushing to 1-x-dev docker tag

It appears that #18551 and #18573 have a mistake in that raymond does not have
an {{else}} on {{#equal}}. This PR notes that Sprig has a hasPrefix function
and so we use this with another if.

Signed-off-by: Andrew Thornton <art27@cantab.net>

* Fix pushing to 1-x-dev docker tag (part 2)

Although we now have the manifest working, we need to create the images.

Here we adjust the .drone.yml to force building of the images

Signed-off-by: Andrew Thornton <art27@cantab.net>

* Fix pushing to 1-x-dev docker tag

OK now we have the images building we should make sure that the main ones stays
dev and the release/v* ones become *-dev-*

Signed-off-by: Andrew Thornton <art27@cantab.net>

* Apply suggestions from code review
 2022-02-03 22:44:51 +01:00
zeripath
bc77b28d9d
Make docker gitea/gitea:v1.16-dev etc refer to the latest build on that branch (#18551) 
* Make docker gitea/gitea:v1.16-dev etc refer to the latest build on that branch

One of the problems with our current docker tagging is that although we
have strict version tags, latest and dev we do not have a way for docker
users to track the current release branch. This PR simply suggests that
we use the 1.x-dev tag for these and we build and push these. This will
give users who want or need unreleased bug fixes the option of tracking
the pre-release version instead of simply jumping to dev.

Signed-off-by: Andrew Thornton <art27@cantab.net>
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
 2022-02-03 09:47:27 +01:00
techknowlogick
115e4772cc
point to s3 endpoint directly (#18497) 
Co-authored-by: 6543 <6543@obermui.de>
 2022-01-31 17:39:39 -05:00
techknowlogick
b2250d2fb3
upload to github & s3 at same time (#18475) 2022-01-30 17:40:44 -05:00