i have updated jenkins from 1.526 to 1.545 and after that any cli command fails with exception. the attached file contains the output of the "enable-job" command. for example the "help" and "version" command produces the same exception. this issue could be the same as JENKINS-20128.
- duplicates
-
JENKINS-20128 HTTP two-way remoting does not work (jenkins-cli.jar without JNLP)
-
- Resolved
-
[JENKINS-21209] any cli command fails with exception
Description | Original: i have updated jenkins from 1.526 to 1.545 and after that any cli command fails with exception. the attached file contains the output of the "enable-job" command. for example the "help" and "version" command produces the same exception. |
New:
i have updated jenkins from 1.526 to 1.545 and after that any cli command fails with exception. the attached file contains the output of the "enable-job" command. for example the "help" and "version" command produces the same exception. this issue could be the same as # |
Description |
Original:
i have updated jenkins from 1.526 to 1.545 and after that any cli command fails with exception. the attached file contains the output of the "enable-job" command. for example the "help" and "version" command produces the same exception. this issue could be the same as # |
New:
i have updated jenkins from 1.526 to 1.545 and after that any cli command fails with exception. the attached file contains the output of the "enable-job" command. for example the "help" and "version" command produces the same exception. this issue could be the same as |
Description |
Original:
i have updated jenkins from 1.526 to 1.545 and after that any cli command fails with exception. the attached file contains the output of the "enable-job" command. for example the "help" and "version" command produces the same exception. this issue could be the same as |
New:
i have updated jenkins from 1.526 to 1.545 and after that any cli command fails with exception. the attached file contains the output of the "enable-job" command. for example the "help" and "version" command produces the same exception. this issue could be the same as |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 153071 ] | New: JNJira + In-Review [ 194456 ] |
Does this still occur in recent Jenkins versions? How is Jenkins installed? What happens when you change the value of the option hudson.diyChunking as described on https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties ?