[JIRA] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Mike Scholze edited a comment on JENKINS-54209 Re: Can't read file: Can't access the file I think cppcheck plugin project is more or less dead. But you can use the new *warnings next generation* plugin. It contains cppcheck and visualize issues perfect perfectly .[https://wiki.jenkins.io/display/JENKINS/Warnings+Next+Generation+Plugin] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194846.154031736.20407.1559625180285%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Mike Scholze commented on JENKINS-54209 Re: Can't read file: Can't access the file I think cppcheck plugin project is more or less dead. But you can use the new warnings next generation plugin. It contains cppcheck and visualize issues perfect. https://wiki.jenkins.io/display/JENKINS/Warnings+Next+Generation+Plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194846.154031736.20397.1559625120410%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Mike Scholze commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors It is fixed with 2.138.2! https://jenkins.io/changelog-stable/ Update Winstone-Jetty from 4.4 to 5.0 to fix HTTP/2 support and threading problems on hosts with 30+ cores. (issue 53239, issue 52804, issue 51136, issue 52358) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Mike Scholze edited a comment on JENKINS-54209 Re: Can't read file: Can't access the file Same here after update from jenkins 2.107.3 to 2.138.2 and cppcheck plugin update from 1.21 to 1.24! * jenkins 2.138.2 * cppcheck plugin 1.24 * cppcheck 1.85Report not located in subdirectory.Downgrade the cppcheck plugin to 1.21 is not a solution, because the plugin can't render the diff html file. We urgently need feedback as our qa pipeline is affected. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Mike Scholze edited a comment on JENKINS-54209 Re: Can't read file: Can't access the file Same here after update from jenkins 2.107.3 to 2.138.2 and cppcheck plugin update from 1.21 to 1.24! * jenkins 2.138.2 * cppcheck plugin 1.24 * cppcheck 1.85Report not located in subdirectory. Downgrade the cppcheck plugin to 1.21 is not a solution, because the plugin can't render the diff html file. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Mike Scholze edited a comment on JENKINS-54209 Re: Can't read file: Can't access the file Same here after update from jenkins 2.107.3 to 2.138.2 and cppcheck plugin update from 1.21 to 1.24! * jenkins 2.138.2 * cppcheck plugin 1.24 * cppcheck 1.85 Report not located in subdirectory. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Mike Scholze edited a comment on JENKINS-54209 Re: Can't read file: Can't access the file Same here after update from jenkins 2.107.3 to 2.138.2 and cppcheck plugin update from 1.21 to 1.24 ! * jenkins 2.138.2 * cppcheck plugin 1.24 * cppcheck 1.85 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Mike Scholze commented on JENKINS-54209 Re: Can't read file: Can't access the file Same here! jenkins 2.138.2 cppcheck plugin 1.24 cppcheck 1.85 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53239) Use default Jetty QueuedThreadPool
Title: Message Title Mike Scholze commented on JENKINS-53239 Re: Use default Jetty QueuedThreadPool +1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title
Mike Scholze edited a comment on JENKINS-33412
Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors
Yes, that worked. (y) I have access to jenkins ui now and the jnlp slaves connected successfully.Tested with the following Dockerfile. I have overwritten the *jenkins.war* with yours (2.139-SNAPSHOT) and added the parameter.{code:java}// DockerfileFROM jenkins/jenkins:2.121.2COPY jenkins_winstone_pr_54.war /usr/share/jenkins/jenkins.warENTRYPOINT ["/sbin/tini", "--", "/usr/local/bin/jenkins.sh", "--useQTP"]{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Mike Scholze commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors Yes, that worked. I have access to jenkins ui now and the jnlp slaves connected successfully. Tested with the following Dockerfile. I have overwritten the jenkins.war with yours and added the parameter. // Dockerfile FROM jenkins/jenkins:2.121.2 COPY jenkins_winstone_pr_54.war /usr/share/jenkins/jenkins.war ENTRYPOINT ["/sbin/tini", "--", "/usr/local/bin/jenkins.sh", "--useQTP"] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Mike Scholze commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors No change with that env var. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title
Mike Scholze edited a comment on JENKINS-33412
Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors
[~olamy] these are not my log files.But now my test scenario: * Host system with 80 cores, ~500G RAM * Ubuntu 16.04.4 LTS * Docker 17.09.0-ce * Test-Docker-Image based on official docker jenkins image + jul.properties file: {noformat}// jul.propertieshandlers=java.util.logging.ConsoleHandler.level=INFOorg.eclipse.jetty.level=ALLjava.util.logging.ConsoleHandler.level=FINEST// DockerfileFROM jenkins/jenkins:2.121.2ENV JAVA_OPTS="${JAVA_OPTS} -Djava.util.logging.config.file=/usr/share/jenkins/jul.properties"COPY jul.properties /usr/share/jenkins/ENTRYPOINT ["/sbin/tini", "--", "/usr/local/bin/jenkins.sh"]{noformat}Logfile: [^jenkins_001_mikescholze_2.121.2.log]
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title
Mike Scholze edited a comment on JENKINS-33412
Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors
[~olamy] these are not my log files.But now my test scenario: * Host system with 80 cores, ~500G RAM * Ubuntu 16.04.4 LTS * Docker 17.09.0-ce * Test-Docker-Image based on official docker jenkins image + jul.properties file:{ code:java noformat }// jul.propertieshandlers=java.util.logging.ConsoleHandler.level=INFOorg.eclipse.jetty.level=ALLjava.util.logging.ConsoleHandler.level=FINEST // DockerfileFROM jenkins/jenkins:2.121.2 ENV JAVA_OPTS="${JAVA_OPTS} -Djava.util.logging.config.file=/usr/share/jenkins/jul.properties" COPY jul.properties /usr/share/jenkins/ ENTRYPOINT ["/sbin/tini", "--", "/usr/local/bin/jenkins.sh"] { code noformat } * Logfile: [^jenkins_001_mikescholze_2.121.2.log]
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title
Mike Scholze edited a comment on JENKINS-33412
Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors
[~olamy] these are not my log files.But now my test scenario: * Host system with 80 cores, ~500G RAM * Ubuntu 16.04.4 LTS * Docker 17.09.0-ce * Test-Docker-Image based on official docker jenkins image + jul.properties file:{code:java}// jul.propertieshandlers=java.util.logging.ConsoleHandler.level=INFOorg.eclipse.jetty.level=ALLjava.util.logging.ConsoleHandler.level=FINEST// DockerfileFROM jenkins/jenkins:2.121.2ENV JAVA_OPTS="${JAVA_OPTS} -Djava.util.logging.config.file=/usr/share/jenkins/jul.properties"COPY jul.properties /usr/share/jenkins/ENTRYPOINT ["/sbin/tini", "--", "/usr/local/bin/jenkins.sh"]{code} * Logfile: [^jenkins_001_mikescholze_2.121.2.log]
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title
Mike Scholze commented on JENKINS-33412
Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors
Olivier Lamy these are not my log files. But now my test scenario:
Ubuntu 16.04.4 LTS
Docker 17.09.0-ce
Test-Docker-Image based on official docker jenkins image + jul.properties file:
// jul.properties
handlers=java.util.logging.ConsoleHandler
.level=INFO
org.eclipse.jetty.level=ALL
java.util.logging.ConsoleHandler.level=FINEST
// Dockerfile
FROM jenkins/jenkins:2.121.2
ENV JAVA_OPTS="${JAVA_OPTS} -Djava.util.logging.config.file=/usr/share/jenkins/jul.properties"
COPY jul.properties /usr/share/jenkins/
ENTRYPOINT ["/sbin/tini", "--", "/usr/local/bin/jenkins.sh"]
Logfile: jenkins_001_mikescholze_2.121.2.log
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Mike Scholze updated an issue Jenkins / JENKINS-33412 Jenkins locks when started in HTTPS mode on a host with 37+ processors Change By: Mike Scholze Attachment: jenkins_001_mikescholze_2.121.2.log Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Mike Scholze commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors same issue with 2.128 and 2.138 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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] (JENKINS-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Mike Scholze edited a comment on JENKINS-51136 Re: Jenkins UI hangs 2.117 - 2.119 @ comment removed, sorry [~ oleg_nenashev olamy ] : Do you know if someone is working on the topic? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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] (JENKINS-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Mike Scholze commented on JENKINS-51136 Re: Jenkins UI hangs 2.117 - 2.119 @Oleg Nenashev: Do you know if someone is working on the topic? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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] (JENKINS-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Mike Scholze updated an issue Jenkins / JENKINS-51136 Jenkins UI hangs 2.117 - 2.119 Change By: Mike Scholze Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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.
