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

save happens after ComputerListener onConfigurationChange event

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major Major
    • core
    • ubuntu quantal
      maven 3
      java 1.6
      jenkins 1.502

      When i make a configuration change the change doesn't get save until after the onConfigurationChange event exits. I think it should be the opposite.. Save the configuration first then fire the event. That way I can at least query what changed and do something.

          [JENKINS-17203] save happens after ComputerListener onConfigurationChange event

          Daniel Beck added a comment -

          It's unclear how this can be reproduced, or even what the problem is: listeners are expected to access the objects directly rather than parsing the XML, which is the part affected by the save.

          Also, from reading current Jenkins.java (~1.564), it appears that saving actually happens before onConfigurationChange most of the time.

          More information is required to analyze this issue.

          Daniel Beck added a comment - It's unclear how this can be reproduced, or even what the problem is: listeners are expected to access the objects directly rather than parsing the XML, which is the part affected by the save. Also, from reading current Jenkins.java (~1.564), it appears that saving actually happens before onConfigurationChange most of the time. More information is required to analyze this issue.

            Unassigned Unassigned
            zaro Khai Do
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: