[JIRA] (JENKINS-49959) ownership-plugin 0.12.0 breaks creating new job from existing job
Title: Message Title Curtis Ruck created an issue Jenkins / JENKINS-49959 ownership-plugin 0.12.0 breaks creating new job from existing job Issue Type: Bug Assignee: Oleg Nenashev Components: ownership-plugin Created: 2018-03-06 19:01 Priority: Critical Reporter: Curtis Ruck On a system with ownership-plugin 0.12.0, when trying to create a new job from an existing job, we receive "java.io.InvalidObjectException: ruckc is missing the Overall/Administer permission" when on the job, the ruckc user has inherited the permissions from the parent ACL. If ruckc gets the Manage Ownership permission directly, the issue isn't present. It appears that the Ownership permission checks need to pull job permissions and adhere to inherited permissions also. Add Comment
[JIRA] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title Curtis Ruck commented on JENKINS-23697 Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) Getting this also on a new job, just straight building https://github.com/codice/ddf.git with a maven job and "clean install". Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [artifactory] (JENKINS-19005) Cannot deploy on Artifactory
Curtis Ruck commented on JENKINS-19005 Cannot deploy on Artifactory I'm having this occur since last thursday/friday. 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-13023) Mantis Plugin causes Configuration Loading Overlay to not disappear.
[
https://issues.jenkins-ci.org/browse/JENKINS-13023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160111#comment-160111
]
Curtis Ruck commented on JENKINS-13023:
---
FF 10, IE 9, and Chrome Stable all show the same issue.
> Mantis Plugin causes Configuration Loading Overlay to not disappear.
>
>
> Key: JENKINS-13023
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13023
> Project: Jenkins
> Issue Type: Bug
> Components: mantis
>Affects Versions: current
>Reporter: Curtis Ruck
>Assignee: sogabe
>
> This appears to come from Mantis's global.jelly, function checkUrl(base) {
> var url = encodeURIComponent(Form.findMatchingInput(base,'mantis.url').value);
> Uncaught TypeError: Object # has no method 'findMatchingInput'
> checkUrlconfigure:384
> (anonymous function)
> e.targetUrlhudson-behavior.js:339
> registerValidatorhudson-behavior.js:344
> applybehavior.js:73
> (anonymous function)behavior.js:79
> Behaviour.applySubtreebehavior.js:68
> Behaviour.applybehavior.js:54
> (anonymous function)behavior.js:49
> window.onload
--
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
[JIRA] (JENKINS-13023) Mantis Plugin causes Configuration Loading Overlay to not disappear.
Curtis Ruck created JENKINS-13023:
-
Summary: Mantis Plugin causes Configuration Loading Overlay to not
disappear.
Key: JENKINS-13023
URL: https://issues.jenkins-ci.org/browse/JENKINS-13023
Project: Jenkins
Issue Type: Bug
Components: mantis
Affects Versions: current
Reporter: Curtis Ruck
Assignee: sogabe
This appears to come from Mantis's global.jelly, function checkUrl(base) { var
url = encodeURIComponent(Form.findMatchingInput(base,'mantis.url').value);
Uncaught TypeError: Object # has no method 'findMatchingInput'
checkUrlconfigure:384
(anonymous function)
e.targetUrlhudson-behavior.js:339
registerValidatorhudson-behavior.js:344
applybehavior.js:73
(anonymous function)behavior.js:79
Behaviour.applySubtreebehavior.js:68
Behaviour.applybehavior.js:54
(anonymous function)behavior.js:49
window.onload
--
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
[JIRA] (JENKINS-12787) LOADING overlay does not go away on the Configure System page
[
https://issues.jenkins-ci.org/browse/JENKINS-12787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160030#comment-160030
]
Curtis Ruck commented on JENKINS-12787:
---
I'm seeing this in the Mantis Plugin.
> LOADING overlay does not go away on the Configure System page
> -
>
> Key: JENKINS-12787
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12787
> Project: Jenkins
> Issue Type: Bug
> Components: gui
>Affects Versions: current
> Environment: Jenkins
>Reporter: Joshua Davis
> Labels: gui, jenkins
>
> After navigating to Manage->Configure System, the LOADING overlay never goes
> away. It is impossible to save any configuration changes.
> EXPECTED:
> * You can save your global configuration.
> Here is the stack trace from Chrome's JS console:
> {code}
> Uncaught TypeError: Object # has no method 'findMatchingInput'
> (anonymous function)
> e.targetUrl hudson-behavior.js:338
> registerValidator hudson-behavior.js:343
> apply behavior.js:73
> (anonymous function) behavior.js:79
> Behaviour.applySubtree behavior.js:68
> Behaviour.applybehavior.js:54
> (anonymous function)behavior.js:49
> window.onload
> {code}
--
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
[JIRA] (JENKINS-12307) Stack Trace when going to main configuration page
[
https://issues.jenkins-ci.org/browse/JENKINS-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159876#comment-159876
]
Curtis Ruck commented on JENKINS-12307:
---
Without disabling the Warnings Plugin, I can't modify anything on the Config
page.
Additionally, we need the warnings plugin for warnings, so we are disabling it,
bouncing jenkins, fixing the configuration, reenabling the plugin, and
continuing forward.
> Stack Trace when going to main configuration page
> -
>
> Key: JENKINS-12307
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12307
> Project: Jenkins
> Issue Type: Bug
> Components: warnings
>Reporter: mwebber
>Assignee: Ulli Hafner
>Priority: Minor
>
> When I go (in the web interface) to the main Jenkins configuration page, a
> stack trace is generated on the Jenkins console. No adverse results appear on
> the web page itself. From the stack track, it looks like it is connected to
> the warnings plugin.
> This is Jenkins 1.446 and Warnings plugin 3.26 (the latest available at the
> time of reporting). I have been noticing this stack track for some time now,
> including under earlier releases (I'm not sure how recently it started).
> The stack trace:
> {noformat}
> 05-Jan-2012 11:35:26 hudson.ExpressionFactory2$JexlExpression evaluate
> WARNING: Caught exception evaluating:
> descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason:
> java.lang.reflect.InvocationTargetException
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
> at
> org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
> at
> org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
> at
> org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
> at
> org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
> at
> org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
> at
> org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
> at
> org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
> at
> hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)
> at
> org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
> at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
> at
> org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
> at
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
> at
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
> at
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
> at
> org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at
> org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
> at
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
> at
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
> at
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
> at org.apache.commons.jelly.i
[JIRA] (JENKINS-5753) Standalone install does not work with Apache + mod_proxy_ajp + SSL
[
https://issues.jenkins-ci.org/browse/JENKINS-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159871#comment-159871
]
Curtis Ruck commented on JENKINS-5753:
--
Still having this issue with httpd 2.2.15, w/ 1.452. We have been using the
Jenkins RPM so its easier to stay current, any chance of switching winstone out
with Jetty?
> Standalone install does not work with Apache + mod_proxy_ajp + SSL
> --
>
> Key: JENKINS-5753
> URL: https://issues.jenkins-ci.org/browse/JENKINS-5753
> Project: Jenkins
> Issue Type: Bug
> Environment: CentOS release 5.4 (Final)
> 2.6.18-164.10.1.el5xen (64 bit)
> java version "1.6.0_16"
> hudson-1.347-1.1
> httpd-2.2.3-31.el5.centos.2
>Reporter: rombert
>
> I've configured hudson to only use the ajp connector using a command line
> similar to
> {noformat}
> /usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized
> -Djava.awt.headless=true -Xmx64m -DHUDSON_HOME=/space/hudson -jar
> /usr/lib/hudson/hudson.war --logfile=/var/log/hudson/hudson.log --daemon
> --prefix=hudson --httpPort=-1 --ajp13Port=8109 --debug=5 --handlerCountMax=10
> --handlerCountMaxIdle=0
> {noformat}
> I'm using the following apache configuration file
> {noformat}
> ProxyRequests Off
> ProxyPreserveHost On
>
> Order deny,allow
> Allow from all
>
> ProxyPass /hudson ajp://localhost:8109/hudson retry=1
> ProxyPassReverse /hudson ajp://localhost:8109/hudson
> {noformat}
> When accessing https://host/hudson , I get a 503 error page from Apache. The
> apache logs contain:
> {noformat}
> [Wed Feb 24 23:58:04 2010] [error] ajp_read_header: ajp_ilink_receive failed
> [Wed Feb 24 23:58:04 2010] [error] (120006)APR does not understand this error
> code: proxy: read response failed from (null) (localhost)
> {noformat}
> while the winstone logs contain:
> {noformat}
> [Winstone 2010/02/24 23:58:04] - Error within request handler thread
> java.lang.StringIndexOutOfBoundsException: String index out of range: 1065
> at java.lang.String.checkBounds(String.java:401)
> at java.lang.String.(String.java:442)
> at
> winstone.ajp13.Ajp13IncomingPacket.readString(Ajp13IncomingPacket.java:275)
> at
> winstone.ajp13.Ajp13IncomingPacket.parsePacket(Ajp13IncomingPacket.java:189)
> at
> winstone.ajp13.Ajp13Listener.allocateRequestResponse(Ajp13Listener.java:179)
> at winstone.RequestHandlerThread.run(RequestHandlerThread.java:79)
> at java.lang.Thread.run(Thread.java:619)
> {noformat}
> It's worth mentioning that this was working with Tomcat 6.0.20 , but stopped
> working when I tried to move over to the standalone install.
> I've tried various combinations with or without prefix, and the only one
> which seems to work is ajp without any prefix.
--
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
[JIRA] (JENKINS-12307) Stack Trace when going to main configuration page
[
https://issues.jenkins-ci.org/browse/JENKINS-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159763#comment-159763
]
Curtis Ruck commented on JENKINS-12307:
---
Are there any workarounds to get the config page to be usable again?
> Stack Trace when going to main configuration page
> -
>
> Key: JENKINS-12307
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12307
> Project: Jenkins
> Issue Type: Bug
> Components: warnings
>Reporter: mwebber
>Assignee: Ulli Hafner
>Priority: Minor
>
> When I go (in the web interface) to the main Jenkins configuration page, a
> stack trace is generated on the Jenkins console. No adverse results appear on
> the web page itself. From the stack track, it looks like it is connected to
> the warnings plugin.
> This is Jenkins 1.446 and Warnings plugin 3.26 (the latest available at the
> time of reporting). I have been noticing this stack track for some time now,
> including under earlier releases (I'm not sure how recently it started).
> The stack trace:
> {noformat}
> 05-Jan-2012 11:35:26 hudson.ExpressionFactory2$JexlExpression evaluate
> WARNING: Caught exception evaluating:
> descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason:
> java.lang.reflect.InvocationTargetException
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
> at
> org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
> at
> org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
> at
> org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
> at
> org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
> at
> org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
> at
> org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
> at
> org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
> at
> hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)
> at
> org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
> at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
> at
> org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
> at
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
> at
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
> at
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
> at
> org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at
> org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
> at
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
> at
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
> at
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
> (snip)
> at
> winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244)
> at winstone.RequestHandlerThread
