[JIRA] (JENKINS-6673) Should be able to filter out disabled builds
Title: Message Title Hari Dara commented on JENKINS-6673 Re: Should be able to filter out disabled builds Scratch what I said above. I actually found a way to make use of this feature to get Jenkins to show only the enabled jobs by default. Create a new List View, say "All Enabled" Configure the view with the following options Under Status Filter drop down, select Enabled Jobs Only Check Use a regular _expression_ to include jobs into the view Enter .* for Regular _expression_ field. Under Manage Jenkins -> Configure System change the Default View to the above view. 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.136768.1275370083000.18686.1559544900421%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-6673) Should be able to filter out disabled builds
Title: Message Title Hari Dara commented on JENKINS-6673 Re: Should be able to filter out disabled builds There is no way to edit the default "All" view, so unless there is a way to create another view that automatically shows all the enabled jobs, there is no practical use of this feature. 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.136768.1275370083000.18678.1559544420243%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56865) Password to access InfluxDB is stored unencrypted on disk
Title: Message Title Aleksi Simell closed an issue as Fixed Fix was done and released in version 1.22. In the future, please submit security related issues to SECURITY project as informed in https://jenkins.io/security/. Jenkins / JENKINS-56865 Password to access InfluxDB is stored unencrypted on disk Change By: Aleksi Simell Status: Open Closed Resolution: Fixed Released As: 1.22 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/
[JIRA] (JENKINS-57774) JenkinsRule: Jetty leaves stray threads running after server.stop()
Title: Message Title
Abhyudaya Sharma edited a comment on JENKINS-57774
Re: JenkinsRule: Jetty leaves stray threads running after server.stop()
Hi. I'm working creating a framework to benchmark Jenkins using Java Microbenchmark Harness. To do that, I'm starting a Jenkins instance similar to how it is done by JenkinsRule. When the instance is terminated (after the benchmark has completed) using server.stop() and Jenkins.cleanup(), these threads keep running and cause JMH to wait and later forcefully kill the JVM.This has been implemented in Role Strategy Plugin so the pom is: [https://github.com/jenkinsci/role-strategy-plugin/blob/master/pom.xml]However, I did manually update all of the Jetty dependencies to the latest version and I was able to observe it again : # {code:java}. apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> 4.0.0 org.jenkins-ci.pluginsplugin3.43role-strategyhpi${revision}${changelist}Role-based Authorization Strategyhttps://wiki.jenkins.io/display/JENKINS/Role+Strategy+Pluginscm:git:ssh://github.com/jenkinsci/${project.artifactId}-plugin.gitscm:git:ssh://g...@github.com/jenkinsci/${project.artifactId}-plugin.githttps://github.com/jenkinsci/${project.artifactId}-plugin ${scmTag} tmaurelThomas Maurel+1rseguyRomain Seguy+1Oleg Nenashevoleg_nenashevo.v.nenas...@gmail.com2.12-SNAPSHOT2.60.381.17repo.jenkins-ci.orghttps://repo.jenkins-ci.org/public/repo.jenkins-ci.orghttps://repo.jenkins-ci.org/public/MIT Licensehttps://www.opensource.org/licenses/mit-license.phprepoorg.jenkins-ci.pluginsmatrix-auth2.2org.hamcresthamcrest-junit2.0.0.0testorg.jenkins-ci.pluginscloudbees-folder6.1.0testorg.jenkins-ci.pluginsjquery1.11.2-0org.jenkins-ci.pluginsjquery-ui1.0.1org.openjdk.jmhjmh-core1.21testorg.openjdk.jmhjmh-generator-annprocess1.21testio.jenkinsconfiguration-as-code${configuration-as-code.version}trueio.jenkinsconfiguration-as-code${configuration-as-code.version}teststestorg.reflectionsreflections0.9.11testorg.eclipse.jetty.websocketwebsocket-api9.4.18.v20190429org.eclipse.jetty.websocketwebsocket-client9.4.18.v20190429org.eclipse.jettyjetty-server9.4.18.v20190429org.eclipse.jettyjetty-servlet9.4.18.v20190429org.eclipse.jettyjetty-security9.4.18.v20190429org.
[JIRA] (JENKINS-57774) JenkinsRule: Jetty leaves stray threads running after server.stop()
Title: Message Title Abhyudaya Sharma commented on JENKINS-57774 Re: JenkinsRule: Jetty leaves stray threads running after server.stop() Hi. I'm working creating a framework to benchmark Jenkins using Java Microbenchmark Harness. To do that, I'm starting a Jenkins instance similar to how it is done by JenkinsRule. When the instance is terminated (after the benchmark has completed) using server.stop() and Jenkins.cleanup(), these threads keep running and cause JMH to wait and later forcefully kill the JVM. This has been implemented in Role Strategy Plugin so the pom is: https://github.com/jenkinsci/role-strategy-plugin/blob/master/pom.xml However, I did manually update all of the Jetty dependencies to the latest version and I was able to observe it again. 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.199721.1559274543000.18664.1559537820913%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title vinoth SS commented on JENKINS-57772 Re: Build strategy for tags is not working, if you specify ignore tags lesser than 7days Steps i tried : Add the "Discover tags" behavior in multibranch pipeline Add the build strategy "Tags" with an empty value for Ignore tags newer than Change the "Tags" build strategy Ignore tags older than from its default 7 to 1 i have created tags, when you manually scan the organization folder again it is working, but not automatically scanning the events and running the tag job is not happening. Automated tag job and build ran successfully if you have Ignore tags older than as its default 7. Then whenever you create tags in Bitbucket , Jenkins events scans automatically and trigger the build as well. hope this is clear...Let me know if im doing anything wrong. Thanks in advance. 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.199719.1559261241000.18661.1559537400115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57774) JenkinsRule: Jetty leaves stray threads running after server.stop()
Title: Message Title Olivier Lamy commented on JENKINS-57774 Re: JenkinsRule: Jetty leaves stray threads running after server.stop() can you please provide a project with a pom. To know which version you are using. And yes last but not least what is the real problem? 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.199721.1559274543000.18657.1559536620330%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48248) pidFile switch should prevent launching of multiple copies
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-48248 pidFile switch should prevent launching of multiple copies Change By: Basil Crow Priority: Minor Major 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.186829.1511808585000.18653.1559514720235%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42930) Use System proxy when available
Title: Message Title Basil Crow updated JENKINS-42930 Released in 3.17. Jenkins / JENKINS-42930 Use System proxy when available Change By: Basil Crow Status: Fixed but Unreleased Resolved 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.179940.1490008795000.18648.1559514120561%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48247) Swarm Client should not restart when labelsFile changes
Title: Message Title Basil Crow commented on JENKINS-48247 Re: Swarm Client should not restart when labelsFile changes Released in 3.17. 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.186828.151180704.18650.1559514120612%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45295) Swarm Client should update labels on the fly when labelsFile changes
Title: Message Title Basil Crow updated JENKINS-45295 Released in 3.17. Jenkins / JENKINS-45295 Swarm Client should update labels on the fly when labelsFile changes Change By: Basil Crow Status: Fixed but Unreleased Resolved 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.183432.149918364.18638.1559513520501%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50970) SLF4J logging not working in Swarm client
Title: Message Title Basil Crow updated JENKINS-50970 Released in 3.17. Jenkins / JENKINS-50970 SLF4J logging not working in Swarm client Change By: Basil Crow Status: Fixed but Unreleased Resolved 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.190118.1524590516000.18640.1559513520533%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34337) Job Naming Strategy doesn't enforce restriction on rename
Title: Message Title James Milligan updated an issue Jenkins / JENKINS-34337 Job Naming Strategy doesn't enforce restriction on rename Change By: James Milligan Component/s: role-strategy-plugin Component/s: core 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.169895.1461076986000.18634.1559511780213%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34337) Job Naming Strategy doesn't enforce restriction on rename
Title: Message Title James Milligan commented on JENKINS-34337 Re: Job Naming Strategy doesn't enforce restriction on rename https://github.com/jenkinsci/role-strategy-plugin/pull/74 opened pending review. 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.169895.1461076986000.18628.1559510400140%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34337) Job Naming Strategy doesn't enforce restriction on rename
Title: Message Title James Milligan updated JENKINS-34337 Jenkins / JENKINS-34337 Job Naming Strategy doesn't enforce restriction on rename Change By: James Milligan Status: In Progress Review 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.169895.1461076986000.18624.1559510340297%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57813) Bump jenkins-core requirement to 2.138
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-57813 Bump jenkins-core requirement to 2.138 Issue Type: Improvement Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2019-06-02 20:35 Priority: Major Reporter: Cyrille Le Clerc Bump jenkins-core requirement to 2.138. Current requirement is 2.89. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title Steven Clark commented on JENKINS-54929 Re: Some final output is missing in Jenkins Pipeline when using the Ansible Plugin So we've been running with the latest PR (https://github.com/jenkinsci/ansible-plugin/pull/30) I created for the past two weeks and this new version of the PR seems to solve the issue. Is it possible to get the maintainer to look through the PR to get a new release of the 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.195937.1543444084000.18605.1559502600405%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55903) High latency networks add extra time to a job completion
Title: Message Title Carlos Sanchez updated JENKINS-55903 This was fixed alreay increasing the exec buffer size Jenkins / JENKINS-55903 High latency networks add extra time to a job completion Change By: Carlos Sanchez Status: Open Fixed but Unreleased Resolution: Fixed 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.197303.1548978942000.18600.1559500200520%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55903) High latency networks add extra time to a job completion
Title: Message Title Carlos Sanchez updated JENKINS-55903 Jenkins / JENKINS-55903 High latency networks add extra time to a job completion Change By: Carlos Sanchez Status: Fixed but Unreleased Resolved 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.197303.1548978942000.18602.1559500200548%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42930) Use System proxy when available
Title: Message Title Basil Crow updated JENKINS-42930 Fixed in #105 and will be released in 3.17. Jenkins / JENKINS-42930 Use System proxy when available Change By: Basil Crow Status: Open Fixed but Unreleased Assignee: Basil Crow Resolution: Fixed Released As: 3.17 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...@g
[JIRA] (JENKINS-48247) Swarm Client should not restart when labelsFile changes
Title: Message Title Basil Crow commented on JENKINS-48247 Re: Swarm Client should not restart when labelsFile changes Fixed in #110 and will be released in 3.17. 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.186828.151180704.18591.1559498760130%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45295) Swarm Client should update labels on the fly when labelsFile changes
Title: Message Title Basil Crow updated JENKINS-45295 Fixed in #110 and will be released in 3.17. Jenkins / JENKINS-45295 Swarm Client should update labels on the fly when labelsFile changes Change By: Basil Crow Status: Open Fixed but Unreleased Assignee: Basil Crow Resolution: Fixed Released As: 3.17 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 em
[JIRA] (JENKINS-57794) Use MySQL API Plugin to load MySQL Connector
Title: Message Title Cyrille Le Clerc started work on JENKINS-57794 Change By: Cyrille Le Clerc Status: Open In Progress 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.199744.1559314246000.18584.1559493120168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57794) Use MySQL API Plugin to load MySQL Connector
Title: Message Title Cyrille Le Clerc updated JENKINS-57794 Jenkins / JENKINS-57794 Use MySQL API Plugin to load MySQL Connector Change By: Cyrille Le Clerc Status: In Progress Review 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.199744.1559314246000.18585.1559493120219%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25421) Allow Swarm client to be used when CSRF is disabled
Title: Message Title Basil Crow commented on JENKINS-25421 Re: Allow Swarm client to be used when CSRF is disabled Is this still a bug on recent versions of Jenkins core and Swarm client? I just tried connecting to a Jenkins master (2.150.1) with Swarm client 3.16 both with and without CSRF enabled on the Jenkins master, and things worked just fine. 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.158985.1415054026000.18576.1559484240827%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36667) swarm client 2.1 unable to connect to jenkins instance
Title: Message Title Basil Crow edited a comment on JENKINS-36667 Re: swarm client 2.1 unable to connect to jenkins instance Is this still a bug on recent versions of Jenkins core and Swarm client? I just tried connecting to a Jenkins master (2.150.1) with Swarm client 3.16 both with and without CSRF enabled on the Jenkins master, and things worked just fine. 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.172699.1468434521000.18580.1559484240902%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47281) swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects
Title: Message Title Basil Crow commented on JENKINS-47281 Re: swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects Is this still a bug on recent versions of Jenkins core and Swarm client? I just tried connecting to a Jenkins master (2.150.1) with Swarm client both with and without CSRF enabled on the Jenkins master, and things worked just fine. 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.185701.1507154346000.18565.1559484240645%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47281) swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects
Title: Message Title Basil Crow edited a comment on JENKINS-47281 Re: swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects Is this still a bug on recent versions of Jenkins core and Swarm client? I just tried connecting to a Jenkins master (2.150.1) with Swarm client 3.16 both with and without CSRF enabled on the Jenkins master, and things worked just fine. 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.185701.1507154346000.18582.1559484240921%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36667) swarm client 2.1 unable to connect to jenkins instance
Title: Message Title Basil Crow commented on JENKINS-36667 Re: swarm client 2.1 unable to connect to jenkins instance Is this still a bug on recent versions of Jenkins core and Swarm client? I just tried connecting to a Jenkins master (2.150.1) with Swarm client both with and without CSRF enabled on the Jenkins master, and things worked just fine. 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.172699.1468434521000.18562.1559484240605%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56874) Log4j2.xml file in the plugin causes unexpected errors
Title: Message Title Yuri Guller commented on JENKINS-56874 Re: Log4j2.xml file in the plugin causes unexpected errors I've identified some of the cases when plugin may attempt to write (or at least initially create the folder structure) logs before the logger is customized with the target folder and actually already pushed a fix for that issue, see PR below: https://github.com/MicroFocus/hpaa-octane-dev/pull/211 I"m pretty sure that this will be a part of the next beta and release, not sure though about the exact timings. Let's see if the issue will reproduce with this fix in. 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.198543.1554368545000.18555.1559483700357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55110) BFA 1.21.0 fails to create a failure cause / scan jobs
Title: Message Title Tim Jacomb commented on JENKINS-55110 Re: BFA 1.21.0 fails to create a failure cause / scan jobs PR: https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/105 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.196171.1544462893000.18552.1559480760762%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55110) BFA 1.21.0 fails to create a failure cause / scan jobs
Title: Message Title Tim Jacomb updated JENKINS-55110 Jenkins / JENKINS-55110 BFA 1.21.0 fails to create a failure cause / scan jobs Change By: Tim Jacomb Status: In Progress Review 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.196171.1544462893000.18541.1559480760565%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55110) BFA 1.21.0 fails to create a failure cause / scan jobs
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-55110 BFA 1.21.0 fails to create a failure cause / scan jobs Change By: Tim Jacomb Priority: Critical Blocker 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.196171.1544462893000.18527.1559480700777%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55110) BFA 1.21.0 fails to create a failure cause / scan jobs
Title: Message Title Tim Jacomb started work on JENKINS-55110 Change By: Tim Jacomb Status: Open In Progress 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.196171.1544462893000.18534.1559480700906%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42755) BFA fails to catch pipeline related exceptions
Title: Message Title Tim Jacomb commented on JENKINS-42755 Re: BFA fails to catch pipeline related exceptions https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/103 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.179744.148950090.18514.1559473561863%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42755) BFA fails to catch pipeline related exceptions
Title: Message Title Tim Jacomb started work on JENKINS-42755 Change By: Tim Jacomb Status: Open In Progress 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.179744.148950090.18488.1559473561545%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42755) BFA fails to catch pipeline related exceptions
Title: Message Title Tim Jacomb updated JENKINS-42755 Jenkins / JENKINS-42755 BFA fails to catch pipeline related exceptions Change By: Tim Jacomb Status: In Progress Review 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.179744.148950090.18501.1559473561694%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57811) Jenkins trying to create duplicate instance of Tomcat
Title: Message Title Philip Rego commented on JENKINS-57811 Re: Jenkins trying to create duplicate instance of Tomcat pom.xml 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.199762.155946189.18484.1559466600076%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57811) Jenkins trying to create duplicate instance of Tomcat
Title: Message Title Philip Rego updated an issue Jenkins / JENKINS-57811 Jenkins trying to create duplicate instance of Tomcat Change By: Philip Rego Comment: [^pom.xml] 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.199762.155946189.18485.1559466600106%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57811) Jenkins trying to create duplicate instance of Tomcat
Title: Message Title Philip Rego updated an issue Jenkins / JENKINS-57811 Jenkins trying to create duplicate instance of Tomcat Change By: Philip Rego Attachment: pom.xml 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.199762.155946189.18483.1559466540056%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57811) Jenkins trying to create duplicate instance of Tomcat
Title: Message Title Philip Rego commented on JENKINS-57811 Re: Jenkins trying to create duplicate instance of Tomcat Fails without any goals or options also Deploying /var/lib/jenkins/workspace/WhatThePhil/target/ROOT.war to container Tomcat 8.x Remote with context [/var/lib/jenkins/workspace/WhatThePhil/target/ROOT.war] is not deployed. Doing a fresh deployment. Deploying [/var/lib/jenkins/workspace/WhatThePhil/target/ROOT.war] ERROR: Build step failed with exception org.codehaus.cargo.container.ContainerException: Failed to deploy [/var/lib/jenkins/workspace/WhatThePhil/target/ROOT.war] at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.deploy(AbstractTomcatManagerDeployer.java:110) at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:184) 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.199762.155946189.18482.1559466360043%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57812) Test connection doesn't work for mongo DB
Title: Message Title Tim Jacomb updated JENKINS-57812 Jenkins / JENKINS-57812 Test connection doesn't work for mongo DB Change By: Tim Jacomb Status: In Progress Review 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.199764.1559464618000.18479.1559465460138%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57812) Test connection doesn't work for mongo DB
Title: Message Title Tim Jacomb assigned an issue to Tomas Westling Jenkins / JENKINS-57812 Test connection doesn't work for mongo DB Change By: Tim Jacomb Assignee: Tim Jacomb Tomas Westling 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.199764.1559464618000.18481.1559465460189%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57812) Test connection doesn't work for mongo DB
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-57812 Test connection doesn't work for mongo DB Change By: Tim Jacomb Issue Type: Improvement Bug 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.199764.1559464618000.18477.1559464680129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57812) Test connection doesn't work for mongo DB
Title: Message Title Tim Jacomb started work on JENKINS-57812 Change By: Tim Jacomb Status: Open In Progress 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.199764.1559464618000.18478.1559464680156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57812) Test connection doesn't work for mongo DB
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-57812 Test connection doesn't work for mongo DB Issue Type: Improvement Assignee: Tim Jacomb Components: build-failure-analyzer-plugin Created: 2019-06-02 08:36 Environment: 1.22.0 Priority: Minor Reporter: Tim Jacomb Test connection always say ok, only way I could make it fail was to not provide a database name Add Comment
[JIRA] (JENKINS-57811) Jenkins trying to create duplicate instance of Tomcat
Title: Message Title Philip Rego created an issue Jenkins / JENKINS-57811 Jenkins trying to create duplicate instance of Tomcat Issue Type: Bug Assignee: Unassigned Attachments: Screenshot from 2019-06-02 03-50-14.png, Screenshot from 2019-06-02 03-51-02.png, Screenshot from 2019-06-02 03-51-09.png Components: deploy-plugin Created: 2019-06-02 07:51 Priority: Blocker Reporter: Philip Rego When you set "clean install" on your root pom. Then Jenkins will try to start a seperate instance of tomcat on your server on the same port. The Jenkins error doesn' t give the right info: Caused by: java.net.SocketException: Connection reset That's not the real issue. On the server it gives: java.net.BindException: Address already in use (Bind failed) Jenkins shouldnt be trying to start another instance. Nowhere did I tell Jenkins to be creating other instances. I'm only deploying to 1 tomcat server. This is a blocking defect. Can't use Jenkins with Tomcat anymore. Add Comment
[JIRA] (JENKINS-56874) Log4j2.xml file in the plugin causes unexpected errors
Title: Message Title Amit Dar updated an issue Jenkins / JENKINS-56874 Log4j2.xml file in the plugin causes unexpected errors Change By: Amit Dar Comment: I'm having the same issue, jenkins 2.164.3 with micro focus plugin 5.8. 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.198543.1554368545000.18464.1559461500242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56874) Log4j2.xml file in the plugin causes unexpected errors
Title: Message Title Amit Dar commented on JENKINS-56874 Re: Log4j2.xml file in the plugin causes unexpected errors I'm having the same issue, jenkins 2.164.3 with micro focus plugin 5.8. 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.198543.1554368545000.18458.1559461440212%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
