While I still think rolling qa into the main sourcegraph pipeline would be the ideal state in the future, there is a legitimate use case for the sourcegraph-async pipeline for running more diagnostic-level tasks such as https://github.com/sourcegraph/sourcegraph/pull/25455 . If we introduce some kind of continuous benchmarking, for example, I imagine it might live in sourcegraph-async as well.
This pipeline was just 1 job for a while, but with the introduction of https://github.com/sourcegraph/sourcegraph/pull/25455 it's starting to get quite large and we might benefit from migrating it to a generated approach where e.g. it can leverage ChangedFiles and special run types etc.
bobheadxi
commented
3 years ago
While I still think rolling
qainto the mainsourcegraphpipeline would be the ideal state in the future, there is a legitimate use case for thesourcegraph-asyncpipeline for running more diagnostic-level tasks such as https://github.com/sourcegraph/sourcegraph/pull/25455 . If we introduce some kind of continuous benchmarking, for example, I imagine it might live insourcegraph-asyncas well.This pipeline was just 1 job for a while, but with the introduction of https://github.com/sourcegraph/sourcegraph/pull/25455 it's starting to get quite large and we might benefit from migrating it to a generated approach where e.g. it can leverage
ChangedFilesand special run types etc.