[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Naresh Rayapati commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data And also other test use case failing with similar errors. For some instances, we test Jenkins locally before we apply any changes to actual instance, part of that we have script which copies over all the hpi files to plugins directory before we start up the jenkins, this is to make sure these new plugins don't have any security issues and also the dependencies look good. 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.199434.155810265.8241.1558501320156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title
Naresh Rayapati edited a comment on JENKINS-57528
Re: Jenkins in Docker does not install detached plugins when there is no UC data
This change seems to be breaking our Jenkins when we upgrade it from 2.177 to 2.178.We tried both the ways:* Upgraded all plugins to latest before upgrading the Jenkins version from 2.177 to 2.178* Upgraded Jenkins to 2.178 and we see these dependency errors before we upgrade all the plugins manually with some errors. I think both the times 2.178 is trying to load lower versions of these implied plugins during the startup and when later actual plugins are being installed and if they require greater version of these base dependencies the installation of that plugin is failing and the chain continues. Not very sure though, can we have more documentation on this implied vs detached plugins and also required plugins and so on. Thank you. Is there anyway to disable this functionality of installing these plugins by default and have users an option to explicitly define all these plugins (like what we do today)?Here with few lines of exception:{code :java }2019-05-22 04:45:51.819+ [id=33] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline SCM API for Blue Ocean v1.16.0 (blueocean-pipeline-scm-api)java.io.IOException: Pipeline SCM API for Blue Ocean version 1.16.0 failed to load. - Pipeline: Multibranch version 2.21 failed to load. Fix this plugin first.at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:868)at hudson.PluginManager$2$1$1.run(PluginManager.java:544)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)at jenkins.model.Jenkins$5.runTask(Jenkins.java:1091)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748)2019-05-22 04:45:51.820+ [id=32] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Favorite v2.3.2 (favorite)java.io.IOException: Favorite version 2.3.2 failed to load. - Matrix Project Plugin version 1.4.1 is older than required. To fix, install version 1.7.1 or later.at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:868)at hudson.PluginManager$2$1$1.run(PluginManager.java:544)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)at jenkins.model.Jenkins$5.runTask(Jenkins.java:1091)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748)2019-05-22 04:45:51.821+ [id=27] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin REST Implementation for Blue Ocean v1.16.0 (blueocean-rest-impl)java.io.IOException: REST Implementation for Blue Ocean version 1.16.0 failed to load. - Pipeline: Groovy version 2.68 failed to load. Fix this plugin first.at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:868)at hudson.PluginManager$2$1$1.run(PluginManager.java:544)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)at
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Naresh Rayapati commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data This change seems to be breaking our Jenkins when we upgrade it from 2.177 to 2.178. We tried both the ways: Upgraded all plugins to latest before upgrading the Jenkins version from 2.177 to 2.178 Upgraded Jenkins to 2.178 and we see these dependency errors before we upgrade all the plugins manually with some errors. I think both the times 2.178 is trying to load lower versions of these implied plugins during the startup and when later actual plugins are being installed and if they require greater version of these base dependencies the installation of that plugin is failing and the chain continues. Is there anyway to disable this functionality of installing these plugins by default and have users an option to explicitly define all these plugins (like what we do today)? Here with few lines of exception: 2019-05-22 04:45:51.819+ [id=33] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline SCM API for Blue Ocean v1.16.0 (blueocean-pipeline-scm-api) java.io.IOException: Pipeline SCM API for Blue Ocean version 1.16.0 failed to load. - Pipeline: Multibranch version 2.21 failed to load. Fix this plugin first. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:868) at hudson.PluginManager$2$1$1.run(PluginManager.java:544) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1091) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 2019-05-22 04:45:51.820+ [id=32] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Favorite v2.3.2 (favorite) java.io.IOException: Favorite version 2.3.2 failed to load. - Matrix Project Plugin version 1.4.1 is older than required. To fix, install version 1.7.1 or later. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:868) at hudson.PluginManager$2$1$1.run(PluginManager.java:544) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1091) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 2019-05-22 04:45:51.821+ [id=27] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin REST Implementation for Blue Ocean v1.16.0 (blueocean-rest-impl) java.io.IOException: REST Implementation for Blue Ocean version 1.16.0 failed to load. - Pipeline: Groovy version 2.68 failed to load. Fix this plugin first. at
[JIRA] (JENKINS-57591) Notifying users via Slack difficult due to no way to specify my Slack username
Title: Message Title trejkaz created an issue Jenkins / JENKINS-57591 Notifying users via Slack difficult due to no way to specify my Slack username Issue Type: Improvement Assignee: Kurt Madel Components: slack-plugin Created: 2019-05-22 03:02 Priority: Minor Reporter: trejkaz The Slack plugin can theoretically be used to directly notify a user about their build. However, in practice, we get errors when this happens, because Slack usernames don't match the usernames on either Jenkins or the Git server the code is coming from. If there were a way to specify our Slack usernames in our Jenkins profile, it would help. Add Comment
[JIRA] (JENKINS-57588) Branch API 2.5.0 rebuilds all jobs in multibranch folder on first scan after upgrade
Title: Message Title Mark Waite started work on JENKINS-57588 Change By: Mark Waite 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.199510.1558468849000.8226.1558491900132%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57588) Branch API 2.5.0 rebuilds all jobs in multibranch folder on first scan after upgrade
Title: Message Title Mark Waite commented on JENKINS-57588 Re: Branch API 2.5.0 rebuilds all jobs in multibranch folder on first scan after upgrade That incremental build resolved the issue. Thanks! 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.199510.1558468849000.8224.1558491480103%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk updated JENKINS-35435 Jenkins / JENKINS-35435 Test connection doesn't work Change By: Artem Stasiuk 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.171232.146532240.8217.1558491181214%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk updated JENKINS-35435 Fixed and released under ec2 fleet plugin version 1.2.1 Jenkins / JENKINS-35435 Test connection doesn't work Change By: Artem Stasiuk 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.171232.146532240.8215.1558491181157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54363) ERROR: Could not send email as a part of the post-build publishers.
Title: Message Title anand acharya commented on JENKINS-54363 Re: ERROR: Could not send email as a part of the post-build publishers. Alex Earl , issue is resolved. I added my email id in the Jenkins mail configuration and now the email extension plugin is triggering emails after build. It seems we need to configure at least one email account in the jenkins mail configuration. If email is not present then null pointer exception is thrown. 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.195113.1540977422000.8208.1558486560140%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57590) 'Exception in thread "main" java.net.SocketException: Permission denied: connect' Error while executing Maven Project
Title: Message Title Bhanu Vutukuri created an issue Jenkins / JENKINS-57590 'Exception in thread "main" java.net.SocketException: Permission denied: connect' Error while executing Maven Project Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2019-05-22 00:01 Environment: Windows 10, JDK 1.8_202, Maven 2.2, Maven Integration Plugin 3.2 Labels: plugin jekins maven maven-plugin Priority: Blocker Reporter: Bhanu Vutukuri An automated test execution is configured as a Jenkins Maven Project. The test job is failing with the following error stack trace below: Running as SYSTEM Building in workspace C:\Users\alt_bhanu.vutukuri\.jenkins\workspace\Dev_Deployment-Test Updating at revision '2019-05-21T12:03:48.767 -0700' --quiet Using sole credentials nareshr/** in realm '< > Authorization Realm' At revision 1534 No changes for since the previous build No emails were triggered. Parsing POMs Established TCP socket on 49867 [Dev_Deployment-Test] $ "C:\Program Files\Java\jdk1.8.0_212/bin/java" -cp C:\Users\alt_bhanu.vutukuri\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven35-agent-1.12.jar;C:\Prolifics\Maven\apache-maven-3.6.0\boot\plexus-classworlds-2.5.2.jar;C:\Prolifics\Maven\apache-maven-3.6.0/conf/logging jenkins.maven3.agent.Maven35Main C:\Prolifics\Maven\apache-maven-3.6.0 C:\Users\alt_bhanu.vutukuri\.jenkins\war\WEB-INF\lib\remoting-3.29.jar C:\Users\alt_bhanu.vutukuri\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven35-interceptor-1.12.jar
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Daniel Stratton updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Daniel Stratton Attachment: debugLog.20190522.0921.txt 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.199458.1558312268000.8204.1558481100160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57589) Fix parsing of container creation time
Title: Message Title rufo a created an issue Jenkins / JENKINS-57589 Fix parsing of container creation time Issue Type: Patch Assignee: Unassigned Components: docker-workflow-plugin Created: 2019-05-21 23:15 Priority: Minor Reporter: rufo a The code that parses the container creation date was a bit of a hack and didn't handle timezones properly. This patch improves it https://github.com/jenkinsci/docker-workflow-plugin/pull/175 Thanks Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-57588) Branch API 2.5.0 rebuilds all jobs in multibranch folder on first scan after upgrade
Title: Message Title Liam Newman commented on JENKINS-57588 Re: Branch API 2.5.0 rebuilds all jobs in multibranch folder on first scan after upgrade Mark Waite Since you were able to repro this do you have an instance where you can try this incremental? https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/branch-api/2.5.1-rc752.20712eff7952/ If trying to repro this on an existing instance that was upgraded, you will of course need to downgrade and then delete the lastSeen files first. 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.199510.1558468849000.8201.1558480200155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57588) Branch API 2.5.0 rebuilds all jobs in multibranch folder on first scan after upgrade
Title: Message Title Mark Waite commented on JENKINS-57588 Re: Branch API 2.5.0 rebuilds all jobs in multibranch folder on first scan after upgrade Refer to pull request 152 for an initial idea that might prevent the build storm. It seems that line 2082 in the diff might not be handling the initial startup case where a job already exists but the lastSeenRevision file has not been written. 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.199510.1558468849000.8181.1558475640053%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57585) Jenkins restart wipes out artifacts on restart - Cucumber Report is an example
Title: Message Title Damian Szczepanik closed an issue as Fixed Jenkins / JENKINS-57585 Jenkins restart wipes out artifacts on restart - Cucumber Report is an example Change By: Damian Szczepanik Status: Resolved Closed 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.199503.1558455683000.8180.1558475520327%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57585) Jenkins restart wipes out artifacts on restart - Cucumber Report is an example
Title: Message Title Damian Szczepanik resolved as Fixed Jenkins / JENKINS-57585 Jenkins restart wipes out artifacts on restart - Cucumber Report is an example Change By: Damian Szczepanik Status: Open Resolved 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.199503.1558455683000.8178.1558475520293%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57585) Jenkins restart wipes out artifacts on restart - Cucumber Report is an example
Title: Message Title Damian Szczepanik commented on JENKINS-57585 Re: Jenkins restart wipes out artifacts on restart - Cucumber Report is an example Similar issue has been reported already https://github.com/damianszczepanik/cucumber-reporting/issues or https://github.com/jenkinsci/cucumber-reports-plugin/issues and it was closed AFAIR due the problem with lack of storage. You can check the history 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.199503.1558455683000.8176.1558475460095%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title
Mark Waite edited a comment on JENKINS-57587
Re: Lightweight checkout gives NPE
I am unable to duplicate the problem you're describing.My attempt to duplicate the problem on Jenkins 2.164.3 with git plugin 3.10.0 on Debian 9 with JDK 8 :# Create [JENKINS-57587 branch|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-57587/README.md] in my jenkins-bugs repository# Create a [pipeline job|https://github.com/MarkEWaite/docker-lfs/blob/940d3bd3a4c27aa56d4d1a9f1efd841927ba095b/ref/jobs/Bugs-Individual/jobs/JENKINS-57587-NPE-on-lightweight-checkout/config.xml#L1]# Configure job to get Pipeline script from SCM using Git# Configure git repository https://github.com/MarkEWaite/jenkins-bugs to checkout branch JENKINS-57587# Leave {{Lightweight checkout}} enabled in the job definition# Save the job definition# Build nowCan you provide more details on your configuration and how it is different from the configuration I tried?My [test job|https://github.com/MarkEWaite/docker-lfs/blob/940d3bd3a4c27aa56d4d1a9f1efd841927ba095b/ref/jobs/Bugs-Individual/jobs/JENKINS-57587-NPE-on-lightweight-checkout/config.xml#L1] uses a [pipeline shared library|https://github.com/MarkEWaite/jenkins-pipeline-utils].
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.199505.1558465141000.8155.1558472880271%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title
Mark Waite edited a comment on JENKINS-57587
Re: Lightweight checkout gives NPE
I am unable to duplicate the problem you're describing.My attempt to duplicate the problem on Jenkins 2.164.3 with git plugin 3.10.0:# Create [JENKINS-57587 branch|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-57587/README.md] in my jenkins-bugs repository# Create a [pipeline job|https://github.com/MarkEWaite/docker-lfs/blob/940d3bd3a4c27aa56d4d1a9f1efd841927ba095b/ref/jobs/Bugs-Individual/jobs/JENKINS-57587-NPE-on-lightweight-checkout/config.xml#L1]# Configure job to get Pipeline script from SCM using Git# Configure git repository https://github.com/MarkEWaite/jenkins-bugs to checkout branch JENKINS-57587# Leave {{Lightweight checkout}} enabled in the job definition# Save the job definition# Build nowCan you provide more details on your configuration and how it is different from the configuration I tried?My [test job|https://github.com/MarkEWaite/docker-lfs/blob/940d3bd3a4c27aa56d4d1a9f1efd841927ba095b/ref/jobs/Bugs-Individual/jobs/JENKINS-57587-NPE-on-lightweight-checkout/config.xml#L1] uses a [pipeline shared library|https://github.com/MarkEWaite/jenkins-pipeline-utils].
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.199505.1558465141000.8153.1558472820255%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title
Mark Waite edited a comment on JENKINS-57587
Re: Lightweight checkout gives NPE
I am unable to duplicate the problem you're describing.My attempt to duplicate the problem on Jenkins 2.164.3 with git plugin 3.10.0:# Create [JENKINS-57587 branch|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-57587/README.md] in my jenkins-bugs repository# Create a [pipeline job|https://github.com/MarkEWaite/docker-lfs/blob/940d3bd3a4c27aa56d4d1a9f1efd841927ba095b/ref/jobs/Bugs-Individual/jobs/ JENKINS-57587 pipeline job -NPE-on-lightweight-checkout/config.xml#L1] # Configure job to get Pipeline script from SCM using Git# Configure git repository https://github.com/MarkEWaite/jenkins-bugs to checkout branch JENKINS-57587# Leave {{Lightweight checkout}} enabled in the job definition# Save the job definition# Build nowCan you provide more details on your configuration and how it is different from the configuration I tried?My [test job|https://github.com/MarkEWaite/docker-lfs/blob/940d3bd3a4c27aa56d4d1a9f1efd841927ba095b/ref/jobs/Bugs-Individual/jobs/JENKINS-57587-NPE-on-lightweight-checkout/config.xml#L1] uses a [pipeline shared library|https://github.com/MarkEWaite/jenkins-pipeline-utils].
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.199505.1558465141000.8151.1558472820232%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57587
Lightweight checkout gives NPE
Change By:
Mark Waite
Jenkins 2.164.3 with Git Plugin 3.9.3With the most basic Pipeline job from SCM with "Lightweight checkout" checked, the following NPE trace is the total job output._Unchecking_ "Lightweight checkout" solves the immediate NPE issue and the job completes.{ noformat { Started by user }}{{java.lang.NullPointerException }} {{ at jenkins.plugins.git.GitSCMFileSystem$1.invoke(GitSCMFileSystem.java:117) }} {{ at jenkins.plugins.git.GitSCMFileSystem$1.invoke(GitSCMFileSystem.java:114) }} {{ at jenkins.plugins.git.GitSCMFileSystem$3.invoke(GitSCMFileSystem.java:193) }} {{ at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.withRepository(AbstractGitAPIImpl.java:29) }} {{ at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.withRepository(CliGitAPIImpl.java:72) }} {{ at jenkins.plugins.git.GitSCMFileSystem.invoke(GitSCMFileSystem.java:189) }} {{ at jenkins.plugins.git.GitSCMFileSystem.(GitSCMFileSystem.java:114) }} {{ at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:353) }} {{ at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:198) }} {{ at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:174) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67) }} {{ at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) }} {{ at hudson.model.ResourceController.execute(ResourceController.java:97) }} {{ at hudson.model.Executor.run(Executor.java:429) }} {{ Finished: FAILURE {noformat } }
Add Comment
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57587
Lightweight checkout gives NPE
Change By:
Mark Waite
Jenkins 2.164.3 with Git Plugin 3.9.3With the most basic Pipeline job from SCM with "Lightweight checkout" checked, the following NPE trace is the total job output._Unchecking_ "Lightweight checkout" solves the immediate NPE issue and the job completes.{noformat { } Started by user }}{{java.lang.NullPointerException at jenkins.plugins.git.GitSCMFileSystem$1.invoke(GitSCMFileSystem.java:117) at jenkins.plugins.git.GitSCMFileSystem$1.invoke(GitSCMFileSystem.java:114) at jenkins.plugins.git.GitSCMFileSystem$3.invoke(GitSCMFileSystem.java:193) at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.withRepository(AbstractGitAPIImpl.java:29) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.withRepository(CliGitAPIImpl.java:72) at jenkins.plugins.git.GitSCMFileSystem.invoke(GitSCMFileSystem.java:189) at jenkins.plugins.git.GitSCMFileSystem.(GitSCMFileSystem.java:114) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:353) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:198) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:174) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{noformat}
Add Comment
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title Mark Waite commented on JENKINS-57587 Re: Lightweight checkout gives NPE I am unable to duplicate the problem you're describing. My attempt to duplicate the problem on Jenkins 2.164.3 with git plugin 3.10.0: Create JENKINS-57587 branch in my jenkins-bugs repository Create a JENKINS-57587 pipeline job Configure job to get Pipeline script from SCM using Git Configure git repository https://github.com/MarkEWaite/jenkins-bugs to checkout branch JENKINS-57587 Leave Lightweight checkout enabled in the job definition Save the job definition Build now Can you provide more details on your configuration and how it is different from the configuration I tried? My test job uses a pipeline shared library. 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.199505.1558465141000.8144.1558471920018%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-57587 Lightweight checkout gives NPE Change By: Mark Waite Assignee: Mark Waite 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.199505.1558465141000.8142.1558471890296%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title Mark Waite commented on JENKINS-57587 Re: Lightweight checkout gives NPE I am unable to duplicate the problem you're describing. My attempt to duplicate the problem on Jenkins 2.164.3 with git plugin 3.10.0: Create JENKINS-57587 branch in my jenkins-bugs repository Create a JENKINS-57587 pipeline job Configure job to get Pipeline script from SCM using Git Configure git repository https://github.com/MarkEWaite/jenkins-bugs to checkout branch JENKINS-57587 Leave Lightweight checkout enabled in the job definition Save the job definition Build now Can you provide more details on your configuration and how it is different from the configuration I tried? My test job uses a pipeline shared library. 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.199505.1558465141000.8140.1558471870238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim commented on JENKINS-57583 Re: Ignore target branch no longer working I downgraded to 1.1.1 of this plugin and still see the same issue. Also, it appears that the merability message isn't always consistently displayed and may be a red herring. Checking pull request #149 ‘Jenkinsfile’ found Met criteria Changes detected: PR-149 (831936ab764be06ae376045e698f855f77e339da+3f65ffafeddbc4ce48a4abf27ec1dd3c0188ec60 (678431339386505e9e029c095b1d5e83c6cd) → 831936ab764be06ae376045e698f855f77e339da+326d0409c9ecc5675988c4c1d7cbf688d2cf2055 (8ab2d59a2fc7f6432b7863951976756ca6911781)) Scheduled build for branch: PR-149 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.199501.1558451822000.8138.1558471740159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57165) Jenkins job fails on Agent with error java.lang.OutOfMemoryError: Java heap space
Title: Message Title Joshua Alday commented on JENKINS-57165 Re: Jenkins job fails on Agent with error java.lang.OutOfMemoryError: Java heap space I get frequent OOM issues with Jenkins to kubernete pods. I use SSH connection, but of course it still starts a slave.jar. Despite having proper JVM properties set, I run into varying OOM issues, including the one mentioned above. 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.198915.1556084557000.8134.1558470660202%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57588) Branch API 2.5.0 rebuilds all jobs in multibranch folder on first scan after upgrade
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57588 Branch API 2.5.0 rebuilds all jobs in multibranch folder on first scan after upgrade Change By: Mark Waite Summary: Branch API 2.5.0 rebuilds all jobs in my multibranch folder on first scan after upgrade 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.199510.1558468849000.8131.1558469340051%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57588) Branch API 2.5.0 rebuilds all jobs in my multibranch folder
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57588
Branch API 2.5.0 rebuilds all jobs in my multibranch folder
Change By:
Mark Waite
I updated to branch API plugin 2.5.0 today. When I scan a multibranch Pipeline (Git branch source or GitHub branch source) the first time after the upgrade to branch API plugin 2.5.0, all jobs in that multibranch Pipeline are started. That means (in my case) that I now have more than 500 jobs in the queue waiting to run.The "Scan repository log" of the multibranch job shows:{noformat}Started by user Mark Waite[Tue May 21 13:37:54 MDT 2019] Starting branch indexing...13:37:55 Connecting to https://api.github.com using MarkEWaite/** (github personal access token for home.markwaite.net)Examining MarkEWaite/jenkins-bugs-private Checking branches... Getting remote branches...Checking branch master Getting remote pull requests... ‘Jenkinsfile’ foundMet criteriaChanges detected: master (null → 49101d07a954d083cae4bb0a06aaa081c6ae0fc8)Scheduled build for branch: masterChecking branch JENKINS-06203 ‘Jenkinsfile’ foundMet criteriaChanges detected: JENKINS-06203 (null → 6de0c64bb4cc6eb12964479bf37f5bb202f52aa4)Scheduled build for branch: JENKINS-06203{noformat}Each repository reports that changes are detected in the transition from {{null}} to a SHA-1. However, I know that almost every one of the branches in that repository have received no changes since before the update. Once the initial scan has completed and the resulting rebuild of all branches is complete, then the "Scan repository log" starts no job and the change detection message says:{noformat}No changes detected: master (still at 49101d07a954d083cae4bb0a06aaa081c6ae0fc8){noformat}
Add Comment
[JIRA] (JENKINS-57588) Branch API 2.5.0 rebuilds all jobs in my multibranch folder
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57588 Branch API 2.5.0 rebuilds all jobs in my multibranch folder Change By: Mark Waite Environment: Jenkins 2. 176 164.3 ( selected for next latest LTS baseline )Git plugin 3.10.0Git client plugin 2.7.7Branch API plugin 2.5.0 Jenkins 2.176 (selected for next LTS baseline)Git plugin 4.0.0-beta10 pre-releaseGit client plugin 3.0.0-beta10 pre-releaseBranch API plugin 2.5.0 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.199510.1558468849000.8126.1558468980053%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57588) Branch API 2.5.0 rebuilds all jobs in my multibranch folder
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57588 Branch API 2.5.0 rebuilds all jobs in my multibranch folder Change By: Mark Waite Issue Type: Task 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.199510.1558468849000.8124.1558468920149%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57588) Branch API 2.5.0 rebuilds all jobs in my multibranch folder
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57588 Branch API 2.5.0 rebuilds all jobs in my multibranch folder Change By: Mark Waite Environment: Jenkins 1 2 . 76 176 (selected for next LTS baseline)Git plugin 3.10.0Git client plugin 2.7.7Branch API plugin 2.5.0 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.199510.1558468849000.8125.1558468920177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57588) Branch API 2.5.0 rebuilds all jobs in my multibranch folder
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-57588 Branch API 2.5.0 rebuilds all jobs in my multibranch folder Issue Type: Task Assignee: Unassigned Components: branch-api-plugin Created: 2019-05-21 20:00 Environment: Jenkins 1.76 (selected for next LTS baseline) Git plugin 3.10.0 Git client plugin 2.7.7 Branch API plugin 2.5.0 Priority: Critical Reporter: Mark Waite I updated to branch API plugin 2.5.0 today. When I scan a multibranch Pipeline (Git branch source or GitHub branch source) the first time after the upgrade to branch API plugin 2.5.0, all jobs in that multibranch Pipeline are started. That means (in my case) that I now have more than 500 jobs in the queue waiting to run. The "Scan repository log" of the multibranch job shows: Started by user Mark Waite [Tue May 21 13:37:54 MDT 2019] Starting branch indexing... 13:37:55 Connecting to https://api.github.com using MarkEWaite/** (github personal access token for home.markwaite.net) Examining MarkEWaite/jenkins-bugs-private Checking branches... Getting remote branches... Checking branch master Getting remote pull requests... ‘Jenkinsfile’ found Met criteria Changes detected: master (null → 49101d07a954d083cae4bb0a06aaa081c6ae0fc8) Scheduled build for branch: master Checking branch JENKINS-06203 ‘Jenkinsfile’ found Met criteria Changes detected: JENKINS-06203 (null → 6de0c64bb4cc6eb12964479bf37f5bb202f52aa4) Scheduled build for branch: JENKINS-06203
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim commented on JENKINS-57583 Re: Ignore target branch no longer working I saw that as well though I'm not familiar with internals of how this all fits together. I have no doubt that this issue could be caused by some other plugin but at the end of the day it's this plugins job to prevent the build from happening which brought me here. Also, I'm not entirely able to play with downgrading packages on our production Jenkins currently. Are you able to replicate at all? 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.199501.1558451822000.8101.1558467900099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57585) Jenkins restart wipes out artifacts on restart - Cucumber Report is an example
Title: Message Title Tyler Wood assigned an issue to Unassigned Jenkins / JENKINS-57585 Jenkins restart wipes out artifacts on restart - Cucumber Report is an example Change By: Tyler Wood Assignee: Damian Szczepanik 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.199503.1558455683000.8099.1558467060506%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57585) Jenkins restart wipes out artifacts on restart - Cucumber Report is an example
Title: Message Title Tyler Wood updated an issue Jenkins / JENKINS-57585 Jenkins restart wipes out artifacts on restart - Cucumber Report is an example Change By: Tyler Wood Component/s: pipeline Component/s: cucumber-reports-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.199503.1558455683000.8097.1558467060443%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title Martin Weber commented on JENKINS-57501 Re: cmakeBuild does not set environment variables in Windows when run in Pipeline "java.lang.ClassCastException: class hudson.plugins.cmake.BuildToolStep.setEnvVars() expects class java.lang.String but received class java.util.ArrayList" You get this, because BuildToolStep.setEnvVars() takes a String, not an array. You may specify more than one envvar, if you separate them by newlines (as stated in the online help). This is the same behavior as in the freestyle project version of the plugin. Anyway, you do not need to pass envvars to BuildToolStep to configure cmake. These varaibles are passed to the build tool (make or nija). The main purpose is to run make install with the DESTDIR variable set to a directory below workspace root in order to ease archiving of artifacts. 4. Both documentation pieces, for withEnv and for envVars, miss examples on how to set multiple variables, they only show how to set a single variable, a very rare case, IMHO. The online help for Build tool | Env. Variables has an example that shows how to set multiple variables. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Félix Belzunce Arcos commented on JENKINS-57583 Re: Ignore target branch no longer working By doing a quick inspection, I would say this is not related. The stacktrace is coming from github_branch_source and without being an expert o the code, I don't see any relationship between this issue and the basic-branch-build-strategies-plugin. https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.5.2/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java#L1564 Have you tried to downgrade ONLY this particular plugin to ensure the issue is here? 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.199501.1558451822000.8085.1558465620159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title
Jeff Blaine created an issue
Jenkins / JENKINS-57587
Lightweight checkout gives NPE
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-05-21 18:59
Labels:
NPE
Priority:
Minor
Reporter:
Jeff Blaine
Jenkins 2.164.3 with Git Plugin 3.9.3 With the most basic Pipeline job from SCM with "Lightweight checkout" checked, the following NPE trace is the total job output. Unchecking "Lightweight checkout" solves the immediate NPE issue and the job completes. Started by user java.lang.NullPointerException {{ at jenkins.plugins.git.GitSCMFileSystem$1.invoke(GitSCMFileSystem.java:117)}} {{ at jenkins.plugins.git.GitSCMFileSystem$1.invoke(GitSCMFileSystem.java:114)}} {{ at jenkins.plugins.git.GitSCMFileSystem$3.invoke(GitSCMFileSystem.java:193)}} {{ at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.withRepository(AbstractGitAPIImpl.java:29)}} {{ at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.withRepository(CliGitAPIImpl.java:72)}} {{ at jenkins.plugins.git.GitSCMFileSystem.invoke(GitSCMFileSystem.java:189)}} {{ at jenkins.plugins.git.GitSCMFileSystem.(GitSCMFileSystem.java:114)}} {{ at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:353)}} {{ at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:198)}} {{ at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:174)}} {{ at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108)}} {{ at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67)}} {{ at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293)}} {{ at hudson.model.ResourceController.execute(ResourceController.java:97)}} {{ at hudson.model.Executor.run(Executor.java:429)}} Finished: FAILURE
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim commented on JENKINS-57583 Re: Ignore target branch no longer working I will also sometimes see PRs getting checked twice. Getting remote pull requests... Checking pull request #4597 Could not determine the mergability of pull request 4597. Retrying 4 more times... ‘Jenkinsfile’ found Met criteria Changes detected: PR-4597 (1d496879cc394a321a189f94d34c9bb8eb52166a+5cf22230284e0ddfffcf260c1bb53c04c4a2597a (f3ce4c9e279465bc0182f71ca3d85bf9e5f02f76) → 1d496879cc394a321a189f94d34c9bb8eb52166a+b177caaafd1be37b8f97fe5f2d557ec1a9a78478 (1d2d5ffb99d3496a07edb2714961af1b01581b36)) Scheduled build for branch: PR-4597 Checking pull request #4597 ‘Jenkinsfile’ found Met criteria No changes detected: PR-4597 (still at 1d496879cc394a321a189f94d34c9bb8eb52166a+b177caaafd1be37b8f97fe5f2d557ec1a9a78478 (1d2d5ffb99d3496a07edb2714961af1b01581b36)) 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.199501.1558451822000.8081.1558464720001%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim commented on JENKINS-57583 Re: Ignore target branch no longer working I will also sometimes see PRs getting checked twice. Getting remote pull requests... Checking pull request #4597 Could not determine the mergability of pull request 4597. Retrying 4 more times... ‘Jenkinsfile’ found Met criteria Changes detected: PR-4597 (1d496879cc394a321a189f94d34c9bb8eb52166a+5cf22230284e0ddfffcf260c1bb53c04c4a2597a (f3ce4c9e279465bc0182f71ca3d85bf9e5f02f76) → 1d496879cc394a321a189f94d34c9bb8eb52166a+b177caaafd1be37b8f97fe5f2d557ec1a9a78478 (1d2d5ffb99d3496a07edb2714961af1b01581b36)) Scheduled build for branch: PR-4597 Checking pull request #4597 ‘Jenkinsfile’ found Met criteria No changes detected: PR-4597 (still at 1d496879cc394a321a189f94d34c9bb8eb52166a+b177caaafd1be37b8f97fe5f2d557ec1a9a78478 (1d2d5ffb99d3496a07edb2714961af1b01581b36)) 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.199501.1558451822000.8080.1558464660043%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57534) P4_CHANGELIST entry in map returned by checkout step is sometimes wrong
Title: Message Title
Stuart Rowe commented on JENKINS-57534
Re: P4_CHANGELIST entry in map returned by checkout step is sometimes wrong
Hi Karl Wirth, I can repro the issue by triggering a job manually with a specific changelist number provided as a parameter. The workspace map is be being restricted through a virtual stream. The requested changelist contains only files excluded by the virtual stream. Looking through the code, I believe the issue is in CheckoutTask#getBuildChange(Workspace workspace) which is called by CheckoutTask#initialise(). In my case, the populate label is set to {'{${Changelist}}'} which references a String parameter to specify the changelist number to sync. The Expand replaces this token and parses an integer from the String parameter value. This integer is used to create a new P4ChangeRef which is then returned as the build change. I believe this function needs to run a second 'p4 changes -m1 //WORKSPACE/...@${build.getChange()}' to determine the correct build change value for the workspace's view. If I have time this week, I can put together a PR with a new test case and fix.
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.199441.1558118694000.8077.1558464000165%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57534) P4_CHANGELIST entry in map returned by checkout step is sometimes wrong
Title: Message Title
Stuart Rowe edited a comment on JENKINS-57534
Re: P4_CHANGELIST entry in map returned by checkout step is sometimes wrong
Hi [~p4karl],I can repro the issue by triggering a job manually with a specific changelist number provided as a parameter. The workspace map is be being restricted through a virtual stream. The requested changelist contains only files excluded by the virtual stream.Looking through the code, I believe the issue is in {{[CheckoutTask#getBuildChange(Workspace workspace)|https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/tasks/CheckoutTask.java#L198]}} which is called by {{[CheckoutTask#initialise()|https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/tasks/CheckoutTask.java#L58]}}. In my case, the populate label is set to \ { ' { ' $ \ {Changelist} } '} } which references a String parameter to specify the changelist number to sync. The {{Expand}} replaces this token and parses an integer from the String parameter value. This integer is used to create a new {{P4ChangeRef}} which is then returned as the build change. I believe this function needs to run a second {{'p4 changes -m1 //WORKSPACE/...@${build.getChange()}'}} to determine the correct build change value for the workspace's view.If I have time this week, I can put together a PR with a new test case and fix.
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.199441.1558118694000.8079.1558464000196%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Elliot Nelson commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) So far, the only thing that has worked for us on Jenkins 2.150+ is disabling the Remember Me option in Global Security. 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.197810.1550821517000.8051.1558460940650%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Chris Burroughs commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should The visualization provided by Pipeline: Stage View Plugin has not been integrated with the new API added in Pipeline: API 2.34, and so that visualization is not currently affected by these changes. I looked but could not find one; is the intention to have a separate ticket for the Stage View plugin integration? 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.175630.1477271041000.7819.1558458843759%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57586) TaskListenerDecorator's close method is not called
Title: Message Title Ted created an issue Jenkins / JENKINS-57586 TaskListenerDecorator's close method is not called Issue Type: Bug Assignee: Unassigned Attachments: update_test.patch Components: workflow-job-plugin Created: 2019-05-21 17:00 Priority: Minor Reporter: Ted master branch workflow-job-2.33 SNAPSHOT, test case attached (diff file) close method is not called in the pipeline lifecycle, I would like to leverage the close method to release resources used in TaskListenerDecorator, any suggestions ? Add Comment
[JIRA] (JENKINS-51919) jUnit output of PHPUnit test fail to parse
Title: Message Title Captain Hypertext commented on JENKINS-51919 Re: jUnit output of PHPUnit test fail to parse Yeah, this issue completely butchered my unit test parsing. I switched to the PHPUnit-X parser and it worked pretty well, still using JUnit output. 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.191405.1528896743000.7814.1558456560187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57585) Jenkins restart wipes out artifacts on restart - Cucumber Report is an example
Title: Message Title Tyler Wood created an issue Jenkins / JENKINS-57585 Jenkins restart wipes out artifacts on restart - Cucumber Report is an example Issue Type: Bug Assignee: Damian Szczepanik Attachments: image-2018-11-14-13-34-26-326.png, image-2018-11-14-13-36-26-480.png, image-2018-11-14-13-38-16-743.png, image-2018-11-16-09-24-36-857.png Components: cucumber-reports-plugin Created: 2019-05-21 16:21 Environment: Jenkins Ver 2.138.3 Priority: Major Reporter: Tyler Wood Our team is losing their Cucumber Reports as well after a Jenkins Restart. This happens every time we have a Windows Update or even a restart due to Jenkins Upgrade. Previous Build before Reboot: New Build after Reboot: It looks like the files are there, but just no link present in Jenkins: Add Comment
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title
Vincent Massol commented on JENKINS-54128
Re: Deprecated calls to Run.getLogFile
ok works with:
new BufferedReader(currentBuild.rawBuild.getLogReader()).with { br ->
def line = null
line = br.readLine()
while (line != null) {
...
line = br.readLine()
}
}
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.194755.1539777336000.7795.1558455060456%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57477) Cancelling a job results in "sendctrlc.x64...exe" stops working
Title: Message Title Kalle Niemitalo commented on JENKINS-57477 Re: Cancelling a job results in "sendctrlc.x64...exe" stops working We also run LTS here, but installing Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.40649 solved the crashes easily. I suggest not hurrying with the backport, in case there is some unexpected problem with the new winp version. 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.196067.1544012607000.7783.1558454220242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41377) Polling has not run yet, although received push event
Title: Message Title Ricardo Santos commented on JENKINS-41377 Re: Polling has not run yet, although received push event +1 same here only happens with pipeline job workaround: Create a freestyle project like "Trigger pipeline job" that will call the pipeline job (trigger other projects..) . 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.178159.148527334.7774.1558454100804%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57584) NullPointerException generating Incident Key
Title: Message Title Billy Dawson created an issue Jenkins / JENKINS-57584 NullPointerException generating Incident Key Issue Type: Bug Assignee: Alexander Leibzon Attachments: Job Config.png, Stack Trace.png Components: pagerduty-plugin Created: 2019-05-21 15:43 Environment: Jenkins 2.164.2 Plugin Version 0.4.1 Priority: Major Reporter: Billy Dawson Hi, we've been using this plugin with no issues for some time however as of this morning one of our jobs has been failing consistently. We have a post-build action (included in screenshots) which, when the incidentKey field is blank, results in a NullPointerException (also included in screenshots) whilst trying to extract the incident key. For now, our workaround is to set a hard value in the incidentKey field. Add Comment
[JIRA] (JENKINS-57477) Cancelling a job results in "sendctrlc.x64...exe" stops working
Title: Message Title michael pechner commented on JENKINS-57477 Re: Cancelling a job results in "sendctrlc.x64...exe" stops working Please consider for back porting. We only use LTS. 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.196067.1544012607000.7760.1558452540361%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56287) dbcp2 migration
Title: Message Title James Withers commented on JENKINS-56287 Re: dbcp2 migration When do you see this being released? 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.197866.1551183804000.7757.1558452480128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev updated JENKINS-57528 Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Released As: Jenkins 2.178 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.199434.155810265.7753.1558451940191%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Oleg Nenashev updated JENKINS-10160 Jenkins / JENKINS-10160 When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Duplicate 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.140348.1309401794000.7707.1558451882576%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Oleg Nenashev commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. We believe that JENKINS-25369 fixes it as well. Please reopen if you experience any issues 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.140348.1309401794000.7703.1558451822895%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim created an issue Jenkins / JENKINS-57583 Ignore target branch no longer working Issue Type: Bug Assignee: Unassigned Components: basic-branch-build-strategies-plugin Created: 2019-05-21 15:17 Priority: Major Reporter: Andrew Widdersheim I have Ignore rebuilding merge branches when only the target branch changed option enabled but it does not seem to work when doing a repository scan. Checking pull request #126 Could not determine the mergability of pull request 126. Retrying 4 more times... ‘Jenkinsfile’ found Met criteria Changes detected: PR-126 (d4c1e76f93b3bd14801516c1492ba086104c9f40+f0f67d5327479b7265b99bcbbcc9dfba41ac9d74 (84faa76b0eb2e77205ecd1d76aad5db154d0043a) → d4c1e76f93b3bd14801516c1492ba086104c9f40+a5b83e33ac3c7e8f950da549835e9ff6b630ec19 (b5dcd562b082ef2d32f265da138488cabe1ab39f)) Scheduled build for branch: PR-126 Checking pull request #125 Could not determine the mergability of pull request 125. Retrying 4 more times... ‘Jenkinsfile’ found Met criteria Changes detected: PR-125 (c58b5220b377015968b931d94e1687275b46c930+f0f67d5327479b7265b99bcbbcc9dfba41ac9d74 (d6aeb08d075198bd6cde73945584bdd77aa3dca0) → c58b5220b377015968b931d94e1687275b46c930+a5b83e33ac3c7e8f950da549835e9ff6b630ec19 (5377880b32efd962cf9efc0f9ef223f891a09a19)) Scheduled build for branch: PR-125 I only ever see the Could not determine the mergability of pull request 125. Retrying 4 more times... line after a change has been merged to the target of some PRs and I rescan. When rescanning without any changes it's fine.
[JIRA] (JENKINS-25369) DNS multicast error messages
Title: Message Title Oleg Nenashev commented on JENKINS-25369 Re: DNS multicast error messages LTS backporting comment: let's do more testing before considering backporting 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.158932.1414624779000.7635.1558451642510%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Patrick Rose commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Thanks to Francisco Fernández, this should now be fixed in 2.178! 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.140348.1309401794000.7632.1558451642380%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57573) Could not download plug ins.
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-57573 Could not download plug ins. Change By: Mark Waite Assignee: Mark Waite 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.199487.1558414103000.7559.1558451580804%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57326) Support jgit and jgitapache with Configuration as Code plugin
Title: Message Title Mark Waite started work on JENKINS-57326 Change By: Mark Waite 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.199098.1556975157000.7561.1558451580833%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25369) DNS multicast error messages
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-25369 DNS multicast error messages Change By: Oleg Nenashev Labels: 2.176.1-rejected dns dnsquestion logging lts-candidate sip 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.158932.1414624779000.7564.1558451580868%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57477) Cancelling a job results in "sendctrlc.x64...exe" stops working
Title: Message Title Oleg Nenashev commented on JENKINS-57477 Re: Cancelling a job results in "sendctrlc.x64...exe" stops working Released in Jenkins 2.178, will consider for LTS backporting 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.196067.1544012607000.7528.1558451521187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57573) Could not download plug ins.
Title: Message Title Mark Waite commented on JENKINS-57573 Re: Could not download plug ins. Please provide more details about the environment where you see the problem, the steps you've taken to investigate the problem, and the results of those steps. 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.199487.1558414103000.7532.1558451521226%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25369) DNS multicast error messages
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-25369 DNS multicast error messages It was released in Jenkins 2.178, but we do not think backporting is justified for now Change By: Oleg Nenashev Released As: Jenkins 2.178 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.158932.1414624779000.7535.1558451521254%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57573) Could not download plug ins.
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57573 Could not download plug ins. Change By: Mark Waite Component/s: core Component/s: git-plugin Component/s: maven-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.199487.1558414103000.7530.1558451521207%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57477) Cancelling a job results in "sendctrlc.x64...exe" stops working
Title: Message Title Oleg Nenashev updated JENKINS-57477 Jenkins / JENKINS-57477 Cancelling a job results in "sendctrlc.x64...exe" stops working Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.178 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.196067.1544012607000.7504.1558451462260%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57477) Cancelling a job results in "sendctrlc.x64...exe" stops working
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57477 Cancelling a job results in "sendctrlc.x64...exe" stops working Change By: Oleg Nenashev Labels: lts-candidate winp 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.196067.1544012607000.7506.1558451462288%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57434) Unable to add or edit roles
Title: Message Title simon townsend edited a comment on JENKINS-57434 Re: Unable to add or edit roles !Screen Shot 2019-05-21 at 10.08.15 AM.png! Also experiencing this issue. I am able to create new roles but cannot assign them due to '' !Screen Shot 2019-05-21 at 10.08.15 AM.png! 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.199247.1557753306000.7464.1558451402220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25369) DNS multicast error messages
Title: Message Title Francisco Fernández updated JENKINS-25369 Jenkins / JENKINS-25369 DNS multicast error messages Change By: Francisco Fernández Status: In Review Resolved 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.158932.1414624779000.7469.1558451402282%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57434) Unable to add or edit roles
Title: Message Title simon townsend updated an issue Jenkins / JENKINS-57434 Unable to add or edit roles Change By: simon townsend Attachment: Screen Shot 2019-05-21 at 10.08.15 AM.png 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.199247.1557753306000.7454.1558451340530%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57434) Unable to add or edit roles
Title: Message Title simon townsend commented on JENKINS-57434 Re: Unable to add or edit roles Also experiencing this issue. I am able to create new roles but cannot assign them due to '' 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.199247.1557753306000.7459.1558451340620%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57582) Add support for configuration-as-code
Title: Message Title Peter bos updated an issue Jenkins / JENKINS-57582 Add support for configuration-as-code Change By: Peter bos Please add support for configuration-as-code for this plugin so we can use it in a fully automated installation of our Jenkins instance. ([https://wiki.jenkins.io/display/JENKINS/Build+Timestamp+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.199499.1558451166000.7451.1558451280222%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57582) Add support for configuration-as-code
Title: Message Title Peter bos created an issue Jenkins / JENKINS-57582 Add support for configuration-as-code Issue Type: New Feature Assignee: Hao CHEN Components: build-timestamp-plugin Created: 2019-05-21 15:06 Priority: Minor Reporter: Peter bos 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.199499.1558451166000.7449.1558451220216%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Alexander Shcherbakov Attachment: zos-connector-explicit-logs.hpi 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.199458.1558312268000.7445.1558450560347%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov commented on JENKINS-57549 Re: Jenkins job doesn't detect completion of mainframe job OK, need to dig more logs - made just explicit logs on reconnect and relogon (new .hpi). Waiting for new logs. 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.199458.1558312268000.7447.1558450560376%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15063) support for multiple security realms with failover
Title: Message Title Andrew Barrett commented on JENKINS-15063 Re: support for multiple security realms with failover Can't say enough how I would like this feature. My org is possibly not going to use ldap with Jenkins because they want a fallback plan. Being able to have a small subset of local user accounts would be the ideal solution. But with the separation of security realms, I'm not sure I can convince them. 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.145783.1346946053000.7391.1558449783332%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15063) support for multiple security realms with failover
Title: Message Title Andrew Barrett updated an issue Jenkins / JENKINS-15063 support for multiple security realms with failover Change By: Andrew Barrett Comment: (y) Can't say enough how I would like this feature. My org is possibly not going to use ldap with Jenkins because they want a fallback plan. Being able to have a small subset of local user accounts would be the ideal solution. But with the separation of security realms, I'm not sure I can convince them. 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.145783.1346946053000.7393.1558449783350%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57458) Trigger job by creation of new p4 labels
Title: Message Title Matthew Dews commented on JENKINS-57458 Re: Trigger job by creation of new p4 labels Hi Karl Wirth, I have not had a chance to try this out yet and based on current priorities don't have plans to. This feature request came out of someone migrating their build process to Jenkins and asking if a "label, then build" workflow was possible. I think a "build, then label" workflow which p4 Jenkins already supports is a better fit for us since it is less maintence for our Helix/Perforce admins. 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.199318.1557843577000.7339.1558448640102%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57182) When configuring a Jira steps site in casc yaml file. If the Jenkins service is restarted, the site is duplicated in Jenkins config
Title: Message Title José Simões commented on JENKINS-57182 Re: When configuring a Jira steps site in casc yaml file. If the Jenkins service is restarted, the site is duplicated in Jenkins config Hi, I am also experiencing this problem. Naresh Rayapati did you find any workaround? 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.198934.1556196877000.7337.1558448520211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57554) Sauce plugin jobs timeout
Title: Message Title suryatej yaramada commented on JENKINS-57554 Re: Sauce plugin jobs timeout Any more information you need let me know so that I can provide more insights for this not sure if any others out there also having same issues 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.199463.1558338546000.7334.1558448340221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54365) Branch and commit fields are empty in BlueOcean UI Header-details element
Title: Message Title Igor Fishman edited a comment on JENKINS-54365 Re: Branch and commit fields are empty in BlueOcean UI Header-details element Hi,We also face same problem.Are the there any plans to resolve this issue in close future?Regards,Igor 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.195116.1540981558000.7331.1558447620102%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50711) plugin doesn't work with ssh link to git repo
Title: Message Title John Elion reopened an issue I understand that a fix has been made, but I am seeing the exact behavior described here right down to the stack trace (with different line numbers) in Jenkins 2.164.2 running on Centos 7 Linux with Git Parameter 0.9.10, Git plugin 3.10.0 and Git Client Plugin 2.7.7. The referenced Wiki page describes a similar error and states that the SSH command is not available. However, in my installation I have confirmed that it is available from an interactive terminal session both on the Jenkins master and the Jenkins slave, from the Jenkins Groovy Console a groovy script that executes an arbitrary command prints the ssh help when "ssh" is the arbitrary command, and when "SSH" is entered as the only command in a "Execute windows batch script" build step in a Freestyle test job running on our Windows Jenkins slave. (It's not clear to me whether this command is being attempted on the master, or on the slave where the job's workspace has already been created.) I mean no disrespect by re-opening this bug, but I believe it is still occurring. Could I ask that this be given a second look? If there is any output or missing information I can provide I will be happy to try to find it. [ Resurgence/jke_vulcan_playground ] Unexpected error! hudson.plugins.git.GitException: Command "git ls-remote -h ssh://vdn-bitbucket.pa10lab.gd-ms.us:7999/resurg/vulcan.git" returned status code 128: stdout: stderr: /tmp/ssh2051896551955727069.sh: line 6: ssh: command not found fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1666) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1657) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteReferences(CliGitAPIImpl.java:2877) Jenkins / JENKINS-50711 plugin doesn't work with ssh link to git repo Change By: John Elion Resolution: Fixed Status: Resolved Reopened
[JIRA] (JENKINS-54365) Branch and commit fields are empty in BlueOcean UI Header-details element
Title: Message Title Igor Fishman commented on JENKINS-54365 Re: Branch and commit fields are empty in BlueOcean UI Header-details element Hi, We also face same problem. Are the any plans to resolve this issue in close future? Regards, Igor 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.195116.1540981558000.7325.1558447500126%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title
Vincent Massol edited a comment on JENKINS-54128
Re: Deprecated calls to Run.getLogFile
Any idea why the following pipeline:{code}node() {echo "test"def reader = currentBuild.rawBuild.getLogReader()reader.eachLine() { line ->echo "Line: ${line}"if (line.matches(".*test.*")) {echo "got it!"}}}{code}Only prints the first log line:{noformat}Started by user Vincent MassolRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/Test[Pipeline] {[Pipeline] echotest[Pipeline] echoLine: Started by user Vincent Massol[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{noformat}?ThanksEDIT: see https://gitter.im/jenkinsci/jenkins?at=5ce3c760ad024978c6026d6f Seems it could be related to https://issues.jenkins-ci.org/browse/ JENKINS-46988
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.194755.1539777336000.7309.1558447321342%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title
Vincent Massol edited a comment on JENKINS-54128
Re: Deprecated calls to Run.getLogFile
Any idea why the following pipeline:{code}node() {echo "test"def reader = currentBuild.rawBuild.getLogReader()reader.eachLine() { line ->echo "Line: ${line}"if (line.matches(".*test.*")) {echo "got it!"}}}{code}Only prints the first log line:{noformat}Started by user Vincent MassolRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/Test[Pipeline] {[Pipeline] echotest[Pipeline] echoLine: Started by user Vincent Massol[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{noformat}?Thanks EDIT: see https://gitter.im/jenkinsci/jenkins?at=5ce3c760ad024978c6026d6f Seems it could be related to https://issues.jenkins-ci.org/browse/JENKINS-46988
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.194755.1539777336000.7307.1558447321311%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52697) Logstash plugin: support JCasC
Title: Message Title Robin Smith commented on JENKINS-52697 Re: Logstash plugin: support JCasC This was fixed a month ago. Any chance of a new release, to include the fix? 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.192583.1532331323000.7291.1558447200237%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52396) Integration with Blue Ocean?
Title: Message Title Paul Allen started work on JENKINS-52396 Change By: Paul Allen 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.192190.1530811976000.7281.1558446300603%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44860) Disable masking of usernames
Title: Message Title Tim Jaacks commented on JENKINS-44860 Re: Disable masking of usernames +1 from me. This is REALLY annoying. We are using "jenkins" as a username as well, while our Jenkins instance is running under "http://our-company-intranet/jenkins/". This bug changes all URLs in the job log to "http://our-company-intranet/", making them unusable. 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.182924.1497380811000.7278.1558445340754%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48969) Getting "No emails were triggered" on console output and also no mail sent.
Title: Message Title cognitive genie edited a comment on JENKINS-48969 Re: Getting "No emails were triggered" on console output and also no mail sent. Hi,I have configured "Email-ext" plugin in jenkins clearly, attaching screenshot for reference also did the SMTP authentication. Also tested configuration by sending test e-mail and got the mail. But when I call the same through the job then I don't get any mail and showing "No emails were triggered " message on console output. Please guide regarding same. 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.187781.1516117903000.7257.1558443540231%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48969) Getting "No emails were triggered" on console output and also no mail sent.
Title: Message Title cognitive genie updated an issue Jenkins / JENKINS-48969 Getting "No emails were triggered" on console output and also no mail sent. Change By: cognitive genie Attachment: Screen Shot 2019-05-21 at 6.20.17 PM.png 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.187781.1516117903000.7249.1558443240512%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57560) Export for JCasC is empty
Title: Message Title Pavel Janoušek closed an issue as Cannot Reproduce Seems working after re-test with core version 2.164.3, CaC 1.15 and Git 3.10. Export contains at least a default git tool configuration now (as I expected previously). Sorry for the confusion Mark. Jenkins / JENKINS-57560 Export for JCasC is empty Change By: Pavel Janoušek Status: Open Closed Resolution: Cannot Reproduce 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.199471.1558357021000.7251.1558443300341%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48969) Getting "No emails were triggered" on console output and also no mail sent.
Title: Message Title cognitive genie updated an issue Jenkins / JENKINS-48969 Getting "No emails were triggered" on console output and also no mail sent. Change By: cognitive genie Attachment: Screen Shot 2019-05-21 at 6.20.17 PM.png 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.187781.1516117903000.7246.1558443120262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48969) Getting "No emails were triggered" on console output and also no mail sent.
Title: Message Title cognitive genie edited a comment on JENKINS-48969 Re: Getting "No emails were triggered" on console output and also no mail sent. Hi,I have configured "Email-ext" plugin in jenkins clearly, attaching screenshot for reference also did the SMTP authentication. Also tested configuration by sending test e-mail and got the mail. But when I call the same through the job then I don't get any mail and showing "No emails were triggered " message on console output. Please guide regarding same. !Screen Shot 2019-05-21 at 6.20.17 PM.png! 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.187781.1516117903000.7254.1558443300379%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48969) Getting "No emails were triggered" on console output and also no mail sent.
Title: Message Title cognitive genie commented on JENKINS-48969 Re: Getting "No emails were triggered" on console output and also no mail sent. Hi, I have configured "Email-ext" plugin in jenkins clearly, attaching screenshot for reference also did the SMTP authentication. Also tested configuration by sending test e-mail and got the mail. But when I call the same through the job then I don't get any mail and showing "No emails were triggered " message on console output. Please guide regarding same. 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.187781.1516117903000.7243.1558443120222%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57524) JCasC export contains only one record
Title: Message Title Pavel Janoušek closed an issue as Fixed Seems working during re-test with core version 2.164.3, CaC 1.15, JDK Tool 1.2. Jenkins / JENKINS-57524 JCasC export contains only one record Change By: Pavel Janoušek Status: Open Closed 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.199429.1558095004000.7230.1558442700891%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48969) Getting "No emails were triggered" on console output and also no mail sent.
Title: Message Title cognitive genie reopened an issue Jenkins / JENKINS-48969 Getting "No emails were triggered" on console output and also no mail sent. Change By: cognitive genie Resolution: Not A Defect Status: Resolved Reopened 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.187781.1516117903000.7239.1558442940458%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57525) JCasC export contains only one record
Title: Message Title Pavel Janoušek closed an issue as Cannot Reproduce Seems working after re-test with core version 2.164.3, CaC 1.15. Jenkins / JENKINS-57525 JCasC export contains only one record Change By: Pavel Janoušek Status: Open Closed Resolution: Cannot Reproduce 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.199430.1558095041000.7240.1558442940470%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57524) JCasC export contains only one record
Title: Message Title Pavel Janoušek closed an issue as Cannot Reproduce Fixing Resolution. Jenkins / JENKINS-57524 JCasC export contains only one record Change By: Pavel Janoušek Status: Reopened Closed Resolution: Cannot Reproduce 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.199429.1558095004000.7235.1558442700960%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
