[JIRA] (JENKINS-61722) Create tests for TestScore (in AutoGrader)
Title: Message Title Mitja Oldenbourg started work on JENKINS-61722 Change By: Mitja Oldenbourg Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205548.1585338376000.4033.1585726500489%40Atlassian.JIRA.
[JIRA] (JENKINS-61722) Create tests for TestScore (in AutoGrader)
Title: Message Title Mitja Oldenbourg assigned an issue to Mitja Oldenbourg Jenkins / JENKINS-61722 Create tests for TestScore (in AutoGrader) Change By: Mitja Oldenbourg Assignee: Mitja Oldenbourg Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205548.1585338376000.4035.1585726561040%40Atlassian.JIRA.
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Romen Rodriguez-Gil commented on JENKINS-61478 Re: "Apply" (and similar) banners look really bad with larger header bar PR: https://github.com/jenkinsci/jenkins/pull/4610 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205161.1584140786000.4061.1585727880210%40Atlassian.JIRA.
[JIRA] (JENKINS-60143) Behaviour SSH Checkout not working after Jenkins restart
Title: Message Title Vincent Letarouilly commented on JENKINS-60143 Re: Behaviour SSH Checkout not working after Jenkins restart This is also happening when triggering a "Reload Configuration from Disk" from the "Manage Jenkins" menu. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.203004.1573562285000.4065.1585734000253%40Atlassian.JIRA.
[JIRA] (JENKINS-61687) Exceptions due to global build discarder
Title: Message Title Daniel Beck commented on JENKINS-61687 Re: Exceptions due to global build discarder Run#delete looks reasonable enough. Correction: This method makes absolutely no sense. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205510.1585173096000.4070.1585735260436%40Atlassian.JIRA.
[JIRA] (JENKINS-61763) Global build discarder trying to rotate the logs for builds not available
Title: Message Title Daniel Beck commented on JENKINS-61763 Re: Global build discarder trying to rotate the logs for builds not available but after reboot settings were defaulted to "Project Build Discarder", attached screen shots before and after reboot https://jenkins.io/changelog/#v2.229 Regarding the reported issue, that's a concurrency bug elsewhere in core: JENKINS-61687 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205600.1585721857000.4072.1585735260463%40Atlassian.JIRA.
[JIRA] (JENKINS-61763) Global build discarder trying to rotate the logs for builds not available
Title: Message Title Daniel Beck closed an issue as Duplicate Jenkins / JENKINS-61763 Global build discarder trying to rotate the logs for builds not available Change By: Daniel Beck Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205600.1585721857000.4074.1585735260501%40Atlassian.JIRA.
[JIRA] (JENKINS-61723) Create tests for AnalysisScore (in AutoGrader)
Title: Message Title Ulli Hafner assigned an issue to Maximilian Kilian There is no need to change the assignee: in Jenkins projects the assignee is the author who is fixing an issue. Intermediate steps like reviews do typically not touch the assignee. Jenkins / JENKINS-61723 Create tests for AnalysisScore (in AutoGrader) Change By: Ulli Hafner Assignee: Ulli Hafner Maximilian Kilian Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205549.158533863
[JIRA] (JENKINS-61745) Scan multibranch with date range or dop '@now'
Title: Message Title Paul Allen commented on JENKINS-61745 Re: Scan multibranch with date range or dop '@now' Added fix: https://github.com/jenkinsci/p4-plugin/commit/62c83c4368a10a2538a04f1988ae59c9c00d11cc Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205574.1585583601000.4079.1585736400123%40Atlassian.JIRA.
[JIRA] (JENKINS-61745) Scan multibranch with date range or dop '@now'
Title: Message Title Paul Allen commented on JENKINS-61745 Re: Scan multibranch with date range or dop '@now' Latest build: https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/446/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205574.1585583601000.4081.1585737120235%40Atlassian.JIRA.
[JIRA] (JENKINS-61765) Automate Release Notes with commit messages using Jenkins JOB DSL
Title: Message Title Aman Gupta created an issue Jenkins / JENKINS-61765 Automate Release Notes with commit messages using Jenkins JOB DSL Issue Type: Task Assignee: Emilio Escobar Components: changelog-history-plugin, job-dsl-plugin Created: 2020-04-01 10:39 Environment: NA Priority: Minor Reporter: Aman Gupta Hi I want to Automate the process of generating the release notes having information about the Commits ( Commit messages etc). using Jenkins JOB DSL (groovy). Add Comment
[JIRA] (JENKINS-61067) Wrong value for GIT_COMMIT after merge?
Title: Message Title Oleksandr Tretiak commented on JENKINS-61067 Re: Wrong value for GIT_COMMIT after merge? We have the same issue with the PR. We are using Multibranch pipelines. If we peek ChangeRequestCheckoutStrategy.MERGE as a result it will try merge the existing branch and use the SHA of it as GIT_COMMIT instead of HEAD Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.204551.1581508949000.4085.1585737960140%40Atlassian.JIRA.
[JIRA] (JENKINS-61766) JUnit report misses test cases from duplicate testsuites
Title: Message Title Kai Bublitz created an issue Jenkins / JENKINS-61766 JUnit report misses test cases from duplicate testsuites Issue Type: Bug Assignee: Unassigned Attachments: JUnit Report.png, test_1.xml, test_2.xml Components: junit-plugin Created: 2020-04-01 10:47 Environment: Jenkins ver. 2.204.6 JUnit Plugin (junit): 1.28 OS: Ubuntu Linux 18.04 Labels: junit junit-plugin Priority: Major Reporter: Kai Bublitz When the same testsuite appears in multiple files with the same timestamp, only the first testsuite is evaluated, any testcases in following files are silently ignored. I attached two test report XML files with typical output of our build runs, yet simplified as much as possible. As you can see, both files contain a different test case of the same testsuite "TestFoo". If the test execution is very fast it can happen that both the testsuites have the same timestamp, in which case every testcase but the first is not included in the report, as you can see on the attached screenshot. The expected behaviour is, that all the testcases are included in the report and the stage fails if any of the testcases failed. I consider this a major bug as it allows failed tests to be ignored and in the consequence broken software can be reported as "successfull" when it isn't.
[JIRA] (JENKINS-61256) Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
Title: Message Title Reinhold Füreder commented on JENKINS-61256 Re: Warning log spam due to new (default) BackgroundGlobalBuildDiscarder I think the "just deleting in UI does not help" was in the meantime fixed by JENKINS-61688 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.204823.1582799473000.4089.1585739460134%40Atlassian.JIRA.
[JIRA] (JENKINS-61256) Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
Title: Message Title Daniel Beck commented on JENKINS-61256 Re: Warning log spam due to new (default) BackgroundGlobalBuildDiscarder Right, and for the reported issue I somehow managed to report a duplicate at JENKINS-61687. Some analysis there, looks more like an existing core bug being exposed through some weird behavior by global build discarders rather than something new. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.204823.1582799473000.4092.1585740420175%40Atlassian.JIRA.
[JIRA] (JENKINS-61256) Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
Title: Message Title Daniel Beck edited a comment on JENKINS-61256 Re: Warning log spam due to new (default) BackgroundGlobalBuildDiscarder Right, and for the reported issue I somehow managed to report a duplicate at JENKINS-61687.Some analysis there, looks more like an existing core bug being exposed (more likely to occur) through some weird behavior by global build discarders rather than something new. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.204823.1582799473000.4094.1585740480191%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Oguz halit sak commented on JENKINS-59503 Re: Plugin does not save settings similar problem here Jenkins 2.229 Plugin 1.4.8 openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode) Centos8 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.202124.1569316263000.4098.1585742640323%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title
Oguz halit sak edited a comment on JENKINS-59503
Re: Plugin does not save settings
similar problem here * {color:#172b4d}Jenkins 2.229{color} * {color:#172b4d}Plugin 1.4.8{color} * {color:#172b4d}openjdk version "1.8.0_242"OpenJDK Runtime Environment (build 1.8.0_242-b08)OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode){color} * {color:#172b4d}Centos8{color} I am changing Notification message and saved but{color:#172b4d}!image-2020-04-01-15-06-22-765.png|width=637,height=287!{color}Not save.{color:#172b4d}!image-2020-04-01-15-08-11-655.png!{color}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.202124.1569316263000.4111.1585743060354%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title
Oguz halit sak edited a comment on JENKINS-59503
Re: Plugin does not save settings
similar problem here * {color:#172b4d}Jenkins 2.229{color} * {color:#172b4d}Plugin 1.4.8{color} * {color:#172b4d}openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode){color} * {color:#172b4d}Centos8{color}I am changing Notification message and saved but{color:#172b4d}!image-2020-04-01-15-06-22-765.png|width=637,height=287!{color}Not save. Where can the problem {color:#172b4d}!image-2020-04-01-15-08-11-655.png!{color}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.202124.1569316263000.4124.1585743180313%40Atlassian.JIRA.
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username
Title: Message Title Josip Gracin commented on JENKINS-60440 Re: Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username Hi! Just confirming that I have the same issue with GitHub. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.203515.1576064724000.4136.1585743300119%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title
Oguz halit sak edited a comment on JENKINS-59503
Re: Plugin does not save settings
similar problem here * {color:#172b4d}Jenkins 2.229{color} * {color:#172b4d}Plugin 1.4.8{color} * {color:#172b4d}openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode){color} * {color:#172b4d}Centos8{color}I am changing Notification message and saved but includes. then clicked "save". {color:#172b4d}!image-2020-04-01-15-06-22-765.png|width=637,height=287!{color} Not does not save. Where can the problem {color:#172b4d}!image-2020-04-01-15-08-11-655.png!{color}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.202124.1569316263000.4141.1585743360334%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Usama Tariq commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Hi, Please let me know how to submit a pull request with a fix for Jira-trigger plugin ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.201336.1566200967000.4154.1585747083875%40Atlassian.JIRA.
[JIRA] (JENKINS-61767) Seeing 504 Gateway timeout after updating to LTS version
Title: Message Title suryatej yaramada created an issue Jenkins / JENKINS-61767 Seeing 504 Gateway timeout after updating to LTS version Issue Type: Bug Assignee: Ivan Fernandez Calvo Attachments: Screenshot from 2020-03-31 12-09-39.png Components: saml-plugin Created: 2020-04-01 14:16 Environment: Jenkins - 2.222.1 , SAML -latest Priority: Minor Reporter: suryatej yaramada After updrading to LTS 2.222.1 version we are seeing 504 Gateway timeouts on Jenkns , where it is running on EKS with custom Dockerfile with base image amazonlinux. we are using ingress with elb . after a refresh it automatically loading page . we are using SAML okta authentication. nothing found so far in logs . Add Comment
[JIRA] (JENKINS-54520) Abort job won't abort publish-over-cifs-plugin step
Title: Message Title Adam Outler commented on JENKINS-54520 Re: Abort job won't abort publish-over-cifs-plugin step I was able to reproduce this when I accidentially set my WINS server to the address of my DNS server. Apparently there may be a problem within the WINS resolution timeout. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.195291.1541609424000.4165.1585751340134%40Atlassian.JIRA.
[JIRA] (JENKINS-24319) Windows slave dying during build - unsatisfied link error
Title: Message Title P4 commented on JENKINS-24319 Re: Windows slave dying during build - unsatisfied link error Recently we have added second Windows agent to our Windows master and immediately started to observe this issue. No such problems on the first Windows agent that is running here for months. This is sanitized log fragment from the agent: mar 31, 2020 10:00:57 PM org.jvnet.winp.Native loadByUrl WARNING: Failed to load DLL from static location java.lang.UnsatisfiedLinkError: Native Library J:\Jenkins\remoting\jarCache\44\winp.x64.BFFE30B3B50581290B1866EF8D48C609.dll already loaded in another classloader at java.lang.ClassLoader.loadLibrary0(Unknown Source) at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.load0(Unknown Source) at java.lang.System.load(Unknown Source) at org.jvnet.winp.Native.loadDll(Native.java:242) at org.jvnet.winp.Native.loadByUrl(Native.java:162) at org.jvnet.winp.Native.load(Native.java:124) at org.jvnet.winp.Native.(Native.java:93) at org.jvnet.winp.WinProcess.enableDebugPrivilege(WinProcess.java:245) at hudson.util.ProcessTree$Windows.(ProcessTree.java:701) at hudson.util.ProcessTree.get(ProcessTree.java:447) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1100) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1091) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:97) at java.lang.Thread.run(Unknown Source) kwi 01, 2020 12:25:05 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Terminated kwi 01, 2020 12:25:05 AM hudson.Launcher$RemoteLaunchCallable$1 join INFO: Failed to synchronize IO streams on the channel hudson.remoting.Channel@1aa3bc97:JNLP4-connect connection to jenkins./: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@1aa3bc97:JNLP4-connect connection to jenkins./:": Remote call on JNLP4-connect connection to jenkins./: failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:948) at hudson.remoting.Channel.syncIO(Channel.java:1683) at hudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:1328) at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolEx
[JIRA] (JENKINS-24319) Windows slave dying during build - unsatisfied link error
Title: Message Title
P4 edited a comment on JENKINS-24319
Re: Windows slave dying during build - unsatisfied link error
Recently we have added second Windows agent to our Windows master and immediately started to observe this issue. No such problems on the first Windows agent that is running here for months. Both systems are Microsoft Windows [Version 10.0.18363.720]. This is sanitized log fragment from the agent:{code :java } mar 31, 2020 10:00:57 PM org.jvnet.winp.Native loadByUrl WARNING: Failed to load DLL from static location java.lang.UnsatisfiedLinkError: Native Library J:\Jenkins\remoting\jarCache\44\winp.x64.BFFE30B3B50581290B1866EF8D48C609.dll already loaded in another classloader at java.lang.ClassLoader.loadLibrary0(Unknown Source) at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.load0(Unknown Source) at java.lang.System.load(Unknown Source) at org.jvnet.winp.Native.loadDll(Native.java:242) at org.jvnet.winp.Native.loadByUrl(Native.java:162) at org.jvnet.winp.Native.load(Native.java:124) at org.jvnet.winp.Native.(Native.java:93) at org.jvnet.winp.WinProcess.enableDebugPrivilege(WinProcess.java:245) at hudson.util.ProcessTree$Windows.(ProcessTree.java:701) at hudson.util.ProcessTree.get(ProcessTree.java:447) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1100) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1091) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:97) at java.lang.Thread.run(Unknown Source)kwi 01, 2020 12:25:05 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Terminated kwi 01, 2020 12:25:05 AM hudson.Launcher$RemoteLaunchCallable$1 join INFO: Failed to synchronize IO streams on the channel hudson.remoting.Channel@1aa3bc97:JNLP4-connect connection to jenkins./: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@1aa3bc97:JNLP4-connect connection to jenkins./:": Remote call on JNLP4-connect connection to jenkins./: failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:948) at hudson.remoting.Channel.syncIO(Channel.java:1683) at hudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:1328) at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:97) at java.lang.Thread.run(Unknown Source) Caused b
[JIRA] (JENKINS-61767) Seeing 504 Gateway timeout after updating to LTS version
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61767 Re: Seeing 504 Gateway timeout after updating to LTS version Did you see the login page? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205604.1585750575000.4185.1585751820282%40Atlassian.JIRA.
[JIRA] (JENKINS-61067) Wrong value for GIT_COMMIT after merge?
Title: Message Title
Oleksandr Tretiak commented on JENKINS-61067
Re: Wrong value for GIT_COMMIT after merge?
Workerround :
String SHORT_COMMIT = sh (returnStdout: true, script: "git ls-remote -q | awk '/${CHANGE_BRANCH.replace("/", "\\/")}/{print substr(\$0,0,7)}'").trim()
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204551.1581508949000.4183.1585751820252%40Atlassian.JIRA.
[JIRA] (JENKINS-61767) Seeing 504 Gateway timeout after updating to LTS version
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-61767 Re: Seeing 504 Gateway timeout after updating to LTS version Did Do you see the login page? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205604.1585750575000.4187.1585751880198%40Atlassian.JIRA.
[JIRA] (JENKINS-61767) Seeing 504 Gateway timeout after updating to LTS version
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-61767 Re: Seeing 504 Gateway timeout after updating to LTS version Do you see the login page? Or the main page of Jenkins? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205604.1585750575000.4189.1585751880296%40Atlassian.JIRA.
[JIRA] (JENKINS-61767) Seeing 504 Gateway timeout after updating to LTS version
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-61767 Re: Seeing 504 Gateway timeout after updating to LTS version Do you see the login page? Or the main page of Jenkins? Do it happens to all users? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205604.1585750575000.4191.1585752000122%40Atlassian.JIRA.
[JIRA] (JENKINS-61767) Seeing 504 Gateway timeout after updating to LTS version
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-61767 Re: Seeing 504 Gateway timeout after updating to LTS version Do you see the login page? Or the main page of Jenkins?Do it happens to all users?Did you check the ingress ELB logs? Did you try to connect locally from the pod? That 503 is returned by ingress, if there is nothing in the Jenkins logs I will said that it is something between ingress and Jenkins , In any case I do not see the relation with the SAML plugin. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205604.1585750575000.4193.1585752180156%40Atlassian.JIRA.
[JIRA] (JENKINS-52391) Restarting Parallel Stages
Title: Message Title
Gabriel Herisanu commented on JENKINS-52391
Re: Restarting Parallel Stages
You can use something like this:
#!groovy
def withCheck(String blockName, Closure closure) {
script {
def buildStage = true
catchError(message: 'check previous build status', stageResult:'SUCCESS', buildResult: 'SUCCESS') {
unstash name:"${blockName}"
buildStage = false
}
if (buildStage) {
closure.call()
writeFile file: "${blockName}", text: "1"
stash name: "${blockName}", includes: "${blockName}"
}
}
}
pipeline {
agent none
options {
preserveStashes()
}
stages {
stage("Build and test") {
parallel() {
stage("Build/Test Win64") {
agent {
label 'generic-agents'
}
steps {
withCheck("build-deploy-Win64") {
echo "test"
}
withCheck("test-Win64") {
echo "test"
}
}
}
stage("Build/Test Win32") {
agent {
label 'generic-agents'
}
steps {
withCheck("build-deploy-Win32") {
echo "test"
}
withCheck("test-Win32") {
echo "test"
}
}
}
}
}
stage("Deploy") {
agent {
label 'generic-agents'
}
steps {
withCheck("build-deploy-win64") {
echo "test"
}
withCheck("test-win64") {
echo "test"
}
}
}
}
}
Add Comment
[JIRA] (JENKINS-52391) Restarting Parallel Stages
Title: Message Title
Gabriel Herisanu edited a comment on JENKINS-52391
Re: Restarting Parallel Stages
You can use something like this:{code:java}#!groovydef withCheck(String blockName, Closure closure) {script {def buildStage = truecatchError(message: 'check previous build status', stageResult:'SUCCESS', buildResult: 'SUCCESS') {unstash name:"${blockName}"buildStage = false}if (buildStage) {closure.call()writeFile file: "${blockName}", text: "1"stash name: "${blockName}", includes: "${blockName}"}}}pipeline {agent noneoptions {preserveStashes()}stages {stage("Build and test") {parallel() {stage("Build/Test Win64") {agent { label ' generic-agents master '}steps { withCheck("build-deploy-Win64") { echo "test" } withCheck("test-Win64") { echo "test" }}}stage("Build/Test Win32") {agent { label ' generic-agents master '}steps { withCheck("build-deploy-Win32") { echo "test" } withCheck("test-Win32") { echo "test" }}}}}stage("Deploy") {agent {label ' generic-agents master '}steps {withCheck("build-deploy-win64") {echo "test"}withCheck("test-win64") {echo "test"}}}}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title
Oguz halit sak edited a comment on JENKINS-59503
Re: Plugin does not save settings
similar problem here * {color:#172b4d}Jenkins 2.229{color} * {color:#172b4d}Plugin 1.4.8{color} * {color:#172b4d}openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode){color} * {color:#172b4d}Centos8{color}I am changing Notification message includes. then clicked "save".{color:#172b4d}!image-2020-04-01-15-06-22-765.png|width= 546 504 ,height= 246 227 !{color}does not save. {color:#172b4d}!image-2020-04-01-15-08-11-655.png|width= 542 497 ,height= 254 233 !{color}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.202124.1569316263000.4267.1585753681122%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title
Oguz halit sak edited a comment on JENKINS-59503
Re: Plugin does not save settings
similar problem here * {color:#172b4d}Jenkins 2.229{color} * {color:#172b4d}Plugin 1.4.8{color} * {color:#172b4d}openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode){color} * {color:#172b4d}Centos8{color}I am changing Notification message includes. then clicked "save".{color:#172b4d}!image-2020-04-01-15-06-22-765.png|width= 504 475 ,height= 227 214 !{color}does not save. {color:#172b4d}!image-2020-04-01-15-08-11-655.png|width= 497 476 ,height= 233 223 !{color}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.202124.1569316263000.4280.1585753681268%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title
Oguz halit sak edited a comment on JENKINS-59503
Re: Plugin does not save settings
similar problem here * {color:#172b4d}Jenkins 2.229{color} * {color:#172b4d}Plugin 1.4.8{color} * {color:#172b4d}openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode){color} * {color:#172b4d}Centos8{color}I am changing Notification message includes. then clicked "save".{color:#172b4d}!image-2020-04-01-15-06-22-765.png|width= 637 546 ,height= 287 246 !{color}does not save. {color:#172b4d}!image-2020-04-01-15-08-11-655.png |width=542,height=254 !{color}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.202124.1569316263000.4254.1585753680961%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title
Oguz halit sak edited a comment on JENKINS-59503
Re: Plugin does not save settings
similar problem here * {color:#172b4d}Jenkins 2.229{color} * {color:#172b4d}Plugin 1.4.8{color} * {color:#172b4d}openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode){color} * {color:#172b4d}Centos8{color}I am changing Notification message includes. then clicked "save".{color:#172b4d}!image-2020-04-01-15-06-22-765.png|width= 475 511 ,height= 214 230 !{color}does not save. {color:#172b4d}!image-2020-04-01-15-08-11-655.png|width= 476 502 ,height= 223 235 !{color}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.202124.1569316263000.4303.1585753740608%40Atlassian.JIRA.
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick commented on JENKINS-51143 Re: List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs #12 was a continuation of #11 Yes, but actually the three lines of code in #11 which actually fixed this issue were right, and #12 did something different and unnecessarily complex. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.190437.1525450293000.4305.1585754400310%40Atlassian.JIRA.
[JIRA] (JENKINS-61768) plugin bundles slf4j-api causing no test output for plugins that depend on it.
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-61768
plugin bundles slf4j-api causing no test output for plugins that depend on it.
Change By:
James Nord
the `analysis-model-api` plugin packages slf4j version 1.8 which is incompatable with Jenkins. (org.jvnet.hudson.plugins.findbugs:library:jar:6.0.3) However it is packed in a uber jar that you can not exclude.{{io.jenkins.plugins:analysis-model-api:jar:8.0.1:compile (optional)}}{{ \ - edu.hm.hafner:analysis-model:jar:8.0.1:compile (optional)}}{{ +- se.bjurr.violations:violations-lib:jar:1.110:compile (optional)}}{{ +- org.jvnet.hudson.plugins.findbugs:library:jar:6.0.3:compile (optional)}} this means if you depend on this plugin (via warnings-ng) for example you end up with no output in unit tests because the slf4j provider (jdk14) provided by jenkins is too old and is ignored {{SLF4J: No SLF4J providers were found.}}{{SLF4J: Defaulting to no-operation (NOP) logger implementation}}{{SLF4J: See [ http://www.slf4j.org/codes.html#noProviders ] for further details.}}{{SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions prior to 1.8.}}{{SLF4J: Ignoring binding found at [jar:file:/C:/Users/jnord/.m2/repository/org/slf4j/slf4j-jdk14/1.7.26/slf4j-jdk14-1.7.26.jar!/org/slf4j/impl/StaticLoggerBinder.class]}}{{SLF4J: See [ http://www.slf4j.org/codes.html#ignoredBindings ] for an explanation.}} as well as the slf4j provider there are other potential evil things packaged such as xerces (which could overwrite the stock JDK parers) multiple XML APIs jcip annotations (comes from core) commons-lang (again comes from core - but causes a different version to be picked up)
Add Comment
[JIRA] (JENKINS-61768) plugin bundles slf4j-api causing no test output for plugins that depend on it.
Title: Message Title James Nord created an issue Jenkins / JENKINS-61768 plugin bundles slf4j-api causing no test output for plugins that depend on it. Issue Type: Bug Assignee: Ulli Hafner Components: analysis-model-api-plugin Created: 2020-04-01 15:26 Priority: Minor Reporter: James Nord the `analysis-model-api` plugin packages slf4j version 1.8 which is incompatable with Jenkins. However it is packed in a uber jar that you can not exclude. io.jenkins.plugins:analysis-model-api:jar:8.0.1:compile (optional) - edu.hm.hafner:analysis-model:jar:8.0.1:compile (optional) +- se.bjurr.violations:violations-lib:jar:1.110:compile (optional) +- org.jvnet.hudson.plugins.findbugs:library:jar:6.0.3:compile (optional) this means if you depend on this plugin (via warnings-ng) for example you end up with no output in unit tests because the slf4j provider (jdk14) provided by jenkins is too old and is ignored SLF4J: No SLF4J providers were found. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#noProviders for further details. SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions prior to 1.8. SLF4J: Ignoring binding found at [jar:file:/C:/Users/jnord/.m2/repository/org/slf4j/slf4j-jdk14/1.7.26/slf4j-jdk14-1.7.26.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#ignoredBindings for an explanation. as well as the slf4j provider there are other potential evil things packaged such as xerces (which could overwrite the stock JDK parers) multiple XML APIs jcip annotations (comes from core) commons-lang (again comes from core - but causes a different version to be picked up)
[JIRA] (JENKINS-61762) Intermittent Socket closed error
Title: Message Title Shivaji Thanneeru updated an issue Jenkins / JENKINS-61762 Intermittent Socket closed error Change By: Shivaji Thanneeru Summary: Interment Intermittent Socket closed error Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205599.1585716788000.4342.1585756980192%40Atlassian.JIRA.
[JIRA] (JENKINS-38699) Confine git commands to workspace directory
Title: Message Title Mark R commented on JENKINS-38699 Re: Confine git commands to workspace directory Looks like a good feature. We ran into this because we have a git mechanism that backs up job config.xmls, nextBuildNumber, and a few other files to git nightly. Every now and then a pipeline jobs git gets corrupted somehow (not sure how) and it picks up the git workspace at the root jobs level. This causes it to checkout git at the root jobs level and causes problems. The workaround of setting the GIT_CEILING_DIRECTORIES worked though we did find it is case sensitive. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.175097.1475592084000.4344.1585757160164%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Oguz halit sak reopened an issue I am changing Notification message includes. then clicked "save". then again open but not sa Jenkins / JENKINS-59503 Plugin does not save settings Change By: Oguz halit sak Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Oguz halit sak edited a comment on JENKINS-59503 Re: Plugin does not save settings I am changing Notification message includes. then clicked "save".!image-2020-04-01-19- 05 07 - 41 16 - 200 720 .png|width= 522 680 ,height= 235 306 !then again open but not sa saved !image-2020-04-01-19- 06 08 - 19 22 - 155 300 .png|width= 523 724 ,height= 245 339 ! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.202124.1569316263000.4362.1585757340699%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title
Oguz halit sak updated an issue
Jenkins / JENKINS-59503
Plugin does not save settings
Change By:
Oguz halit sak
Comment:
similar problem here * {color:#172b4d}Jenkins 2.229{color} * {color:#172b4d}Plugin 1.4.8{color} * {color:#172b4d}openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode){color} * {color:#172b4d}Centos8{color}I am changing Notification message includes. then clicked "save".{color:#172b4d}!image-2020-04-01-15-06-22-765.png|width=511,height=230!{color}does not save. {color:#172b4d}!image-2020-04-01-15-08-11-655.png|width=502,height=235!{color}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.202124.1569316263000.4375.1585757340870%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title
Oguz halit sak edited a comment on JENKINS-59503
Re: Plugin does not save settings
similar problem here * {color:#172b4d}Jenkins 2.229{color} * {color:#172b4d}Plugin 1.4.8{color} * {color:#172b4d}openjdk version "1.8.0_242"OpenJDK Runtime Environment (build 1.8.0_242-b08)OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode){color} * {color:#172b4d}Centos8{color} I am changing Notification message includes. then clicked "save".!image-2020-04-01-19-07-16-720.png|width=680,height=306!then again open but not saved !image-2020-04-01-19-08-22-300.png|width=724,height=339!
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.202124.1569316263000.4388.1585757412676%40Atlassian.JIRA.
[JIRA] (JENKINS-61769) git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches
Title: Message Title krishna prasad created an issue Jenkins / JENKINS-61769 git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches Issue Type: Bug Assignee: Boguslaw Klimas Attachments: image-2020-04-01-21-41-34-429.png Components: git-parameter-plugin Created: 2020-04-01 16:12 Priority: Minor Reporter: krishna prasad I have configured Jenkins git parameter plugin for selecting appropriate branches before building a job. I am using two repositories for building a single job. For one of the repositories its showing two remote sever as origin and origin1 but actually it has only one it is origin. I have checked the repository and given the result as below $ git ls-remote --heads origin d8c63b4c1f1a87cba2b5065d3c2018193079fb80 refs/heads/ 3b390cec5ede9ec4dede3b83dc8d05969a286b70 refs/heads/ ea0908b790a8491584bfe0f7e7ba459ee6307cb0 refs/heads/ a1225d5a8f1a24ef4c65384b6833224358d30587 refs/heads/ 74977aed5ed375d2afae0e35d3ec73fa214e63e1 refs/heads/ 9e3e0fa0c93829b9dbb945f3d7788e77462f15c9 refs/heads/feature/scenario ff9af7bcd7d6c06cbb573656cf73abe2c0b26538 refs/heads/master $ git ls-remote From https://github.developer.allianz.io/cta-crui/crui-data-model.git ff9af7bcd7d6c06cbb573656cf73abe2c0b26538 HEAD d8c63b4c1f1a87cba2b5065d3c2018193079fb80 refs/heads/ 3b390cec5ede9ec4dede3b83dc8d05969a286b70 refs/heads/ ea0908b790a8491584bfe0f7e7ba459ee6307cb0 refs/heads/ a1225d5a8f1a24ef4c65384b6833224358d30587 refs/heads/ 74977aed5ed375d2afae0e35d3ec73fa214e63e1 refs/heads/ 9e3e0fa0c93829b9dbb945f3d7788e77462f15c9 refs/heads/feature/scenario ff9af7bcd7d6c06cbb573656cf73abe2c0b26538 refs/heads/maste
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title Roman Pickl closed an issue as Fixed Jenkins / JENKINS-58177 Leading - in workspace directory names mangled in multibranch pipeline Change By: Roman Pickl Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.200228.1561442061000.4404.1585757880258%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Gábor Tasnádi updated an issue Jenkins / JENKINS-61480 Dark Theme Change By: Gábor Tasnádi Attachment: dark.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205164.1584202104000.4407.1585759260295%40Atlassian.JIRA.
[JIRA] (JENKINS-61762) Intermittent Socket closed error
Title: Message Title Shivaji Thanneeru updated an issue Jenkins / JENKINS-61762 Intermittent Socket closed error Change By: Shivaji Thanneeru Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205599.1585716788000.4409.1585759380247%40Atlassian.JIRA.
[JIRA] (JENKINS-61732) additional refspecs at the organisational level is unworkable
Title: Message Title Brian J Murrell commented on JENKINS-61732 Re: additional refspecs at the organisational level is unworkable Fair enough. How can one find out what the parameters to the default checkout are being used? IOW, if I wanted to start with replicating exactly what the default checkout does and then alter it to my needs, how would I know what that default checkout looks like? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205560.1585492427000.4411.1585759500130%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Gábor Tasnádi updated an issue Jenkins / JENKINS-61480 Dark Theme Change By: Gábor Tasnádi Attachment: dark.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205164.1584202104000.4414.1585759800164%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Gábor Tasnádi commented on JENKINS-61480 Re: Dark Theme So I'm working it and thought it would be nice for it to be compatible with whoever wants his plugin to be compatible with it. I made a regex that can find css colors in a file and replace it with another color like this: How I imagined it would get all css files that being rendered on a page, search it in the static resources, make a copy with substituted colors and re-link them in the header. But now I got kinda stuck on how could it get all css links on a currently rendered page, first thought was I should get the StaplerResponse and crawl it from the html response, but it doesn't have a body. Any suggestions guys? Oleg Nenashev, Félix Queiruga Balado By the way, the current design looks like this Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205164.1584202104000.4417.1585760160176%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Gábor Tasnádi updated an issue Jenkins / JENKINS-61480 Dark Theme Change By: Gábor Tasnádi Comment: So I'm working it and thought it would be nice for it to be compatible with whoever wants his plugin to be compatible with it. I made a regex that can find css colors in a file and replace it with another color like this:!dark.png|width=604,height=450!How I imagined it would get all css files that being rendered on a page, search it in the static resources, make a copy with substituted colors and re-link them in the header. But now I got kinda stuck on how could it get all css links on a currently rendered page, first thought was I should get the StaplerResponse and crawl it from the html response, but it doesn't have a body. Any suggestions guys? [~oleg_nenashev], [~fqueiruga]By the way, the current design looks like this!dark.png|width=981,height=484! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Gábor Tasnádi updated an issue Jenkins / JENKINS-61480 Dark Theme Change By: Gábor Tasnádi Attachment: regex.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205164.1584202104000.4421.1585760220535%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Gábor Tasnádi commented on JENKINS-61480 Re: Dark Theme So I'm working it and thought it would be nice for it to be compatible with whoever wants his plugin to be compatible with it. I made a regex that can find css colors in a file and replace it with another color like this: How I imagined it would get all css files that being rendered on a page, search it in the static resources, make a copy with substituted colors and re-link them in the header. But now I got kinda stuck on how could it get all css links on a currently rendered page, first thought was I should get the StaplerResponse and crawl it from the html response, but it doesn't have a body. Any suggestions guys? Oleg Nenashev, Félix Queiruga Balado By the way, the current design looks like this Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205164.1584202104000.4426.1585760280141%40Atlassian.JIRA.
[JIRA] (JENKINS-61601) Unable to trigger job on deletion of branch when configured with job DSL.
Title: Message Title Levi Blaney updated an issue Jenkins / JENKINS-61601 Unable to trigger job on deletion of branch when configured with job DSL. Change By: Levi Blaney Attachment: image-2020-04-01-22-32-50-050.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205299.1584706587000.4429.1585760580185%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Gábor Tasnádi updated an issue Jenkins / JENKINS-61480 Dark Theme Change By: Gábor Tasnádi Attachment: dark.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205164.1584202104000.4432.1585760820173%40Atlassian.JIRA.
[JIRA] (JENKINS-61601) Unable to trigger job on deletion of branch when configured with job DSL.
Title: Message Title Levi Blaney commented on JENKINS-61601 Re: Unable to trigger job on deletion of branch when configured with job DSL. Aytunc BEKEN, Thanks for patching that so quickly. The error is now gone from the logs but still we don't see the job being triggered. The logs now have a warning. 2020-04-01 16:48:28.803+ [id=6070] WARNING o.j.p.w.m.PipelineTriggerProperty#triggerActionJobs: [MultiBranch Action Triggers Plugin] feat%2Ffusionpub_timeout not included by the Include Filter 2020-04-01 16:48:28.804+ [id=6070] WARNING o.j.p.w.m.PipelineTriggerProperty#triggerActionJobs: [MultiBranch Action Triggers Plugin] feat%2Ffusionpub_timeout not included by the Include Filter 2020-04-01 16:48:28.804+ [id=6070] WARNING o.j.p.w.m.PipelineTriggerProperty#triggerActionJobs: [MultiBranch Action Triggers Plugin] feat%2Ffusionpub_timeout not included by the Include Filter 2020-04-01 16:48:28.804+ [id=6070] WARNING o.j.p.w.m.PipelineTriggerProperty#triggerActionJobs: [MultiBranch Action Triggers Plugin] feat%2Ffusionpub_timeout not included by the Include Filter 2020-04-01 16:48:28.812+ [id=6098] INFOj.b.WorkspaceLocatorImpl$Deleter$CleanupTask#run: deleting obsolete workspace /var/jenkins_home/workspace/y-Feature_feat_fusionpub_timeout@libs on master As you can see in my co-workers post we don't specify an include filter in the DSL, but it is in the Jenkins GUI. Maybe defaulted somehow? It should catch everything? Our branches are prefixed with fix/ and feat/ which the multiple pipeline job URL encodes it? Is that messing up the filter? I could try specifying the include filter in the DSL if you think that would help? This setup used to work but did break sometime around December? We felt we did something so didn't report the issue. We really enjoy the plugin, it's what makes the multipipeline job usable for us. Thanks Add Comment
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick commented on JENKINS-51143 Re: List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Since I do not much trust the mock-based tests in this plugin, here is my interactive verification: Run 2.222.1, setup wizard to get admin user but skipping plugin installation. From Available, install view-job-filters (from UC: 2.1.1), workflow-basic-steps, workflow-cps, workflow-job. Create an enabled freestyle project, a disabled one, an enabled Pipeline project, and a disabled one. (Otherwise empty—no need for build steps or any builds.) Create a custom list view using the core Status Filter of Disabled jobs only, selecting also Use a regular _expression_ to include jobs into the view with .+; and another with Enabled jobs only. These views correctly show the disabled or enabled freestyle and Pipeline projects, respectively. Create a custom list view using the plugin-provided Job Statuses Filter with Disabled checked and Include Matched - Add jobs that match this filter; and another with Include Unmatched - Add jobs that don't match this filter. Note that the former includes the disabled freestyle project yet omits the disabled Pipeline project, while the latter omits the disabled freestyle project yet includes the disabled Pipeline project, reproducing the bug. Build view-job-filter.hpi from #18, install via Plugin Manager » Advanced, restart. Now running 2.2-SNAPSHOT. See that the plugin-based views now correctly handle the disabled Pipeline project, matching the behavior of the core-based views. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick updated JENKINS-51143 Jenkins / JENKINS-51143 List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.190437.1525450293000.4446.1585761300616%40Atlassian.JIRA.
[JIRA] (JENKINS-61732) additional refspecs at the organisational level is unworkable
Title: Message Title Mark Waite commented on JENKINS-61732 Re: additional refspecs at the organisational level is unworkable Brian J Murrell There are several sample jobs like this one, this one, and this one which show techniques like echoing the values of parts of the scm object to see them. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205560.1585492427000.4455.1585761480366%40Atlassian.JIRA.
[JIRA] (JENKINS-24319) Windows slave dying during build - unsatisfied link error
Title: Message Title P4 commented on JENKINS-24319 Re: Windows slave dying during build - unsatisfied link error Let me have a moment. It looks like we have issues with L1 of the networking. Just replaced the cat6 cable and connected to the other outlet. Hope it is about that and not Jenkins itself. I am sorry about the confusion. Will report back in case of further issues. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.156838.1408446495000.4458.1585761480411%40Atlassian.JIRA.
[JIRA] (JENKINS-61601) Unable to trigger job on deletion of branch when configured with job DSL.
Title: Message Title
Levi Blaney edited a comment on JENKINS-61601
Re: Unable to trigger job on deletion of branch when configured with job DSL.
[~aytuncbeken],Thanks for patching that so quickly. The error is now gone from the logs but still we don't see the job being triggered. The logs now have a warning. {code:java}2020-04-01 16:48:28.803+ [id=6070] WARNING o.j.p.w.m.PipelineTriggerProperty#triggerActionJobs: [MultiBranch Action Triggers Plugin] feat%2Ffusionpub_timeout not included by the Include Filter2020-04-01 16:48:28.804+ [id=6070] WARNING o.j.p.w.m.PipelineTriggerProperty#triggerActionJobs: [MultiBranch Action Triggers Plugin] feat%2Ffusionpub_timeout not included by the Include Filter2020-04-01 16:48:28.804+ [id=6070] WARNING o.j.p.w.m.PipelineTriggerProperty#triggerActionJobs: [MultiBranch Action Triggers Plugin] feat%2Ffusionpub_timeout not included by the Include Filter2020-04-01 16:48:28.804+ [id=6070] WARNING o.j.p.w.m.PipelineTriggerProperty#triggerActionJobs: [MultiBranch Action Triggers Plugin] feat%2Ffusionpub_timeout not included by the Include Filter2020-04-01 16:48:28.812+ [id=6098] INFOj.b.WorkspaceLocatorImpl$Deleter$CleanupTask#run: deleting obsolete workspace /var/jenkins_home/workspace/y-Feature_feat_fusionpub_timeout@libs on master{code} As you can see in my co-workers post we don't specify an include filter in the DSL, but it is in the Jenkins GUI. Maybe defaulted somehow?!image-2020-04-01-22-32-50-050.png|width=706,height=217!It should catch everything? Our branches are prefixed with fix/ and feat/ which the multiple pipeline job URL encodes it? Is that messing up the filter? I could try specifying the include filter in the DSL if you think that would help? This setup used to work but did break sometime around December? We felt we did something so didn't report the issue. We really enjoy the plugin, it's what makes the multipipeline job usable for us. Thanks EDIT: Just noticed our job XML is missing the * even though the GUI shows it? Let me add it to DSL.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61767) Seeing 504 Gateway timeout after updating to LTS version
Title: Message Title Ivan Fernandez Calvo closed an issue as Incomplete Jenkins / JENKINS-61767 Seeing 504 Gateway timeout after updating to LTS version Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205604.1585750575000.4468.1585761600222%40Atlassian.JIRA.
[JIRA] (JENKINS-56813) Job filter: exclude disabled jobs does not work
Title: Message Title Jesse Glick resolved as Not A Defect To create a view showing all enabled jobs, add a Job Statuses Filter with Disabled checked and select Include Unmatched - Add jobs that don't match this filter. Do not select jobs or check the regular _expression_ filter option. Or you can use the core built-in filter without using this plugin. See JENKINS-51143 for a fuller explanation. Using a GUI to define a boolean predicate is not great, and the particular way this is handled in Jenkins list views is especially confusing. Jenkins / JENKINS-56813 Job filter: exclude disabled jobs does not work Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-58801) Enable filter View by type "Folder"
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58801 Enable filter View by type "Folder" Change By: Jesse Glick Component/s: cloudbees-folder-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.20.1564983968000.4474.1585762020186%40Atlassian.JIRA.
[JIRA] (JENKINS-58801) Enable filter View by type "Folder"
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58801 Enable filter View by type "Folder" Change By: Jesse Glick Labels: folders Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.20.1564983968000.4477.1585762080188%40Atlassian.JIRA.
[JIRA] (JENKINS-30182) view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column
Title: Message Title
Jesse Glick updated JENKINS-30182
Not sure about the rest, but the {{java.lang.ClassCastException: hudson.views.BuildFilterColumn$JobWrapper cannot be cast to hudson.model.TopLevelItem at jenkins.model.Jenkins.getRootDirFor(Jenkins.java:306)}} should have been fixed by PR 17 (was causing a test failures when updating the Jenkins baseline).
Jenkins / JENKINS-30182
view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column
Change By:
Jesse Glick
Status:
Open Fixed but Unreleased
Assignee:
Jacob Robertson Jesse Glick
Resolution:
Fixed
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61601) Unable to trigger job on deletion of branch when configured with job DSL.
Title: Message Title Levi Blaney commented on JENKINS-61601 Re: Unable to trigger job on deletion of branch when configured with job DSL. Adding the include filter to our JobDSL did put it in the config.xml and the plugin is now working perfectly Aytunc BEKEN, I will ping Neha Singh and have her close this issue =) Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205299.1584706587000.4489.1585762260214%40Atlassian.JIRA.
[JIRA] (JENKINS-61732) additional refspecs at the organisational level is unworkable
Title: Message Title
Mark Waite edited a comment on JENKINS-61732
Re: additional refspecs at the organisational level is unworkable
[~brianjmurrell] There are several sample jobs like [this one|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-42860/Jenkinsfile], [this one|https://github.com/MarkEWaite/jenkins-bugs/blob/master/Jenkinsfile], and [this one|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-52844/Jenkinsfile] which show techniques like echoing the values of parts of the scm object to see them. Since the default checkout settings are defined in the multibranch pipeline job itself, the {{scm}} object is the best way to find them. Many of my multibranch pipeline jobs define a reference repository and declare that the checkout should honor the refsepec in checkout. Others do not.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.205560.1585492427000.4486.1585762260169%40Atlassian.JIRA.
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick updated JENKINS-51143 Jenkins / JENKINS-51143 List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.2 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.190437.1525450293000.4498.1585762381096%40Atlassian.JIRA.
[JIRA] (JENKINS-30182) view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30182 view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column Change By: Jesse Glick Released As: 2.2 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.164765.1440703818000.4500.1585762381140%40Atlassian.JIRA.
[JIRA] (JENKINS-61732) additional refspecs at the organisational level is unworkable
Title: Message Title Brian J Murrell commented on JENKINS-61732 Re: additional refspecs at the organisational level is unworkable OK. So then, is using a "bare" checkout command effectively do the same thing as not specifying skipDefaultCheckout? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205560.1585492427000.4508.1585763160116%40Atlassian.JIRA.
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick updated JENKINS-51143 Jenkins / JENKINS-51143 List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Change By: Jesse Glick Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.190437.1525450293000.4516.1585763401206%40Atlassian.JIRA.
[JIRA] (JENKINS-30182) view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column
Title: Message Title Jesse Glick updated JENKINS-30182 Jenkins / JENKINS-30182 view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column Change By: Jesse Glick Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.164765.1440703818000.4514.1585763401118%40Atlassian.JIRA.
[JIRA] (JENKINS-61732) additional refspecs at the organisational level is unworkable
Title: Message Title
Mark Waite commented on JENKINS-61732
Re: additional refspecs at the organisational level is unworkable
A declarative pipeline with skipDefaultCheckout} and the first step as {{checkout scm is the same as not declaring skipDefaultCheckout and not specifying checkout scm as the first step.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.205560.1585492427000.4525.1585763460185%40Atlassian.JIRA.
[JIRA] (JENKINS-61732) additional refspecs at the organisational level is unworkable
Title: Message Title
Mark Waite edited a comment on JENKINS-61732
Re: additional refspecs at the organisational level is unworkable
A declarative pipeline with {{skipDefaultCheckout} } and the first step as {{checkout scm}} is the same as not declaring {{skipDefaultCheckout}} and not specifying {{checkout scm}} as the first step.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.205560.1585492427000.4527.1585763460213%40Atlassian.JIRA.
[JIRA] (JENKINS-61770) Directive-Generator Omits "Extensible Choice" Parameter
Title: Message Title Tim Black created an issue Jenkins / JENKINS-61770 Directive-Generator Omits "Extensible Choice" Parameter Issue Type: Improvement Assignee: Unassigned Components: extensible-choice-parameter-plugin Created: 2020-04-01 18:10 Environment: Jenkins ver. 2.190.3 Extensible Choice 1.6.0 Extended Choice 0.78 Priority: Major Reporter: Tim Black Directive-Generator on my Jenkins instance includes "Extended Choice" and other param types just fine, but does not include "Extensible Choice" Parameter type. Is this a documentation omission, or does Extensible Choice not support pipeline (declarative)? If it doesn't support declarative pipeline and this is the reason it's not in directive generator, I would like to see a reference to the scripted pipeline syntax somewhere in the documentation. Add Comment
[JIRA] (JENKINS-61768) plugin bundles slf4j-api causing no test output for plugins that depend on it.
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61768 plugin bundles slf4j-api causing no test output for plugins that depend on it. Change By: Ulli Hafner Component/s: analysis-model Component/s: analysis-model-api-plugin URL: https://github.com/jenkinsci/analysis-model/pull/336 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205605.1585754769000.4548.1585764960114%40Atlassian.JIRA.
[JIRA] (JENKINS-61768) plugin bundles slf4j-api causing no test output for plugins that depend on it.
Title: Message Title Ulli Hafner updated JENKINS-61768 I noticed that as well a couple of days ago. In https://github.com/jenkinsci/analysis-model/pull/336 I removed the transitive dependency to SLF4J 1.8. Jenkins / JENKINS-61768 plugin bundles slf4j-api causing no test output for plugins that depend on it. Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop re
[JIRA] (JENKINS-61762) Intermittent Socket closed or Read timed out error
Title: Message Title Shivaji Thanneeru updated an issue Jenkins / JENKINS-61762 Intermittent Socket closed or Read timed out error Change By: Shivaji Thanneeru Summary: Intermittent Socket closed or Read timed out error Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205599.1585716788000.4552.1585765560235%40Atlassian.JIRA.
[JIRA] (JENKINS-61762) Intermittent Socket closed or Read timed out error
Title: Message Title
Shivaji Thanneeru updated an issue
Jenkins / JENKINS-61762
Intermittent Socket closed or Read timed out error
Change By:
Shivaji Thanneeru
jiraEditIssue, jiraNewIssue and jiraJqlSearch are some time failing with "Socket Closed" or "Read timed out" error. {code:java}JIRA: Site - JIRA-PROD - Updating issue: Ticket-1234Error Code: -1Error Message: Socket closed[Pipeline] }[Pipeline] // scriptError when executing always post condition:hudson.AbortException: Socket closed at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132) at org.thoughtslive.jenkins.plugins.jira.steps.EditIssueStep$Execution.run(EditIssueStep.java:80){code} {code:java}JIRA: Site - JIRA-PROD - Creating new issue: IssueInput(update=null, fields={project={key=REI}, summary=Build Error., description=New JIRA Created from Jenkins., issuetype={name=Bug}})Error Code: -1Error Message: Socket closed[Pipeline] }[Pipeline] // scriptError when executing regression post condition:hudson.AbortException: Socket closed at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132) at org.thoughtslive.jenkins.plugins.jira.steps.NewIssueStep$Execution.run(NewIssueStep.java:84) at org.thoughtslive.jenkins.plugins.jira.steps.NewIssueStep$Execution.run(NewIssueStep.java:53) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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){code} {code:java}JIRA: Site - JIRA-PROD - Search JQL: project = "Release Engineering Internal" AND description ~ "New JIRA Created from Jenkins" ORDER BY id DESC startAt: 0 maxResults: 1Error Code: -1Error Message: Read timed out[Pipeline] }[Pipeline] // scriptError when executing failure post condition:hudson.AbortException: Read timed out at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132) at org.thoughtslive.jenkins.plugins.jira.steps.JqlSearchStep$Execution.run(JqlSearchStep.java:89) at org.thoughtslive.jenkins.plugins.jira.steps.JqlSearchStep$Execution.run(JqlSearchStep.java:65) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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){code}
[JIRA] (JENKINS-61769) git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches
Title: Message Title Boguslaw Klimas commented on JENKINS-61769 Re: git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches Hi, Are you try used 'use-repository' option? https://github.com/jenkinsci/git-parameter-plugin#use-repository Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205606.1585757549000.4556.1585766220213%40Atlassian.JIRA.
[JIRA] (JENKINS-57500) Update outdated dependencies
Title: Message Title Radek Antoniuk closed an issue as Fixed Jenkins / JENKINS-57500 Update outdated dependencies Change By: Radek Antoniuk Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.199363.1557993399000.4578.1585767780267%40Atlassian.JIRA.
[JIRA] (JENKINS-61661) Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided
Title: Message Title Radek Antoniuk commented on JENKINS-61661 Re: Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided Andreas Nusser indeed that makes sense, would you like to give it a shot and contribute with a Pull Request to add a logger? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205393.1585048689000.4580.1585768020117%40Atlassian.JIRA.
[JIRA] (JENKINS-61361) Replace "accountId" workaround when jira-rest-java-client is updated
Title: Message Title Radek Antoniuk commented on JENKINS-61361 Re: Replace "accountId" workaround when jira-rest-java-client is updated Stefan Cordes would you mind creating a Pull Request for this so that it just sits and waits for the needed dependencies? that would be really helpful, thank you! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205013.1583485957000.4582.1585768080131%40Atlassian.JIRA.
[JIRA] (JENKINS-61244) Jira issue: getting error while assigning issue to a assginee
Title: Message Title Radek Antoniuk updated JENKINS-61244 No version information was provided, so I'm assuming this was fixed in 3.0.12. https://github.com/jenkinsci/jira-plugin/releases/tag/3.0.12 Jenkins / JENKINS-61244 Jira issue: getting error while assigning issue to a assginee Change By: Radek Antoniuk Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving e
[JIRA] (JENKINS-61244) Jira issue: getting error while assigning issue to a assginee
Title: Message Title Radek Antoniuk updated JENKINS-61244 Jenkins / JENKINS-61244 Jira issue: getting error while assigning issue to a assginee Change By: Radek Antoniuk Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.204810.1582747506000.4587.1585768320571%40Atlassian.JIRA.
[JIRA] (JENKINS-57619) Unable to find valid certification path
Title: Message Title Radek Antoniuk updated JENKINS-57619 Jenkins / JENKINS-57619 Unable to find valid certification path Change By: Radek Antoniuk Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.199547.1558546618000.4590.1585768500332%40Atlassian.JIRA.
[JIRA] (JENKINS-57619) Unable to find valid certification path
Title: Message Title Radek Antoniuk updated JENKINS-57619 Jenkins / JENKINS-57619 Unable to find valid certification path Change By: Radek Antoniuk Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.199547.1558546618000.4592.1585768500372%40Atlassian.JIRA.
[JIRA] (JENKINS-57004) Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED
Title: Message Title Radek Antoniuk commented on JENKINS-57004 Re: Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED Alexey Grigorov in 3.0.12 there were quite big changes to the Java Client used, can you give it a shot with the current version? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.198705.1555286407000.4594.1585768560118%40Atlassian.JIRA.
[JIRA] (JENKINS-54486) Not created JIRA issue after build failed
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce Jenkins / JENKINS-54486 Not created JIRA issue after build failed Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.195256.1541502017000.4600.1585768621688%40Atlassian.JIRA.
[JIRA] (JENKINS-56417) Jenkins cannot release Jira version 'No content to map to Object due to end of input'
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce Jenkins / JENKINS-56417 Jenkins cannot release Jira version 'No content to map to Object due to end of input' Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.198008.1551797348000.4596.1585768621577%40Atlassian.JIRA.
[JIRA] (JENKINS-55982) JIRA Plugin does not respect proxy in some requests
Title: Message Title Radek Antoniuk closed an issue as Incomplete Reporter timeout. Jenkins / JENKINS-55982 JIRA Plugin does not respect proxy in some requests Change By: Radek Antoniuk Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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
[JIRA] (JENKINS-48876) Inprogress Stories from current sprint when closed in future sprint. Will the story points be credited to sprint where stories were burned or into the original sprint where it w
Title: Message Title Radek Antoniuk closed an issue as Not A Defect Jenkins / JENKINS-48876 Inprogress Stories from current sprint when closed in future sprint. Will the story points be credited to sprint where stories were burned or into the original sprint where it was created Change By: Radek Antoniuk Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.187671.1515582347000.4605.1585768680404%40Atlassian.JIRA.
[JIRA] (JENKINS-48878) if user is deleted what happens for the issues
Title: Message Title Radek Antoniuk closed an issue as Not A Defect Jenkins / JENKINS-48878 if user is deleted what happens for the issues Change By: Radek Antoniuk Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.187673.1515582421000.4603.1585768680361%40Atlassian.JIRA.
[JIRA] (JENKINS-46695) NullPointer Exception and possible downstream pipeline issue
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce Jenkins / JENKINS-46695 NullPointer Exception and possible downstream pipeline issue Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.185038.1504736204000.4607.1585768740177%40Atlassian.JIRA.
[JIRA] (JENKINS-48609) Unable to query JIRA
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce Jenkins / JENKINS-48609 Unable to query JIRA Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.187257.1513615676000.4609.1585768800234%40Atlassian.JIRA.
