[JIRA] (JENKINS-57793) Creates addition empty connection cfg. after applying JCasC
Title: Message Title Nicolas De Loof commented on JENKINS-57793 Re: Creates addition empty connection cfg. after applying JCasC gitlab is supported and fully tested by JCasC plugin "integrations" module. see https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/integrations/src/test/resources/io/jenkins/plugins/casc/GitLabTest.yml please also tell us which version of gitlab plugin you're using. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199742.1559312157000.24809.1560236881560%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57334) "Run on planned host" from Build section not working
Title: Message Title Anda Sorina Laakso commented on JENKINS-57334 Re: "Run on planned host" from Build section not working HI, I attached for you a new version today on the ftp folder. Please run again the tests and send me by email the console logs. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199108.1557111748000.24811.1560237540271%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36002) Add $ErrorActionPreference = "Stop" to the top of each script before executing
Title: Message Title Raúl Salinas-Monteagudo commented on JENKINS-36002 Re: Add $ErrorActionPreference = "Stop" to the top of each script before executing This is a great idea, in most cases, you don't want scripts to go on when they encounter failures. I'd rather have false positive abortions than false negatives. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171951.1466067563000.24814.1560238800229%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57383) Issue when testing proxy
Title: Message Title E D commented on JENKINS-57383 Re: Issue when testing proxy I can confirm the error too! Jenkins Version: Jenkins ver. 2.176.1 java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.Integer at org.apache.commons.httpclient.HttpMethodDirector.applyConnectionParams(HttpMethodDirector.java:360) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:404) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:178) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:404) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:330) at hudson.ProxyConfiguration$DescriptorImpl.doValidateProxy(ProxyConfiguration.java:409) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To un
[JIRA] (JENKINS-57383) Issue when testing proxy
Title: Message Title E D updated an issue Jenkins / JENKINS-57383 Issue when testing proxy Change By: E D Environment: Jenkins ver. 2.176.1 Alpine Docker Image Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199165.1557396422000.24823.1560239640291%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57950) EC2 Plugin: NullPointerException on Generate Key
Title: Message Title
Yuki INOUE created an issue
Jenkins / JENKINS-57950
EC2 Plugin: NullPointerException on Generate Key
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2019-06-11 08:04
Environment:
Jenkins: ver. 2.180 OS: Amazon Linux release 2 (Karoo) Java: * openjdk version "1.8.0_201" * OpenJDK Runtime Environment (build 1.8.0_201-b09) * OpenJDK 64-Bit Server VM (build 25.201-b09, mixed mode) For the plugin, I installed AWS EC2 Plugin ( org.jenkins-ci.plugins:ec2:1.43 ).
Priority:
Minor
Reporter:
Yuki INOUE
Today I tried to start using Jenkins EC2 Plugin. To use this plugin, I understand I need to configure Amazon EC2 cloud from the System Configuration. In the configuration page ('/configure'), I selected "Cloud -> Add -> Amazon EC2". Then, configurations for EC2 shows up. Since I wanted to create a new ssh key and use it for the key pair for slaves, I clicked "Generate Key" button in EC2 Key Pair's Private Key field, and following ERROR occurred. ``` java.lang.NullPointerException at sun.invoke.util.ValueConversions.unboxBoolean(ValueConversions.java:103) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher yes. also tried: One possible workaround: Go the "Plugin Manager" "Advanced" tab. 2. Without any change press the "submit" button of the "HTTP Proxy Configuration". 3. Go to the "Updates" tab. 4. Press the "Check now" button. no success Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195909.1543385478000.24827.1560240660298%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau edited a comment on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher [~danielbeck] yes.also tried :One the one possible workaround: # Go the "Plugin Manager" "Advanced" tab.2. Without any change press the "submit" button of the "HTTP Proxy Configuration".3. Go to the "Updates" tab.4. Press the "Check now" button.no success Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195909.1543385478000.24838.1560240720810%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher weird thing is that: I can't check the udpates. But I can install new plugins: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195909.1543385478000.24860.1560240900856%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Mathieu Rousseau Attachment: image-2019-06-11-04-14-31-336.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195909.1543385478000.24858.1560240900835%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher hum. replaced https to http and worked. https://updates.jenkins-ci.org/update-center.json to http://updates.jenkins-ci.org/update-center.json Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195909.1543385478000.24871.1560241740288%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-57945 p4 sync corrupts symlinks Change By: Karl Wirth Assignee: Paul Allen Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199921.1560203497000.24883.1560242700295%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57945 p4 sync corrupts symlinks Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199921.1560203497000.24885.1560242700328%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Karl Wirth commented on JENKINS-57945 Re: p4 sync corrupts symlinks Hi Michael Rose - Thanks for letting us know. I will qualify this then get dev involved. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199921.1560203497000.24887.1560242820110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57435) Cannot configure SSH credentials via Job DSL
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-57435 Cannot configure SSH credentials via Job DSL Change By: Daniel Spilker Component/s: ssh-credentials-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199248.1557757091000.24889.1560242940159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57435) Cannot configure SSH credentials via Job DSL
Title: Message Title Daniel Spilker assigned an issue to Unassigned Jenkins / JENKINS-57435 Cannot configure SSH credentials via Job DSL Change By: Daniel Spilker Assignee: Daniel Spilker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199248.1557757091000.24892.1560243000559%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57951) Use JIRA plugin to maintain release notes
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57951 Use JIRA plugin to maintain release notes Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-11 08:52 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsub
[JIRA] (JENKINS-57303) Duplicate builds triggered from webhook (push) on branch pipelines
Title: Message Title Mads Navntoft Noe commented on JENKINS-57303 Re: Duplicate builds triggered from webhook (push) on branch pipelines Using the "(Deprecated )Suppress automatic SCM triggering" property strategy, new branches are not being built initially. Does anybody have an idea for a workaround for this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199071.1556792966000.24896.1560243300119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57952) ISSUE TO TEST MAIL FORWARDING RULES
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-57952 ISSUE TO TEST MAIL FORWARDING RULES Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2019-06-11 09:07 Priority: Trivial Reporter: Karl Wirth PLEASE IGNORE - This is a test of the mail forwarding. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57952) ISSUE TO TEST MAIL FORWARDING RULES
Title: Message Title Karl Wirth closed an issue as Not A Defect Jenkins / JENKINS-57952 ISSUE TO TEST MAIL FORWARDING RULES Change By: Karl Wirth Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199933.1560244058000.24924.1560244320363%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Daniel Beck commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher The canonical domain is now updates.jenkins.io, perhaps that works better? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195909.1543385478000.24926.1560244320421%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57953) Gitlab Merge Request Builder uses outdated Gitlab API
Title: Message Title holoadmin holoadmin created an issue Jenkins / JENKINS-57953 Gitlab Merge Request Builder uses outdated Gitlab API Issue Type: Bug Assignee: Unassigned Components: gitlab-merge-request-jenkins Created: 2019-06-11 09:30 Environment: Jenkins 2.176.1 Gitlab Merge Request Builder 2.0.0 Labels: plugin gitlab merge requests Priority: Blocker Reporter: holoadmin holoadmin As also mentioned on https://wiki.jenkins.io/display/JENKINS/Gitlab+Merge+Request+Builder+Plugin?focusedCommentId=143494428#comment-143494428 the Gitlab Merge Request Builder plug-In still uses the deprecated API v3. by now it should be v4 ! (https://docs.gitlab.com/ee/api/v3_to_v4.html) Therefor we get an error while trying to create a Job (and ofcourse it never runs since the connection doesn't work) java.io.FileNotFoundException: https://our.gitlab.installation/api/v3/projects → suggestion: change request URL from /api/v3/projects to /api/v4/projects Full stack trace java.io.FileNotFoundException: https://holo-git.holo.local/api/v3/projects at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source) at org.gitlab.api.http.GitlabHTTPRequestor.parse(GitlabHTTPRequestor.java:324) at org.gitlab.api.http.GitlabHTTPRequestor.access$
[JIRA] (JENKINS-57954) jiraTransitionIssue doesn't transition "sub-tickets"
Title: Message Title
Benzo Angel created an issue
Jenkins / JENKINS-57954
jiraTransitionIssue doesn't transition "sub-tickets"
Issue Type:
Bug
Assignee:
Naresh Rayapati
Components:
jira-steps-plugin
Created:
2019-06-11 09:35
Environment:
Jenkins ver. 2.150.1
Priority:
Critical
Reporter:
Benzo Angel
Jira Steps couldn't transition sub-tickets: [Pipeline] jiraTransitionIssue*14:12:24* JIRA: Site - CompanySite - Transition issue with idOrKey: XXX-420*14:12:26* Error Code: 404*14:12:26* Error Message: {"errorMessages":["Issue does not exist or you do not have permission to see it."],"errors":{}}[Pipeline] echo*14:12:26* hudson.AbortException: {"errorMessages":["Issue does not exist or you do not have permission to see it."],"errors":{}} NB: The sub-ticket exists. i could transition normal tickets without a problem. I used "curl" instead to make it working.
Add Comment
[JIRA] (JENKINS-57954) jiraTransitionIssue doesn't transition "sub-tickets"
Title: Message Title
Benzo Angel updated an issue
Jenkins / JENKINS-57954
jiraTransitionIssue doesn't transition "sub-tickets"
Change By:
Benzo Angel
Jira Steps couldn't transition sub-tickets:[Pipeline] jiraTransitionIssue*14:12:24* JIRA: Site - CompanySite - Transition issue with idOrKey: XXX-420*14:12:26* Error Code: 404*14:12:26* Error Message: \ {"errorMessages":["Issue does not exist or you do not have permission to see it."],"errors":{}}[Pipeline] echo*14:12:26* hudson.AbortException: \ {"errorMessages":["Issue does not exist or you do not have permission to see it."],"errors":{}}NB: {color:# FF ff }The sub-ticket exists. i could transition normal tickets without a problem any problems .{color}I used "curl" instead to make it working.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199935.1560245706000.24964.1560245820190%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-55945 Got IllegalStateException while restart Jenkins Change By: Daniel Beck Labels: regression Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.24966.1560246240573%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45228) Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command
Title: Message Title Geoffroy Jabouley commented on JENKINS-45228 Re: Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command Hello also facing this issue in some cases where files where modified/added into source branch of PR. Any idea when/if LFS credentials support will be added to the merge portion of the git plugin? Maybe at leat providing some implementation guidance for a future contribution BR Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183359.1498813755000.24984.1560246420425%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57905) Build Flow Job unable to save build
Title: Message Title Gopal Ahir commented on JENKINS-57905 Re: Build Flow Job unable to save build Hi Craig Rodrigues, Is there any update? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199870.1559894727000.25002.1560246600214%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) p4-plugin
Title: Message Title Kieron Kierzo created an issue Jenkins / JENKINS-57955 p4-plugin Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-06-11 10:06 Environment: Windows Host and Agent, Jenkins ver. 2.176.1 (Pipeline in SCM) Labels: windows Priority: Major Reporter: Kieron Kierzo I sync my client workspace in three environments Windows, Mac and Linux My step after syncing the workspace is to set up a symlink in each environment that points to a local third party dependencies folder used by the build. I'm not wishing to add my third party dependencies folder to source control as the folder is about 18GB and would vastly increase the sync time and unnecessary as this folder doesn't change. After adding the symlink and running the build, on the second run... the p4 plugin issues a force clean workspace before it syncs the workspace again. On Mac and Linux, the third party symlink is deleted and recreated each time... However on windows, instead of removing the link, it follows in to the link and deletes the contents of the dependencies folder, when all I am looking to to is unlink it. On windows the command I am using to create the link is: mklink /J "%WORKSPACE%\3rdparty" "C:\Jenkins\3rdparty" And on Mac and Linux its: ln -s /Jenkins/workspace/ 3rdparty I notice that the cleanup command is an "rm -rf" which I am guessing must be handled differently on the windows agent. it must be the recursive flag that's entering the folder. maybe whats needed is the ability to run a custom removal command. (This will also fix another issue with
[JIRA] (JENKINS-57955) p4-plugin
Title: Message Title Kieron Kierzo updated an issue Jenkins / JENKINS-57955 p4-plugin Change By: Kieron Kierzo URL: https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/client/ClientHelper.java#L478 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.25005.1560249600065%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56271) xUnit produce an empty report for NUnit3 type
Title: Message Title George Cimpoies commented on JENKINS-56271 Re: xUnit produce an empty report for NUnit3 type Nikolas Falco I think there's a small mistake, the fix is actually in version 2.3.2 according to the commits and not 2.3.2, right? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197843.155110973.25008.1560249720200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title
Karl Wirth commented on JENKINS-57945
Re: p4 sync corrupts symlinks
Michael Rose Thanks again. Problem reproduced. Reproduction steps: (1) mkdir linktest (2) cd linktest (3) echo Content > target.txt (4) ln -s target.txt link (5) p4 add * && p4 submit -d "Adding links" (6) Create a new pipeline job that maps the 'linktest' directory. For example:
pipeline {
agent { label 'master' }
stages {
stage("Repro") {
steps {
script {
// Try same sync with checkout and p4sync. Swap by commenting out command not being tested.
// p4sync charset: 'none', credential: 'Jenkins', populate: forceClean(have: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: false), source: depotSource('//depot/testlink/...')
checkout perforce(credential: 'Jenkins', populate: forceClean(have: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: false), workspace: manualSpec(charset: 'none', cleanup: false, name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}', pinHost: false, spec: clientSpec(allwrite: false, backup: true, changeView: '', clobber: true, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE', view: '//depot/testlink/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}/...')))
// List directory contents
sh 'ls -lR'
}
}
}
}
}
(7) When job runs with 'p4sync' the 'link' file is a plain text file containing the word 'target.txt':
-r--r--r-- 1 jenkins jenkins 20 Jun 11 10:27 link
When job runs with 'checkout' the file is a symlink:
lrwxrwxrwx 1 jenkins jenkins 20 Jun 11 10:33 link -> target.txt
Add Comment
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-57945 p4 sync corrupts symlinks Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199921.1560203497000.25015.1560250201872%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57945 p4 sync corrupts symlinks Change By: Karl Wirth Labels: P4_SUPPORT P4_A Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199921.1560203497000.25013.1560250201460%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) p4-plugin
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-57955 p4-plugin Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.25017.1560250980111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) p4-plugin
Title: Message Title Karl Wirth commented on JENKINS-57955 Re: p4-plugin Hi Kieron Kierzo - Thanks for reporting this. I'll check to see if creating a link instead of a junction changes the behavior. Do you need the force clean workspace? If not then the workaround may be to use a different sync option such as 'Sync Only': https://www.perforce.com/manuals/jenkins/Content/P4Jenkins/populate-sync-only.html?Highlight=%22Sync%20Only%22 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.25019.1560251280093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57713) Cloud agent provisioning errors due to Remoting behaviour change
Title: Message Title Oleg Nenashev commented on JENKINS-57713 Re: Cloud agent provisioning errors due to Remoting behaviour change The weekly revert was done in Jenkins 2.180. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199655.1559046575000.25024.1560252060651%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57759) Revert remoting bump to avoid regression
Title: Message Title Oleg Nenashev updated JENKINS-57759 It was done in Jenkins 2.180. Now Jeff Thompson has an action item to follow-up on the regression in JENKINS-57713 Jenkins / JENKINS-57759 Revert remoting bump to avoid regression Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.180 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199705.1559205665000.25021.
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Oleg Nenashev updated JENKINS-57121 The change was released in Jenkins 2.180. The change introduces new binary API, so it is not backportable Jenkins / JENKINS-57121 list view jobnames is missing getter and setter for jcasc compliance Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.180 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198871.1
[JIRA] (JENKINS-57956) Cancel outdated jobs not working properly with multiple jobs ont the same pull request
Title: Message Title Bartlomiej Poleszak created an issue Jenkins / JENKINS-57956 Cancel outdated jobs not working properly with multiple jobs ont the same pull request Issue Type: Bug Assignee: Jakub Bochenski Components: stash-pullrequest-builder-plugin Created: 2019-06-11 11:34 Environment: Jenkins ver. 2.180 stash-pullrequest-builder-plugin 1.9 Priority: Minor Reporter: Bartlomiej Poleszak The bug (with pull request which resolves it) has been posted some time ago in the old repo issue page: https://github.com/nemccarthy/stash-pullrequest-builder-plugin/issues/121 Issue description by jordijansen: Hi, I'm having a issue using the "Cancel outdated jobs" option. I'm having two job definitions that built the same repository (so they get triggered on the same Pull Requests, however they do two completly different things). When I have the option "Cancel outdated jobs" activated it will also cancel the jobs of the other job definition. For example: Lets say I have have jobs A and B. I create a PullRequest, Job A is added to the queue. A little while later Job B is added to the queue because it triggers on the same repository/pull request. Job B cancels Job A because the Cancel outdated jobs option is activated. I think it should only cancel the Jobs that are of the same definition (Job A may only cancel jobs of Job A type).
[JIRA] (JENKINS-57957) Jenkins crashes when sending an email
Title: Message Title Rohan Keskar created an issue Jenkins / JENKINS-57957 Jenkins crashes when sending an email Issue Type: Bug Assignee: David van Laatum Attachments: Jenkins_error.JPG Components: email-ext-plugin, email-ext-recipients-column-plugin, emailext-template-plugin, notification-plugin Created: 2019-06-11 11:38 Environment: AWS EC2- Ubuntu 16.04.5 LTS 64bit Java - JDK-8 Jenkins ver. 2.164.3 Labels: plugin email Priority: Blocker Reporter: Rohan Keskar Jenkins fails to send an email when the user selects the 'Send Mail' option from the Project's menu. Jenkins is redirected to the bug page and hence crashes after sending the mail. Steps to Reproduce- 1)Install email plugins and notif plugins. 2)Create a project and build it 3)After building open the project dashboard. 4)Select the 'Send Mail' option from the Left Menu. 5)Enter the sender and recipient details. 6)Click on "Send Mail" Stack trace java.lang.NoSuchMethodError: hudson.plugins.emailext.ExtendedEmailPublisherDescriptor.createSession()Ljavax/mail/Session; at org.jenkinsci.plugins.jobmail.actions.JobMailProjectAction.createMimeMessage(JobMailProjectAction.java:352) at org.jenkinsci.plugins.jobmail.actions.JobMailProjectAction.createMessage(JobMailProjectAction.java:287) at org.jenkinsci.plugins.jobmail.actions.JobMailProjectAction.sendMail(JobMailProjectAction.java:260) at org.jenkins
[JIRA] (JENKINS-57928) Add JCasc support to JMH benchmarks
Title: Message Title Abhyudaya Sharma started work on JENKINS-57928 Change By: Abhyudaya Sharma Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199902.1560142004000.25037.1560254040274%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57958) Add changelog for 2.176.1 LTS release
Title: Message Title Harald Albers created an issue Jenkins / JENKINS-57958 Add changelog for 2.176.1 LTS release Issue Type: Task Assignee: Unassigned Components: _unsorted Created: 2019-06-11 12:20 Priority: Minor Reporter: Harald Albers Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199939.1560255613000.25038.1560255660192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57893) Mask Kubernetes secrets bound to containers in build log
Title: Message Title Jesse Glick updated JENKINS-57893 Jenkins / JENKINS-57893 Mask Kubernetes secrets bound to containers in build log Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199857.1559845148000.25039.1560255900189%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54008) Loading library fails - Error fetching remote repo 'origin'
Title: Message Title
Ilguiz Latypov commented on JENKINS-54008
Re: Loading library fails - Error fetching remote repo 'origin'
Ah sorry I targeted a wrong bug. I thought it was related to my frustration with the git plugin showing a "fatal: Could not read from remote repository" error. I think if the git plugin could add this trace message before invoking git,
echo "Checking out branch ${branch} with credentials ${credentialsId} from ${url} ..."
dozens of devops would be happier.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194621.1539241642000.25044.1560256620561%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54008) Loading library fails - Error fetching remote repo 'origin'
Title: Message Title
Ilguiz Latypov edited a comment on JENKINS-54008
Re: Loading library fails - Error fetching remote repo 'origin'
Ah sorry I targeted a wrong bug. I thought it was related to my frustration with the git plugin showing a "fatal: Could not read from remote repository" error. I think if the git plugin could add this trace message before invoking git,{noformat}echo "Checking out branch ${branch} with credentials ${credentialsId} from ${url} ..."{noformat}dozens of devops would be happier. Mu problem resolved when I saw that I was using a wrong credential, which did not agree with the error message.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194621.1539241642000.25046.1560256620584%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28942) Allow plugins to declare that they do not use certain implied dependencies
Title: Message Title Jesse Glick commented on JENKINS-28942 Re: Allow plugins to declare that they do not use certain implied dependencies form-element-path #8 is an example of where this would be helpful. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163400.1434531203000.25092.1560258420181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54008) Loading library fails - Error fetching remote repo 'origin'
Title: Message Title
Ilguiz Latypov edited a comment on JENKINS-54008
Re: Loading library fails - Error fetching remote repo 'origin'
Ah sorry I targeted a wrong bug. I thought it was related to my frustration with the git plugin showing a " an error implying connectivity issues,{noformat} fatal: Could not read from remote repository " error. {noformat} I think if the git plugin could add this trace message before invoking git,{noformat}echo "Checking out branch ${branch} with credentials ${credentialsId} from ${url} ..."{noformat}dozens of devops would be happier. Mu My problem resolved when I saw that I was using a wrong credential, which did not agree with the error message.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194621.1539241642000.25121.1560259320171%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54008) Loading library fails - Error fetching remote repo 'origin'
Title: Message Title
Ilguiz Latypov edited a comment on JENKINS-54008
Re: Loading library fails - Error fetching remote repo 'origin'
Ah sorry I targeted a wrong bug. I thought it was related to my frustration with the git plugin showing an error implying connectivity issues, {noformat}fatal: Could not read from remote repository{noformat} I think if the git plugin could add this trace message before invoking git, {noformat}echo "Checking out branch ${branch} with credentials ${credentialsId} from ${url} ..."{noformat} dozens of devops would be happier.My problem resolved when I saw that I was using a wrong credential, which did not agree with the error message. Oh and whoever suggested to try a bare {{git@git../repo.git}} URL on StackOverflow: this ignored the port number after the host name (we use a TCP port for reasons unknown). The proper {{ssh://HOST:PORT/REPO.git}} URL worked.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194621.1539241642000.25135.1560259441199%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Charusheela Bopardikar commented on JENKINS-56248 Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false) Tested pull request https://github.com/jenkinsci/p4-plugin/pull/95 and looks to be working fine with Jenkins version 2.164.3. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197815.1550844551000.25133.1560259440979%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Jesse Glick commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data There was an ATH regression which it is hoped form-element-path #8 will help correct. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.25116.1560259080173%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57668) Extend K8s plugin's Cloud API to launch Kafka agents
Title: Message Title Long Nguyen started work on JENKINS-57668 Change By: Long Nguyen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199601.1558718371000.25141.1560260700119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57959) Upgrade past args4j 2.32
Title: Message Title Basil Crow started work on JENKINS-57959 Change By: Basil Crow Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199940.1560260408000.25140.1560260460181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57959) Upgrade past args4j 2.32
Title: Message Title Basil Crow created an issue Jenkins / JENKINS-57959 Upgrade past args4j 2.32 Issue Type: Task Assignee: Basil Crow Components: core, remoting Created: 2019-06-11 13:40 Priority: Minor Reporter: Basil Crow Problem After an attempted upgrade of args4j in jenkinsci/swarm-plugin#120, the following exception was thrown: java.lang.IllegalStateException: Cannot set value to a final field 'hudson.remoting.jnlp.Main.urls'. at org.kohsuke.args4j.spi.Setters.create(Setters.java:32) at org.kohsuke.args4j.ClassParser.parse(ClassParser.java:34) at org.kohsuke.args4j.CmdLineParser.(CmdLineParser.java:96) at org.kohsuke.args4j.CmdLineParser.(CmdLineParser.java:71) at hudson.remoting.jnlp.Main._main(Main.java:215) at hudson.remoting.jnlp.Main.main(Main.java:188) at hudson.plugins.swarm.SwarmClient.connect(SwarmClient.java:325) at hudson.plugins.swarm.Client.run(Client.java:193) at hudson.plugins.swarm.Client.main(Client.java:130) Evaluation As of args4j 2.32, "final fields can no longer be set." If an args4j field is marked with the final keyword, an IllegalStateException is thrown. Solution Remove the final keyword from the fields that we expect args4j to set. Phase 1 Implemented in jenkinsci/remoting#326. See the PR for testing done. Phase 2 Once this change is merged and released, we can proceed with updating args4j in Jenkins core, which also involves updating the args4j dependency in Remoting. I'm explicitly postponing that work to a future PR, since at the present time Jenkins core is not using the latest version of Remoting due to a Remoting bug (see jenkinsci/jenkins#4047).
[JIRA] (JENKINS-57960) Add depends-on to wait for healthchecks to finish
Title: Message Title Janosch Deurer created an issue Jenkins / JENKINS-57960 Add depends-on to wait for healthchecks to finish Issue Type: Improvement Assignee: Unassigned Components: docker-workflow-plugin Created: 2019-06-11 13:55 Labels: docker Priority: Minor Reporter: Janosch Deurer It would be really helpful to have a syntax to wait for docker health-checks of a specific container to finish before continuing. This could be similar to the depends-on syntax of docker-compose. Right now this has to be implemented by hand in the Jenkinsfile. Add Comment
[JIRA] (JENKINS-57896) Launching Zookeeper and Kafka in K8s Function
Title: Message Title Long Nguyen updated JENKINS-57896 Jenkins / JENKINS-57896 Launching Zookeeper and Kafka in K8s Function Change By: Long Nguyen Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199860.1559851236000.25143.1560262260136%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-171) Error cloning remote repo 'origin'
Title: Message Title louis Catarino created an issue test / TEST-171 Error cloning remote repo 'origin' Issue Type: Bug Assignee: Unassigned Attachments: Annotation 2019-06-11 161319.png Components: foo Created: 2019-06-11 14:16 Priority: Blocker Reporter: louis Catarino Hello , i'm new on this forum escuse me in advance if i apply to the wrong place i am currently learning jenkins , and to create my build job i have an error message that i can not fix could you help me please Thanks Add Comment
[JIRA] (JENKINS-57957) Jenkins crashes when user sends an email
Title: Message Title Rohan Keskar updated an issue Jenkins / JENKINS-57957 Jenkins crashes when user sends an email Change By: Rohan Keskar Summary: Jenkins crashes when sending user sends an email Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199938.1560253115000.25147.1560263400502%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57957) Jenkins crashes when user tries to send an email
Title: Message Title Rohan Keskar updated an issue Jenkins / JENKINS-57957 Jenkins crashes when user tries to send an email Change By: Rohan Keskar Summary: Jenkins crashes when user sends tries to send an email Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199938.1560253115000.25149.1560263520230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-171) Error cloning remote repo 'origin'
Title: Message Title louis Catarino closed an issue as Fixed test / TEST-171 Error cloning remote repo 'origin' Change By: louis Catarino Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199943.1560262569000.25150.1560263580095%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57961) Add ability to set nvm version for complete pipeline either in options or environment
Title: Message Title sivanarayana baisani created an issue Jenkins / JENKINS-57961 Add ability to set nvm version for complete pipeline either in options or environment Issue Type: New Feature Assignee: Tomas Salazar Components: nvm-wrapper-plugin Created: 2019-06-11 14:33 Labels: plugin Priority: Major Reporter: sivanarayana baisani Its very difficult to give the .nvm version for a pipeline that have multiple stages where the nvm version is to be defined. So it would be good if we have an option to set the version for complete pipeline Add Comment
[JIRA] (JENKINS-49183) Retry in Declarative options passes stage but causes false fail in pipeline
Title: Message Title
Devin Nusbaum commented on JENKINS-49183
Re: Retry in Declarative options passes stage but causes false fail in pipeline
I think this is a dupe of JENKINS-46354, which was fixed in Pipeline Declarative Plugin version 1.3.8. Here is the Pipeline I used to verify that the issue was fixed:
pipeline {
agent any
stages {
stage("test") {
options {
retry(3)
}
steps {
sh 'if (( $RANDOM % 2 )); then exit 0; else exit 1; fi;'
}
}
}
}
Here is the log output from a build with one retry:
Started by user unknown or anonymous
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in /Users/dnusbaum/Projects/pipeline-model-definition-plugin/pipeline-model-definition/work/workspace/retry
[Pipeline] {
[Pipeline] stage
[Pipeline] { (test)
[Pipeline] retry
[Pipeline] {
[Pipeline] sh
+ (( 5334 % 2 ))
+ exit 1
[Pipeline] }
ERROR: script returned exit code 1
Retrying
[Pipeline] {
[Pipeline] sh
+ (( 24899 % 2 ))
+ exit 0
[Pipeline] }
[Pipeline] // retry
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS
I also tested with the options at the top level rather than in the stage, and got the same result. I am going to close this as a dupe of JENKINS-46354, feel free to reopen if you are still seeing the issue. If you do reopen the ticket, please include a simple Pipeline that reproduces the problem so we can understand how it differs from JENKINS-46354.
Add Comment
[JIRA] (JENKINS-49183) Retry in Declarative options passes stage but causes false fail in pipeline
Title: Message Title Devin Nusbaum resolved as Duplicate Jenkins / JENKINS-49183 Retry in Declarative options passes stage but causes false fail in pipeline Change By: Devin Nusbaum Status: Open Resolved Resolution: Duplicate Released As: pipeline-model-definition 1.3.8 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188020.1516956301000.25180.1560263708721%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57956) Cancel outdated jobs not working properly with multiple jobs ont the same pull request
Title: Message Title Jakub Bochenski commented on JENKINS-57956 Re: Cancel outdated jobs not working properly with multiple jobs ont the same pull request Bartlomiej Poleszak the repository you mention is abandoned and outside of control of the jenkins project. Please feel free to re-submit the PR to the official repository at https://github.com/jenkinsci/stash-pullrequest-builder-plugin This functionality has been moved to StashRepository. We also require some basic unit test coverage for new changes Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199937.1560252872000.25204.1560263880531%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45318) Add dependancy on net.i2p.crypto inside sshd module
Title: Message Title Stefan Spieker closed an issue as Fixed Already merged as far as I can see: https://github.com/jenkinsci/sshd-module/pull/25 Jenkins / JENKINS-45318 Add dependancy on net.i2p.crypto inside sshd module Change By: Stefan Spieker Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183458.1499267159000.25206.1560264180474%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57669) Write K8s spec for Zookeeper and Kafka nodes
Title: Message Title Long Nguyen updated JENKINS-57669 Jenkins / JENKINS-57669 Write K8s spec for Zookeeper and Kafka nodes Change By: Long Nguyen Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199602.1558718399000.25209.1560264420187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57667) Launching Zookeeper and Kafka in K8s UI
Title: Message Title Long Nguyen updated JENKINS-57667 Jenkins / JENKINS-57667 Launching Zookeeper and Kafka in K8s UI Change By: Long Nguyen Status: In Review Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199600.155871834.25210.1560264420346%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57962) Jenkins log is flooded with 'You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator'
Title: Message Title Christopher Crowe created an issue Jenkins / JENKINS-57962 Jenkins log is flooded with 'You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator' Issue Type: Bug Assignee: Emilio Escobar Components: changelog-history-plugin Created: 2019-06-11 14:50 Environment: linux - centos 7 Jenkins 2.164.3 Labels: changelog annotate Priority: Minor Reporter: Christopher Crowe Log output (https://jenkins/log/all) the following warning is spammed: ... Jun 11, 2019 10:39:49 AM WARNING hudson.scm.ChangeLogAnnotator annotate You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator Jun 11, 2019 10:39:49 AM WARNING hudson.scm.ChangeLogAnnotator annotate You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator Jun 11, 2019 10:39:49 AM WARNING hudson.scm.ChangeLogAnnotator annotate You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator Jun 11, 2019 10:39:49 AM WARNING hudson.scm.ChangeLogAnnotator annotate You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator Jun 11, 2019 10:39:49 AM WARNING hudson.scm.ChangeLogAnnotator annotate You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator Jun 11, 2019 10:39:49 AM WARNING hudson.scm.ChangeLogAnnotator annotate You must override the newer overload of annotate from org.jenkin
[JIRA] (JENKINS-5256) Cannot save changes in node configuration
Title: Message Title Adam Romano commented on JENKINS-5256 Re: Cannot save changes in node configuration I'm still having this issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.135345.1263363246000.25221.1560265020373%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino hey , Could you help me please :D ? !image-2019-06-11-16-59-20-387.png! !image-2019-06-11-17-02-59-844.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25226.1560265440327%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino hey , Could you help me please :D ? !image-2019-06-11-17-02-59-844.png! !image-2019-06-11-17-03-58-044.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25228.1560265440352%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino Attachment: image-2019-06-11-16-59-20-387.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25225.1560265440312%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino created an issue Jenkins / JENKINS-57963 Failed to connect to repository Issue Type: Bug Assignee: Unassigned Attachments: image-2019-06-11-16-59-14-007.png, image-2019-06-11-17-02-59-844.png, image-2019-06-11-17-03-58-044.png Components: _unsorted Created: 2019-06-11 15:03 Priority: Blocker Reporter: louis Catarino hey , Could you help me please ? Add Comment
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino Attachment: image-2019-06-11-17-03-58-044.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25227.1560265440341%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino Attachment: image-2019-06-11-17-04-52-764.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25230.1560265500186%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino hey , Could you help me please :D ? !image-2019-06-11-17-02-59-844.png!!image-2019-06-11-17- 04-52-764.png!!image-2019-06-11-17- 03-58-044.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25231.1560265500200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino Attachment: image-2019-06-11-16-59-14-007.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25229.1560265500135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57922) Ability to specify output directory for translation-tool.pl
Title: Message Title Mustafa Ulu assigned an issue to Mustafa Ulu Jenkins / JENKINS-57922 Ability to specify output directory for translation-tool.pl Change By: Mustafa Ulu Assignee: Mustafa Ulu Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199895.156010731.25232.1560266520106%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45228) Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command
Title: Message Title Geoffroy Jabouley edited a comment on JENKINS-45228 Re: Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command Helloalso facing this issue in some cases where files where modified/added into source branch of PR.Any idea when/if LFS credentials support will be added to the merge portion of the git plugin? Maybe at leat least providing some implementation guidance for a future contributionBR Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183359.1498813755000.25250.1560266641018%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57964) Documentation unclear for node() in scripted pipeline
Title: Message Title leemeador created an issue Jenkins / JENKINS-57964 Documentation unclear for node() in scripted pipeline Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2019-06-11 15:23 Environment: n/a Labels: documentation scripted node Priority: Minor Reporter: leemeador On this page in the documentation, it describes node(). https://jenkins.io/doc/pipeline/steps/workflow-durable-task-step/#node-allocate-node Some examples of using the operators have no quotes. Some have quotes around the individual components (eg. 'linux' || 'osx'). None have the full correct syntax (eg. 'linux || osx'). If you use the form with the quotes around the individual components, you get an error saying that node() does not allow a boolean argument. Of course, we are used to the error messaages occasionally having no useful information. I suggest changing the documentation to NOT include the example with quotes around the components. (It says exactly this: For example, "osx (10.11)" || "Windows Server") I also suggest putting something up at the top that shows a full example with an _expression_ as well as a single agent's label.
[JIRA] (JENKINS-48430) Provided config file is sometimes not complete
Title: Message Title Dominik Bartholdi commented on JENKINS-48430 Re: Provided config file is sometimes not complete I would very much like to fix this, but as stated previously, I'm not able to reproduce the issue in my env. I have an idea for a fix, but would need someone to try it before I ship it. Anyone willing to help/test out? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187028.1512645914000.25261.1560266880250%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) p4-plugin
Title: Message Title
Karl Wirth commented on JENKINS-57955
Re: p4-plugin
Hi Kieron Kierzo, I have been able to reproduce this behavior. Changing it to 'mklink /D' does not solve the problem. If it works for you, using 'sync only' is one workaround. Would another be to run 'rmdir' on the junction before the end of the job then recreate it next time? Reproduction steps: 1. Create a file on the build machine called 'C:\filestore\Jenkins\temp\symlink_target1\file1'. 2. Add a file to '//depot/win_symlink/...'. 3. Create a pipeline job with the following config:
pipeline {
agent { label 'Windows10' }
stages {
stage("Repro") {
steps {
script {
checkout perforce(credential: 'JenkinsMaster', populate: forceClean(have: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: false), workspace: manualSpec(charset: 'none', cleanup: false, name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}', pinHost: false, spec: clientSpec(allwrite: false, backup: true, changeView: '', clobber: true, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE', view: '//depot/win_symlink/...
bat 'dir /b /s'
bat 'mklink /J "linkeddir" "C:\\filestore\\Jenkins\\temp\\symlink_target1"'
bat 'dir /b /s'
}
}
}
}
}
4. Build the job. 5. Build the job again. Result seen - 'C:\filestore\Jenkins\temp\symlink_target1\file1' is deleted. Expected result - 'C:\filestore\Jenkins\temp\symlink_target1\file1' is not deleted.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are su
[JIRA] (JENKINS-57955) p4-plugin
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57955 p4-plugin Change By: Karl Wirth Labels: windows P4_B Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.25284.1560268020238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57965) Clicking "Save" on node config throws java.lang.NullPointerException
Title: Message Title Adam Romano created an issue Jenkins / JENKINS-57965 Clicking "Save" on node config throws java.lang.NullPointerException Issue Type: Bug Assignee: Unassigned Attachments: Screenshot 2019-06-11 at 15.24.52.png, Screenshot 2019-06-11 at 15.25.03.png Components: core Created: 2019-06-11 15:46 Environment: Jenkins 2.164.1 Priority: Blocker Reporter: Adam Romano On the Build Executor Status list, select a node, open the dropdown, change something (or change nothing, same result) and click save. a j ava.lang.NullPointerException is thrown. Add Comment
[JIRA] (JENKINS-57955) p4-plugin
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57955 p4-plugin Change By: Karl Wirth Environment: Windows Host and Agent, Jenkins ver. 2.176.1 (Pipeline in SCM) P4-Plugin 1.10.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.25287.1560268080182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) p4-plugin
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-57955 p4-plugin Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.25289.1560268080206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36111) p4 plugin cleanup behavior wrong with AutoCleanImpl and linked directory
Title: Message Title Karl Wirth commented on JENKINS-36111 Re: p4 plugin cleanup behavior wrong with AutoCleanImpl and linked directory Newer case has come in on this topic - JENKINS-57955. Am closing this one in favour of new case with repro steps. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172074.1466510323000.25292.1560268140126%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36111) p4 plugin cleanup behavior wrong with AutoCleanImpl and linked directory
Title: Message Title Karl Wirth closed an issue as Fixed Closing in favour of JENKINS-57955. Jenkins / JENKINS-36111 p4 plugin cleanup behavior wrong with AutoCleanImpl and linked directory Change By: Karl Wirth Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172074.1466510323000.25295.1560268200522%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57955 Clean and sync incorrectly follows junction/directory symlinks on Windows Change By: Karl Wirth Summary: p4-plugin Clean and sync incorrectly follows junction/directory symlinks on Windows Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.25297.1560268260218%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57965) Clicking "Save" on node config throws java.lang.NullPointerException
Title: Message Title Adam Romano updated an issue Jenkins / JENKINS-57965 Clicking "Save" on node config throws java.lang.NullPointerException Change By: Adam Romano Labels: regression Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199948.1560268008000.25298.1560268260233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38257) Feature to define non-actual user
Title: Message Title Kalle Niemitalo commented on JENKINS-38257 Re: Feature to define non-actual user Jenkins 2.176.1 LTS now includes JENKINS-24513, which warns about builds running as SYSTEM. But virtual users are difficult to define when Jenkins is using SAML Plugin against Microsoft's AD FS. I wonder if, instead of the "significant changes" in JENKINS-32596, this could be implemented: as a security realm wrapper plugin that lets the admin select an inner security realm for the real users and define some additional virtual users, or as a composite security realm plugin that lets the admin select two or more inner security realms, one of which could then be Jenkins’ own user database. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174420.1473972094000.25310.1560269040321%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57833) All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log
Title: Message Title Cyrille Le Clerc commented on JENKINS-57833 Re: All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log Markus Till can you please search for any xerces jar file in the plugins that you have loaded in your instance. It is typically outdated versions of xerces that cause issues with the DocumentBuilderFactory. Can you on the master run "find -iname "xerces"" under "JENKINS_HOME/plugins". It looks like $ cd /plugins # verify that we are in the right folder verifying the number of jar files we found $ find -iname "*.jar" | wc - $ find -iname "*xerces*.jar" Result typically looks like: $ find -iname "*.jar" | wc -l 1262 $ find -iname "xerces*.jar" ./analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar $ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199790.1559631863000.25312.1560269460187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57966) Multibranch Pipeline Indexing fails with ClassCastException in svn
Title: Message Title Daniel Eichert created an issue Jenkins / JENKINS-57966 Multibranch Pipeline Indexing fails with ClassCastException in svn Issue Type: Bug Assignee: rsandell Components: multi-branch-project-plugin (not Pipeline), pipeline Created: 2019-06-11 16:42 Environment: Jenkins is running on a RHEL 7 Jenkins Version is 2.180 Labels: multibranch pipeline branch Priority: Critical Reporter: Daniel Eichert When I was indexing my jobs today I got an ClassCastException, the result of this mistake is hat my MultiBranch Pipeline job cannot find any branches and therefore the folder stays empty. This is a critical issue for me. I would appreciate any help. Here is my error message: ERROR: [Tue Jun 11 18:16:54 CEST 2019] Could not fetch branches from source 78aad773-0322-49fb-99da-95df2966fe5b java.lang.ClassCastException: [[J cannot be cast to org.mapdb.BTreeMap$BNode at org.mapdb.BTreeMap.put2(BTreeMap.java:663) at org.mapdb.BTreeMap.put(BTreeMap.java:643) at org.mapdb.DB.catPut(DB.java:105) at org.mapdb.DB.createHashMap(DB.java:443) at org.mapdb.DB$HTreeMapMaker.make(DB.java:216) at org.mapdb.DB.getHashMap(DB.java:356) at org.mapdb.DB.getHashMap(DB.java:329) at jenkins.scm.impl.subversion.SVNRepositoryView.(SVNRepositoryView.java:115) at jenkins.scm.impl.subversion.SubversionSCMSource.openSession(Subvers
[JIRA] (JENKINS-57966) Multibranch Pipeline Indexing fails with ClassCastException in svn
Title: Message Title
Daniel Eichert updated an issue
Jenkins / JENKINS-57966
Multibranch Pipeline Indexing fails with ClassCastException in svn
Change By:
Daniel Eichert
When I was indexing my jobs today I got an ClassCastException, the result of this mistake is hat my MultiBranch Pipeline job cannot find any branches and therefore the folder stays empty. This is a critical issue for me. I would appreciate any help. Here is my error message:{code:java}ERROR: [Tue Jun 11 18:16:54 CEST 2019] Could not fetch branches from source 78aad773-0322-49fb-99da-95df2966fe5bjava.lang.ClassCastException: [[J cannot be cast to org.mapdb.BTreeMap$BNodeat org.mapdb.BTreeMap.put2(BTreeMap.java:663)at org.mapdb.BTreeMap.put(BTreeMap.java:643)at org.mapdb.DB.catPut(DB.java:105)at org.mapdb.DB.createHashMap(DB.java:443)at org.mapdb.DB$HTreeMapMaker.make(DB.java:216)at org.mapdb.DB.getHashMap(DB.java:356)at org.mapdb.DB.getHashMap(DB.java:329)at jenkins.scm.impl.subversion.SVNRepositoryView.(SVNRepositoryView.java:115)at jenkins.scm.impl.subversion.SubversionSCMSource.openSession(SubversionSCMSource.java:336)at jenkins.scm.impl.subversion.SubversionSCMSource.retrieve(SubversionSCMSource.java:240) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373)at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283)at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634)at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277)at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164)at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1025)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429)[Tue Jun 11 18:16:54 CEST 2019] Finished branch indexing. Indexing took 74 msFATAL: Failed to recompute children of truemdmBuildReports » testjava.lang.ClassCastException: [[J cannot be cast to org.mapdb.BTreeMap$BNodeat org.mapdb.BTreeMap.put2(BTreeMap.java:663)at org.mapdb.BTreeMap.put(BTreeMap.java:643)at org.mapdb.DB.catPut(DB.java:105)at org.mapdb.DB.createHashMap(DB.java:443)at org.mapdb.DB$HTreeMapMaker.make(DB.java:216)at org.mapdb.DB.getHashMap(DB.java:356)at org.mapdb.DB.getHashMap(DB.java:329)at jenkins.scm.impl.subversion.SVNRepositoryView.(SVNRepositoryView.java:115)at jenkins.scm.impl.subversion.SubversionSCMSource.openSession(SubversionSCMSource.java:336)at jenkins.scm.impl.subversion.SubversionSCMSource.retrieve(SubversionSCMSource.java:240) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373)at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283)at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at com.cloudbees.hudson.plugins.folder
[JIRA] (JENKINS-57967) vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher
Title: Message Title Nick Jones created an issue Jenkins / JENKINS-57967 vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2019-06-11 16:51 Environment: vSphere Cloud 2.19, SSH Slaves 1.30.0 Priority: Blocker Reporter: Nick Jones Having upgraded to SSH Slaves 1.30, our vSphere Cloud plugin no longer works – agent nodes fail to provision, and a message like the following gets logged: Unexpected exception encountered while provisioning agent agent1 java.lang.NoSuchMethodError: hudson.plugins.sshslaves.SSHLauncher.(Ljava/lang/String;ILjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/Integer;Ljava/lang/Integer;Ljava/lang/Integer;)V at org.jenkinsci.plugins.vSphereCloudSlaveTemplate.determineLauncher(vSphereCloudSlaveTemplate.java:481) at org.jenkinsci.plugins.vSphereCloudSlaveTemplate.provision(vSphereCloudSlaveTemplate.java:451) at org.jenkinsci.plugins.vSphereCloudSlaveTemplate.provision(vSphereCloudSlaveTemplate.java:396) at org.jenkinsci.plugins.vSphereCloud$VSpherePlannedNode.provisionNewNode(vSphereCloud.java:534) at org.jenkinsci.plugins.vSphereCloud$VSpherePlannedNode.access$100(vSphereCloud.java:496) at org.jenkinsci.plugins.vSphereCloud$VSpherePlannedNode$1.call(vSphereCloud.java:510) at org.jenkinsci.plugins.vSphereCloud$VSpherePlannedNode$1.call(vSphereCloud.java:506) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExe
[JIRA] (JENKINS-57967) vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-57967 vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher Change By: Nick Jones Component/s: ssh-slaves-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199950.1560271877000.25334.1560271980171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46515) Launcher will retry connections forever under some irrecoverable status
Title: Message Title Jeff Thompson commented on JENKINS-46515 Re: Launcher will retry connections forever under some irrecoverable status The Remoting release (3.30) containing this change was reverted from Jenkins core because it introduced a regression in some other scenarios, particularly involving cloud agents. I'm going to revert it from the Remoting master branch and create a new release without it and containing the changes included in 3.30. See #JENKINS-57759 and #JENKINS-57713 Javier Delgado (or someone else), if you are interested you can re-open this issue or create a similar one and propose a new approach that resolves the issues described here and maintains sequence needed by the other scenarios. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184832.1503993829000.25355.1560274680274%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57968) set the source root
Title: Message Title Henry Borchers created an issue Jenkins / JENKINS-57968 set the source root Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-06-11 17:43 Priority: Minor Reporter: Henry Borchers My pipelines generate my builds out of source which has provide me with a problem with any warning messages that use relative paths for the file names. warnings-ng is able to parse the warning messages beautifully but it's unable to link it back to the scm directory or source root. For reference, my jenkins workspace looks a little like this... / /scm/ /scm/.git/ /build/ /reports/ /dist/ /logs/ What I would love is to use is something like this is my pipeline recordIssues( tools: [myPy(name: 'MyPy', pattern: 'logs/mypy.log')], sourcePath: "scm" ) I love this plugin. it's saved me from so much trouble
[JIRA] (JENKINS-57713) Cloud agent provisioning errors due to Remoting behaviour change
Title: Message Title Jeff Thompson commented on JENKINS-57713 Re: Cloud agent provisioning errors due to Remoting behaviour change It's not clear to me how to preserve the sequencing behavior describes and also achieve the sequencing change Javier Delgado desired in #JENKINS-46515. Different scenarios or implementations rely on or are impacted by the sequence differently. There might be some way to add a flag to invoke the new behavior, while not impacting the existing but I'm not sure if that could meet the needs. Unfortunately, the sequencing isn't well-specified or clarified. I'll reference this Jira issue to remove the changes for #JENKINS-46515 / jenkinsci/remoting#193 from the Remoting master branch. Once done, I'll release a new Remoting version with the other changes. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199655.1559046575000.25361.1560275460272%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57968) Set the source root for Warnings-ng plugin
Title: Message Title Henry Borchers updated an issue Jenkins / JENKINS-57968 Set the source root for Warnings-ng plugin Change By: Henry Borchers Summary: set Set the source root for Warnings-ng plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199952.1560274992000.25369.1560275580283%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57968) set the source root for Warnings-ng plugin
Title: Message Title Henry Borchers updated an issue Jenkins / JENKINS-57968 set the source root for Warnings-ng plugin Change By: Henry Borchers Summary: set the source rootfor Warnings-ng plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199952.1560274992000.25367.1560275580261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
