CI ideas #1099

New Issue

Open

opened 2022-03-31 05:42:53 +00:00 by qwerty287 · 1 comment

qwerty287 commented

2022-03-31 05:42:53 +00:00

Collaborator

I'll describe some things I'd recommend to our CI service, this is mainly a summary issue:

use Woodpecker/Codeberg CI (#1104)
- we are using it already for tea4j-autodeploy
- this allows us to run checks on pull requests
we should run tests, at least on PRs
- unit tests
- integration tests (also see #1098, #1104 (comment))
- code coverage
we could require the formatting of Java files with the IntelliJ profile and the editorconfig to follow consistent code styles (#1155)
- I wrote a Woodpecker plugin for this task
linters are almost a necessary thing (see https://developer.android.com/studio/write/lint#commandline)
an idea on PRs: publish a build artifact, e.g. to the cloud we are using right now for releases, that allows easy testing - download APK, install, run
- would need credentials on PRs, we can protect this by requiring a confirmation for all builds (a feature for Woodpecker to make this better configurable is here)
once Woodpecker implemented cron jobs, we can automate locale updates (#141, for implementation on push see #1155)
we can block certain contents, also ideal for simple stuff (e.g. the use of @author instead of Author)
- another Woodpecker plugin I wrote can block or even require certain regular expressions

I'll describe some things I'd recommend to our CI service, this is mainly a summary issue: - [x] use Woodpecker/Codeberg CI (#1104) * we are using it already for tea4j-autodeploy * this allows us to run checks on pull requests - [ ] we should run tests, at least on PRs - [x] unit tests - [ ] integration tests (also see #1098, https://codeberg.org/gitnex/GitNex/pulls/1104#issuecomment-418282) - [ ] code coverage - [x] we could require the formatting of Java files with the IntelliJ profile and the editorconfig to follow consistent code styles (#1155) * I wrote [a Woodpecker plugin for this task](https://codeberg.org/qwerty287/woodpecker-intellij-formatter) - [ ] linters are almost a necessary thing (see https://developer.android.com/studio/write/lint#commandline) - [ ] an idea on PRs: publish a build artifact, e.g. to the cloud we are using right now for releases, that allows easy testing - download APK, install, run * would need credentials on PRs, we can protect this by requiring a confirmation for all builds (a feature for Woodpecker to make this better configurable is [here](https://github.com/woodpecker-ci/woodpecker/issues/819)) - [x] once [Woodpecker implemented cron jobs](https://github.com/woodpecker-ci/woodpecker/issues/8), we can automate locale updates (#141, for implementation on push see #1155) - [x] we can block certain contents, also ideal for simple stuff (e.g. the use of `@author` instead of `Author`) * another [Woodpecker plugin I wrote](https://codeberg.org/qwerty287/woodpecker-regex-check) can block or even require certain regular expressions

👍 1

qwerty287 added the

⚙️ CI

🧪 Testing

🗓️ Summary

labels 2022-03-31 05:42:53 +00:00

6543 commented

2022-03-31 23:47:24 +00:00

Collaborator

to the cron job thing ... this was a problem at gitea quite long too the cron tasks are relatively new to drone ...

what was done there was a step that would only exec on push event on master branch to update locales if needed.
so each merge you get to run a push to locales and then a pull

-> to migrate this to cron event later is easy afterwards ...

to the cron job thing ... this was a problem at gitea quite long too the cron tasks are relatively new to drone ... what was done there was a step that would only exec on push event on master branch to update locales if needed. so each merge you get to run a push to locales and then a pull -> to migrate this to cron event later is easy afterwards ...

👍 1

qwerty287 referenced this issue

2022-04-07 07:16:40 +00:00

Move to woodpecker CI #1104

mmarif referenced this issue from a commit

2022-05-13 17:35:10 +00:00

Move to woodpecker CI (#1104)

qwerty287 self-assigned this 2022-05-15 11:18:03 +00:00

~~qwerty287 referenced this issue 2022-06-14 05:48:27 +00:00~~

Fix bugs #1154

qwerty287 referenced this issue

2022-06-14 07:09:25 +00:00

Extend CI workflows #1155

6543 referenced this issue from a commit

2022-07-29 12:08:45 +00:00

Extend CI workflows (#1155)

No Branch/Tag Specified

Branches Tags

attachments

main

release-5.2

release-5.1

release-5.0

release-4.5

release-4.4

release-4.3

release-4.2

release-4.1

release-4.0

release-3.5

release-3.4

release-3.3

release-3.2

release-3.1

release-3.0

release-2.5

release-2.4

release-2.3

release-2.2

release-2.1

release-2.0

release-1.5

release-1.1

release-1.2

release-1.3

release-1.4

5.2.0

5.1.1

5.1.0

5.0.1

5.0.0

4.5.0

4.4.0

4.3.0

4.2.2

4.2.1

4.2.0

4.1.0

4.0.0

3.5.1

3.5.0

3.4.0

3.3.0

3.3.0-rc3

3.3.0-rc2

3.3.0-rc1

3.2.0

3.2.0-rc1

3.1.2

3.1.1

3.1.0

3.1.0-rc2

3.1.0-rc1

3.0.1

3.0.0

3.0.0-rc3

3.0.0-rc2

3.0.0-rc1

2.5.1

2.5.0

2.5.0-rc4

2.4.1

2.4.0

2.3.2

2.3.1

2.3.0

2.2.2

2.2.1

2.2.0

2.1.3

2.1.2

2.1.1

2.1.0

2.0.0

1.5.0

1.1.0

1.2.0

1.3.0

1.4.0

Labels

Clear labels

This won't get fixed

Related to the CI/CD

Contains or will result in breaking changes

Bugfix ported to a release branch for point release

Related to the user interface or experience

🪜 Upstream

🟦 Website

Related to the website

🙇‍♂️ Needs-help

🛰️ API-dependency

Requires and waits for changes in Gitea's API

🛡️ Blocked

Waits for something else that must be solved first

🏗️ Build

🗒️ Changelog

🗄️ Repository

Related to this repository and it's management

No Label

Milestone

Clear milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

No Assignees

qwerty287

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitnex/GitNex#1099

Reference in New Issue

Repository

gitnex/GitNex

Title

Body

There is no content yet.

Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?