-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Extend exclude
with php
and dependencies
settings
#184
Extend exclude
with php
and dependencies
settings
#184
Conversation
ef05689
to
e0d6d97
Compare
@internalsystemerror is the CI failure related to what you fixed in #190 ? |
It looks like the only issue here is that it's no longer adding the |
e0d6d97
to
183a40c
Compare
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.
@boesing @internalsystemerror should I rebase and release this to |
It is not properly working yet, please ignore this for any release. I'll handle this once I find some time to work on this. There is no pressure on this topic and no high need (at least for me) as of now 👍🏼 |
Ok, just beware that it will go into |
Signed-off-by: Maximilian Bösing <[email protected]>
Signed-off-by: Maximilian Bösing <[email protected]>
This fixes the problem that the job name does not match for tools due to the fact that the name already contains the human-readable name containing the version and dependencies string. Signed-off-by: Maximilian Bösing <[email protected]>
Signed-off-by: Maximilian Bösing <[email protected]>
Signed-off-by: Maximilian Bösing <[email protected]>
ecfd879
to
5c3b655
Compare
The exclusion strategy, when it was introduced, was meant to handle exact job names. By having the new feature of excluding tool names as well, we should still support the fill job.name as well so that we can still properly exclude jobs based on the initial exclusion strategy. Signed-off-by: Maximilian Bösing <[email protected]>
…iguration` Signed-off-by: Maximilian Bösing <[email protected]>
With one of the newer versions of the matrix action, `test.env` files were introduced and thus have to be added to the new test cases as well. Signed-off-by: Maximilian Bösing <[email protected]>
This allows us to reference to that definition which eases the usage in several parts of the configuration. Having the list of supported PHP versions maintained in more than one location may become annoying and thus this changes makes a lot of sense. Signed-off-by: Maximilian Bösing <[email protected]>
This was introduced in a more recent matrix version and thus was missing the expected matrix from the initial version of this feature. Signed-off-by: Maximilian Bösing <[email protected]>
… from `.laminas-ci.json` reflects proper PHP version Signed-off-by: Maximilian Bösing <[email protected]>
Stable PHP should represent an actual PHP version and thus `lowest` and `latest` or even wildcard references make no sense. Signed-off-by: Maximilian Bösing <[email protected]>
… `php` enum values Signed-off-by: Maximilian Bösing <[email protected]>
… match, not `all` Signed-off-by: Maximilian Bösing <[email protected]>
…d `php` specific enum strings Signed-off-by: Maximilian Bösing <[email protected]>
4bad2af
to
7f557d2
Compare
Signed-off-by: Maximilian Bösing <[email protected]>
Due to the fact that there is no `composer.lock` file available, the matrix will not generate any `locked` jobs. Signed-off-by: Maximilian Bösing <[email protected]>
Description
This introduces the ability to exclude specific jobs for specific PHP and/or composer dependency sets.
Fixes #93