Quantcast

[JIRA] (JENKINS-14721) 500 error switching to Pegdown

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14721) 500 error switching to Pegdown

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Affects Versions: current
Assignee: bap
Attachments: stacktrace.out
Components: pegdown-formatter-plugin
Created: 07/Aug/12 11:58 PM
Description:

Attempting to use Pegdown formatter plugin. At /configure, select "enable security," realm "Jenkins's own user database," with "Project-based Matrix Authorization Strategy."

Change Markup Formatter selector to "PegDown," hit save, get 500 error with stacktrace (attached).

Jenkins version 1.476, PegDown formatter plugin 1.3.

Project: Jenkins
Priority: Major Major
Reporter: Charles Johnson
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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14721) 500 error switching to Pegdown

JIRA noreply@jenkins-ci.org
Charles Johnson resolved Bug JENKINS-14721 as Fixed

This now works correctly as of Jenkins 1.477

Change By: Charles Johnson (15/Aug/12 6:20 PM)
Status: Open Resolved
Resolution: Fixed
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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14721) 500 error switching to Pegdown

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
bap closed Bug JENKINS-14721 as Fixed
Change By: bap (13/Sep/12 10:03 AM)
Status: Resolved Closed
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
Loading...