Fixed broken plugins in plugins.txt

README.md

@@ -169,7 +169,7 @@ On the top-right corner of the page:
 It is finally __jenkins__ time. The standard Jenkins setup has a number of steps which can be automated with the [configuration-as-code][url-plugin-casc] plugin. 
 
 The standard Jenkins setup has a number of steps that can be automated with the [configuration-as-code][url-plugin-casc] plugin. Given its fast-paced and complex ecosystem, plugin versions compatibility tend to break regarding interdependencies and the situation becomes worse for those living on the bleeding edge versions. For such reasons, it is reasonable to create a selection of plugin versions which were known to be in a working state for __reducing__ the chances of using broken plugin versions. For this, let's use a custom [Dockerfile](Dockerfile) that will:
-* use the __jenkins/jenkins:lts-jdk11__ as base image, a stable version offering __LTS__ (Long-Term Support).
+* use the __jenkins/jenkins:lts__ as base image, a stable version offering __LTS__ (Long-Term Support).
 * use the __configuration-as-code__ plugin, so that we script the initial Jenkins [configuration](jcasc.yaml).
 * use the `jenkins-plugin-cli` command line utility to install a collection of [plugins](plugins.txt) versions that are known to be working.
 

plugins.txt

@@ -1,8 +1,8 @@
 ant:497.v94e7d9fffa_b_9
 authorize-project:1.7.1
-branch-api:2.1128.v717130d4f816
+branch-api:2.1148.vce12cfcdf090
 build-timeout:1.31
-configuration-as-code:1714.v09593e830cfa
+configuration-as-code:1775.v810dc950b_514
 docker-commons:439.va_3cb_0a_6a_fb_29
 docker-java-api:3.3.1-79.v20b_53427e041
 docker-plugin:1.5
@@ -15,6 +15,6 @@ pipeline-github-lib:42.v0739460cda_c4
 pipeline-model-definition:2.2144.v077a_d1928a_40
 pipeline-stage-view:2.33
 ssh-slaves:2.916.vd17b_43357ce4
-warnings-ng:10.5.2
+warnings-ng:11.3.0
 workflow-aggregator:596.v8c21c963d92d
 ws-cleanup:0.45