[FTR] split configs by target into multiple manifest files (#187440)

## Summary

Part of #186515

Split FTR configs manifest into multiple files based on distro
(serverless/stateful) and area of testing (platform/solutions)
Update the CI scripts to support the change, but without logic
modification

More context:

With this change we will have a clear split of FTR test configs owned by
Platform and Solutions. It is a starting point to make configs
discoverable, our test pipelines be flexible and run tests based on
distro/solution.
This commit is contained in:
Dzmitry Lemechko 2024-07-19 15:00:53 +02:00 committed by GitHub
parent 76c19c61c9
commit 88464e5b6d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
17 changed files with 784 additions and 631 deletions

View file

@ -10,11 +10,24 @@ require('../src/setup_node_env');
var yaml = require('js-yaml');
var fs = require('fs');
var path = require('path');
var manifestsJsonPath = path.resolve(__dirname, '../.buildkite/ftr_configs_manifests.json');
console.log(manifestsJsonPath);
var manifestsSource = JSON.parse(fs.readFileSync(manifestsJsonPath, 'utf8'));
var allManifestPaths = Object.values(manifestsSource).flat();
try {
yaml.load(fs.readFileSync('.buildkite/ftr_configs.yml', 'utf8')).enabled.forEach(function (x) {
console.log(x);
});
for (var manifestRelPath of allManifestPaths) {
var manifest = yaml.load(fs.readFileSync(manifestRelPath, 'utf8'));
if (manifest.enabled) {
manifest.enabled.forEach(function (x) {
console.log(x);
});
} else {
console.log(`${manifestRelPath} has no enabled FTR configs`);
}
}
} catch (e) {
console.log(e);
}