[JIRA] (JENKINS-12875) No valid crumb was included in the request errors all around
Michael Decker commented on JENKINS-12875 No valid crumb was included in the request errors all around I've same issue, if I try to disable a project (use Jenkins v1.502): http://rhodan:8080/jenkins/job/myproject_3562/disable It looks like, I would have the same issue, if I would try to enable it, if it is disabled: JENKINS-14501 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12875) No valid crumb was included in the request errors all around
Michael Decker edited a comment on JENKINS-12875 No valid crumb was included in the request errors all around I've same issue, if I try to disable a project (use Jenkins v1.502): http://rhodan:8080/jenkins/job/myproject_3562/disable It looks like, I would have the same issue, if I would try to enable it, if it is disabled: JENKINS-14501 I tried to added these line to /opt/tomcat/bin/catalina.sh, but it didn't solve the issue: SNIP JAVA_OPTS="$JAVA_OPTS -Dhudson.security.csrf.requestfield=crumb" SNAP This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15622) After renaming job, old job page is opened again
Michael Decker created JENKINS-15622 After renaming job, old job page is opened again Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: JenkinsRenameIssue.txt Components: core Created: 25/Oct/12 8:01 AM Description: Steps: 1. Open job MyJob_A: http://myjenkins/jenkins/job/MyJob_A 2. Invoke a rename to MyJob_B http://myjenkins/jenkins/job/MyJob_A/rename?newName=MyJob_B 3. Confirm the rename - expected: new job is opened: http://myjenkins/jenkins/job/MyJob_B - current and invalid result: old job is opened NullPointerException http://myjenkins/jenkins/job/MyJob_A Environment: Jenkins v1.485 and v1.487 Project: Jenkins Labels: jenkins job Priority: Minor Reporter: Michael Decker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
