diff --git a/doc/src/nextlevel-ci/researchAnsible.rst b/doc/src/nextlevel-ci/researchAnsible.rst index 3856aa5..fdf9bba 100644 --- a/doc/src/nextlevel-ci/researchAnsible.rst +++ b/doc/src/nextlevel-ci/researchAnsible.rst @@ -1445,6 +1445,43 @@ After synchronizing the AWX project *NWL CI* the new job template is added: So far everything worked fine. +Getting Plugins Versions and Available Updates +********************************************** +Login to the Server where the docker Jenkins instance is running on and perform the following commands: + +.. code-block:: + + # first getting the jenkins-cli.jar: + curl '10.115.101.101:8080/jnlpJars/jenkins-cli.jar' > jenkins-cli.jar + + # get a full list of the installed plugins including their version and updates in brackets: + java -jar ./jenkins-cli.jar -s : -auth : list-plugins + + # just get the plugins with an available update: + java -jar ./jenkins-cli.jar -s : -auth : list-plugins | grep -e ')$' | awk '{ print $1,":",$(NF-1)," --> ",$NF }' + # output of this command gives this: + workflow-cps : 3697.vb_470e454c232 --> (3705.va_6a_c2775a_c17) + pipeline-model-extensions : 2.2141.v5402e818a_779 --> (2.2144.v077a_d1928a_40) + pipeline-stage-tags-metadata : 2.2141.v5402e818a_779 --> (2.2144.v077a_d1928a_40) + jdk-tool : 63.v62d2fd4b_4793 --> (66.vd8fa_64ee91b_d) + pipeline-model-definition : 2.2141.v5402e818a_779 --> (2.2144.v077a_d1928a_40) + git : 5.1.0 --> (5.2.0) + cloudbees-bitbucket-branch-source : 809.vc1d904b_30426 --> (825.va_6a_dc46a_f97d) + javax-mail-api : 1.6.2-8 --> (1.6.2-9) + command-launcher : 90.v669d7ccb_7c31 --> (100.v2f6722292ee8) + workflow-api : 1223.v41b_0279c361a --> (1232.v1679fa_2f0f76) + pipeline-model-api : 2.2141.v5402e818a_779 --> (2.2144.v077a_d1928a_40) + matrix-auth : 3.1.9 --> (3.1.10) + font-awesome-api : 6.4.0-1 --> (6.4.0-2) + sshd : 3.249.v2dc2ea_416e33 --> (3.303.vefc7119b_ec23) + +In our case : = http://10.115.101.101:8080/ + +.. note:: + In a CI environment the versions of the plugins are important too. Imagine a plugin changes its behavior or becomes + obsolete while your daily integration work. Then you have to run a pipeline for an old release to debug something. + Without this information you might be lost. Especially in the case if one can update plugins on the Jenkins UI. + .. |awxCredentials| image:: ./media/awx-credentials.png :width: 700px