Template

mirror of https://codeberg.org/forgejo/forgejo synced 2024-11-30 13:56:09 +01: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 09:45:19 +08:00

20 KiB

Raw Blame History

date

title

slug

weight

toc

draft

2019-02-14T11:51:04+08:00

横向对比 Gitea 与其它 Git 托管工具

comparison

false

sidebar

parent	name	weight	identifier
features	横向对比	5	comparison

横向对比 Gitea 与其它 Git 托管工具

这里列出了 Gitea 与其它一些 Git 托管工具之间的异同，以便确认 Gitea 是否能够满足您的需求。

请注意，此列表中的某些表项可能已经过时，因为我们并没有定期检查其它产品的功能是否有所更改。你可以前往 Github issue 来帮助我们更新过时的内容，感谢！

表格中的符号含义:

✓ - 支持
⁄ - 部分支持
✘ - 不支持
? - 不确定

主要特性

特性	Gitea	Gogs	GitHub EE	GitLab CE	GitLab EE	BitBucket	RhodeCode CE
开源免费	✓	✓	✘	✓	✘	✘	✓
低资源开销 (RAM/CPU)	✓	✓	✘	✘	✘	✘	✘
支持多种数据库	✓	✓	✘	⁄	⁄	✓	✓
支持多种操作系统	✓	✓	✘	✘	✘	✘	✓
升级简便	✓	✓	✘	✓	✓	✘	✓
支持 Markdown	✓	✓	✓	✓	✓	✓	✓
支持 Orgmode	✓	✘	✓	✘	✘	✘	?
支持 CSV	✓	✘	✓	✘	✘	✓	?
支持第三方渲染工具	✓	✘	✘	✘	✘	✓	?
Git 驱动的静态 pages	✘	✘	✓	✓	✓	✘	✘
Git 驱动的集成化 wiki	✓	✓	✓	✓	✓	✓ (cloud only)	✘
部署令牌	✓	✓	✓	✓	✓	✓	✓
仓库写权限令牌	✓	✘	✓	✓	✓	✓	✓
内置容器 Registry	✓	✘	✓	✓	✓	✘	✘
外部 Git 镜像	✓	✓	✘	✘	✓	✓	✓
WebAuthn (2FA)	✓	✘	✓	✓	✓	✓	?
内置 CI/CD	✓	✘	✓	✓	✓	✘	✘
子组织：组织内的组织	✘	✘	✘	✓	✓	✘	✓

代码管理

特性	Gitea	Gogs	GitHub EE	GitLab CE	GitLab EE	BitBucket	RhodeCode CE
仓库主题描述	✓	✘	✓	✓	✓	✘	✘
仓库内代码搜索	✓	✘	✓	✓	✓	✓	✓
全局代码搜索	✓	✘	✓	✘	✓	✓	✓
Git LFS 2.0	✓	✘	✓	✓	✓	✓	✓
组织里程碑	✘	✘	✘	✓	✓	✘	✘
细粒度用户角色 (例如 Code, Issues, Wiki)	✓	✘	✘	✓	✓	✘	✘
提交人的身份验证	⁄	✘	?	✓	✓	✓	✘
GPG 签名的提交	✓	✘	✓	✓	✓	✓	✓
SSH 签名的提交	✓	✘	✘	✘	✘	?	?
拒绝未用通过验证的提交	✓	✘	✓	✓	✓	✓	✓
仓库活跃度页面	✓	✘	✓	✓	✓	✓	✓
分支管理	✓	✘	✓	✓	✓	✓	✓
建立新分支	✓	✘	✓	✓	✓	✘	✘
在线代码编辑	✓	✓	✓	✓	✓	✓	✓
提交的统计图表	✓	✘	✓	✓	✓	✓	✓
模板仓库	✓	✘	✓	✘	✓	✓	✘

工单管理

