WIP: automated-testing #9

Draft

cascode wants to merge 30 commits from automated-testing into main

pull from: automated-testing

merge into: MountainTownTechnology:main

MountainTownTechnology:main

MountainTownTechnology:setup-initial-schema

MountainTownTechnology:docs-formatting

Conversation 2 Commits 30 Files Changed 3 +52 -2

cascode commented 2023-10-21 16:14:38 -04:00

Collaborator

Copy Link

#3

Using gitea actions runner for automated lint, build, and test.

When a PR is opened or a push is made to main or a push is made to a branch that has an open PR, if it includes changes to the cargo files or files in the src directory, then these checks will run in CI.

The builder image is based on an official rust builder on alpine. It may make more sense to use one of their debian-based images as the base instead; up for discussion, i just have personal preference towards alpine. added a dockerfile for the builder in the ci folder.

if we increase the max upload size on nginx, then i can upload the builder image to the communitymedia container registry and change all the image tags to refer there (which will make the ci workflow portable outside of just my personal runner)

right now we have one runner on one of my machines. the gitea runner documentation is kinda bad and the feature itself feels pretty beta (at least in comparison to gitlab), ran into some weird stuff. but it's working ok now. i can document some of that in an additional ci-readme if that would be useful. setting up new runners should be pretty straightforward now that i understand the process.

TODO before merging:

• switch images to use container registry
• only run checks when committing code or cargo changes

TODO at some future date tbd, i can make a new issue for these:

• caching build from build stage to test stage
• caching build or deps from one workflow execution to the next
• caching git checkout from one stage to the next

(i feel ok leaving these as-is for now because i'm the only one who may incur costs from this lack of caching right now, since mine is the only runner)

#3 Using gitea actions runner for automated lint, build, and test. When a PR is opened or a push is made to main or a push is made to a branch that has an open PR, if it includes changes to the cargo files or files in the src directory, then these checks will run in CI. The builder image is based on an official rust builder on alpine. It may make more sense to use one of their debian-based images as the base instead; up for discussion, i just have personal preference towards alpine. added a dockerfile for the builder in the ci folder. **if we increase the max upload size on nginx**, then i can upload the builder image to the communitymedia container registry and change all the image tags to refer there (which will make the ci workflow portable outside of just my personal runner) right now we have one runner on one of my machines. the gitea runner documentation is kinda bad and the feature itself feels pretty beta (at least in comparison to gitlab), ran into some weird stuff. but it's working ok now. i can document some of that in an additional ci-readme if that would be useful. setting up new runners should be pretty straightforward now that i understand the process. TODO before merging: - [ ] switch images to use container registry - [x] only run checks when committing code or cargo changes TODO at some future date tbd, i can make a new issue for these: - caching build from build stage to test stage - caching build or deps from one workflow execution to the next - caching git checkout from one stage to the next (i feel ok leaving these as-is for now because i'm the only one who may incur costs from this lack of caching right now, since mine is the only runner)

cascode added 18 commits 2023-10-21 16:14:39 -04:00

0e92eda123 add automated format check

b53c875eac test

a27214c8da Revert "test" ...

This reverts commit 81158ca818.

b98fd1352a add rustfmt

35bb9081ab add debug ls

7e49f33b95 add debug ls

9c97e00d5a add checkout

8fb226fafd add node

2659b641ba test

a32e7757c5 test

f55d57c8ef fix fmt

e56a40a469 move some steps into the base image

3ef2eff8c3 automated build and test

668e5dbacd names and images changes

d6dfe7e525 image changes

c287334af2 add build deps to ci docker image

c7b13c2572 image changes

563f6dd3e4 only run for push on main, or for pr

cascode added 1 commit 2023-10-21 16:16:02 -04:00

39391d17a4 reorder triggers

cascode added 1 commit 2023-10-21 16:17:23 -04:00

3fa9d65966 change triggers

cascode added 1 commit 2023-10-21 16:24:52 -04:00

763ebea60a change triggers

cascode commented 2023-10-21 16:28:52 -04:00

Author

Collaborator

Copy Link

also, are we going to do PR squashes, or should i squash this myself before merge?

also, are we going to do PR squashes, or should i squash this myself before merge?

cascode requested review from ajr 2023-10-21 16:29:16 -04:00

cascode requested review from sundog 2023-10-21 16:29:16 -04:00

cascode requested review from vulfox 2023-10-21 16:29:32 -04:00

cascode added 1 commit 2023-10-21 16:40:10 -04:00

7682dc022c try removing runner tag

cascode added 1 commit 2023-10-21 16:41:37 -04:00

cf0d51fca5 remove runner tag

cascode added 1 commit 2023-10-21 16:50:40 -04:00

79d263cbb7 only run on some path changes

cascode added 1 commit 2023-10-21 16:54:39 -04:00

06708f6038 re-merge file

cascode added 1 commit 2023-10-21 17:10:53 -04:00

a0e6005acd more concise

cascode added 2 commits 2023-10-21 17:12:22 -04:00

f9417f49de Revert "more concise" ...

This reverts commit a0e6005acd.

3cad519f00 more concise

cascode added 1 commit 2023-10-21 17:14:09 -04:00

0c3ecb2730 var for images

cascode added 1 commit 2023-10-21 17:14:41 -04:00

13d7fce0be Revert "var for images" ...

This reverts commit 0c3ecb2730.

enot commented 2023-10-21 18:48:41 -04:00

Collaborator

Copy Link

also, are we going to do PR squashes, or should i squash this myself before merge?

I vote PR squashes, that way we can get a little messy but just squash to merge.

> also, are we going to do PR squashes, or should i squash this myself before merge? I vote PR squashes, that way we can get a little messy but just squash to merge.

👍 2

cascode force-pushed automated-testing from 13d7fce0be to 1d1f05cfb6 2023-10-26 20:32:29 -04:00 Compare

cascode force-pushed automated-testing from 1d1f05cfb6 to d85d6285d2 2023-10-26 20:34:17 -04:00 Compare

All checks were successful

checks / lint (pull_request) Successful in 5s

Details

checks / build (pull_request) Successful in 2m15s

Details

checks / test (pull_request) Successful in 2m9s

Details

This pull request is marked as a work in progress.

This branch is out-of-date with the base branch

You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.

git checkout -b automated-testing main

git pull origin automated-testing

Step 2:

Merge the changes and update on Gitea.

git checkout main

git merge --no-ff automated-testing

git push origin main

Sign in to join this conversation.

Reviewers

No reviewers

ajr

sundog

vulfox

Labels

Clear labels   

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

wontfix

This won't be fixed

No Label

bug

duplicate

enhancement

help wanted

invalid

question

wontfix

Milestone

Clear milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

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: MountainTownTechnology/aural_isle#9

No description provided.