-
-
Notifications
You must be signed in to change notification settings - Fork 317
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
Improve cicd #1424
Improve cicd #1424
Conversation
ildyria
commented
Jul 27, 2022
- add a linter step to catch early php syntax error.
- Add more structure and unify the CI.
- Still run test even if code style fails.
- Add support for artifact upload on master branch (which aims to simulate a master release build).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only have limited understanding of Github workflow files. I checked out the old Build.yml
and did a manual diff with the new CICD.yml
on my local machine as Github does not recognize that CICD.yml
is basically a merger of Build.yml
and phpstan.yml
plus some additions. From what I have seen it looks sane.
As I cannot say much about the workflow on the semantic level, I only have some less important comments about the syntax. I simply noticed some inconsistencies.
I will standardize the strings with double quotes (even though they are not necessary per say). |
The big difference is that there are dependencies between the different parts of the runs to potentially fail early. I just hope that the build artifact step will work on master. This should allow us to have a "release-like" zip file built on each commit on master, potentially allowing us to give the "lastest" build from master without having to build a formal release. :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With my little understand it looks good. Maybe we should just give it a try. 🙈
I believe you decided for without double quotes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I just spotted that after I had a look on the dependency graph. I believe we want to check for syntax errors here.
Addressed:
|
Apparently GitHub Actions diagrams are terrible at showing dependencies clearly (I accept that's a non-trivial task, and the interactive nature helps a lot, but it's still annoying) |