From 2f84eccebf70b2817b21fcc0f02559542496fdb6 Mon Sep 17 00:00:00 2001 From: Gilles Peskine Date: Tue, 19 Nov 2024 17:19:43 +0100 Subject: [PATCH] Link to the list of available plugins on each CI Signed-off-by: Gilles Peskine --- developer_guide.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/developer_guide.md b/developer_guide.md index b3f95abe2..91a646929 100644 --- a/developer_guide.md +++ b/developer_guide.md @@ -97,6 +97,8 @@ The Groovy language gives access to the Java standard library. However, on Jenki Jenkins (with the plugins we have installed) makes some extra functions available, in particular [pipeline steps](https://www.jenkins.io/doc/pipeline/steps/workflow-basic-steps/). +The two CI instances may have different sets of plugins. You can see the plugin list on [OpenCI](https://review.trustedfirmware.org/plugins/gitiles/ci/dockerfiles/+/refs/heads/master/jessie-amd64-jenkins-master/plugins.txt) and on the [internal CI](https://jenkins-mbedtls.oss.arm.com/manage/pluginManager/installed). + #### Global variables Note that Groovy does not have global variables as such. Each module (`*.groovy` file) is a class, and that class can have multiple instances. Therefore, avoid using script-scope variables in a Groovy module that is loaded from another module. There's existing code that does this, but it's fragile and has caused us headaches so we are moving away from that.