2016-11-24 08:40:16 +01:00
|
|
|
// Copyright 2016 The Gitea Authors. All rights reserved.
|
2022-11-27 19:20:29 +01:00
|
|
|
// SPDX-License-Identifier: MIT
|
2016-11-24 08:40:16 +01:00
|
|
|
|
|
|
|
package routers
|
|
|
|
|
|
|
|
import (
|
2019-12-15 10:51:28 +01:00
|
|
|
"context"
|
2021-10-21 11:22:43 +02:00
|
|
|
"reflect"
|
|
|
|
"runtime"
|
2016-11-24 08:40:16 +01:00
|
|
|
|
|
|
|
"code.gitea.io/gitea/models"
|
2021-12-10 09:14:24 +01:00
|
|
|
asymkey_model "code.gitea.io/gitea/models/asymkey"
|
2017-10-26 03:37:33 +02:00
|
|
|
"code.gitea.io/gitea/modules/cache"
|
2020-05-07 23:49:00 +02:00
|
|
|
"code.gitea.io/gitea/modules/eventsource"
|
2019-03-27 10:33:00 +01:00
|
|
|
"code.gitea.io/gitea/modules/git"
|
2016-12-06 18:58:31 +01:00
|
|
|
"code.gitea.io/gitea/modules/highlight"
|
2019-12-08 20:15:35 +01:00
|
|
|
code_indexer "code.gitea.io/gitea/modules/indexer/code"
|
2019-02-21 01:54:05 +01:00
|
|
|
issue_indexer "code.gitea.io/gitea/modules/indexer/issues"
|
2020-02-11 10:34:17 +01:00
|
|
|
stats_indexer "code.gitea.io/gitea/modules/indexer/stats"
|
2016-11-24 08:40:16 +01:00
|
|
|
"code.gitea.io/gitea/modules/log"
|
2017-09-16 19:17:57 +02:00
|
|
|
"code.gitea.io/gitea/modules/markup"
|
2019-05-25 19:15:39 +02:00
|
|
|
"code.gitea.io/gitea/modules/markup/external"
|
2019-10-25 16:46:37 +02:00
|
|
|
"code.gitea.io/gitea/modules/notification"
|
2016-11-24 08:40:16 +01:00
|
|
|
"code.gitea.io/gitea/modules/setting"
|
|
|
|
"code.gitea.io/gitea/modules/ssh"
|
2020-08-18 06:23:45 +02:00
|
|
|
"code.gitea.io/gitea/modules/storage"
|
2020-07-12 11:10:56 +02:00
|
|
|
"code.gitea.io/gitea/modules/svg"
|
2022-10-17 01:29:26 +02:00
|
|
|
"code.gitea.io/gitea/modules/system"
|
2022-08-28 11:43:25 +02:00
|
|
|
"code.gitea.io/gitea/modules/templates"
|
2021-01-05 14:05:40 +01:00
|
|
|
"code.gitea.io/gitea/modules/translation"
|
2022-05-10 23:55:54 +02:00
|
|
|
"code.gitea.io/gitea/modules/util"
|
2021-06-09 01:33:54 +02:00
|
|
|
"code.gitea.io/gitea/modules/web"
|
Implement actions (#21937)
Close #13539.
Co-authored by: @lunny @appleboy @fuxiaohei and others.
Related projects:
- https://gitea.com/gitea/actions-proto-def
- https://gitea.com/gitea/actions-proto-go
- https://gitea.com/gitea/act
- https://gitea.com/gitea/act_runner
### Summary
The target of this PR is to bring a basic implementation of "Actions",
an internal CI/CD system of Gitea. That means even though it has been
merged, the state of the feature is **EXPERIMENTAL**, and please note
that:
- It is disabled by default;
- It shouldn't be used in a production environment currently;
- It shouldn't be used in a public Gitea instance currently;
- Breaking changes may be made before it's stable.
**Please comment on #13539 if you have any different product design
ideas**, all decisions reached there will be adopted here. But in this
PR, we don't talk about **naming, feature-creep or alternatives**.
### β οΈ Breaking
`gitea-actions` will become a reserved user name. If a user with the
name already exists in the database, it is recommended to rename it.
### Some important reviews
- What is `DEFAULT_ACTIONS_URL` in `app.ini` for?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1055954954
- Why the api for runners is not under the normal `/api/v1` prefix?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061173592
- Why DBFS?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061301178
- Why ignore events triggered by `gitea-actions` bot?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1063254103
- Why there's no permission control for actions?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1090229868
### What it looks like
<details>
#### Manage runners
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205870657-c72f590e-2e08-4cd4-be7f-2e0abb299bbf.png">
#### List runs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872794-50fde990-2b45-48c1-a178-908e4ec5b627.png">
#### View logs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872501-9b7b9000-9542-4991-8f55-18ccdada77c3.png">
</details>
### How to try it
<details>
#### 1. Start Gitea
Clone this branch and [install from
source](https://docs.gitea.io/en-us/install-from-source).
Add additional configurations in `app.ini` to enable Actions:
```ini
[actions]
ENABLED = true
```
Start it.
If all is well, you'll see the management page of runners:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205877365-8e30a780-9b10-4154-b3e8-ee6c3cb35a59.png">
#### 2. Start runner
Clone the [act_runner](https://gitea.com/gitea/act_runner), and follow
the
[README](https://gitea.com/gitea/act_runner/src/branch/main/README.md)
to start it.
If all is well, you'll see a new runner has been added:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205878000-216f5937-e696-470d-b66c-8473987d91c3.png">
#### 3. Enable actions for a repo
Create a new repo or open an existing one, check the `Actions` checkbox
in settings and submit.
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879705-53e09208-73c0-4b3e-a123-2dcf9aba4b9c.png">
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879383-23f3d08f-1a85-41dd-a8b3-54e2ee6453e8.png">
If all is well, you'll see a new tab "Actions":
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205881648-a8072d8c-5803-4d76-b8a8-9b2fb49516c1.png">
#### 4. Upload workflow files
Upload some workflow files to `.gitea/workflows/xxx.yaml`, you can
follow the [quickstart](https://docs.github.com/en/actions/quickstart)
of GitHub Actions. Yes, Gitea Actions is compatible with GitHub Actions
in most cases, you can use the same demo:
```yaml
name: GitHub Actions Demo
run-name: ${{ github.actor }} is testing out GitHub Actions π
on: [push]
jobs:
Explore-GitHub-Actions:
runs-on: ubuntu-latest
steps:
- run: echo "π The job was automatically triggered by a ${{ github.event_name }} event."
- run: echo "π§ This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- run: echo "π The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
- name: Check out repository code
uses: actions/checkout@v3
- run: echo "π‘ The ${{ github.repository }} repository has been cloned to the runner."
- run: echo "π₯οΈ The workflow is now ready to test your code on the runner."
- name: List files in the repository
run: |
ls ${{ github.workspace }}
- run: echo "π This job's status is ${{ job.status }}."
```
If all is well, you'll see a new run in `Actions` tab:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884473-79a874bc-171b-4aaf-acd5-0241a45c3b53.png">
#### 5. Check the logs of jobs
Click a run and you'll see the logs:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884800-994b0374-67f7-48ff-be9a-4c53f3141547.png">
#### 6. Go on
You can try more examples in [the
documents](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
of GitHub Actions, then you might find a lot of bugs.
Come on, PRs are welcome.
</details>
See also: [Feature Preview: Gitea
Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/)
---------
Co-authored-by: a1012112796 <1012112796@qq.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
2023-01-31 02:45:19 +01:00
|
|
|
actions_router "code.gitea.io/gitea/routers/api/actions"
|
2023-02-07 11:23:49 +01:00
|
|
|
forgejo "code.gitea.io/gitea/routers/api/forgejo/v1"
|
2022-03-30 10:42:47 +02:00
|
|
|
packages_router "code.gitea.io/gitea/routers/api/packages"
|
2021-06-09 01:33:54 +02:00
|
|
|
apiv1 "code.gitea.io/gitea/routers/api/v1"
|
|
|
|
"code.gitea.io/gitea/routers/common"
|
|
|
|
"code.gitea.io/gitea/routers/private"
|
|
|
|
web_routers "code.gitea.io/gitea/routers/web"
|
Implement actions (#21937)
Close #13539.
Co-authored by: @lunny @appleboy @fuxiaohei and others.
Related projects:
- https://gitea.com/gitea/actions-proto-def
- https://gitea.com/gitea/actions-proto-go
- https://gitea.com/gitea/act
- https://gitea.com/gitea/act_runner
### Summary
The target of this PR is to bring a basic implementation of "Actions",
an internal CI/CD system of Gitea. That means even though it has been
merged, the state of the feature is **EXPERIMENTAL**, and please note
that:
- It is disabled by default;
- It shouldn't be used in a production environment currently;
- It shouldn't be used in a public Gitea instance currently;
- Breaking changes may be made before it's stable.
**Please comment on #13539 if you have any different product design
ideas**, all decisions reached there will be adopted here. But in this
PR, we don't talk about **naming, feature-creep or alternatives**.
### β οΈ Breaking
`gitea-actions` will become a reserved user name. If a user with the
name already exists in the database, it is recommended to rename it.
### Some important reviews
- What is `DEFAULT_ACTIONS_URL` in `app.ini` for?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1055954954
- Why the api for runners is not under the normal `/api/v1` prefix?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061173592
- Why DBFS?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061301178
- Why ignore events triggered by `gitea-actions` bot?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1063254103
- Why there's no permission control for actions?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1090229868
### What it looks like
<details>
#### Manage runners
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205870657-c72f590e-2e08-4cd4-be7f-2e0abb299bbf.png">
#### List runs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872794-50fde990-2b45-48c1-a178-908e4ec5b627.png">
#### View logs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872501-9b7b9000-9542-4991-8f55-18ccdada77c3.png">
</details>
### How to try it
<details>
#### 1. Start Gitea
Clone this branch and [install from
source](https://docs.gitea.io/en-us/install-from-source).
Add additional configurations in `app.ini` to enable Actions:
```ini
[actions]
ENABLED = true
```
Start it.
If all is well, you'll see the management page of runners:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205877365-8e30a780-9b10-4154-b3e8-ee6c3cb35a59.png">
#### 2. Start runner
Clone the [act_runner](https://gitea.com/gitea/act_runner), and follow
the
[README](https://gitea.com/gitea/act_runner/src/branch/main/README.md)
to start it.
If all is well, you'll see a new runner has been added:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205878000-216f5937-e696-470d-b66c-8473987d91c3.png">
#### 3. Enable actions for a repo
Create a new repo or open an existing one, check the `Actions` checkbox
in settings and submit.
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879705-53e09208-73c0-4b3e-a123-2dcf9aba4b9c.png">
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879383-23f3d08f-1a85-41dd-a8b3-54e2ee6453e8.png">
If all is well, you'll see a new tab "Actions":
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205881648-a8072d8c-5803-4d76-b8a8-9b2fb49516c1.png">
#### 4. Upload workflow files
Upload some workflow files to `.gitea/workflows/xxx.yaml`, you can
follow the [quickstart](https://docs.github.com/en/actions/quickstart)
of GitHub Actions. Yes, Gitea Actions is compatible with GitHub Actions
in most cases, you can use the same demo:
```yaml
name: GitHub Actions Demo
run-name: ${{ github.actor }} is testing out GitHub Actions π
on: [push]
jobs:
Explore-GitHub-Actions:
runs-on: ubuntu-latest
steps:
- run: echo "π The job was automatically triggered by a ${{ github.event_name }} event."
- run: echo "π§ This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- run: echo "π The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
- name: Check out repository code
uses: actions/checkout@v3
- run: echo "π‘ The ${{ github.repository }} repository has been cloned to the runner."
- run: echo "π₯οΈ The workflow is now ready to test your code on the runner."
- name: List files in the repository
run: |
ls ${{ github.workspace }}
- run: echo "π This job's status is ${{ job.status }}."
```
If all is well, you'll see a new run in `Actions` tab:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884473-79a874bc-171b-4aaf-acd5-0241a45c3b53.png">
#### 5. Check the logs of jobs
Click a run and you'll see the logs:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884800-994b0374-67f7-48ff-be9a-4c53f3141547.png">
#### 6. Go on
You can try more examples in [the
documents](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
of GitHub Actions, then you might find a lot of bugs.
Come on, PRs are welcome.
</details>
See also: [Feature Preview: Gitea
Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/)
---------
Co-authored-by: a1012112796 <1012112796@qq.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
2023-01-31 02:45:19 +01:00
|
|
|
actions_service "code.gitea.io/gitea/services/actions"
|
2021-06-09 19:53:16 +02:00
|
|
|
"code.gitea.io/gitea/services/auth"
|
2021-07-24 12:16:34 +02:00
|
|
|
"code.gitea.io/gitea/services/auth/source/oauth2"
|
2022-05-07 19:05:52 +02:00
|
|
|
"code.gitea.io/gitea/services/automerge"
|
2021-11-16 14:30:11 +01:00
|
|
|
"code.gitea.io/gitea/services/cron"
|
2019-09-24 07:02:49 +02:00
|
|
|
"code.gitea.io/gitea/services/mailer"
|
2023-01-14 16:57:10 +01:00
|
|
|
mailer_incoming "code.gitea.io/gitea/services/mailer/incoming"
|
2022-10-22 19:15:52 +02:00
|
|
|
markup_service "code.gitea.io/gitea/services/markup"
|
2021-11-16 16:25:33 +01:00
|
|
|
repo_migrations "code.gitea.io/gitea/services/migrations"
|
2019-10-01 15:40:17 +02:00
|
|
|
mirror_service "code.gitea.io/gitea/services/mirror"
|
2019-12-07 03:44:10 +01:00
|
|
|
pull_service "code.gitea.io/gitea/services/pull"
|
2021-11-17 16:17:31 +01:00
|
|
|
repo_service "code.gitea.io/gitea/services/repository"
|
2021-12-06 08:19:28 +01:00
|
|
|
"code.gitea.io/gitea/services/repository/archiver"
|
2021-11-18 07:47:57 +01:00
|
|
|
"code.gitea.io/gitea/services/task"
|
2020-12-08 11:41:14 +01:00
|
|
|
"code.gitea.io/gitea/services/webhook"
|
2016-11-24 08:40:16 +01:00
|
|
|
)
|
|
|
|
|
2021-10-21 11:22:43 +02:00
|
|
|
func mustInit(fn func() error) {
|
|
|
|
err := fn()
|
|
|
|
if err != nil {
|
|
|
|
ptr := reflect.ValueOf(fn).Pointer()
|
|
|
|
fi := runtime.FuncForPC(ptr)
|
|
|
|
log.Fatal("%s failed: %v", fi.Name(), err)
|
2020-08-18 06:23:45 +02:00
|
|
|
}
|
2021-10-21 11:22:43 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
func mustInitCtx(ctx context.Context, fn func(ctx context.Context) error) {
|
|
|
|
err := fn(ctx)
|
|
|
|
if err != nil {
|
|
|
|
ptr := reflect.ValueOf(fn).Pointer()
|
|
|
|
fi := runtime.FuncForPC(ptr)
|
|
|
|
log.Fatal("%s(ctx) failed: %v", fi.Name(), err)
|
2020-09-11 16:14:48 +02:00
|
|
|
}
|
2021-10-21 11:22:43 +02:00
|
|
|
}
|
|
|
|
|
2022-10-28 18:53:08 +02:00
|
|
|
func syncAppConfForGit(ctx context.Context) error {
|
2022-10-17 01:29:26 +02:00
|
|
|
runtimeState := new(system.RuntimeState)
|
|
|
|
if err := system.AppState.Get(runtimeState); err != nil {
|
2021-10-21 11:22:43 +02:00
|
|
|
return err
|
2021-07-10 23:54:15 +02:00
|
|
|
}
|
2022-10-28 18:53:08 +02:00
|
|
|
|
|
|
|
updated := false
|
2021-10-21 11:22:43 +02:00
|
|
|
if runtimeState.LastAppPath != setting.AppPath {
|
|
|
|
log.Info("AppPath changed from '%s' to '%s'", runtimeState.LastAppPath, setting.AppPath)
|
2022-10-28 18:53:08 +02:00
|
|
|
runtimeState.LastAppPath = setting.AppPath
|
|
|
|
updated = true
|
|
|
|
}
|
|
|
|
if runtimeState.LastCustomConf != setting.CustomConf {
|
|
|
|
log.Info("CustomConf changed from '%s' to '%s'", runtimeState.LastCustomConf, setting.CustomConf)
|
|
|
|
runtimeState.LastCustomConf = setting.CustomConf
|
|
|
|
updated = true
|
|
|
|
}
|
2021-10-21 11:22:43 +02:00
|
|
|
|
2022-10-28 18:53:08 +02:00
|
|
|
if updated {
|
2021-10-21 11:22:43 +02:00
|
|
|
log.Info("re-sync repository hooks ...")
|
2021-11-17 16:17:31 +01:00
|
|
|
mustInitCtx(ctx, repo_service.SyncRepositoryHooks)
|
2021-10-21 11:22:43 +02:00
|
|
|
|
|
|
|
log.Info("re-write ssh public keys ...")
|
2021-12-10 09:14:24 +01:00
|
|
|
mustInit(asymkey_model.RewriteAllPublicKeys)
|
2021-10-21 11:22:43 +02:00
|
|
|
|
2022-10-17 01:29:26 +02:00
|
|
|
return system.AppState.Set(runtimeState)
|
2021-06-23 23:12:38 +02:00
|
|
|
}
|
2021-10-21 11:22:43 +02:00
|
|
|
return nil
|
2016-11-24 08:40:16 +01:00
|
|
|
}
|
|
|
|
|
2021-12-01 08:50:01 +01:00
|
|
|
// GlobalInitInstalled is for global installed configuration.
|
|
|
|
func GlobalInitInstalled(ctx context.Context) {
|
2020-10-19 23:03:08 +02:00
|
|
|
if !setting.InstallLock {
|
|
|
|
log.Fatal("Gitea is not installed")
|
|
|
|
}
|
2021-01-27 04:57:18 +01:00
|
|
|
|
2022-08-09 05:22:24 +02:00
|
|
|
mustInitCtx(ctx, git.InitFull)
|
2023-04-19 15:40:42 +02:00
|
|
|
log.Info("Gitea Version: %s%s", setting.AppVer, setting.AppBuiltWith)
|
2022-06-10 03:57:49 +02:00
|
|
|
log.Info("Git Version: %s (home: %s)", git.VersionInfo(), git.HomeDir())
|
2021-06-27 02:56:58 +02:00
|
|
|
log.Info("AppPath: %s", setting.AppPath)
|
|
|
|
log.Info("AppWorkPath: %s", setting.AppWorkPath)
|
|
|
|
log.Info("Custom path: %s", setting.CustomPath)
|
2023-02-19 17:12:01 +01:00
|
|
|
log.Info("Log path: %s", setting.Log.RootPath)
|
2021-09-14 03:24:57 +02:00
|
|
|
log.Info("Configuration file: %s", setting.CustomConf)
|
2022-05-10 23:55:54 +02:00
|
|
|
log.Info("Run Mode: %s", util.ToTitleCase(setting.RunMode))
|
2019-08-24 11:24:45 +02:00
|
|
|
|
2020-05-17 01:31:38 +02:00
|
|
|
// Setup i18n
|
2022-08-28 11:43:25 +02:00
|
|
|
translation.InitLocales(ctx)
|
2020-05-17 01:31:38 +02:00
|
|
|
|
2023-02-19 17:12:01 +01:00
|
|
|
setting.LoadSettings()
|
2022-05-08 18:46:32 +02:00
|
|
|
mustInit(storage.Init)
|
|
|
|
|
2022-08-28 11:43:25 +02:00
|
|
|
mailer.NewContext(ctx)
|
2021-10-21 11:22:43 +02:00
|
|
|
mustInit(cache.NewContext)
|
|
|
|
notification.NewContext()
|
|
|
|
mustInit(archiver.Init)
|
2016-11-24 08:40:16 +01:00
|
|
|
|
2020-10-19 23:03:08 +02:00
|
|
|
highlight.NewContext()
|
2021-04-20 00:25:08 +02:00
|
|
|
external.RegisterRenderers()
|
2022-10-22 19:15:52 +02:00
|
|
|
markup.Init(markup_service.ProcessorHelper())
|
2021-01-27 04:57:18 +01:00
|
|
|
|
|
|
|
if setting.EnableSQLite3 {
|
2021-11-09 19:55:24 +01:00
|
|
|
log.Info("SQLite3 support is enabled")
|
2023-03-07 11:51:06 +01:00
|
|
|
} else if setting.Database.Type.IsSQLite3() {
|
2021-11-09 19:55:24 +01:00
|
|
|
log.Fatal("SQLite3 support is disabled, but it is used for database setting. Please get or build a Gitea release with SQLite3 support.")
|
2021-01-27 04:57:18 +01:00
|
|
|
}
|
2019-01-19 22:17:08 +01:00
|
|
|
|
2021-10-21 11:22:43 +02:00
|
|
|
mustInitCtx(ctx, common.InitDBEngine)
|
|
|
|
log.Info("ORM engine initialization successful!")
|
2022-10-17 01:29:26 +02:00
|
|
|
mustInit(system.Init)
|
2021-10-21 11:22:43 +02:00
|
|
|
mustInit(oauth2.Init)
|
2016-11-24 08:40:16 +01:00
|
|
|
|
2023-02-24 11:23:13 +01:00
|
|
|
mustInitCtx(ctx, models.Init)
|
2022-05-08 18:46:32 +02:00
|
|
|
mustInit(repo_service.Init)
|
2016-11-24 08:40:16 +01:00
|
|
|
|
2020-10-19 23:03:08 +02:00
|
|
|
// Booting long running goroutines.
|
|
|
|
issue_indexer.InitIssueIndexer(false)
|
|
|
|
code_indexer.Init()
|
2021-10-21 11:22:43 +02:00
|
|
|
mustInit(stats_indexer.Init)
|
|
|
|
|
2020-10-19 23:03:08 +02:00
|
|
|
mirror_service.InitSyncMirrors()
|
2022-04-25 20:03:01 +02:00
|
|
|
mustInit(webhook.Init)
|
2021-10-21 11:22:43 +02:00
|
|
|
mustInit(pull_service.Init)
|
2022-05-07 19:05:52 +02:00
|
|
|
mustInit(automerge.Init)
|
2021-10-21 11:22:43 +02:00
|
|
|
mustInit(task.Init)
|
|
|
|
mustInit(repo_migrations.Init)
|
2020-10-19 23:03:08 +02:00
|
|
|
eventsource.GetManager().Init()
|
2023-01-14 16:57:10 +01:00
|
|
|
mustInitCtx(ctx, mailer_incoming.Init)
|
2020-10-19 23:03:08 +02:00
|
|
|
|
2022-10-28 18:53:08 +02:00
|
|
|
mustInitCtx(ctx, syncAppConfForGit)
|
2021-10-21 11:22:43 +02:00
|
|
|
|
2022-07-10 08:50:26 +02:00
|
|
|
mustInit(ssh.Init)
|
|
|
|
|
2021-06-09 19:53:16 +02:00
|
|
|
auth.Init()
|
2023-04-12 12:16:45 +02:00
|
|
|
mustInit(svg.Init)
|
2022-07-15 17:20:05 +02:00
|
|
|
|
Implement actions (#21937)
Close #13539.
Co-authored by: @lunny @appleboy @fuxiaohei and others.
Related projects:
- https://gitea.com/gitea/actions-proto-def
- https://gitea.com/gitea/actions-proto-go
- https://gitea.com/gitea/act
- https://gitea.com/gitea/act_runner
### Summary
The target of this PR is to bring a basic implementation of "Actions",
an internal CI/CD system of Gitea. That means even though it has been
merged, the state of the feature is **EXPERIMENTAL**, and please note
that:
- It is disabled by default;
- It shouldn't be used in a production environment currently;
- It shouldn't be used in a public Gitea instance currently;
- Breaking changes may be made before it's stable.
**Please comment on #13539 if you have any different product design
ideas**, all decisions reached there will be adopted here. But in this
PR, we don't talk about **naming, feature-creep or alternatives**.
### β οΈ Breaking
`gitea-actions` will become a reserved user name. If a user with the
name already exists in the database, it is recommended to rename it.
### Some important reviews
- What is `DEFAULT_ACTIONS_URL` in `app.ini` for?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1055954954
- Why the api for runners is not under the normal `/api/v1` prefix?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061173592
- Why DBFS?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061301178
- Why ignore events triggered by `gitea-actions` bot?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1063254103
- Why there's no permission control for actions?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1090229868
### What it looks like
<details>
#### Manage runners
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205870657-c72f590e-2e08-4cd4-be7f-2e0abb299bbf.png">
#### List runs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872794-50fde990-2b45-48c1-a178-908e4ec5b627.png">
#### View logs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872501-9b7b9000-9542-4991-8f55-18ccdada77c3.png">
</details>
### How to try it
<details>
#### 1. Start Gitea
Clone this branch and [install from
source](https://docs.gitea.io/en-us/install-from-source).
Add additional configurations in `app.ini` to enable Actions:
```ini
[actions]
ENABLED = true
```
Start it.
If all is well, you'll see the management page of runners:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205877365-8e30a780-9b10-4154-b3e8-ee6c3cb35a59.png">
#### 2. Start runner
Clone the [act_runner](https://gitea.com/gitea/act_runner), and follow
the
[README](https://gitea.com/gitea/act_runner/src/branch/main/README.md)
to start it.
If all is well, you'll see a new runner has been added:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205878000-216f5937-e696-470d-b66c-8473987d91c3.png">
#### 3. Enable actions for a repo
Create a new repo or open an existing one, check the `Actions` checkbox
in settings and submit.
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879705-53e09208-73c0-4b3e-a123-2dcf9aba4b9c.png">
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879383-23f3d08f-1a85-41dd-a8b3-54e2ee6453e8.png">
If all is well, you'll see a new tab "Actions":
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205881648-a8072d8c-5803-4d76-b8a8-9b2fb49516c1.png">
#### 4. Upload workflow files
Upload some workflow files to `.gitea/workflows/xxx.yaml`, you can
follow the [quickstart](https://docs.github.com/en/actions/quickstart)
of GitHub Actions. Yes, Gitea Actions is compatible with GitHub Actions
in most cases, you can use the same demo:
```yaml
name: GitHub Actions Demo
run-name: ${{ github.actor }} is testing out GitHub Actions π
on: [push]
jobs:
Explore-GitHub-Actions:
runs-on: ubuntu-latest
steps:
- run: echo "π The job was automatically triggered by a ${{ github.event_name }} event."
- run: echo "π§ This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- run: echo "π The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
- name: Check out repository code
uses: actions/checkout@v3
- run: echo "π‘ The ${{ github.repository }} repository has been cloned to the runner."
- run: echo "π₯οΈ The workflow is now ready to test your code on the runner."
- name: List files in the repository
run: |
ls ${{ github.workspace }}
- run: echo "π This job's status is ${{ job.status }}."
```
If all is well, you'll see a new run in `Actions` tab:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884473-79a874bc-171b-4aaf-acd5-0241a45c3b53.png">
#### 5. Check the logs of jobs
Click a run and you'll see the logs:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884800-994b0374-67f7-48ff-be9a-4c53f3141547.png">
#### 6. Go on
You can try more examples in [the
documents](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
of GitHub Actions, then you might find a lot of bugs.
Come on, PRs are welcome.
</details>
See also: [Feature Preview: Gitea
Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/)
---------
Co-authored-by: a1012112796 <1012112796@qq.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
2023-01-31 02:45:19 +01:00
|
|
|
actions_service.Init()
|
|
|
|
|
2022-07-15 17:20:05 +02:00
|
|
|
// Finally start up the cron
|
|
|
|
cron.NewContext(ctx)
|
2016-11-24 08:40:16 +01:00
|
|
|
}
|
2021-06-09 01:33:54 +02:00
|
|
|
|
|
|
|
// NormalRoutes represents non install routes
|
2023-06-05 11:04:47 +02:00
|
|
|
func NormalRoutes(middlewares ...any) *web.Route {
|
2023-04-30 14:22:23 +02:00
|
|
|
_ = templates.HTMLRenderer()
|
2021-06-09 01:33:54 +02:00
|
|
|
r := web.NewRoute()
|
2023-04-27 08:06:45 +02:00
|
|
|
r.Use(common.ProtocolMiddlewares()...)
|
2021-06-09 01:33:54 +02:00
|
|
|
|
2023-06-05 11:04:47 +02:00
|
|
|
r.Mount("/", web_routers.Routes(middlewares...))
|
2023-06-18 09:59:09 +02:00
|
|
|
r.Mount("/api/v1", apiv1.Routes())
|
2023-02-07 11:23:49 +01:00
|
|
|
r.Mount("/api/forgejo/v1", forgejo.Routes())
|
2021-06-09 01:33:54 +02:00
|
|
|
r.Mount("/api/internal", private.Routes())
|
2022-11-12 19:59:15 +01:00
|
|
|
|
2023-06-16 08:32:43 +02:00
|
|
|
r.Post("/-/fetch-redirect", common.FetchRedirectDelegate)
|
|
|
|
|
2022-03-30 10:42:47 +02:00
|
|
|
if setting.Packages.Enabled {
|
2022-11-12 19:59:15 +01:00
|
|
|
// This implements package support for most package managers
|
2023-06-18 09:59:09 +02:00
|
|
|
r.Mount("/api/packages", packages_router.CommonRoutes())
|
2022-11-12 19:59:15 +01:00
|
|
|
// This implements the OCI API (Note this is not preceded by /api but is instead /v2)
|
2023-06-18 09:59:09 +02:00
|
|
|
r.Mount("/v2", packages_router.ContainerRoutes())
|
2022-03-30 10:42:47 +02:00
|
|
|
}
|
Implement actions (#21937)
Close #13539.
Co-authored by: @lunny @appleboy @fuxiaohei and others.
Related projects:
- https://gitea.com/gitea/actions-proto-def
- https://gitea.com/gitea/actions-proto-go
- https://gitea.com/gitea/act
- https://gitea.com/gitea/act_runner
### Summary
The target of this PR is to bring a basic implementation of "Actions",
an internal CI/CD system of Gitea. That means even though it has been
merged, the state of the feature is **EXPERIMENTAL**, and please note
that:
- It is disabled by default;
- It shouldn't be used in a production environment currently;
- It shouldn't be used in a public Gitea instance currently;
- Breaking changes may be made before it's stable.
**Please comment on #13539 if you have any different product design
ideas**, all decisions reached there will be adopted here. But in this
PR, we don't talk about **naming, feature-creep or alternatives**.
### β οΈ Breaking
`gitea-actions` will become a reserved user name. If a user with the
name already exists in the database, it is recommended to rename it.
### Some important reviews
- What is `DEFAULT_ACTIONS_URL` in `app.ini` for?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1055954954
- Why the api for runners is not under the normal `/api/v1` prefix?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061173592
- Why DBFS?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061301178
- Why ignore events triggered by `gitea-actions` bot?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1063254103
- Why there's no permission control for actions?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1090229868
### What it looks like
<details>
#### Manage runners
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205870657-c72f590e-2e08-4cd4-be7f-2e0abb299bbf.png">
#### List runs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872794-50fde990-2b45-48c1-a178-908e4ec5b627.png">
#### View logs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872501-9b7b9000-9542-4991-8f55-18ccdada77c3.png">
</details>
### How to try it
<details>
#### 1. Start Gitea
Clone this branch and [install from
source](https://docs.gitea.io/en-us/install-from-source).
Add additional configurations in `app.ini` to enable Actions:
```ini
[actions]
ENABLED = true
```
Start it.
If all is well, you'll see the management page of runners:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205877365-8e30a780-9b10-4154-b3e8-ee6c3cb35a59.png">
#### 2. Start runner
Clone the [act_runner](https://gitea.com/gitea/act_runner), and follow
the
[README](https://gitea.com/gitea/act_runner/src/branch/main/README.md)
to start it.
If all is well, you'll see a new runner has been added:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205878000-216f5937-e696-470d-b66c-8473987d91c3.png">
#### 3. Enable actions for a repo
Create a new repo or open an existing one, check the `Actions` checkbox
in settings and submit.
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879705-53e09208-73c0-4b3e-a123-2dcf9aba4b9c.png">
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879383-23f3d08f-1a85-41dd-a8b3-54e2ee6453e8.png">
If all is well, you'll see a new tab "Actions":
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205881648-a8072d8c-5803-4d76-b8a8-9b2fb49516c1.png">
#### 4. Upload workflow files
Upload some workflow files to `.gitea/workflows/xxx.yaml`, you can
follow the [quickstart](https://docs.github.com/en/actions/quickstart)
of GitHub Actions. Yes, Gitea Actions is compatible with GitHub Actions
in most cases, you can use the same demo:
```yaml
name: GitHub Actions Demo
run-name: ${{ github.actor }} is testing out GitHub Actions π
on: [push]
jobs:
Explore-GitHub-Actions:
runs-on: ubuntu-latest
steps:
- run: echo "π The job was automatically triggered by a ${{ github.event_name }} event."
- run: echo "π§ This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- run: echo "π The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
- name: Check out repository code
uses: actions/checkout@v3
- run: echo "π‘ The ${{ github.repository }} repository has been cloned to the runner."
- run: echo "π₯οΈ The workflow is now ready to test your code on the runner."
- name: List files in the repository
run: |
ls ${{ github.workspace }}
- run: echo "π This job's status is ${{ job.status }}."
```
If all is well, you'll see a new run in `Actions` tab:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884473-79a874bc-171b-4aaf-acd5-0241a45c3b53.png">
#### 5. Check the logs of jobs
Click a run and you'll see the logs:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884800-994b0374-67f7-48ff-be9a-4c53f3141547.png">
#### 6. Go on
You can try more examples in [the
documents](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
of GitHub Actions, then you might find a lot of bugs.
Come on, PRs are welcome.
</details>
See also: [Feature Preview: Gitea
Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/)
---------
Co-authored-by: a1012112796 <1012112796@qq.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
2023-01-31 02:45:19 +01:00
|
|
|
|
|
|
|
if setting.Actions.Enabled {
|
|
|
|
prefix := "/api/actions"
|
2023-06-18 09:59:09 +02:00
|
|
|
r.Mount(prefix, actions_router.Routes(prefix))
|
2023-05-19 15:37:57 +02:00
|
|
|
|
|
|
|
// TODO: Pipeline api used for runner internal communication with gitea server. but only artifact is used for now.
|
|
|
|
// In Github, it uses ACTIONS_RUNTIME_URL=https://pipelines.actions.githubusercontent.com/fLgcSHkPGySXeIFrg8W8OBSfeg3b5Fls1A1CwX566g8PayEGlg/
|
|
|
|
// TODO: this prefix should be generated with a token string with runner ?
|
|
|
|
prefix = "/api/actions_pipeline"
|
2023-05-21 03:50:53 +02:00
|
|
|
r.Mount(prefix, actions_router.ArtifactsRoutes(prefix))
|
Implement actions (#21937)
Close #13539.
Co-authored by: @lunny @appleboy @fuxiaohei and others.
Related projects:
- https://gitea.com/gitea/actions-proto-def
- https://gitea.com/gitea/actions-proto-go
- https://gitea.com/gitea/act
- https://gitea.com/gitea/act_runner
### Summary
The target of this PR is to bring a basic implementation of "Actions",
an internal CI/CD system of Gitea. That means even though it has been
merged, the state of the feature is **EXPERIMENTAL**, and please note
that:
- It is disabled by default;
- It shouldn't be used in a production environment currently;
- It shouldn't be used in a public Gitea instance currently;
- Breaking changes may be made before it's stable.
**Please comment on #13539 if you have any different product design
ideas**, all decisions reached there will be adopted here. But in this
PR, we don't talk about **naming, feature-creep or alternatives**.
### β οΈ Breaking
`gitea-actions` will become a reserved user name. If a user with the
name already exists in the database, it is recommended to rename it.
### Some important reviews
- What is `DEFAULT_ACTIONS_URL` in `app.ini` for?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1055954954
- Why the api for runners is not under the normal `/api/v1` prefix?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061173592
- Why DBFS?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061301178
- Why ignore events triggered by `gitea-actions` bot?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1063254103
- Why there's no permission control for actions?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1090229868
### What it looks like
<details>
#### Manage runners
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205870657-c72f590e-2e08-4cd4-be7f-2e0abb299bbf.png">
#### List runs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872794-50fde990-2b45-48c1-a178-908e4ec5b627.png">
#### View logs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872501-9b7b9000-9542-4991-8f55-18ccdada77c3.png">
</details>
### How to try it
<details>
#### 1. Start Gitea
Clone this branch and [install from
source](https://docs.gitea.io/en-us/install-from-source).
Add additional configurations in `app.ini` to enable Actions:
```ini
[actions]
ENABLED = true
```
Start it.
If all is well, you'll see the management page of runners:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205877365-8e30a780-9b10-4154-b3e8-ee6c3cb35a59.png">
#### 2. Start runner
Clone the [act_runner](https://gitea.com/gitea/act_runner), and follow
the
[README](https://gitea.com/gitea/act_runner/src/branch/main/README.md)
to start it.
If all is well, you'll see a new runner has been added:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205878000-216f5937-e696-470d-b66c-8473987d91c3.png">
#### 3. Enable actions for a repo
Create a new repo or open an existing one, check the `Actions` checkbox
in settings and submit.
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879705-53e09208-73c0-4b3e-a123-2dcf9aba4b9c.png">
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879383-23f3d08f-1a85-41dd-a8b3-54e2ee6453e8.png">
If all is well, you'll see a new tab "Actions":
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205881648-a8072d8c-5803-4d76-b8a8-9b2fb49516c1.png">
#### 4. Upload workflow files
Upload some workflow files to `.gitea/workflows/xxx.yaml`, you can
follow the [quickstart](https://docs.github.com/en/actions/quickstart)
of GitHub Actions. Yes, Gitea Actions is compatible with GitHub Actions
in most cases, you can use the same demo:
```yaml
name: GitHub Actions Demo
run-name: ${{ github.actor }} is testing out GitHub Actions π
on: [push]
jobs:
Explore-GitHub-Actions:
runs-on: ubuntu-latest
steps:
- run: echo "π The job was automatically triggered by a ${{ github.event_name }} event."
- run: echo "π§ This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- run: echo "π The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
- name: Check out repository code
uses: actions/checkout@v3
- run: echo "π‘ The ${{ github.repository }} repository has been cloned to the runner."
- run: echo "π₯οΈ The workflow is now ready to test your code on the runner."
- name: List files in the repository
run: |
ls ${{ github.workspace }}
- run: echo "π This job's status is ${{ job.status }}."
```
If all is well, you'll see a new run in `Actions` tab:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884473-79a874bc-171b-4aaf-acd5-0241a45c3b53.png">
#### 5. Check the logs of jobs
Click a run and you'll see the logs:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884800-994b0374-67f7-48ff-be9a-4c53f3141547.png">
#### 6. Go on
You can try more examples in [the
documents](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
of GitHub Actions, then you might find a lot of bugs.
Come on, PRs are welcome.
</details>
See also: [Feature Preview: Gitea
Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/)
---------
Co-authored-by: a1012112796 <1012112796@qq.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
2023-01-31 02:45:19 +01:00
|
|
|
}
|
|
|
|
|
2021-06-09 01:33:54 +02:00
|
|
|
return r
|
|
|
|
}
|