Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Postponed
    • Component/s: scripttrigger-plugin
    • Labels:
      None
    • Environment:
      Windows XP server 2003
    • Similar Issues:

      Description

      It would be very useful to have a "Poll Now" feature that causes the script trigger to begin polling.
      As it is now, you must either wait or manually configure the project's schedule to be sooner (and then change it back after testing).

      The "Poll Now" feature is currently available for SCM triggers, and it should work identically to that functionality.
      The "Poll Now" option would go right above the "ScriptTrigger Log" option with the same icon except with a little green play triangle (at least if the goal is to match the SCM trigger mechanism identically).

      Thanks!

        Attachments

          Activity

          Hide
          gbois Gregory Boissinot added a comment -

          As I know, the plugin that provides 'Poll Now' feature requires a high level of Jenkins.
          ScriptTrigger plugin only requires Jenkins 1.410+.

          Additionally, are you sure this new existing button doesn't work with scriptrigger plugin?

          Could you give more information?

          Show
          gbois Gregory Boissinot added a comment - As I know, the plugin that provides 'Poll Now' feature requires a high level of Jenkins. ScriptTrigger plugin only requires Jenkins 1.410+. Additionally, are you sure this new existing button doesn't work with scriptrigger plugin? Could you give more information?
          Hide
          pixman20 pixman20 added a comment -

          I am currently running the latest Jenkins (1.457) and the latest of the scripttrigger plugin (0.16).

          By simply selecting the "Poll SCM" checkbox (utilizing CVS plugin for SCM) in the configuration history I am able to see the "Poll Now" button on the main job page, however when deselecting "Poll SCM" and selecting the "[ScriptTrigger] - Poll with a shell or batch script" checkbox there is no "Poll Now"-like button to hit. That then requires manual tweaking of the configuration file to get the trigger to poll on demand by setting the schedule for a time within the next minute.

          If the button can be added it would probably be best to have it called something along the lines of "Poll ScriptTrigger" since both "Poll SCM" and the scripttrigger polling checkboxes can be selected allowing for multiple "Poll Now" buttons on the main job page.

          I'm not sure if that is the information that you wanted, so let me know if you need more.

          If this seems to "out of the way" for very minor functionality, I'd be alright with closing this issue. However, it if it's fairly simple then it would be very nice to have (and cut time testing out my script .

          Show
          pixman20 pixman20 added a comment - I am currently running the latest Jenkins (1.457) and the latest of the scripttrigger plugin (0.16). By simply selecting the "Poll SCM" checkbox (utilizing CVS plugin for SCM) in the configuration history I am able to see the "Poll Now" button on the main job page, however when deselecting "Poll SCM" and selecting the " [ScriptTrigger] - Poll with a shell or batch script" checkbox there is no "Poll Now"-like button to hit. That then requires manual tweaking of the configuration file to get the trigger to poll on demand by setting the schedule for a time within the next minute. If the button can be added it would probably be best to have it called something along the lines of "Poll ScriptTrigger" since both "Poll SCM" and the scripttrigger polling checkboxes can be selected allowing for multiple "Poll Now" buttons on the main job page. I'm not sure if that is the information that you wanted, so let me know if you need more. If this seems to "out of the way" for very minor functionality, I'd be alright with closing this issue. However, it if it's fairly simple then it would be very nice to have (and cut time testing out my script .
          Hide
          gbois Gregory Boissinot added a comment -

          'Poll Now' SCM button is only available in a recent version of Jenkins. Clicking on this button calls the /poll action not available in Jenkins 1.410.
          ScriptTrigger is compatible to 1.410 and I would like to keep compatibility to 1.410.
          Moreover, I'm not convince of the utility of this feature.
          Is not only for test?

          Show
          gbois Gregory Boissinot added a comment - 'Poll Now' SCM button is only available in a recent version of Jenkins. Clicking on this button calls the /poll action not available in Jenkins 1.410. ScriptTrigger is compatible to 1.410 and I would like to keep compatibility to 1.410. Moreover, I'm not convince of the utility of this feature. Is not only for test?
          Hide
          pixman20 pixman20 added a comment -

          For my purposes it would be for testing, but it is also nice to have for other users that want to run the polling script without waiting for the next event. This is especially useful for users who only have access to the "Poll Now" functionality and not to the configuration page.

          Having said that, I agree that it is best to keep ScriptTrigger compatible with earlier versions of Jenkins so that others may get more critical fixes/updates without being forced to upgrade their version of Jenkins.

          The 2 best options seem to be:
          1) Close the issue
          2) Put the issue on hold until ScriptTrigger needs to be updated to a newer Jenkins for other reasons.

          Thanks for looking into this.

          Show
          pixman20 pixman20 added a comment - For my purposes it would be for testing, but it is also nice to have for other users that want to run the polling script without waiting for the next event. This is especially useful for users who only have access to the "Poll Now" functionality and not to the configuration page. Having said that, I agree that it is best to keep ScriptTrigger compatible with earlier versions of Jenkins so that others may get more critical fixes/updates without being forced to upgrade their version of Jenkins. The 2 best options seem to be: 1) Close the issue 2) Put the issue on hold until ScriptTrigger needs to be updated to a newer Jenkins for other reasons. Thanks for looking into this.
          Hide
          gbois Gregory Boissinot added a comment -

          Thank you so much for your inputs.
          I'm choosing to postpone the issue resolution due to the Jenkins compatibility to Jenkins 1.410.

          Show
          gbois Gregory Boissinot added a comment - Thank you so much for your inputs. I'm choosing to postpone the issue resolution due to the Jenkins compatibility to Jenkins 1.410.

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              pixman20 pixman20
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: