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 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.

          mmocnak added a comment -

          Still i can reproduce it on 1.102

          mmocnak added a comment - Still i can reproduce it on 1.102

          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.

          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).

          Kohsuke Kawaguchi added a comment - Sorry, I just tried http://deadlock.nbextras.org/hudson/job/mevenide/78/api/xml and http://deadlock.nbextras.org/hudson/job/mevenide/api/xml but both works. Any URL to reproduce the problem?

          mmocnak added a comment -

          mmocnak added a comment - Try this: http://deadlock.nbextras.org/hudson/job/trunk/2947/api/xml

          Added missing annotation there.

          I should write a static error checker to detect problems like this during the
          build, I guess.

          Kohsuke Kawaguchi added a comment - Added missing annotation there. I should write a static error checker to detect problems like this during the build, I guess.

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

              Created:
              Updated:
              Resolved: