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

Reload Configuration from disk disrupts build elements and pipeline

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • None
    • Jenkins ver. 1.642.1
      build-pipeline-plugin 1.4.9
      swarm 2.0
      nodelabelparameter 1.7.1
      hipchat 1.0.0

      Creating 2 new build jobs one dependent on the other by "trigger parameterized build on other projects" or "Build after other projects are built". This results in the relationship being observed here:

      Trigger the upstream build (in our case takes hours to complete) and observe the downstream relationship within the pipeline view:

      Now reload configuration from disk, and reload the build pipeline view:

      The resulting effects are as follows:
      Hipchat notification for upstream job (start) is sent
      CLI Exec on swarm slave runs and completes
      Hipchat notification for upstream job (complete) is never sent
      Downstream build job is never executed.

        1. Packer-windows-2008-r2__Jenkins_.png
          35 kB
          James Powis
        2. pipe_test__Jenkins_.png
          35 kB
          James Powis
        3. pipe_test__Jenkins_2.png
          30 kB
          James Powis
        4. upstream_config.xml
          4 kB
          James Powis

            Unassigned Unassigned
            james_powis James Powis
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: