Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-44647

Support pipeline jobs (i.e. call the script on pipeline job completion)

      The plugin does not handle pipelines. It would be nice to have the script called too for pipelines, even tough all variables can't probably be provided as they are for regular jobs.

      Or maybe it could even be called on each pipeline step completion.

          [JENKINS-44647] Support pipeline jobs (i.e. call the script on pipeline job completion)

          Kendall Trego added a comment -

          I've created a pull request here to resolve this issue: https://github.com/jenkinsci/global-post-script-plugin/pull/5

          Kendall Trego added a comment - I've created a pull request here to resolve this issue:  https://github.com/jenkinsci/global-post-script-plugin/pull/5

          Hao CHEN added a comment -

          Merged and released, please verify.

          Hao CHEN added a comment - Merged and released, please verify.

          Luca Naldini added a comment -

          Just me or the tests fail when building with maven?

          Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 1.805 sec <<< FAILURE! - in com.orctom.jenkins.plugin.globalpostscript.ScriptTest
          
          testExecuteGroovy2(com.orctom.jenkins.plugin.globalpostscript.ScriptTest)  Time elapsed: 1.734 sec  <<< FAILURE!
          
          org.junit.ComparisonFailure: expected:<[dropdeploy to: server1]> but was:<[]>
          
          at org.junit.Assert.assertEquals(Assert.java:115)
          
          at org.junit.Assert.assertEquals(Assert.java:144)
          
          at com.orctom.jenkins.plugin.globalpostscript.ScriptTest.testExecuteGroovy2(ScriptTest.java:106)
          
          
          
          testExecuteGroovy(com.orctom.jenkins.plugin.globalpostscript.ScriptTest)  Time elapsed: 0.013 sec  <<< FAILURE!
          
          org.junit.ComparisonFailure: expected:<[dropdeploy to: server1]> but was:<[]>
          
          at org.junit.Assert.assertEquals(Assert.java:115)
          
          at org.junit.Assert.assertEquals(Assert.java:144)
          
          at com.orctom.jenkins.plugin.globalpostscript.ScriptTest.testExecuteGroovy(ScriptTest.java:94)
          
          
          
          Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.311 sec - in InjectedTest
          
          
          
          Results :
          
          
          
          Failed tests:
          
            ScriptTest.testExecuteGroovy2:106 expected:<[dropdeploy to: server1]> but was:<[]>
          
            ScriptTest.testExecuteGroovy:94 expected:<[dropdeploy to: server1]> but was:<[]>
          
          
          
          Tests run: 9, Failures: 2, Errors: 0, Skipped: 0

          Luca Naldini added a comment - Just me or the tests fail when building with maven? Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 1.805 sec <<< FAILURE! - in com.orctom.jenkins.plugin.globalpostscript.ScriptTest testExecuteGroovy2(com.orctom.jenkins.plugin.globalpostscript.ScriptTest)  Time elapsed: 1.734 sec  <<< FAILURE! org.junit.ComparisonFailure: expected:<[dropdeploy to: server1]> but was:<[]> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at com.orctom.jenkins.plugin.globalpostscript.ScriptTest.testExecuteGroovy2(ScriptTest.java:106) testExecuteGroovy(com.orctom.jenkins.plugin.globalpostscript.ScriptTest)  Time elapsed: 0.013 sec  <<< FAILURE! org.junit.ComparisonFailure: expected:<[dropdeploy to: server1]> but was:<[]> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at com.orctom.jenkins.plugin.globalpostscript.ScriptTest.testExecuteGroovy(ScriptTest.java:94) Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.311 sec - in InjectedTest Results : Failed tests:   ScriptTest.testExecuteGroovy2:106 expected:<[dropdeploy to: server1]> but was:<[]>   ScriptTest.testExecuteGroovy:94 expected:<[dropdeploy to: server1]> but was:<[]> Tests run: 9, Failures: 2, Errors: 0, Skipped: 0

          Kendall Trego added a comment - - edited

          Just ran tests from head: they pass on my system.

           

          However, the plugin is not available for download through the jenkins plugin tool, not sure what the process is to release it there.

          EDIT: The plugin shows in jenkins now, I hadn't checked for updates properly. Works as I expect.

          Kendall Trego added a comment - - edited Just ran tests from head: they pass on my system.   However, the plugin is not available for download through the jenkins plugin tool, not sure what the process is to release it there. EDIT: The plugin shows in jenkins now, I hadn't checked for updates properly. Works as I expect.

          orctom this seems to be fully complete. We can mark this ticket DONE.

          Mohammed Abdullah added a comment - orctom  this seems to be fully complete. We can mark this ticket DONE.

            orctom Hao CHEN
            alexf Alexandre Feblot
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: