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

promoted-builds action does not build on tied node

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Component/s: promoted-builds-plugin
    • Labels:
      None
    • Environment:
      Platform: All, OS: All

      Description

      as actions for promoted-builds, I have configured an ant task.

      I would expect that this task is built using the same "configuration" as the
      project itself, i.e. also tied to the same node, or that alternatively, the
      promotion action can be configured to be tied to a node itself.

      None of this is the case, that is:

      • I cannot configure the node on which the promotion action is executed
      • the promotion action will pick a "free" node to build (and it relies on having
        a free node available)

      Hudson 1.316
      promoted-builds plugin 1.4

        Issue Links

          Activity

          tjenny tjenny created issue -
          Hide
          kmmoens kmmoens added a comment -

          I'm facing the same issue with promoted builds 1.5 on Hudson 1.338. In my setup I have a complicated release process where the connection between the slave and the master is slow in upload speed, as such I want to send as less data as possible to the master machine which also runs an HTTP server. Due to this, I want to be to

          1) Run an action on the slave machine, which should be the default behaviour of an action
          2) Have the possibility to run a job on the master also, based on artefacts.

          Show
          kmmoens kmmoens added a comment - I'm facing the same issue with promoted builds 1.5 on Hudson 1.338. In my setup I have a complicated release process where the connection between the slave and the master is slow in upload speed, as such I want to send as less data as possible to the master machine which also runs an HTTP server. Due to this, I want to be to 1) Run an action on the slave machine, which should be the default behaviour of an action 2) Have the possibility to run a job on the master also, based on artefacts.
          mindless Alan Harder made changes -
          Field Original Value New Value
          Link This issue is duplicated by JENKINS-4994 [ JENKINS-4994 ]
          Hide
          mindless Alan Harder added a comment -

          I committed a change that will fix the case described above (tied to master node, or tied to any single node).. however, when a label is used the promotion may run on any node in that label group, not necessarily the exact node where the promoted build ran.. not sure how to make that happen, as node selection is at the project level.

          Show
          mindless Alan Harder added a comment - I committed a change that will fix the case described above (tied to master node, or tied to any single node).. however, when a label is used the promotion may run on any node in that label group, not necessarily the exact node where the promoted build ran.. not sure how to make that happen, as node selection is at the project level.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in hudson
          User: : mindless
          Path:
          trunk/hudson/plugins/promoted-builds/src/main/java/hudson/plugins/promoted_builds/PromotionProcess.java
          http://jenkins-ci.org/commit/29435
          Log:
          [promoted-builds] JENKINS-4089 Run promotion on same label as main project..
          would actally like to run on exact node the promoted build ran on, but label
          selection is at the project level so we don't have access to the build-specific
          info when the label is selected for this promotion.

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : mindless Path: trunk/hudson/plugins/promoted-builds/src/main/java/hudson/plugins/promoted_builds/PromotionProcess.java http://jenkins-ci.org/commit/29435 Log: [promoted-builds] JENKINS-4089 Run promotion on same label as main project.. would actally like to run on exact node the promoted build ran on, but label selection is at the project level so we don't have access to the build-specific info when the label is selected for this promotion.
          Hide
          petehayes Peter Hayes added a comment -

          Closing this issue as it now works as expected. Another issue could be opened related to tying to specific node that the promoted build ran on, but personally I think being workspace agnostic should be a requirement of use.

          Show
          petehayes Peter Hayes added a comment - Closing this issue as it now works as expected. Another issue could be opened related to tying to specific node that the promoted build ran on, but personally I think being workspace agnostic should be a requirement of use.
          petehayes Peter Hayes made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              tjenny tjenny
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: