• Evergreen - Milestone 1

      See here and  here

      GitPluginTest is currently failing in the ATH since build number 72

          [JENKINS-50790] GitPluginTest are failing in the ATH

          I am experimenting with skipping the available plugins page and just request the installation via a REST call, initial experiments seem promising

          Raul Arabaolaza added a comment - I am experimenting with skipping the available plugins page and just request the installation via a REST call, initial experiments seem promising

          Jesse Glick added a comment -

          There have been past attempts to load plugins via REST rather than GUI, and that code is still there; you just need a switch to activate it. It does not work all that well as the plugin manager has some subtle logic which is not easily replicated. I would rather just track down the cause of delays and fix them. Run a profiler or whatever. Is the problem in JavaScript or the mock UC service itself?

          Jesse Glick added a comment - There have been past attempts to load plugins via REST rather than GUI, and that code is still there; you just need a switch to activate it. It does not work all that well as the plugin manager has some subtle logic which is not easily replicated. I would rather just track down the cause of delays and fix them. Run a profiler or whatever. Is the problem in JavaScript or the mock UC service itself?

          What I can see is the http call to pluginManager/available performed by the UI when clicking on the Available tab the one that takes too much time. My understanding is that the endpoint calls the mock UC under the covers, as I have checked that same call with an instance run via java -jar (outside ATH) and it takes much less time ~ 10 seconds

          Raul Arabaolaza added a comment - What I can see is the http call to pluginManager/available performed by the UI when clicking on the Available tab the one that takes too much time. My understanding is that the endpoint calls the mock UC under the covers, as I have checked that same call with an instance run via java -jar (outside ATH) and it takes much less time ~ 10 seconds

          Maybe you refer to this code path? I am not going that way, I am making a request to trigger the installation via UC instead of using the buttons in the `Available Plugins Page` and let it handle dependencies and all that stuff, not sure however about versioning constraints at this point

          Raul Arabaolaza added a comment - Maybe you refer to this code path ? I am not going that way, I am making a request to trigger the installation via UC instead of using the buttons in the `Available Plugins Page` and let it handle dependencies and all that stuff, not sure however about versioning constraints at this point

          So after a conversation with jglick it seems the problem is in the core itself since 2.112, the addition of detached plugins causing an exponential explosion in a recursive call. He is working on a fix, in the meanwhile a temporary increase in the timeout should be enough to make everything stable again

          Raul Arabaolaza added a comment - So after a conversation with jglick it seems the problem is in the core itself since 2.112, the addition of detached plugins causing an exponential explosion in a recursive call. He is working on a fix, in the meanwhile a temporary increase in the timeout should be enough to make everything stable again

          Not sure if the fix in JENKINS-51205 is enough, I am still receiving email alerts about instability on git-plugin, however at this moment ci.jenkins.io is down so I can not check the status

          Raul Arabaolaza added a comment - Not sure if the fix in JENKINS-51205 is enough, I am still receiving email alerts about instability on git-plugin, however at this moment ci.jenkins.io is down so I can not check the status

          It seems it worked, I am going to get this open for a pair of days and close if nothing new arises

          Raul Arabaolaza added a comment - It seems it worked, I am going to get this open for a pair of days and close if nothing new arises

          Jesse Glick added a comment -

          Makes sense.

          Jesse Glick added a comment - Makes sense.

          Last builds of git-plugin have no failures, so I am going to close this.

          Raul Arabaolaza added a comment - Last builds of git-plugin have no failures, so I am going to close this.

          The fix for JENKINS-51205 solved this problem

          Raul Arabaolaza added a comment - The fix for JENKINS-51205 solved this problem

            rarabaolaza Raul Arabaolaza
            rarabaolaza Raul Arabaolaza
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: