Memory Footprint: Simplify logics to parse configs
Build configs are available via Jenkins env params. There is no need to
parse build configs with build manager, which makes the code hard to
understand.
Signed-off-by: Xinyu Zhang <xinyu.zhang@arm.com>
Change-Id: I3299fd08f268e020c3f0bfb829f8acd4dd4de06c
diff --git a/jenkins/ci.jpl b/jenkins/ci.jpl
index 070846f..12b496b 100644
--- a/jenkins/ci.jpl
+++ b/jenkins/ci.jpl
@@ -111,9 +111,7 @@
params += string(name: 'PSA_ARCH_TESTS_VERSION', value: env.PSA_ARCH_TESTS_VERSION)
params += string(name: 'PSA_ARCH_TESTS_URL', value: env.PSA_ARCH_TESTS_URL)
params += string(name: 'SHARE_FOLDER', value: env.SHARE_FOLDER)
- if (env.JOB_NAME.equals("tf-m-nightly")) { //Setting the Memory footprint gathering.
- params += string(name: 'SQUAD_CONFIGURATIONS', value: env.SQUAD_CONFIGURATIONS)
- }
+ params += string(name: 'SQUAD_CONFIGURATIONS', value: env.SQUAD_CONFIGURATIONS)
return { -> results
def build_res = build(job: 'tf-m-build-config', parameters: params, propagate: false)
def build_url = build_res.getAbsoluteUrl()