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

Job restarted with Centralized Job(Re)Action plugin don't keep parameters from the original build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • logaction
    • None

      A parameterized build that is restarted again with Centralized Job(Re)Action plugin loose the parameters, and its not possible to used in the new job.

          [JENKINS-8233] Job restarted with Centralized Job(Re)Action plugin don't keep parameters from the original build

          sblanco created issue -

          Oleg Nenashev added a comment -

          Fixed the component.
          BTW, the Naginator Plugin seems to be a modern solution

          Oleg Nenashev added a comment - Fixed the component. BTW, the Naginator Plugin seems to be a modern solution
          Oleg Nenashev made changes -
          Component/s New: logaction [ 16220 ]
          Component/s Original: other [ 15490 ]

          Tim-Christian Bloss added a comment -

          The problem exists in "Centralized Job(Re)Action plugin" 1.2 and there's no release of a fixed version available/released yet.

          Even if "Naginator Plugin" may be a more modern/flexible plugin, which we're already using, the "Centralized Job(Re)Action plugin" has the advantage of being a "global" trigger, processing the log output of each and every job, while the "Naginator Plugin" requires individual configuration.

          Environment: Jenkins 1.565.3, Centralized Job(Re)Action plugin 1.2, Tomcat 7.0.54, JRE1.7.0_71, Debian GNU/Linux 7, amd64, de_DE.UTF-8

          Besides this problem, the plugin works as expected.

          Tim-Christian Bloss added a comment - The problem exists in "Centralized Job(Re)Action plugin" 1.2 and there's no release of a fixed version available/released yet. Even if "Naginator Plugin" may be a more modern/flexible plugin, which we're already using, the "Centralized Job(Re)Action plugin" has the advantage of being a "global" trigger, processing the log output of each and every job, while the "Naginator Plugin" requires individual configuration. Environment: Jenkins 1.565.3, Centralized Job(Re)Action plugin 1.2, Tomcat 7.0.54, JRE1.7.0_71, Debian GNU/Linux 7, amd64, de_DE.UTF-8 Besides this problem, the plugin works as expected.

          Oleg Nenashev added a comment -

          I'm not sure if the plugin is being supported now.
          If you want to contribute/take the ownership, contact jieryn@gmail.com and then send a e-mail to jenkinsci-dev@googlegroups.com

          Oleg Nenashev added a comment - I'm not sure if the plugin is being supported now. If you want to contribute/take the ownership, contact jieryn@gmail.com and then send a e-mail to jenkinsci-dev@googlegroups.com
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 138343 ] New: JNJira + In-Review [ 174874 ]

            Unassigned Unassigned
            sblanco sblanco
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: