Skip to content
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

Optimize CI Pipeline #209

Open
SoulKa opened this issue Jan 26, 2025 · 0 comments
Open

Optimize CI Pipeline #209

SoulKa opened this issue Jan 26, 2025 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers setup Initial Setup has to be done testing Issue related to implementing test automation

Comments

@SoulKa
Copy link
Collaborator

SoulKa commented Jan 26, 2025

Is your feature request related to a problem? Please describe.
Inmost cases, The CI pipeline takes longer than it needs, since it runs npm run package which tests if the code is buildable.

Describe the solution you'd like
In my opinion, it's enough to test if the application is buildable if any dependency changed (package.json or package-lock.json was modified). If they are unchange in a PR, the npm run package step should be skipped.

What else could be changed
Please check if it makes sense to add an automerge to the dependerbot.
Allow also. EXXETA#123 in the commit-message
allow everything when branch starts with fix/ feature/

@SoulKa SoulKa added enhancement New feature or request good first issue Good for newcomers setup Initial Setup has to be done testing Issue related to implementing test automation labels Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers setup Initial Setup has to be done testing Issue related to implementing test automation
Projects
None yet
Development

No branches or pull requests

1 participant