From 0f17f1ca285751d5a554016252b3027b3c98be90 Mon Sep 17 00:00:00 2001 From: Lennart Jern Date: Fri, 14 Jan 2022 10:19:20 +0200 Subject: [PATCH] Add parameters for CAPI and CAPM3 releases We want to be able to test upgrades from different versions. These parameters can be used to specify the release we start the upgrade from. No default value is provided to avoid hard coding a specific release. The values are automatically set to the latest available release for the selected API version when left empty (by scripts in metal3-dev-env). Change-Id: I7eaca37048b9eb3a8a1801e661c537fcec3b7040 --- jjb/airship/job_master_feature_tests_upgrade_ubuntu.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/jjb/airship/job_master_feature_tests_upgrade_ubuntu.yml b/jjb/airship/job_master_feature_tests_upgrade_ubuntu.yml index f88215818..a829627bf 100644 --- a/jjb/airship/job_master_feature_tests_upgrade_ubuntu.yml +++ b/jjb/airship/job_master_feature_tests_upgrade_ubuntu.yml @@ -61,10 +61,16 @@ name: CAPI_VERSION default: 'v1alpha4' description: 'Cluster API version.' + - string: + name: CAPIRELEASE + description: 'Cluster API release tag to upgrade from, e.g. v1.0.0' - string: name: CAPM3_VERSION default: 'v1alpha5' description: 'Cluster API provider Metal3 version.' + - string: + name: CAPM3RELEASE + description: 'CAPM3 release tag to upgrade from, e.g. v1.0.0' - string: name: TARGET_NODE_OS default: 'Ubuntu' -- 2.25.1