[JIRA] [core] (JENKINS-12017) Seriously slow rendering/loading times for the job/foo/configure page
Hiran Chaudhuri commented on JENKINS-12017 Seriously slow rendering/loading times for the job/foo/configure page Some way out: Meanwhile I tested some more containers. It seems regardless which version of JBoss or Tomcat you use the performance is incredibly slow. The performance issue does not come from a specific plugin. As soon as you switch to the builtin Winstone servlet container Jenkins responds fast. To run it with the internal container, launch it like: java -jar jenkins.jar If noone can investigate where this problem comes from or how otherwise it could be resolved then it may make sense to not name the distribution 'war'? 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] [ssh-slaves] (JENKINS-22651) Could not copy slave.jar into ... on slave
Yves Schumann commented on JENKINS-22651 Could not copy slave.jar into ... on slave You made my day! That was the input which leads to the right direction. Did not even know that there is such a difference in between ssh and scp. You're completely right, plain ssh works but scp not: jenkins@flieger:~$ scp -i .ssh/builder07 tmp/foobar.txt alpine_2_7_x86:~/ Couldn't open /dev/null: Permission denied lost connection jenkins@flieger:~$ After setting proper permissions on /dev/null, jenkins is able to connect to the node again. Thank you very much for the push into the right directions. Have to investigate now, why the permission on /dev/null was set wrong. But that's a different story... 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] [core] (JENKINS-23994) Add autocompletion for logger names when configuring a log recorder
SCM/JIRA link daemon commented on JENKINS-23994 Add autocompletion for logger names when configuring a log recorder Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/logging/LogRecorder.java core/src/main/resources/hudson/logging/LogRecorder/configure.jelly http://jenkins-ci.org/commit/jenkins/316b21db26c8c629207aab30de6fd056642f3249 Log: FIXED JENKINS-23994 Autocomplete logger names 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] [core] (JENKINS-23994) Add autocompletion for logger names when configuring a log recorder
SCM/JIRA link daemon commented on JENKINS-23994 Add autocompletion for logger names when configuring a log recorder Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/logging/LogRecorder.java core/src/main/resources/hudson/logging/LogRecorder/configure.jelly http://jenkins-ci.org/commit/jenkins/01c8c2239dac8fe5536cc613130746ddb6889d97 Log: Merge pull request #1339 from daniel-beck/JENKINS-23994 FIXED JENKINS-23994 Autocomplete logger names 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] [core] (JENKINS-23994) Add autocompletion for logger names when configuring a log recorder
SCM/JIRA link daemon resolved JENKINS-23994 as Fixed Add autocompletion for logger names when configuring a log recorder Change By: SCM/JIRA link daemon (27/Jul/14 7:45 AM) Status: InProgress 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 -- 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] [ssh-slaves] (JENKINS-22651) Could not copy slave.jar into ... on slave
Yves Schumann edited a comment on JENKINS-22651 Could not copy slave.jar into ... on slave You made my day! That was the input which leads to the right direction. Did not even know that there is such a difference in between ssh and scp. You're completely right, plain ssh works but scp not: jenkins@flieger:~$ scp -i .ssh/builder07 tmp/foobar.txt alpine_2_7_x86:~/ Couldn't open /dev/null: Permission denied lost connection jenkins@flieger:~$ After setting proper permissions on /dev/null, jenkins is able to connect to the node again. Thank you very much for the push into the right direction. Have to investigate now, why the permission on /dev/null was set wrong. But that's a different story... 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] [ssh-slaves] (JENKINS-22651) Could not copy slave.jar into ... on slave
Daniel Beck resolved JENKINS-22651 as Not A Defect Could not copy slave.jar into ... on slave Resolving as not a defect: Server configuration issue. Change By: Daniel Beck (27/Jul/14 7:56 AM) Status: Open Resolved Resolution: NotADefect 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] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
John Ferlito commented on JENKINS-22820 Changes are not commited when using a recent git client I'm seeing the same issue. Let me know if there is anything I can do to help debug. 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] [core] (JENKINS-23994) Add autocompletion for logger names when configuring a log recorder
dogfood commented on JENKINS-23994 Add autocompletion for logger names when configuring a log recorder Integrated in jenkins_main_trunk #3554 FIXED JENKINS-23994 Autocomplete logger names (Revision 316b21db26c8c629207aab30de6fd056642f3249) Result = SUCCESS daniel-beck : 316b21db26c8c629207aab30de6fd056642f3249 Files : core/src/main/resources/hudson/logging/LogRecorder/configure.jelly core/src/main/java/hudson/logging/LogRecorder.java 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] [cli] (JENKINS-23988) @CLIMethods do not support authentication via SecurityRealm's CLIAuthenticator
Daniel Beck started work on JENKINS-23988 @CLIMethods do not support authentication via SecurityRealms CLIAuthenticator Change By: Daniel Beck (27/Jul/14 10:30 AM) Status: Open InProgress 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] [core] (JENKINS-12017) Seriously slow rendering/loading times for the job/foo/configure page
Daniel Beck commented on JENKINS-12017 Seriously slow rendering/loading times for the job/foo/configure page Would be interesting to see a sampling of thread dumps while the config page is loading, to see in what code the thread is spending most time. 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] [core] (JENKINS-23435) Job scheduled with 'H' breaks with Invalid input expecting EOF
Daniel Beck resolved JENKINS-23435 as Not A Defect Job scheduled with H breaks with Invalid input expecting EOF Not a defect: A correct cron _expression_ has five components, yours has six. Change By: Daniel Beck (27/Jul/14 10:43 AM) Status: Open Resolved Resolution: NotADefect 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] [ant] (JENKINS-23207) Issue when saving/applying changes.
Daniel Beck commented on JENKINS-23207 Issue when saving/applying changes. Use your browser's developer tools to determine the full request (headers, body, everything) sent. Post it here. Include a full list of plugins installed, and a screenshot of the job config page showing everything you'd like to configure (i.e. what your input is). 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] [core] (JENKINS-23068) Jenkins logs that Jetty SNAPSHOT version is used during startup
Daniel Beck
commented on JENKINS-23068
Jenkins logs that Jetty SNAPSHOT version is used during startup
It seems winstone 2.x should set the system property jetty.version, as it's used by org.eclipse.jetty.server.Server to provide the log output:
static
{
if (Server.class.getPackage()!=null
"Eclipse.org - Jetty".equals(Server.class.getPackage().getImplementationVendor())
Server.class.getPackage().getImplementationVersion()!=null)
__version=Server.class.getPackage().getImplementationVersion();
else
__version=System.getProperty("jetty.version","8.y.z-SNAPSHOT");
}
The actual Jetty distribution used is a real release, jetty-8.1.12.v20130726
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] [core] (JENKINS-17825) Configure Job page makes IE10 crash down completely
Daniel Beck commented on JENKINS-17825 Configure Job page makes IE10 crash down completely Martin: Any non-default plugins installed? 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] [extra-columns] (JENKINS-23756) Column suggestion for Extra Column plugin
Fred G commented on JENKINS-23756 Column suggestion for Extra Column plugin Yes, this issue can be 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 -- 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-12017) Seriously slow rendering/loading times for the job/foo/configure page
Hiran Chaudhuri commented on JENKINS-12017 Seriously slow rendering/loading times for the job/foo/configure page I do not think a thread dump would be very representative unless we are in a deadlock situation. When I tried to use the JVisualVM profiler (included in Oracle JDK) it seemed that a lot of time is spent in the java reflection API called during tag rendering. 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] [core] (JENKINS-12017) Seriously slow rendering/loading times for the job/foo/configure page
Hiran Chaudhuri edited a comment on JENKINS-12017 Seriously slow rendering/loading times for the job/foo/configure page Some way out: Meanwhile I tested some more containers. It seems regardless which version of JBoss or Tomcat you use the performance is incredibly slow. The performance issue does not come from a specific plugin. As soon as you switch to the builtin Winstone servlet container Jenkins responds fast. To run it with the internal container, launch it like: java -jar jenkins.war If noone can investigate where this problem comes from or how otherwise it could be resolved then it may make sense to not name the distribution 'war'? 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] [cppcheck] (JENKINS-23185) Setting build status to FAILURE for new error when errors were fixed
SCM/JIRA link daemon commented on JENKINS-23185 Setting build status to FAILURE for new error when errors were fixed Code changed in jenkins User: Michal Turek Path: src/main/java/org/jenkinsci/plugins/cppcheck/util/CppcheckBuildResultEvaluator.java http://jenkins-ci.org/commit/cppcheck-plugin/cb4e2040c7a92ac16f8fca293d8e19f313b96fcc Log: JENKINS-23185 Setting build status to FAILURE for new error when errors were fixed CppcheckBuildResultEvaluator.isErrorCountExceeded() used comparison count threshold but users expect count = threshold. For example the threshold had to be set to 0 to change build status on 1 new issue. Setting 1 in threshold configuration to detect 1 issue is much better. Information in build log extended to contain also the value that exceeded the threshold. Word "errors" replaced by "issues". 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] [cppcheck] (JENKINS-23185) Setting build status to FAILURE for new error when errors were fixed
SCM/JIRA link daemon commented on JENKINS-23185 Setting build status to FAILURE for new error when errors were fixed Code changed in jenkins User: Michal Turek Path: src/main/java/org/jenkinsci/plugins/cppcheck/util/CppcheckBuildResultEvaluator.java http://jenkins-ci.org/commit/cppcheck-plugin/87401a045be16953d82178c189ddff52d5154407 Log: Merge pull request #20 from mixalturek/master JENKINS-23185 Setting build status to FAILURE for new error when error... Compare: https://github.com/jenkinsci/cppcheck-plugin/compare/a49002550cbd...87401a045be1 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] [cppcheck] (JENKINS-23185) Setting build status to FAILURE for new error when errors were fixed
Michal Turek resolved JENKINS-23185 as Fixed Setting build status to FAILURE for new error when errors were fixed Fixed, will be released in version 1.19. Change By: Michal Turek (27/Jul/14 2:49 PM) Status: InProgress Resolved Fix Version/s: current 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 -- 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] [cppcheck] (JENKINS-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
Michal Turek started work on JENKINS-23888 Add query parameter support for filtering errors based on new, resolved or unchanged Change By: Michal Turek (27/Jul/14 2:53 PM) Status: Open InProgress 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] [cppcheck] (JENKINS-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
Michal Turek assigned JENKINS-23888 to Michal Turek Add query parameter support for filtering errors based on new, resolved or unchanged Change By: Michal Turek (27/Jul/14 2:53 PM) Assignee: GregoryBoissinot MichalTurek 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] [core] (JENKINS-23840) Update default font to Helvetica
SCM/JIRA link daemon commented on JENKINS-23840 Update default font to Helvetica Code changed in jenkins User: Daniel Beck Path: changelog.html http://jenkins-ci.org/commit/jenkins/280f36de014ea8c793f889a49f0475290afee595 Log: Reference JENKINS-23840 for #1315 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] [core] (JENKINS-18902) Clicking the (detail) link under Changes in dependency shows incorrect changes
SCM/JIRA link daemon resolved JENKINS-18902 as Fixed Clicking the (detail) link under Changes in dependency shows incorrect changes Change By: SCM/JIRA link daemon (27/Jul/14 3:47 PM) Status: InProgress 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 -- 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-18902) Clicking the (detail) link under Changes in dependency shows incorrect changes
SCM/JIRA link daemon commented on JENKINS-18902 Clicking the (detail) link under Changes in dependency shows incorrect changes Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/Functions.java core/src/main/resources/hudson/model/AbstractProject/changes.jelly core/src/main/resources/hudson/model/AbstractProject/changes.properties core/src/main/resources/hudson/model/AbstractProject/changes_da.properties core/src/main/resources/hudson/model/AbstractProject/changes_de.properties core/src/main/resources/hudson/model/AbstractProject/changes_es.properties core/src/main/resources/hudson/model/AbstractProject/changes_fr.properties core/src/main/resources/hudson/model/AbstractProject/changes_ja.properties core/src/main/resources/hudson/model/AbstractProject/changes_lv.properties core/src/main/resources/hudson/model/AbstractProject/changes_pt_BR.properties core/src/main/resources/hudson/model/AbstractProject/changes_ru.properties core/src/main/resources/hudson/model/AbstractProject/changes_tr.properties core/src/main/resources/hudson/model/AbstractProject/changes_zh_TW.properties http://jenkins-ci.org/commit/jenkins/25acdd8850ba949d42417febe735dc518e29db80 Log: FIXED JENKINS-18902 Exclude lower bound of range from changes 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] [core] (JENKINS-18902) Clicking the (detail) link under Changes in dependency shows incorrect changes
SCM/JIRA link daemon commented on JENKINS-18902 Clicking the (detail) link under Changes in dependency shows incorrect changes Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/Functions.java core/src/main/resources/hudson/model/AbstractProject/changes.jelly core/src/main/resources/hudson/model/AbstractProject/changes.properties core/src/main/resources/hudson/model/AbstractProject/changes_da.properties core/src/main/resources/hudson/model/AbstractProject/changes_de.properties core/src/main/resources/hudson/model/AbstractProject/changes_es.properties core/src/main/resources/hudson/model/AbstractProject/changes_fr.properties core/src/main/resources/hudson/model/AbstractProject/changes_ja.properties core/src/main/resources/hudson/model/AbstractProject/changes_lv.properties core/src/main/resources/hudson/model/AbstractProject/changes_pt_BR.properties core/src/main/resources/hudson/model/AbstractProject/changes_ru.properties core/src/main/resources/hudson/model/AbstractProject/changes_tr.properties core/src/main/resources/hudson/model/AbstractProject/changes_zh_TW.properties http://jenkins-ci.org/commit/jenkins/578b513f5379c8efae32f0369be8a9c5e9a06988 Log: Merge pull request #1303 from daniel-beck/JENKINS-18902 FIXED JENKINS-18902 Exclude lower bound of range from changes Compare: https://github.com/jenkinsci/jenkins/compare/75578e9fbd5b...578b513f5379 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] [core] (JENKINS-12017) Seriously slow rendering/loading times for the job/foo/configure page
evernat edited a comment on JENKINS-12017 Seriously slow rendering/loading times for the job/foo/configure page Hiran Chaudhuri, Jenkins is often launched with the internal container, but other containers are also supported by the community. In particular, I think that the Jetty and Tomcat containers are probably well supported. As can be seen in this issue, it has happened that the job/foo/configure page was slow. And it was often caused by one plugin or the other and by a specific job context (size of logs, size of artifacts). So, first, you should give your specific Jenkins (1.572?), Tomcat version, Java version, OS, list of plugins, slaves, number of jobs, ... And then yes, please take samples of thread dump when the page is loading (http://localhost:8080/threadDump), so we can try to find the cause. My own Monitoring plugin may also help with the general performance of a server. The community may help you, and possibly find a Jenkins bug, only if you give some data. 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] [core] (JENKINS-12017) Seriously slow rendering/loading times for the job/foo/configure page
evernat commented on JENKINS-12017 Seriously slow rendering/loading times for the job/foo/configure page Hiran Chaudhuri Jenkins is often launched with the internal container, but other containers are also supported by the community. In particular, I think that the Jetty and Tomcat containers are probably well supported. As can be seen in this issue, it has happened that the job/foo/configure page was slow. And it was often caused by one plugin or the other and by a specific job context (size of logs, size of artifacts). So, first, you should give your specific Jenkins (1.572?), Tomcat version, Java version, OS, list of plugins, slaves, number of jobs, ... And then yes, please take samples of thread dump when the page is loading (http://localhost:8080/threadDump), so we can try to find the cause. My own Monitoring plugin may also help with the general performance of a server. The community may help you, and possibly find a Jenkins bug, only if you give some data. 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] [gradle] (JENKINS-22237) Gradle available versions should be in descending order.
Gregory SSI-YAN-KAI commented on JENKINS-22237 Gradle available versions should be in descending order. Pull request submitted: https://github.com/jenkinsci/backend-crawler/pull/23 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] [gradle] (JENKINS-13130) Gradle Plugin - Gradle distribution URL has changed
Gregory SSI-YAN-KAI commented on JENKINS-13130 Gradle Plugin - Gradle distribution URL has changed This issue has been fixed with commit: https://github.com/jenkinsci/backend-crawler/commit/7517d64e7eeec2775c86441e6fe32760626d096f#diff-3c3161ef96eeb66ea8060f56589c8437 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] [cppcheck] (JENKINS-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
Michal Turek updated JENKINS-23888 Add query parameter support for filtering errors based on new, resolved or unchanged Change By: Michal Turek (27/Jul/14 5:16 PM) Attachment: state_filter.png 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] [core] (JENKINS-18902) Clicking the (detail) link under Changes in dependency shows incorrect changes
dogfood commented on JENKINS-18902 Clicking the (detail) link under Changes in dependency shows incorrect changes Integrated in jenkins_main_trunk #3556 FIXED JENKINS-18902 Exclude lower bound of range from changes (Revision 25acdd8850ba949d42417febe735dc518e29db80) Result = SUCCESS daniel-beck : 25acdd8850ba949d42417febe735dc518e29db80 Files : core/src/main/resources/hudson/model/AbstractProject/changes_tr.properties core/src/main/resources/hudson/model/AbstractProject/changes_ja.properties core/src/main/resources/hudson/model/AbstractProject/changes_da.properties core/src/main/resources/hudson/model/AbstractProject/changes_es.properties core/src/main/resources/hudson/model/AbstractProject/changes_lv.properties core/src/main/resources/hudson/model/AbstractProject/changes_fr.properties core/src/main/java/hudson/Functions.java core/src/main/resources/hudson/model/AbstractProject/changes_zh_TW.properties core/src/main/resources/hudson/model/AbstractProject/changes.jelly core/src/main/resources/hudson/model/AbstractProject/changes_de.properties core/src/main/resources/hudson/model/AbstractProject/changes_ru.properties core/src/main/resources/hudson/model/AbstractProject/changes.properties core/src/main/resources/hudson/model/AbstractProject/changes_pt_BR.properties 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] [cppcheck] (JENKINS-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
SCM/JIRA link daemon commented on JENKINS-23888 Add query parameter support for filtering errors based on new, resolved or unchanged Code changed in jenkins User: Michal Turek Path: src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckDiffState.java src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckResult.java src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckResult/details.jelly src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckSourceAll/index.jelly http://jenkins-ci.org/commit/cppcheck-plugin/d48f4da9b8136073d7ec4d49bd7c5483065c4d28 Log: JENKINS-23888 Add query parameter support for filtering errors based on new, resolved or unchanged New optional "states" parameter added to cppcheckResult/source.all page. It's a comma separated filter with states to include to the output (e.g. "?states=new,solved"). 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] [cppcheck] (JENKINS-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
Michal Turek resolved JENKINS-23888 as Fixed Add query parameter support for filtering errors based on new, resolved or unchanged Implemented, will be released in version 1.19. Change By: Michal Turek (27/Jul/14 5:19 PM) Status: InProgress Resolved Fix Version/s: current 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 -- 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] [cppcheck] (JENKINS-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
SCM/JIRA link daemon commented on JENKINS-23888 Add query parameter support for filtering errors based on new, resolved or unchanged Code changed in jenkins User: Michal Turek Path: src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckDiffState.java src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckResult.java src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckResult/details.jelly src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckSourceAll/index.jelly http://jenkins-ci.org/commit/cppcheck-plugin/2a17c3587b65b337c59ae36d9c5d5de508c2ad79 Log: Merge pull request #21 from mixalturek/master JENKINS-23888 Add query parameter support for filtering errors based o... Compare: https://github.com/jenkinsci/cppcheck-plugin/compare/87401a045be1...2a17c3587b65 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] [core] (JENKINS-20663) file name encoding broken in zip archives
Daniel Beck commented on JENKINS-20663 file name encoding broken in zip archives Jesse's fix was released today in 1.574. Feedback would be great. 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] [perforce] (JENKINS-9572) Cannot use regular expressions on Poll Exclude User(s) to restrict build triggers to a particular list of users.
Gregory SSI-YAN-KAI commented on JENKINS-9572 Cannot use regular expressions on Poll Exclude User(s) to restrict build triggers to a particular list of users. I did not reproduce the problem outlined in the description with version 1.3.27. The regular _expression_ that I used is: ^((?!(john\.doe|jane\.smith)).*)$ The documentation is pretty explicit: it states that the "Poll Exclude User(s)" feature supports Java regular expressions with a link to http://docs.oracle.com/javase/6/docs/api/java/util/regex/Pattern.html I think the issue can be 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 -- 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] [github] (JENKINS-23995) Adding commit status context in github-plugin
Marc Tardif created JENKINS-23995 Adding commit status context in github-plugin Issue Type: Improvement Assignee: Unassigned Components: github Created: 27/Jul/14 9:19 PM Description: The github-api seems to support the new commit status context in org.kohsuke.github.GHRepository. Are there any plans to use this option in com.cloudbees.jenkins.GitHubCommitNotifier? Project: Jenkins Priority: Major Reporter: Marc Tardif 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] [core] (JENKINS-23996) Toggling show test # and failure # to just show failures ignored in some cases in multi-configuration jobs
Mark Waite updated JENKINS-23996 Toggling show test # and failure # to just show failures ignored in some cases in multi-configuration jobs Change By: Mark Waite (27/Jul/14 11:30 PM) Summary: Toggling between showtest#andfailure# and to justshowfailuresignoredin somecasesin multi-configurationjobs 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] [core] (JENKINS-23996) Toggling between show test # and failure # and just show failures ignored in multi-configuration jobs
Mark Waite created JENKINS-23996 Toggling between show test # and failure # and just show failures ignored in multi-configuration jobs Issue Type: Bug Assignee: Unassigned Components: core Created: 27/Jul/14 11:30 PM Description: A multi-configuration job is composed of one or more configurations. The results of the build in each of those configurations can be reached from the top level job page. The top level job page correctly toggles JUnit test results between "just show failures" and "show test # and failure #" when I click the link below the JUnit test result graph. The job page for any of the configurations do not toggle JUnit test results between "just show failures" and "show test # and failure #" when I click the link below the JUnit test result graph. Clicking the link does not change the displayed graph for that configuration. If I change the top level job page, the new setting is honored in each configuration job page. It is only within the configuration job page that the click on the toggle link is ignored. Steps to show the problem: Define a multi-configuration job with at least two configurations Include a component in the job which will generate junit test results Configure the job to display JUnit test results Run the job twice so that test results are visible in a graph on the top page of the job Toggle the graph on the top page between "just show failures" and not Open the job page of one of the configurations Attempt to toggle the graph between "just show failures" and not on the configuration job page Environment: Jenkins 1.554.3 Debian 7.0 x64 (Wheezy) Oracle JDK 1.7.0_65 Project: Jenkins Priority: Trivial Reporter: Mark Waite 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] [jira] (JENKINS-18166) Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7
John Gibson commented on JENKINS-18166 Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7 Just a heads up that SOAP won't be removed until JIRA 8. Atlassian updated the linked article last month. 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] [git] (JENKINS-22547) Git timeout setting does not work for checkout
Mark Waite commented on JENKINS-22547 Git timeout setting does not work for checkout The next git-client-plugin release after 1.10.0 will include the API support (and unit tests) for timeout on the checkout command. That is necessary to add timeout on checkout, but it is not sufficient. I hope to prepare a merge request for the git plugin which will provide the user interface necessary to access that API. While reviewing the git-plugin, it looks like the simplest approach will be to add a new "Additional Behaviour" for "Advanced checkout behaviours". The initial implementation would contain a single field for the user provided value of the checkout timeout in minutes. 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] [maven] (JENKINS-22277) Add support for Maven 3.2.1
Stephan Schroevers resolved JENKINS-22277 as Duplicate Add support for Maven 3.2.1 Change By: Stephan Schroevers (28/Jul/14 4:11 AM) Status: Open Resolved Resolution: Duplicate 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] [maven] (JENKINS-22277) Add support for Maven 3.2.1
Stephan Schroevers closed JENKINS-22277 as Duplicate Add support for Maven 3.2.1 Change By: Stephan Schroevers (28/Jul/14 4:13 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 -- 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] [maven] (JENKINS-22077) Allow automatic install of Maven 3.2.1
Stephan Schroevers resolved JENKINS-22077 as Fixed Allow automatic install of Maven 3.2.1 Change By: Stephan Schroevers (28/Jul/14 4:15 AM) 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 -- 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] [maven] (JENKINS-22077) Allow automatic install of Maven 3.2.1
Stephan Schroevers closed JENKINS-22077 as Fixed Allow automatic install of Maven 3.2.1 Change By: Stephan Schroevers (28/Jul/14 4:16 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 -- 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] [git] (JENKINS-22547) Git timeout setting does not work for checkout
Mark Waite assigned JENKINS-22547 to Mark Waite Git timeout setting does not work for checkout Change By: Mark Waite (28/Jul/14 4:21 AM) Assignee: NicolasDeLoof MarkWaite 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] [groovy] (JENKINS-23997) Unable to specify multiple jars on classpath for a system groovy script
Ben Sullivan created JENKINS-23997 Unable to specify multiple jars on classpath for a system groovy script Issue Type: Bug Affects Versions: current Assignee: vjuranek Components: groovy Created: 28/Jul/14 5:43 AM Description: Hi - apologies I wasn't sure what to do here so I raised an issue. Sorry if this is not standard protocol. So on 1.574 I am trying to create a system Groovy script that requires two jars. The field where you enter the jar names asks you to enter a jar one per line but the field only allows one line. The groovy script alternative indeed allows a multi line list of jars so that works but the system script does not. Is there a workaround for the time being I can use? Could you confirm either way if you believe this is a bug and if it is, is there work in the pipeline to address it? Many thanks Ben Project: Jenkins Priority: Major Reporter: Ben Sullivan 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.
