• Type: Bug
• Resolution: Duplicate
• Priority: Blocker
• Component/s: jms-messaging-plugin
• Labels:

  • tables-to-divs-regression
• Environment:

  Jenkins 2.286 running in podman
  
  image url:
  docker.io/jenkins/jenkins:jdk11

1. system.log

   16 kB

   2021-03-31 03:55

2. error.log

   10 kB

   2021-03-31 03:49

[JENKINS-65267] JMS messaging plugin causes JSONObject["hudson-triggers-SCMTrigger"] is not a JSONObject if SCM polling enabled on 2.277.1

Aleksandr created issue - 2021-03-31 03:49

Aleksandr made changes - 2021-03-31 03:50

Priority

Original: Minor [ 4 ]

New: Blocker [ 1 ]

Aleksandr made changes - 2021-03-31 03:55

Attachment

Original: system.log [ 54386 ]

Aleksandr made changes - 2021-03-31 03:55

Attachment

New: system.log [ 54388 ]

Aleksandr made changes - 2021-03-31 03:56

Description

Original: Hello everybody! When I try to save the task, I get an error (in attachment "error.log") There is also a system log with json-data. Json is completely correct This happened after a recent jenkins update   Please help solve the problem. If the problem is in one of the plugins - how to understand which one?

New: Hello everybody! When I try to save the task, I get an error (in attachment "error.log") There is also a system log with json-data. Json is completely correct This happened after a recent jenkins update   The error disappears if you remove the SCM polling schedule   Please help solve the problem. If the problem is in one of the plugins - how to understand which one?

Aleksandr made changes - 2021-03-31 03:59

Description

Original: Hello everybody! When I try to save the task, I get an error (in attachment "error.log") There is also a system log with json-data. Json is completely correct This happened after a recent jenkins update   The error disappears if you remove the SCM polling schedule   Please help solve the problem. If the problem is in one of the plugins - how to understand which one?

New: Hello everybody! When I try to save the task, I get an error (in attachment "error.log") There is also a system log with json-data. Json is completely correct This happened after a recent jenkins update   The error disappears if you remove the SCM polling schedule   Please help solve the problem. If the problem is in one of the plugins - how to understand which one?

Aleksandr made changes - 2021-03-31 05:07

Environment

New: Jenkins 2.286 running in podman image url: docker.io/jenkins/jenkins:jdk11

Mark Waite made changes - 2021-03-31 05:22

Component/s		New: jms-messaging-plugin [ 21951 ]
Component/s	Original: core [ 15593 ]

Mark Waite made changes - 2021-03-31 05:22

Labels

New: tables-to-divs-regression

Mark Waite made changes - 2021-03-31 05:23

Summary

Original: JSONObject["hudson-triggers-SCMTrigger"] is not a JSONObject.

New: JMS messaging plugin causes JSONObject["hudson-triggers-SCMTrigger"] is not a JSONObject if SCM polling enabled on 2.277.1

Mark Waite made changes - 2021-03-31 05:28

Link

New: This issue duplicates JENKINS-62863 [ JENKINS-62863 ]

Mark Waite made changes - 2021-03-31 05:28

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]