[
https://issues.jenkins-ci.org/browse/JENKINS-12806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159176#comment-159176
]
Mike Henderson commented on JENKINS-12806:
------------------------------------------
If I remove security by allowing everyone to do anything the bug changes to
showing a parsing error in the workspace mapping at the line where it flows
over 2975 bytes.
This error does not seem to effect the job itself and the entire workspace is
synced just fine. I hope that helps to pinpoint the issue.
> Perforce Plugin causes config page to throw error if workspace mapping
> exceeds 2974 bytes
> -----------------------------------------------------------------------------------------
>
> Key: JENKINS-12806
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12806
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
> Affects Versions: current
> Environment: Windows 2003 R1 32 Bit / Jenkins 1.450 / Perforce 1.3.7
> Reporter: Mike Henderson
> Labels: jenkins, user, windows
> Attachments: config.xml
>
>
> I have a job that gathers a lot of different components from Perforce and we
> recently added a few new lines. After the job built once we attemt to go
> back into the config screen for the job and the settings come up but we get a
> "ERROR" just below the mapping that once you click on it it shows a 404 error
> and after that the user is logged out of Jenkins. If I delete the project
> mapping from the config.xml and reload from the disk the job is editable
> again until the next build. I have tried to use the clientspec feature but
> this also adds back in the <projectPath> key in the config.xml and again the
> error reoccurs after the first build. Right now the only work around is to
> modify the job file manually with a text editor. The jobs seem to build just
> fine. I have attached a job config file to show the issue. If I reduce the
> mapping down to 2974 bytes the error goes away and does not seem to return.
> My feeling is it is in the parser of the mapping, but that is a guess. For
> user login control we currently are using "Project-based Matrix Authorization
> Strategy" with "Jenkins's own user database".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
