Run full dependency validation on PR as well as master #15505
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Before
We would pass the changed integration eg
ddev validate dep rabbitmq
when running on PR.After
Both for PRs and for master we run
ddev validate dep
.Motivation
agent_requirements.in
. The logic is that these errors will be caught soon enough by themaster
CI. Unfortunately this can result in a problem: we break the agent build and there's a lot of pressure to fix our master CI.agent_requirements.in
we discovered that we broke the agent build. It would have been useful to checkagent_requirements.in
in the first PR and deal with agent build problems earlier.Alternative
We could try to address the original problem, by considering only a subset of
agent_requirements.in
deps that's relevant to a given integration. This is the proper solution, but it looks like more work. In my opinion for insufficient performance gain. We could potentially keep the current fix while creating a card for the tools squad to implement the proper fix.Additional Notes
Review checklist (to be filled by reviewers)
changelog/
andintegration/
labels attachedqa/skip-qa
label.