Revive continuous integration system #18

New issue

Open

opened 2024-11-11 16:31:13 +00:00 by glen · 2 comments

glen commented

2024-11-11 16:31:13 +00:00

Owner

Goals

Whenever we open or add commits to a pull request, do the following tasks in app-proto:

Build the application.
Build and run the Cargo tests.
Build and run the examples.

Only allow the pull request to be merged under the following conditions:

All three build targets compile successfully and without warnings.
The tests all pass.
The examples run without errors.

Implementation

@glen

Configure Forgejo Actions.
Install a Forgejo Runner.
- "For security reasons it is not recommended to install the runner on the same machine as the main instance."

@Vectornaut

Write the actions.
Write a script that runs the action steps directly on the development machine.
- Use Python if we need to parse YAML or something like that. Otherwise, a shell script is fine.

### Goals Whenever we open or add commits to a pull request, do the following tasks in [`app-proto`](src/branch/main/app-proto): - Build the application. - Build and run the Cargo tests. - Build and run the examples. Only allow the pull request to be merged under the following conditions: - All three build targets compile successfully and without warnings. - The tests all pass. - The examples run without errors. ### Implementation #### @glen - [x] [Configure](https://forgejo.org/docs/next/admin/actions/) Forgejo Actions. - [ ] [Install](https://forgejo.org/docs/latest/admin/runner-installation/) a Forgejo Runner. - "For security reasons it is not recommended to install the runner on the same machine as the main instance." #### @Vectornaut - [x] [Write](https://forgejo.org/docs/latest/user/actions/) the actions. - [ ] Write a script that runs the action steps directly on the development machine. - Use Python if we need to parse YAML or something like that. Otherwise, a shell script is fine.

Vectornaut changed title from ~~Revive gitea CI and add test that app-proto compiles without warnings.~~ to Revive continuous integration system

2025-02-25 22:03:35 +00:00

Vectornaut self-assigned this 2025-02-28 22:35:44 +00:00

glen was assigned by Vectornaut

2025-02-28 22:35:53 +00:00

glen commented

2025-02-28 23:53:08 +00:00

Author

Owner

@glen wrote in glen/dyna3#18 (comment):

Configure Forgejo Actions.

I don't actually see anything that needs to be done, do you? It seems like the defaults are all fine... Do you see any parameters that actually need to be set?

@glen wrote in https://code.studioinfinity.org/glen/dyna3/issues/18#issue-421: > * [Configure](https://forgejo.org/docs/next/admin/actions/) Forgejo Actions. I don't actually see anything that needs to be done, do you? It seems like the defaults are all fine... Do you see any parameters that actually need to be set?

Vectornaut commented

2025-03-04 01:43:17 +00:00

Member

I don't actually see anything that needs to be done, do you? It seems like the defaults are all fine...

After looking it over during today's meeting, I agree that it seems possible to set up Forgejo Actions without doing anything in the Actions admin guide. It looks like it'll be enough to follow the runner setup guide and then write some actions.

> I don't actually see anything that needs to be done, do you? It seems like the defaults are all fine... After looking it over during today's meeting, I agree that it seems possible to set up Forgejo Actions without doing anything in the [Actions admin guide](https://forgejo.org/docs/next/admin/actions/). It looks like it'll be enough to follow the runner setup guide and then write some actions.

glen added the

maintenance

label 2025-03-12 22:38:46 +00:00

Vectornaut referenced this issue

2025-03-14 00:05:19 +00:00

Set up continuous integration in Forgejo #75