Issue #3466101 by fjgarlin, cmlara, jonathan1055: firecow: 'parallel' property...

Issue #3466101 by fjgarlin, cmlara, jonathan1055: firecow: 'parallel' property type must be integer at test-only changes.parallel

docs/jobs/test-only-changes.md

@@ -13,3 +13,14 @@ The log has extra information showing which files have been changed in the merge
 If this job ends with a green pass it means that the bug or feature does not have test coverage, because the tests pass even with the unmodified source files.
 
 It can also be used to demonstrate new test coverage for existing source code which is not being changed. To do this, make a temporary change to the source (to simulate a bug) which will cause the new test to fail in the regular `phpunit` job. However the `test-only changes` job should pass green. This is the reverse outcome compared the usual scenario described above, but it does indicate that the new test provides coverage as intended. 
+
+## Parallel option
+
+If the `phpunit` job uses `parallel`, those options will be inherited by the `test-only changes` job. The `parallel` options could be a number, to split a job into several ones, or could be a matrix of options, each one passed to a different parallel job. This means that in some cases, keeping this value makes sense but in others it does not.
+
+If you want the `test-only changes` job to not have parallel options, you can do this in your `.gitlab-ci.yml`:
+```
+test-only changes:
+  # Remove the parallel definition that is defined in the customized phpunit.
+  parallel:
+```

includes/include.drupalci.main.yml

@@ -1059,8 +1059,6 @@ test-only changes:
       when: manual
   interruptible: true
   allow_failure: true
-  # Remove parallel definition, in case it was defined in a customized phpunit.
-  parallel:
   script:
     - *calculate-gitlab-ref
     - *show-environment-variables