[JIRA] [extended-choice-parameter-plugin] (JENKINS-31458) Exception when saving job configuration
Title: Message Title Max Burdge commented on JENKINS-31458 Re: Exception when saving job configuration Same problem after upgrading to Jenkins 1.638. Using Extended Choice Parameters 0.52. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [jira-issue-updater-plugin] (JENKINS-31134) Role with id: Developer does not exist on Update Relevant Issues
Title: Message Title Max Burdge updated an issue Jenkins / JENKINS-31134 Role with id: Developer does not exist on Update Relevant Issues Change By: Max Burdge Summary: Failure to Role with id: Developer does not exist on Update JIRA issue Relevant Issues Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [jira-issue-updater-plugin] (JENKINS-31134) Failure to Update JIRA issue
Title: Message Title
Max Burdge created an issue
Jenkins / JENKINS-31134
Failure to Update JIRA issue
Issue Type:
Bug
Assignee:
Unassigned
Components:
jira-issue-updater-plugin
Created:
23/Oct/15 1:56 PM
Priority:
Minor
Reporter:
Max Burdge
Get this error since upgrade to 2.0.2:
jira rest client add comment error. cause: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors= {commentLevel=Role with id: Developer does not exist.}
, errorMessages=[]}]}
Jenkins version: 1.622 JIRA version: 6.47
Add Comment
[JIRA] [build-pipeline-plugin] (JENKINS-27537) Regular list project view failing to load with Build Pipeline 1.4.5 installed
Title: Message Title Max Burdge commented on JENKINS-27537 Re: Regular list project view failing to load with Build Pipeline 1.4.5 installed Same issue here, Jenkins 1.600 Build Pipeline 1.4.7. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-27537) Regular list project view failing to load with Build Pipeline 1.4.5 installed
Title: Message Title Max Burdge commented on JENKINS-27537 Re: Regular list project view failing to load with Build Pipeline 1.4.5 installed Tried downgrading Build Pipeline to 1.4.5, but error is still happening (Jenkins 1.600). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Max Burdge commented on JENKINS-24821 Jenkins missing build size in Build History Trend I have the same problem. Jenkins 1.587. Disk Usage 0.24. 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/d/optout.
[JIRA] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Max Burdge commented on JENKINS-17248 java.lang.NullPointerException by start Also experiencing this after upgrade to 1.508 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-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
Max Burdge commented on JENKINS-11024 Some commands dont work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others I would also like a solution or workaround for this issue. 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-14710) net.sf.json.JSONException: JSONObject[cvspassFile] not found when saving main configuration
Max Burdge updated JENKINS-14710 net.sf.json.JSONException: JSONObject[cvspassFile] not found when saving main configuration Change By: Max Burdge (07/Aug/12 2:16 PM) Component/s: cvs 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
