WIP: ci-action #55
No reviewers
Labels
No Label
bug
component
executor
component
framework
component
parser
component
UI
duplicate
enhancement
help wanted
invalid
priority
p0
priority
p1
priority
p2
priority
p3
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: JOJ/JOJ3#55
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "ci-action"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Current idea is first create env for build work s.t. the pr check will be faster after that if update env is needed, update the ci-test image.
Where is the ci-test image built?
OK, I see it.
But how much time does it save compared to the original workflow?
about 1 min if no update in teapot for job building
I re-run the build / build (push) here and it keeps using about 90s?
You should wait for a Linux server to develop if each test takes you 90s.
i mean 1 min faster
yes, 150-60=90, but it is still too slow for development
The joint-teapot setup has now been removed from the master branch, making it faster.
Close it for now. Will reuse it if we need joint-teapot in CI in the future.
So the bottleneck now is how to cache linters used by golangci-lint when building the runner image. We can not use actions/cache here so there is no easy solution.
Pull request closed