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

add automated format check 0e92eda123

test b53c875eac

Revert "test" ... a27214c8da

This reverts commit 81158ca818.

add rustfmt b98fd1352a

add debug ls 35bb9081ab

add debug ls 7e49f33b95

add checkout 9c97e00d5a

add node 8fb226fafd

test 2659b641ba

test a32e7757c5

fix fmt f55d57c8ef

move some steps into the base image e56a40a469

automated build and test 3ef2eff8c3

names and images changes 668e5dbacd

image changes d6dfe7e525

add build deps to ci docker image c287334af2

image changes c7b13c2572

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

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

reorder triggers 39391d17a4

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

change triggers 3fa9d65966

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

change triggers 763ebea60a

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

try removing runner tag 7682dc022c

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

remove runner tag cf0d51fca5

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

only run on some path changes 79d263cbb7

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

re-merge file 06708f6038

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

more concise a0e6005acd

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

Revert "more concise" ... f9417f49de

This reverts commit a0e6005acd.

more concise 3cad519f00

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

var for images 0c3ecb2730

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

Revert "var for images" ... 13d7fce0be

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

Hide all checks

checks / lint (pull_request) Successful in 5s

checks / build (pull_request) Successful in 2m15s

checks / test (pull_request) Successful in 2m9s

This pull request is marked as a work in progress.

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

View command line instructions

Checkout

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

git fetch -u origin automated-testing:automated-testing

git checkout automated-testing

Sign in to join this conversation.

Reviewers

No Reviewers

sundog

ajr

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

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

ajr andyc axle_r betodealmeida cascode dag enot nebunez rangerrick sundog tompurl vulfox

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MountainTownTechnology/aural_isle#9

No description provided.