I'd like to handle a specific use-case for our repo, in which the full test suite can take several hours (e.g. for our nightly master builds), but is modular using GitLab CI/CD env variables w/manual pipeline builds -- so certain test stages can be skipped, and/or developers can specify a filter string to select the specific test suites that should run.
The above setup works for triggering a single manual pipeline invocation, but our intent is that once the default variables are overridden for an MR (via manual pipeline), those variable values should be used for testing all future updates to that MR. (e.g. marge bot would notice the custom variables from a previous pipeline, and re-use them for her testing).
This is a bit more dynamic/user-configurable than #114's job-regexp -- we'd like to be able to support different user-specified variables for every MR.
I'd like to handle a specific use-case for our repo, in which the full test suite can take several hours (e.g. for our nightly
masterbuilds), but is modular using GitLab CI/CD env variables w/manual pipeline builds -- so certain test stages can be skipped, and/or developers can specify a filter string to select the specific test suites that should run.The above setup works for triggering a single manual pipeline invocation, but our intent is that once the default variables are overridden for an MR (via manual pipeline), those variable values should be used for testing all future updates to that MR. (e.g. marge bot would notice the custom variables from a previous pipeline, and re-use them for her testing).
This is a bit more dynamic/user-configurable than #114's job-regexp -- we'd like to be able to support different user-specified variables for every MR.