特性	Gitea	Gogs	GitHub EE	GitLab CE	GitLab EE	BitBucket	RhodeCode CE
工单跟踪	✓	✓	✓	✓	✓	✓ (cloud only)	✘
工单模板	✓	✓	✓	✓	✓	✘	✘
标签	✓	✓	✓	✓	✓	✘	✘
时间跟踪	✓	✘	✓	✓	✓	✘	✘
支持多个负责人	✓	✘	✓	✘	✓	✘	✘
关联的工单	✘	✘	⁄	✓	✓	✘	✘
私密工单	✘	✘	✘	✓	✓	✘	✘
评论反馈	✓	✘	✓	✓	✓	✘	✘
锁定讨论	✓	✘	✓	✓	✓	✘	✘
工单批处理	✓	✘	✓	✓	✓	✘	✘
工单看板	✓	✘	✘	✓	✓	✘	✘
从工单创建分支	✘	✘	✘	✓	✓	✘	✘
工单搜索	✓	✘	✓	✓	✓	✓	✘
工单全局搜索	✘	✘	✓	✓	✓	✓	✘
工单依赖关系	✓	✘	✘	✘	✘	✘	✘
通过 Email 创建工单	✘	✘	✘	✓	✓	✓	✘
服务台	✘	✘	✘	✓	✓	✘	✘

Pull/Merge requests

特性	Gitea	Gogs	GitHub EE	GitLab CE	GitLab EE	BitBucket	RhodeCode CE
Pull/Merge requests	✓	✓	✓	✓	✓	✓	✓
Squash merging	✓	✘	✓	✓	✓	✓	✓
Rebase merging	✓	✓	✓	✘	⁄	✘	✓
评论 Pull/Merge request 中的某行代码	✓	✘	✓	✓	✓	✓	✓
指定 Pull/Merge request 的审核人	✓	✘	⁄	✓	✓	✓	✓
解决 Merge 冲突	✘	✘	✓	✓	✓	✓	✘
限制某些用户的 push 和 merge 权限	✓	✘	✓	⁄	✓	✓	✓
回退某些 commits 或 merge request	✓	✘	✓	✓	✓	✓	✘
Pull/Merge requests 模板	✓	✓	✓	✓	✓	✘	✘
查看 Cherry-picking 的更改	✓	✘	✘	✓	✓	✘	✘
下载 Patch	✓	✘	✓	✓	✓	/	✘

第三方集成

特性	Gitea	Gogs	GitHub EE	GitLab CE	GitLab EE	BitBucket	RhodeCode CE
支持 Webhook	✓	✓	✓	✓	✓	✓	✓
自定义 Git 钩子	✓	✓	✓	✓	✓	✓	✓
集成 AD / LDAP	✓	✓	✓	✓	✓	✓	✓
支持多个 LDAP / AD 服务	✓	✓	✘	✘	✓	✓	✓
LDAP 用户同步	✓	✘	✓	✓	✓	✓	✓
SAML 2.0 service provider	✘	✘	✓	✓	✓	✓	✘
支持 OpenId 连接	✓	✘	✓	✓	✓	?	✘
集成 OAuth 2.0（外部授权）	✓	✘	⁄	✓	✓	?	✓
作为 OAuth 2.0 provider	✓	✘	✓	✓	✓	✓	✘
二次验证 (2FA)	✓	✓	✓	✓	✓	✓	✘
集成 Mattermost/Slack	✓	✓	⁄	✓	✓	⁄	✓
集成 Discord	✓	✓	✓	✓	✓	✘	✘
集成 Microsoft Teams	✓	✘	✓	✓	✓	✓	✘
显示外部 CI/CD 的状态	✓	✘	✓	✓	✓	✓	✓

20 KiB Raw Blame History Unescape Escape

横向对比 Gitea 与其它 Git 托管工具

主要特性

代码管理

工单管理

Pull/Merge requests

第三方集成

20 KiB

Raw Blame History