Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Speed up woodpecker pipelines #1910

Closed
anbraten opened this issue Jul 1, 2023 · 3 comments
Closed

Speed up woodpecker pipelines #1910

anbraten opened this issue Jul 1, 2023 · 3 comments
Labels
build CI pipeline related enhancement improve existing features

Comments

@anbraten
Copy link
Member

anbraten commented Jul 1, 2023

The pipelines executed for PRs in this repo could be improved to save resources and speed up:

  • use more path filters
  • only push images if requested for a PR (could be done by adding a label to the PR)
  • only run build for amd64 architecture as cross-compiling is pretty slow
  • ...
@qwerty287 qwerty287 added build CI pipeline related enhancement improve existing features labels Jul 2, 2023
@qwerty287
Copy link
Contributor

What do you think about skipping test and web pipelines on master pushes/merging PRs? They only contain linters and test and since almost everything is done via PRs the code should be checked by them already when a commit is pushed to the PR.

@anbraten
Copy link
Member Author

anbraten commented Jul 2, 2023

Yeah sounds fine to me

@6543
Copy link
Member

6543 commented Jul 9, 2023

did some bits at #1966

qwerty287 added a commit that referenced this issue Aug 7, 2023
- Use workflow-global conditions to also skip the `clone` step for
`docs` and `web` workflows
- never run `test` and `web` for pushes (they're running for PRs and
every change we do must pass checks on PRs, so they're unnecessary)

#1910
@woodpecker-ci woodpecker-ci locked and limited conversation to collaborators Aug 8, 2023
@pat-s pat-s converted this issue into discussion #2172 Aug 8, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
build CI pipeline related enhancement improve existing features
Projects
None yet
Development

No branches or pull requests

3 participants