Currently, it seems the normal "issues"/"branch on commit" tests for contrib modules use Drupal 8.2.x. However, 8.1.x is currently active, so (as far as I understand) contrib modules should be compatible with that. Using 8.2.x for the automatic tests could allow incompatibilities with the currently active Core version to go unnoticed, somewhat undermining the purpose of an automatic test suite.
Is there a specific reason for using Drupal 8.2.x, or could we change this?
Is it maybe even something I can change myself, just for my projects? (Didn't find anything, though.) I know starting tests manually with "Custom parameters" allows you to pick a Core version as well, but I don't see any way to get that for the automated test runs.
Comments
Comment #2
MixologicComment #3
MixologicDrupal CI supports whatever branch drupal.org tells it to check out, So this is a UI/UX thing we need to add to PIFT.
Comment #4
jhodgdonI think this has been done? When I go to add/edit a test, I see options to configure a specific branch or to use the default (default is still the in-development latest branch). Tenatively marking this Fixed.