Export compiler path in CppCheck & FoorPrint
CppCheck & FootPrint also need to use GCC v7.3.1.
Export PATH to GCC v7.3.1 in these jobs.
Signed-off-by: Xinyu Zhang <xinyu.zhang@arm.com>
Change-Id: Iab24eb1311c53f5d071eb3208dc1345fa67f4c80
diff --git a/jenkins/build-config.jpl b/jenkins/build-config.jpl
index fd22714..480f598 100644
--- a/jenkins/build-config.jpl
+++ b/jenkins/build-config.jpl
@@ -1,6 +1,6 @@
#!/usr/bin/env groovy
//-------------------------------------------------------------------------------
-// Copyright (c) 2020-2021, Arm Limited and Contributors. All rights reserved.
+// Copyright (c) 2020-2022, Arm Limited and Contributors. All rights reserved.
//
// SPDX-License-Identifier: BSD-3-Clause
//
@@ -45,7 +45,7 @@
}
if (env.SQUAD_CONFIGURATIONS != ""){
//Creating a folder to store memory footprint artifacts and launching the memory footprint script.
- sh "mkdir tf-m-ci-scripts/Memory_footprint/"
+ sh "mkdir tf-m-ci-scripts/Memory_footprint/ ; export PATH=${env.PATH}:${env.GCC_7_3_1_PATH}"
withCredentials([string(credentialsId: 'QA_REPORTS_TOKEN', variable: 'TOKEN')]) {
sh(script: "python3 tf-m-ci-scripts/memory_footprint.py ${env.WORKSPACE}/trusted-firmware-m/ ${env.CONFIG_NAME} \'${env.SQUAD_CONFIGURATIONS}\' ${TOKEN}", returnStdout: true)
}