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

XML API for job where the changes are is not possible

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • other
    • None
    • Platform: All, OS: All

      Found in version 1.101

      If i want to use XML API on job build where the recent changes are the
      exceptions is thrown.

      See attached stack trace.

          [JENKINS-468] XML API for job where the changes are is not possible

          mmocnak created issue -

          mmocnak added a comment -

          Created an attachment (id=56)
          stack trace

          mmocnak added a comment - Created an attachment (id=56) stack trace

          Fixed in 1.102. Or you can try the snapshot, as always.

          Kohsuke Kawaguchi added a comment - Fixed in 1.102. Or you can try the snapshot, as always.
          Kohsuke Kawaguchi made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          mmocnak added a comment -

          Still i can reproduce it on 1.102

          mmocnak added a comment - Still i can reproduce it on 1.102
          mmocnak made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

          You should have seen a different stack trace though, because the User class now
          has the @ExposedBean annotation on it.

          Kohsuke Kawaguchi added a comment - You should have seen a different stack trace though, because the User class now has the @ExposedBean annotation on it.
          Kohsuke Kawaguchi made changes -
          Status Original: Reopened [ 4 ] New: In Progress [ 3 ]

          mmocnak added a comment -

          Yes that's right. Try to use hudson instance on deadlock.nbextras.org/hudson.
          There you can reproduce the problem.

          mmocnak added a comment - Yes that's right. Try to use hudson instance on deadlock.nbextras.org/hudson. There you can reproduce the problem.

          Jesse Glick added a comment -

          By the way, I update the Hudson instance on deadlock at irregular intervals,
          always building from current trunk sources (so the date should correspond
          roughly to CVS timestamp).

          Jesse Glick added a comment - By the way, I update the Hudson instance on deadlock at irregular intervals, always building from current trunk sources (so the date should correspond roughly to CVS timestamp).

            Unassigned Unassigned
            mmocnak mmocnak
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: