Sometimes maintainers need to test patches before they have fully enabled issue testing on their project. DrupalCI should allow maintainers to run ad-hoc tests against arbitrary patches even if issue testing is not enabled for that project/branch.

This would allow maintainers to initially use drupalci to get their project into a state where it is passing the tests without it hindering other issues due to known failures.

Comments

Mixologic created an issue. See original summary.

mglaman’s picture

mglaman
Primary language English
Location WI, USA
commented

+1; major use case is Drupal Commerce. We required Composer from Day 0. So we were and still are on Travis. But we have funky test failures on DrupalCI, with no strong way to debug or run possible fixes... without borking our issue workflow due to 100% failure rate.

drumm’s picture

drumm
he/him
Location NY, US
commented
Status: Active » Closed (outdated)