I imagine it searches .info file. Are also .info files of submodules searched and their dependencies added to list? If I add a dependency in a patch, is this taken into consideration when testing that patch?

Thank you for your answers.

Comments

jthorson’s picture

jthorson commented

The logic is all contained within the 'Project Dependency" project ... it pulls the information from a pre-populated database table on drupal.org. Unfortunately, it does not parse the actual info file at run-time, so dependencies added in a patch will not be included.

When dependencies are added via a commit, it may take up to 24 hours for the dependency parsing to update the database tables used in determining dependencies for a test ... if, after a day, the test is still not picking up the dependency, we occasionally have had to manually trigger a jenkins script to update the dependencies for the specific project.

slashrsm’s picture

slashrsm commented
Status: Active » Fixed

THX!

lucascaro’s picture

lucascaro commented

just FYI there is currently a problem in how this calculates dependencies (see #1712656: Dependencies for modules are not updated.)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.