[JIRA] (JENKINS-13865) Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy.

[ https://issues.jenkins-ci.org/browse/JENKINS-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163145#comment-163145 ] Jason Howk commented on JENKINS-13865: -- And fixed in 2128c9d7 > Jenkin

[JIRA] (JENKINS-13336) Invalid JSON is produced during remote api operations when a changeSet contains duplicate keys.

[ https://issues.jenkins-ci.org/browse/JENKINS-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163144#comment-163144 ] Jason Howk edited comment on JENKINS-13336 at 5/23/12 10:34 PM: --

[JIRA] (JENKINS-13336) Invalid JSON is produced during remote api operations when a changeSet contains duplicate keys.

[ https://issues.jenkins-ci.org/browse/JENKINS-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163144#comment-163144 ] Jason Howk commented on JENKINS-13336: -- This looks like it was fixed in f65c3484 which

[JIRA] (JENKINS-13865) Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy.

[ https://issues.jenkins-ci.org/browse/JENKINS-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163141#comment-163141 ] Jason Howk commented on JENKINS-13865: -- Looks like the issue was due to commit ff4b0255

[JIRA] (JENKINS-13865) Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy.

[ https://issues.jenkins-ci.org/browse/JENKINS-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163094#comment-163094 ] Jason Howk commented on JENKINS-13865: -- What we need is not to use the ansi escape code

[JIRA] (JENKINS-13865) Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy.

[ https://issues.jenkins-ci.org/browse/JENKINS-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Howk updated JENKINS-13865: - Description: Jenkins /queue/api does not produce properly formatted JSON when build in queue w

[JIRA] (JENKINS-13865) Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy.

[ https://issues.jenkins-ci.org/browse/JENKINS-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Howk updated JENKINS-13865: - Description: Jenkins /queue/api does not produce properly formatted JSON when build in queue w

[JIRA] (JENKINS-13865) Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy.

[ https://issues.jenkins-ci.org/browse/JENKINS-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Howk updated JENKINS-13865: - Description: Jenkins /queue/api does not produce properly formatted JSON when build in queue w

[JIRA] (JENKINS-13556) Unprintable character in executor name in JSON API output

[ https://issues.jenkins-ci.org/browse/JENKINS-13556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163093#comment-163093 ] Jason Howk commented on JENKINS-13556: -- It's the ConsoleNote class that's attempting to

[JIRA] (JENKINS-13865) Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy.

[ https://issues.jenkins-ci.org/browse/JENKINS-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163092#comment-163092 ] Jason Howk commented on JENKINS-13865: -- One more update: This appears to be due to the

[JIRA] (JENKINS-13865) Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy.

Jason Howk created JENKINS-13865: Summary: Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy. Key: JENKINS-13865 URL: https://issues.jenkins-ci

[JIRA] (JENKINS-13336) Invalid JSON is produced during remote api operations when a changeSet contains duplicate keys.

[ https://issues.jenkins-ci.org/browse/JENKINS-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13336 stopped by Jason Howk. > Invalid JSON is produced during remote api operations when a changeSet > contains duplicate keys. >

[JIRA] (JENKINS-13336) Invalid JSON is produced during remote api operations when a changeSet contains duplicate keys.

[ https://issues.jenkins-ci.org/browse/JENKINS-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > Invalid JSON is produced during remote api operations when a changeSet > contains duplicate keys. > -

[JIRA] (JENKINS-13584) Default view selected in Jenkins configuration is not reported properly via remote API.

Jason Howk created JENKINS-13584: Summary: Default view selected in Jenkins configuration is not reported properly via remote API. Key: JENKINS-13584 URL: https://issues.jenkins-ci.org/browse/JENKINS-13584

[JIRA] (JENKINS-13336) Invalid JSON is produced during remote api operations when a changeSet contains duplicate keys.

Jason Howk created JENKINS-13336: Summary: Invalid JSON is produced during remote api operations when a changeSet contains duplicate keys. Key: JENKINS-13336 URL: https://issues.jenkins-ci.org/browse/JENKINS-13336