• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: envinject-plugin
• Labels:

  • configuration
  • job
  • plugin
• Environment:

  Win 7 Pro x68, Jenkins 1.521

[JENKINS-18630] EnvInject causes javascript hang when configuring job

kd Jm created issue - 2013-07-05 11:01

kd Jm made changes - 2013-07-05 11:01

Description

Original: - install EnvInject - load the configuration page of an existing or a new job - the javascript hangs or crashes: the page will always retain the grey overlay 'loading page'. Fields can be filled in, but upon clicking save, on error is shown, saying "Status Code: 400 Exception: This page expects a form submission"

New: - install EnvInject - load the configuration page of an existing or a new job - the javascript hangs or crashes: the page will always retain the grey overlay 'loading page'. Fields can be filled in, but upon clicking save, on error is shown, saying "Status Code: 400 Exception: This page expects a form submission" - this is checked on multiple browsers - uninstalling envinject fixes the problem.

Collapse comment: John Armenia added a comment - 2013-07-05 16:51

John Armenia added a comment - 2013-07-05 16:51

I can confirm I am seeing this as well.

Expand comment: John Armenia added a comment - 2013-07-05 16:51

John Armenia added a comment - 2013-07-05 16:51 I can confirm I am seeing this as well.

Collapse comment: Michael Lang added a comment - 2013-07-05 20:44, Edited by Michael Lang - 2013-07-05 20:45

Michael Lang added a comment - 2013-07-05 20:44 - edited

Same here. Although it looks like they're trying to address the issue in the next release (of jenkins). See this commit: https://github.com/jenkinsci/jenkins/commit/0256f0a74e9b3373fa9fa14ba32bf9cb99dd5ec3.

I was able to resolve this issue by downgrading to jenkins 1.519

Expand comment: Michael Lang added a comment - 2013-07-05 20:44, Edited by Michael Lang - 2013-07-05 20:45

Michael Lang added a comment - 2013-07-05 20:44 - edited Same here. Although it looks like they're trying to address the issue in the next release (of jenkins). See this commit: https://github.com/jenkinsci/jenkins/commit/0256f0a74e9b3373fa9fa14ba32bf9cb99dd5ec3 . I was able to resolve this issue by downgrading to jenkins 1.519

John Armenia made changes - 2013-07-08 12:11

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Collapse comment: John Armenia added a comment - 2013-07-08 12:12

John Armenia added a comment - 2013-07-08 12:12

Resolved in 1.522

Expand comment: John Armenia added a comment - 2013-07-08 12:12

John Armenia added a comment - 2013-07-08 12:12 Resolved in 1.522

Collapse comment: kd Jm added a comment - 2013-07-09 07:22

kd Jm added a comment - 2013-07-09 07:22

I confirm that: resolved in 1.522. Hurray!

Expand comment: kd Jm added a comment - 2013-07-09 07:22

kd Jm added a comment - 2013-07-09 07:22 I confirm that: resolved in 1.522. Hurray!

R. Tyler Croy made changes - 2016-07-25 23:55

Workflow

Original: JNJira [ 149940 ]

New: JNJira + In-Review [ 193362 ]