Hello,
We've noticed, since upgrading the Gerrit trigger plugin from 2.28 to 2.34 and then 2.35.1, an issue when we create or update a pipeline that uses this plugin and also dynamic configuration:
if we add a comment, push a new patchset for the same change that worked before, the same pipe won't be triggered anymore and the only errors I could find are displayed below.
Get dynamic projects directly for URL: https://.../job/.../view/gm-J-commands/job/...s/lastSuccessfulBuild/artifact/gerrit/gm_main_soc4g_gerrit_cfg.txt
Sep 14, 2021 10:08:44 AM SEVERE com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger updateTriggerConfigURL
IOException for project: test-prod-unsigned and URL: https://.../job/.../view/gm-J-commands/job/.../lastSuccessfulBuild/artifact/gerrit/gm_main_soc4g_gerrit_cfg.txt Message: https://.../job/GM/view/gm-J-commands/job/.../lastSuccessfulBuild/artifact/gerrit/gm_main_soc4g_gerrit_cfg.txt
java.io.FileNotFoundException: https://.../job/GM/view/gm-J-commands/job/.../lastSuccessfulBuild/artifact/gerrit/gm_main_soc4g_gerrit_cfg.txt
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1896)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:268)
at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritDynamicUrlProcessor.fetch(GerritDynamicUrlProcessor.java:266)
at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.DynamicConfigurationCacheProxy.fetchThroughCache(DynamicConfigurationCacheProxy.java:56)
at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.updateTriggerConfigURL(GerritTrigger.java:1924)
at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerTimerTask.run(GerritTriggerTimerTask.java:63)
at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:67)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
The workaround in this case was to force a new save on the same pipeline, something minor, like a new parameter and then the trigger worked again.
Need to mention that we store the dynamic config file on another job from the same master, as build artifacts - .../lastSuccessfulBuild/artifact/gerrit/main_gerrit_cfg.txt. The poll interval is default, 30 sec.
The same configuration is present on a similar master from our company and there we didn't see the issue, with 2.28 version of Gerrit trigger plugin.
Does anyone else seen the same issue with the latest version of the plugin?
Regards.