[JIRA] (JENKINS-42756) Jacoco Memory Allocation after Job is Terminated
Title: Message Title centic resolved as Not A Defect This seems to be more related to JaCoCo itself, not Jenkins, there closing this here. Jenkins / JENKINS-42756 Jacoco Memory Allocation after Job is Terminated Change By: centic Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-42873) NPE when retry a failed job when there is a similar job in queue
Title: Message Title ikedam commented on JENKINS-42873 Re: NPE when retry a failed job when there is a similar job in queue Let me know the version of Jenkins you use. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18395) Add post-build step
Title: Message Title Janario Oliveira closed an issue as Incomplete Jenkins / JENKINS-18395 Add post-build step Change By: Janario Oliveira Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18395) Add post-build step
Title: Message Title Janario Oliveira resolved as Incomplete Jenkins / JENKINS-18395 Add post-build step Change By: Janario Oliveira Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39744) Hide Authorization Custom Header
Title: Message Title Janario Oliveira closed an issue as Fixed Jenkins / JENKINS-39744 Hide Authorization Custom Header Change By: Janario Oliveira Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39744) Hide Authorization Custom Header
Title: Message Title Janario Oliveira resolved as Fixed Jenkins / JENKINS-39744 Hide Authorization Custom Header Change By: Janario Oliveira Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41803) httpRequest step called outside node causes exception
Title: Message Title Janario Oliveira commented on JENKINS-41803 Re: httpRequest step called outside node causes exception Can you add the full script that throws the error? And also the log printed from the job execution. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41726) form auth in http-request plugin getting HTTP/1.1 408 Request Timeout response
Title: Message Title Janario Oliveira commented on JENKINS-41726 Re: form auth in http-request plugin getting HTTP/1.1 408 Request Timeout response How long does it take to throw the error? Have you tried to increase the timeout configuration in the job? The only difference I saw from GET 200 to POST 208 is that 200 is using http://localhost:8080 and the other http://127.0.0.1:8080 . This shouldn't have difference unless you have a wrong configuration in hosts. Have you tried form with localhost instead of 127.0.0.1? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41934) HTTPS/TLS Cert check bypassed
Title: Message Title Janario Oliveira resolved as Fixed Jenkins / JENKINS-41934 HTTPS/TLS Cert check bypassed Change By: Janario Oliveira Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41934) HTTPS/TLS Cert check bypassed
Title: Message Title Janario Oliveira commented on JENKINS-41934 Re: HTTPS/TLS Cert check bypassed The certificate was ignored. I added a configuration ignoreSslErrors that when true will ignore invalid certificates. The default is false but in old jobs to keep compatibility it will be deserialized as true. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41934) HTTPS/TLS Cert check bypassed
Title: Message Title Janario Oliveira started work on JENKINS-41934 Change By: Janario Oliveira Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42303) handshake_failure for (AWS) HTTPS/SSL urls with the HTTP Request plugin
Title: Message Title Janario Oliveira started work on JENKINS-42303 Change By: Janario Oliveira Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42303) handshake_failure for (AWS) HTTPS/SSL urls with the HTTP Request plugin
Title: Message Title Janario Oliveira commented on JENKINS-42303 Re: handshake_failure for (AWS) HTTPS/SSL urls with the HTTP Request plugin As I tested it was an error in httpclient. I updated it and testing again it worked HttpClient issue https://issues.apache.org/jira/browse/HTTPCLIENT-1726 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42303) handshake_failure for (AWS) HTTPS/SSL urls with the HTTP Request plugin
Title: Message Title Janario Oliveira resolved as Fixed Jenkins / JENKINS-42303 handshake_failure for (AWS) HTTPS/SSL urls with the HTTP Request plugin Change By: Janario Oliveira Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41934) HTTPS/TLS Cert check bypassed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41934 Re: HTTPS/TLS Cert check bypassed Code changed in jenkins User: Janario Oliveira Path: src/main/java/jenkins/plugins/http_request/HttpRequest.java src/main/java/jenkins/plugins/http_request/HttpRequestStep.java src/main/resources/jenkins/plugins/http_request/HttpRequest/config.jelly src/main/webapp/help-ignoreSslErrors.html http://jenkins-ci.org/commit/http-request-plugin/5d631d58f6ca0435880a26a8ef57b860719578d3 Log: JENKINS-41934 Added conf to ignore certificate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42626) «by build results» shortcut link cannot be added
Title: Message Title ikedam commented on JENKINS-42626 Re: «by build results» shortcut link cannot be added This is caused for the following exception: Caused by: java.lang.NullPointerException: Cannot get property 'resultsToCheck' on null object at org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:60) at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:172) at org.codehaus.groovy.runtime.callsite.NullCallSite.getProperty(NullCallSite.java:47) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:296) at config$_run_closure3.doCall(config.groovy:39) at config$_run_closure3.doCall(config.groovy) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1024) at groovy.lang.Closure.call(Closure.java:414) at groovy.lang.Closure.call(Closure.java:408) at org.kohsuke.stapler.jelly.groovy.JellyBuilder$1.run(JellyBuilder.java:264) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) ... 99 more (config.groovy is https://github.com/jenkinsci/matrix-combinations-plugin/blob/matrix-combinations-parameter-1.1.0/src/main/resources/hudson/plugins/matrix_configuration_parameter/shortcut/ResultShortcut/config.groovy ) Add Comment
[JIRA] (JENKINS-42303) handshake_failure for (AWS) HTTPS/SSL urls with the HTTP Request plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42303 Re: handshake_failure for (AWS) HTTPS/SSL urls with the HTTP Request plugin Code changed in jenkins User: Janario Oliveira Path: pom.xml src/main/java/jenkins/plugins/http_request/MimeType.java src/test/java/jenkins/plugins/http_request/HttpRequestTestBase.java http://jenkins-ci.org/commit/http-request-plugin/3ea28a4cc7b480d97397614a3378fcc4316705aa Log: JENKINS-42303 - Updated httpclient. HTTPCLIENT-1726 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41934) HTTPS/TLS Cert check bypassed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41934 Re: HTTPS/TLS Cert check bypassed Code changed in jenkins User: Janario Oliveira Path: src/main/java/jenkins/plugins/http_request/HttpRequest.java http://jenkins-ci.org/commit/http-request-plugin/ce565aa74b4d72779ab16306fb5f5ea63058b89b Log: JENKINS-41934 Added conf to ignore certificate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42626) «by build results» shortcut link cannot be added
Title: Message Title ikedam updated an issue Jenkins / JENKINS-42626 «by build results» shortcut link cannot be added Change By: ikedam Priority: Minor Major Environment: matrix-combinations-parameter-1.1.0 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42626) «by build results» shortcut link cannot be added
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-42626 «by build results» shortcut link cannot be added Change By: ikedam Assignee: ikedam Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42903) HTML in description is always escaped
Title: Message Title ikedam created an issue Jenkins / JENKINS-42903 HTML in description is always escaped Issue Type: Bug Assignee: ikedam Components: extensible-choice-parameter-plugin Created: 2017/Mar/18 4:27 AM Environment: extensible-choice-parameter-1.3.3 Jenkins >= 2.32.2 Jenkins >= 2.44 Priority: Minor Reporter: ikedam HTMLs in the description is no longer displayed without escaping for SECURITY-353. To fix: use `ParameterDefinition#getFormattedDescription` introduced in Jenkins-1.521. 1.532 is the least LTS. Set `escapeEntryTitleAndDescription` to false. It might be useful if itroducing the previewing feature like this: This is introduced since Jenkins-1.554.
[JIRA] (JENKINS-42902) HTML in description is always escaped
Title: Message Title ikedam updated an issue Jenkins / JENKINS-42902 HTML in description is always escaped Change By: ikedam Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42902) HTML in description is always escaped
Title: Message Title ikedam created an issue Jenkins / JENKINS-42902 HTML in description is always escaped Issue Type: Improvement Assignee: ikedam Components: matrix-combinations-parameter-plugin Created: 2017/Mar/18 4:25 AM Environment: matrix-combinations-parameter-1.1.0 Jenkins >= 2.32.2 Jenkins >= 2.44 Priority: Minor Reporter: ikedam HTMLs in the description is no longer displayed without escaping for SECURITY-353. To fix: use `ParameterDefinition#getFormattedDescription` introduced in Jenkins-1.521. 1.532 is the least LTS. Set `escapeEntryTitleAndDescription` to false. It might be useful if itroducing the previewing feature like this: This is introduced since Jenkins-1.554.
[JIRA] (JENKINS-42901) Blue Ocean dashboard should be more "activity" like
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-42901 Blue Ocean dashboard should be more "activity" like Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/18 4:02 AM Priority: Minor Reporter: Daniel Beck Blue Ocean shows a flattened list of jobs on its "bashboard" that is limited to a fixed number of items. Trying to show more items is extremely annoying. Aaaand it's ordered alphabetically. A typical organization will have projects in Jenkins that haven't been built in a while. In fact, I expect that the relevance of a project to a user starting at the dashboard can in many cases be approximated by its most recent build activity, i.e. a project recently built is likely more relevant than one that hasn't been built in a while. Therefore the dashboard should at least optionally allow to show items by date of last activity on any branch, or e.g. show items alphabetically, but limit the initial set of N items shown to those N most recently active ones. Add Comment
[JIRA] (JENKINS-41773) Copy Artifact sometimes crashes on startup (Jenkins#getDescriptorByType looks sometimes return null)
Title: Message Title
ikedam commented on JENKINS-41773
Re: Copy Artifact sometimes crashes on startup (Jenkins#getDescriptorByType looks sometimes return null)
Christopher Head Would you see what is output when you run the following code in Manage Jenkins > Script Console ? (when the copyartifact crashed in startup):
import hudson.plugins.copyartifact.BuildSelector;
import hudson.plugins.copyartifact.BuildSelectorParameter;
println('-')
println(Jenkins.instance.getDescriptorByType(BuildSelectorParameter.DescriptorImpl.class));
println('-')
println(Jenkins.instance.getDescriptorByType(BuildSelectorParameter.DescriptorImpl.class).getBuildSelectors());
println('-')
println(Jenkins.instance.>getDescriptorList(BuildSelector.class));
println('-')
An example output in my environment:
-
hudson.plugins.copyartifact.BuildSelectorParameter$DescriptorImpl@433514fe
-
[hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@6e3bcc25, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@39642e00, hudson.plugins.copyartifact.TriggeredBuildSelector$DescriptorImpl@1f631eff, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@1263654f, hudson.plugins.copyartifact.DownstreamBuildSelector$DescriptorImpl@2289c9c2, hudson.plugins.copyartifact.PermalinkBuildSelector$DescriptorImpl@3a85f7bd, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@3d1682f4, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@34d6d104, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@587dd985]
-
[hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@6e3bcc25, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@39642e00, hudson.plugins.copyartifact.TriggeredBuildSelector$DescriptorImpl@1f631eff, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@1263654f, hudson.plugins.copyartifact.DownstreamBuildSelector$DescriptorImpl@2289c9c2, hudson.plugins.copyartifact.PermalinkBuildSelector$DescriptorImpl@3a85f7bd, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@3d1682f4, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@34d6d104, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@587dd985]
-
Add Comment
[JIRA] (JENKINS-42900) Job-DSL stash notifier creates "Unreadable Data".
Title: Message Title
Chaz Ruhl created an issue
Jenkins / JENKINS-42900
Job-DSL stash notifier creates "Unreadable Data".
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2017/Mar/18 1:41 AM
Environment:
Jenkins 2.32.3 Stash notifier plugin- 1.11.6 job-dsl plugin - 1.52
Labels:
job-dsl-plugin stash-notifier publisher
Priority:
Minor
Reporter:
Chaz Ruhl
When following the job dsl documentation for the Stash notifier plugin (https://jenkinsci.github.io/job-dsl-plugin/#path/job-publishers-stashNotifier) code: job('blah') { publishers { stashNotifier() } } It produces the following XML: false false This triggers an "Unreadable Data" message: MissingFieldException: No field 'stashUserName' found in class 'org.jenkinsci.plugins.stashNotifier.StashNotifier', MissingFieldException: No field 'stashUserPassword' found in class 'org.jenkinsci.plugins.stashNotifier.StashNotifier'
[JIRA] (JENKINS-39680) httpRequest method in Pipeline causes weird behavior
Title: Message Title
Janario Oliveira edited a comment on JENKINS-39680
Re: httpRequest method in Pipeline causes weird behavior
I've tried it and It is working ok {code:java}def body = 'test'def response = httpRequest acceptType: 'APPLICATION_JSON', contentType: 'APPLICATION_JSON', httpMode: 'POST', requestBody: body, consoleLogResponseBody: true, url: 'http://requestb.in/1ecf72r1', validResponseContent: 'ok'println "Sent a notification, got a $response response"{code}This will log: {code:java}Running: Perform an HTTP Request and return a response objectHttpMode: POSTURL: http://requestb.in/1ecf72r1Content-type: application/jsonAccept: application/jsonSending request to url: http://requestb.in/1ecf72r1Response Code: HTTP/1.1 200 OKResponse: okSuccess code from [100‥399]Running: Print MessageSent a notification, got a Status: 200, Response: ok responseRunning: End of WorkflowFinished: SUCCESS{code} Note that I changed _validResponseContent: '"success":true'_ to _validResponseContent: 'ok'_ otherwise I receive an error {code:java}ERROR: Fail: Response with length 2 doesn't contain '"success":true'{code} [~tyrelh] Can you confirm if the response content has _'"success":true'_?Can you attach the full job log?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39680) httpRequest method in Pipeline causes weird behavior
Title: Message Title Janario Oliveira stopped work on JENKINS-39680 Change By: Janario Oliveira Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39680) httpRequest method in Pipeline causes weird behavior
Title: Message Title Janario Oliveira commented on JENKINS-39680 Re: httpRequest method in Pipeline causes weird behavior I've tried it and It is working ok def body = 'test' def response = httpRequest acceptType: 'APPLICATION_JSON', contentType: 'APPLICATION_JSON', httpMode: 'POST', requestBody: body, consoleLogResponseBody: true, url: 'http://requestb.in/1ecf72r1', validResponseContent: 'ok' println "Sent a notification, got a $response response" This will log: Running: Perform an HTTP Request and return a response object HttpMode: POST URL: http://requestb.in/1ecf72r1 Content-type: application/json Accept: application/json Sending request to url: http://requestb.in/1ecf72r1 Response Code: HTTP/1.1 200 OK Response: ok Success code from [100‥399] Running: Print Message Sent a notification, got a Status: 200, Response: ok response Running: End of Workflow Finished: SUCCESS Note that I changed validResponseContent: '"success":true' to validResponseContent: 'ok' otherwise I receive an error ERROR: Fail: Response with length 2 doesn't contain '"success":true' Can you confirm if the response content has '"success":true'? Can you attach the full job log? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-39680) httpRequest method in Pipeline causes weird behavior
Title: Message Title Janario Oliveira started work on JENKINS-39680 Change By: Janario Oliveira Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27045) Cannot use jenkins-cli with github oauth plugin
Title: Message Title Sam Gleske resolved as Fixed Resolved by https://github.com/jenkinsci/github-oauth-plugin/pull/77 Jenkins / JENKINS-27045 Cannot use jenkins-cli with github oauth plugin Change By: Sam Gleske Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.goog
[JIRA] (JENKINS-42858) Credentials environment variable isn't evaluated/available in the environment directive
Title: Message Title Andrew Bayer started work on JENKINS-42858 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27045) Cannot use jenkins-cli with github oauth plugin
Title: Message Title Sam Gleske commented on JENKINS-27045 Re: Cannot use jenkins-cli with github oauth plugin Joshua Hoblitt https://github.com/jenkinsci/github-oauth-plugin/blob/github-oauth-0.25/pom.xml#L16-L17 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42858) Credentials environment variable isn't evaluated/available in the environment directive
Title: Message Title Andrew Bayer updated JENKINS-42858 Jenkins / JENKINS-42858 Credentials environment variable isn't evaluated/available in the environment directive Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42858) Credentials environment variable isn't evaluated/available in the environment directive
Title: Message Title Andrew Bayer commented on JENKINS-42858 Re: Credentials environment variable isn't evaluated/available in the environment directive And https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/141 is now up fixing this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42858) Credentials environment variable isn't evaluated/available in the environment directive
Title: Message Title Andrew Bayer commented on JENKINS-42858 Re: Credentials environment variable isn't evaluated/available in the environment directive I take that back - the logic for hiding credentials in the console log is good enough to deal with this, and that's really the only potential problem. Woot. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42858) Credentials environment variable isn't evaluated/available in the environment directive
Title: Message Title Andrew Bayer commented on JENKINS-42858 Re: Credentials environment variable isn't evaluated/available in the environment directive So...while I can implement this, there's a good question of whether we should implement it. Credentials are supposed to be secrets, after all - adding them to other environment variables kinda breaks that expectation. rsandell, what are your thoughts? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42891) Using `vars/pipeline.groovy` causes script-security error starting with Jenkins 2.32.3
Title: Message Title Andrew Bayer resolved as Not A Defect Sadly, once you've got Declarative Pipelines installed (which comes automatically now), you can't have a variable in your Pipelines named pipeline, just as you can't have one named docker or scm or env - trying to use the same name as a global variable will just cause problems. So you should rename your vars/pipeline.groovy to something else. Sorry for the inconvenience. Jenkins / JENKINS-42891 Using `vars/pipeline.groovy` causes script-security error starting with Jenkins 2.32.3 Change By: Andrew Bayer Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-37817) checkout scm should be able to override extensions/settings
Title: Message Title Sorin Sbarnea commented on JENKINS-37817 Re: checkout scm should be able to override extensions/settings Any updates on this? I find really confusing that the getBranches permission cannot be approved at never reaches the Script approval list. Have a look at this sample pipeline that replicates the error: https://github.com/pycontribs/powertape/blob/master/Jenkinsfile#L72 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34359) HTTP/1.1 500 error running SOAPUI REST project from Jenkins
Title: Message Title Janario Oliveira updated an issue Jenkins / JENKINS-34359 HTTP/1.1 500 error running SOAPUI REST project from Jenkins Change By: Janario Oliveira Component/s: core Component/s: http-request-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41396) Declarative: Add method definition section to root pipeline block
Title: Message Title
Andrew Bayer commented on JENKINS-41396
Re: Declarative: Add method definition section to root pipeline block
So for reasons I'm fairly sheepish about (I needed a break from the Really Hard Problems of JENKINS-42829, JENKINS-42753, JENKINS-42748, and all their demented friends), I just spent a few hours on this, only to discover that there's a big problem. You simply can't define a method anywhere in Groovy except right inside a class, so
methods {
def foo() {
return "BANANAS ARE TASTY SOMETIMES"
}
}
won't get past the second phase in Groovy compilation (i.e., conversion) and that's something we just plain can't get around, at least not without doing some truly twisted magic in the parse phase of compilation in certain weird-ass edge cases - and that's ANTLR territory, so, well, I am not gonna mess with that. So, alternatives - we could do something like:
methods {
define {
name someMethodName
returnType Foo.class // optional, defaulting to dynamic, a.k.a. "def"
parameter { // optional, multiple parameter { } blocks allowed
name someParamName
paramType String.class // optional, dunno how we'd do List and friends anyway
defaultValue "foo" // optional again
}
nonCPS true // optional
body {
return someParamName
}
}
}
But that...looks awful. Just godawful. I'm considering whether I can transform the following into a proper method behind the scenes:
methods {
someMethodName { String someParam ->
return someParam
}
}
I think I can? But there are still some caveats - no way to define return type, so the transformed method in the shared library (oh yeah, I figured out how to do a dynamically generated non-source-control backed shared library) would be def someMethodName(String someParam) ... but I think that's ok. Not sure how to mark @NonCPS - the annotation can only go on methods, so we can't just toss it on the method call/closure above, so we'd theoretically need some other way to record that. And beyond that, it's not exactly a comfortable syntax for non-Groovy people, is it? Grr.
[JIRA] (JENKINS-42676) Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade
Title: Message Title Fritz Elfert resolved as Done Jenkins / JENKINS-42676 Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade Change By: Fritz Elfert Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42676) Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade
Title: Message Title Fritz Elfert closed an issue as Done Jenkins / JENKINS-42676 Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade Change By: Fritz Elfert Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42676) Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade
Title: Message Title Fritz Elfert commented on JENKINS-42676 Re: Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade Since the old style provisioning will be deprecated in the next release anyway, I'm closing this as resolved. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36281) Dashboard trend graphs not displayed following plugin upgrade
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36281 Re: Dashboard trend graphs not displayed following plugin upgrade Code changed in jenkins User: Ulli Hafner Path: analysis-core.iml pom.xml http://jenkins-ci.org/commit/analysis-core-plugin/95bd089086f3979817b7ed3fad8df27bfeed389a Log: [FIXED JENKINS-36281] Downgrade to joda-time 1.6. Use the same library as dashboard-view to avoid classloading problems. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42005) Cannot provision when there are instances created from snapshot (google-compute-engine)
Title: Message Title Fritz Elfert started work on JENKINS-42005 Change By: Fritz Elfert Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41878) Runtime Exception while using jira trigger plugin in maven job
Title: Message Title Wisen Tanasa commented on JENKINS-41878 Re: Runtime Exception while using jira trigger plugin in maven job Fixed under 0.4.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41878) Runtime Exception while using jira trigger plugin in maven job
Title: Message Title Wisen Tanasa resolved as Fixed Jenkins / JENKINS-41878 Runtime Exception while using jira trigger plugin in maven job Change By: Wisen Tanasa Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42899) puppet.codeDeploy fails if environment provided is "HEAD"
Title: Message Title Carl Caum updated an issue Jenkins / JENKINS-42899 puppet.codeDeploy fails if environment provided is "HEAD" Change By: Carl Caum Summary: puppet.codeDeploy fails if environment provided is null "HEAD" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42899) puppet.codeDeploy fails if environment provided is null
Title: Message Title
Carl Caum created an issue
Jenkins / JENKINS-42899
puppet.codeDeploy fails if environment provided is null
Issue Type:
Bug
Assignee:
Carl Caum
Components:
puppet-enterprise-pipeline-plugin
Created:
2017/Mar/17 9:53 PM
Priority:
Minor
Reporter:
Carl Caum
node {
def env = "HEAD";
puppet.codeDeploy env;
}
.. causes the following error:
com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at line 1 column 2 path $
at com.google.gson.Gson.fromJson(Gson.java:899)
at com.google.gson.Gson.fromJson(Gson.java:852)
at com.google.gson.Gson.fromJson(Gson.java:801)
at org.jenkinsci.plugins.puppetenterprise.apimanagers.puppetcodemanagerv1.CodeManagerDeploysV1.execute(CodeManagerDeploysV1.java:52)
at org.jenkinsci.plugins.puppetenterprise.models.PuppetCodeManager.deploy(PuppetCodeManager.java:51)
at org.jenkinsci.plugins.workflow.steps.CodeDeployStep$CodeDeployStepExecution.run(CodeDeployStep.java:90)
at org.jenkinsci.plugins.workflow.steps.CodeDeployStep$CodeDeployStepExecution.run(CodeDeployStep.java:64)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start(AbstractSynchronousStepExecution.java:42)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:184)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:126)
at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call
[JIRA] (JENKINS-42787) Got groovy Compilation Error in WorkflowScript
Title: Message Title Andrew Bayer resolved as Duplicate Jenkins / JENKINS-42787 Got groovy Compilation Error in WorkflowScript Change By: Andrew Bayer Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42005) Cannot provision when there are instances created from snapshot (google-compute-engine)
Title: Message Title Fritz Elfert commented on JENKINS-42005 Re: Cannot provision when there are instances created from snapshot (google-compute-engine) Instead of waiting for the next jclouds release (which could be quite some time considering that 2.0.1 just was released not long ago), I simply copied the four relevant source files into the plugin's sources and excluded them from the dependencies. This should fix the issue right now without the need for a custom jclouds build. Tomasz Wojtun: Please try the latest code without a custom build of jclouds. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42005) Cannot provision when there are instances created from snapshot (google-compute-engine)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42005 Re: Cannot provision when there are instances created from snapshot (google-compute-engine) Code changed in jenkins User: Fritz Elfert Path: jclouds-plugin/pom.xml jclouds-plugin/src/findbugs/excludesFilter.xml jclouds-plugin/src/main/java/org/jclouds/googlecomputeengine/compute/GoogleComputeEngineServiceAdapter.java jclouds-plugin/src/main/java/org/jclouds/googlecomputeengine/compute/config/GoogleComputeEngineServiceContextModule.java jclouds-plugin/src/main/java/org/jclouds/googlecomputeengine/compute/functions/InstanceToNodeMetadata.java jclouds-plugin/src/main/java/org/jclouds/googlecomputeengine/compute/loaders/DiskURIToImage.java pom.xml http://jenkins-ci.org/commit/jclouds-plugin/e4dd1ebebf962d685a1f460e60f2e85db4aa4bfb Log: Fix JENKINS-42005 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42856) Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-42856 Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel Change By: Nick Jones Environment: Windows 2012 R2 master and slaves, Jenkins 2.32.3 LTS, Win32-OpenSSH 0.0.10.0, Cygwin 2.7.0, SSH Slaves plugin 1.14 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42894) Job-dsl-plugin support for envInject plugin
Title: Message Title Andrew Hibbert commented on JENKINS-42894 Re: Job-dsl-plugin support for envInject plugin I receive this error Processing DSL script BuildJenkinsBaseMasterImageDSL.groovy ERROR: (BuildJenkinsBaseMasterImageDSL.groovy, line 27) No signature of method: javaposse.jobdsl.dsl.jobs.FreeStyleJob.envInjectJobProperty() is applicable for argument types: (BuildJenkinsBaseMasterImageDSL$_run_closure1$_closure3) values: [BuildJenkinsBaseMasterImageDSL$_run_closure1$_closure3@60c21744] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42856) Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel
Title: Message Title Nick Jones closed an issue as Not A Defect As this appears to be a bug in Microsoft's OpenSSH port, I'd agree with Stephen Connolly that this is not a bug in Jenkins or its SSH Slaves plugin. I'm happy to have this issue out there documenting that the Cygwin OpenSSH works instead. Jenkins / JENKINS-42856 Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel Change By: Nick Jones Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you a
[JIRA] (JENKINS-42856) Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel
Title: Message Title Stephen Connolly commented on JENKINS-42856 Re: Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel Nick Jones that's great news. Just to clarify, this is not an issue with the ssh-slaves plugin. There is something about the Microsoft port of OpenSSH that prevents it from working. If it was an issue with the ssh-slaves plugin then using a launch method such as: would connect the agent. However, one cannot get that to work with Microsoft's port of OpenSSH. Thus I conclude that the issue is with Microsoft's port of OpenSSH in general. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42856) Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-42856 Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel Change By: Stephen Connolly Attachment: Screen Shot 2017-03-17 at 20.59.21.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42898) Jenkins Swarm jar is added to Maven Project classpath
Title: Message Title Alexander Komarov created an issue Jenkins / JENKINS-42898 Jenkins Swarm jar is added to Maven Project classpath Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: maven-plugin, swarm-plugin Created: 2017/Mar/17 8:50 PM Environment: Master: CentOS 6.8, Oracle JDK 1.7 Slave: CentOS 7, Oracle JDK 1.8.0_121 (both jenkins agent and this job) Jenkins: 2.50 (rpm) Plugin: Jenkins Swarm 3.3 Plugin: Maven Integration 2.15.1 Priority: Minor Reporter: Alexander Komarov Apologies that I don't know whether this is an issue with Swarm or Maven plugin... When a slave started via jenkins swarm runs the main maven project build step (maven itself), the jenkins-swarm.jar (executable jar) is added to the classpath. From what I can tell this has always been the case, but now it is a problem because the new version of the swarm jar (3.3) contains slf4j, and now our maven builds fail due to multiple versions of slf4j classes on the classpath. Since swarm 2.0 jar did not contain slf4j, this was not an issue. Is the jar being added for a reason or am I misconfiguring something? 00:00:38.012 ERROR: Failed to parse POMs 00:00:38.013 java.io.IOException: Remote call on Channel to Maven [/jdk-sun-1.8/bin/java, -XX:MaxPermSize=1024m, -Xmx1024m, -cp, /data/jenkins-slave/maven32-agent.jar:/data/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.5/boot/plexus-classworlds-2.5.2.jar:/data/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.5/conf/logging, jenkins.maven3.agent.Maven32Main, /data/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/Ma
[JIRA] (JENKINS-42897) input step can return a null when approved via link in console output
Title: Message Title Erik Lattimore created an issue Jenkins / JENKINS-42897 input step can return a null when approved via link in console output Issue Type: Bug Assignee: Unassigned Components: pipeline-input-step-plugin Created: 2017/Mar/17 8:48 PM Priority: Minor Reporter: Erik Lattimore We have code similar to: String inputParams = input([message: "Continue with apply?", submitter: "foo,bar", submitterParameter: "approver"]) This all works as expected when the Approve button is clicked in the standard main project page. However, when the link that shows up in the unified Console Output is used to approve the build, inputParams because a null value. Add Comment
[JIRA] (JENKINS-42896) Jenkins Plugin Update page fails if timeout or similar HTTP error occurs.
Title: Message Title Ken Smith created an issue Jenkins / JENKINS-42896 Jenkins Plugin Update page fails if timeout or similar HTTP error occurs. Issue Type: Bug Assignee: Unassigned Components: update-sites-manager-plugin Created: 2017/Mar/17 8:28 PM Priority: Minor Reporter: Ken Smith See stack trace below, that shows up when timeout occurs for "Check for Updates" is run. Check update should be able to log error, but then continue from update site timeout, 404 or similar error. Update check should not just die. java.io.IOException: Server returned HTTP response code: 403 for URL: https://foo.com/fooUpdateSite/update-center.json?id=foo-update&version=2.32.3 at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1876) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) at hudson.model.DownloadService.loadJSON(DownloadService.java:171) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:190) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1619) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175) at org.kohsuke.stapler.Function.bindAndInvok
[JIRA] (JENKINS-37008) Jenkins vSphere cloud plugin does not expose guest info to pipeline
Title: Message Title Richard Meserve commented on JENKINS-37008 Re: Jenkins vSphere cloud plugin does not expose guest info to pipeline I've tried just about every combination I can think of to get the hostname of the VM, including $VSPHERE_HostName, $env.VSPHERE_HostName, env.HostName, env.hostName, VSPHERE.hostName, VSPHERE.HostName, and many others. ip = vSphere buildStep: [$class: 'ExposeGuestInfo', envVariablePrefix: 'VSPHERE', vm: vmName], serverName: "vSphere Server" Yes, it returns the IP, but I also want to get the VM's reported hostname, which is logged as such: [vSphere] Added environmental variable "VSPHERE_HostName" with a value of "feature-beta-testing" This seems like it should be available either via $VSPHERE_HostName, or $env.VSPHERE_HostName. Both return null. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42829) [Regression] Jenkins pipeline start failing in on when/expression clause with custom method call with No such DSL method found among steps
Title: Message Title Florian Mignotet commented on JENKINS-42829 Re: [Regression] Jenkins pipeline start failing in on when/_expression_ clause with custom method call with No such DSL method found among steps Great. I'll try it. Thanks you very much for the workaround. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42829) [Regression] Jenkins pipeline start failing in on when/expression clause with custom method call with No such DSL method found among steps
Title: Message Title
Andrew Bayer commented on JENKINS-42829
Re: [Regression] Jenkins pipeline start failing in on when/_expression_ clause with custom method call with No such DSL method found among steps
So I'm not 100% sure that JENKINS-42753 is going to happen as such - but I've got a workaround for you anyway. Put your methods in a shared library, and then use the shared library via the libraries directive - i.e., for Florian Mignotet's example, first, install the pipeline-utility-steps plugin to get the readJSON step, and then...
vars/checkStagesToRun.groovy
// shared library - vars/checkStagesToRun.groovy in the shared library repo
def call(String stagesParam, String stageToCheck) {
def parameters = readJSON(stagesParam)
def stagesToRun = [
clean: parameters.fabrication.clean,
prepare: parameters.fabrication.prepare,
build: parameters.fabrication.build,
artifacts: parameters.fabrication.artifacts,
qa: parameters.tests.run
]
return stagesToRun[stageToCheck]
}
Next, configure your shared library in Jenkins (see jenkins.io's docs for more info). Let's assume we're calling the library stageChecks and we're going to use the master branch. And then, in your Jenkinsfile:
Jenkinsfile
pipeline {
agent {
label 'linux'
}
libraries {
lib('stageChecks@master')
}
stages {
stage('Clean') {
when {
_expression_ {
checkStagesToRun(params.STAGES, 'clean')
}
}
[...]
That will work. I just tested it. =) It could probably be simplified a bit here and there, but I wanted to get this general workaround to you ASAP.
Add Comment
[JIRA] (JENKINS-42895) Pipeline stage view is not showing the stages visually
Title: Message Title Jenny Huang updated an issue Jenkins / JENKINS-42895 Pipeline stage view is not showing the stages visually Change By: Jenny Huang Summary: Pipeline stage view is not showing the stages visually Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42895) Pipeline stage view is not showing
Title: Message Title Jenny Huang created an issue Jenkins / JENKINS-42895 Pipeline stage view is not showing Issue Type: Bug Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2017/Mar/17 7:27 PM Environment: Windows Priority: Minor Reporter: Jenny Huang The pipeline stage view is not showing up after I switched the git repo from gitLab to gitHub. Add Comment
[JIRA] (JENKINS-11337) Git plugin only triggers a build for one branch
Title: Message Title Mark Waite commented on JENKINS-11337 Re: Git plugin only triggers a build for one branch I'm a little more skeptical of passing parameters because parameter passing has created security issues. You might consider making changes to the plugin to allow the new strategy you create to alter the default behavior for jobs which use that strategy. If the new strategy was being used, then the lower levels of the git plugin would build all revisions, instead of building all revisions which have not yet been built. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42123) No feedback when clicking "connect" when entering Github access key
Title: Message Title Cliff Meyers updated JENKINS-42123 Jenkins / JENKINS-42123 No feedback when clicking "connect" when entering Github access key Change By: Cliff Meyers Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42123) No feedback when clicking "connect" when entering Github access key
Title: Message Title Cliff Meyers commented on JENKINS-42123 Re: No feedback when clicking "connect" when entering Github access key PR: https://github.com/jenkinsci/blueocean-plugin/pull/912 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42504) Pipeline build hangs with "Failed to load build state" due to org.acegisecurity.AccessDeniedException
Title: Message Title spencer malone edited a comment on JENKINS-42504 Re: Pipeline build hangs with "Failed to load build state" due to org.acegisecurity.AccessDeniedException I'm experiencing similar behavior. Anything more information we can provide to help expedite this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42504) Pipeline build hangs with "Failed to load build state" due to org.acegisecurity.AccessDeniedException
Title: Message Title spencer malone commented on JENKINS-42504 Re: Pipeline build hangs with "Failed to load build state" due to org.acegisecurity.AccessDeniedException I'm experiencing similar behavior. Anything more information we can provide to help expedite this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42894) Job-dsl-plugin support for envInject plugin
Title: Message Title Andrew Hibbert commented on JENKINS-42894 Re: Job-dsl-plugin support for envInject plugin In particular the "Evaluated Groovy script" bit Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42857) Multi-line, concatenated-string values aren't parsed/passed in/to "environment" variable
Title: Message Title Stephen Donner commented on JENKINS-42857 Re: Multi-line, concatenated-string values aren't parsed/passed in/to "environment" variable Sorry, yeah :-\ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42894) Job-dsl-plugin support for envInject plugin
Title: Message Title Andrew Hibbert created an issue Jenkins / JENKINS-42894 Job-dsl-plugin support for envInject plugin Issue Type: Bug Assignee: Oleg Nenashev Components: envinject-plugin, job-dsl-plugin Created: 2017/Mar/17 6:04 PM Priority: Minor Reporter: Andrew Hibbert Hi, I would like to create jobs using the envInject plugin using the job-dsl-plugin though this doesn't seem to be supported yet Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42891) Using `vars/pipeline.groovy` causes script-security error starting with Jenkins 2.32.3
Title: Message Title
Torben Knerr updated an issue
Jenkins / JENKINS-42891
Using `vars/pipeline.groovy` causes script-security error starting with Jenkins 2.32.3
Change By:
Torben Knerr
We are using a global lib with `vars/pipeline.groovy` in Jenkins 2.32.1 and everything works fine. When using the same lib with Jenkins 2.32.3 we suddenly get failing pipeline builds with this error: {code:java}org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter doTry org.jenkinsci.plugins.workflow.cps.CpsClosure2) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:183) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:117) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:103) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16) ...{code} The `vars/pipeline.groovy` looks as simple as that: {code:java}def doStuff() {echo "hello!"}{code} And within our `Jenkinsfile` we call it like that: {code:java}node {stage("do stuff") {pipeline.doStuff() // throws above exception }}{code} It pretty much looks like a script-security plugin issue on first sight. (this was updated from 1.25 to 1.27 when we use Jenkins 2.32.3). However, after having simplified our `vars/pipeline.groovy` to such a mininmal helper method example there is really nothing that script security should complain about. But it still does throw the exception above.In a desperate move I renamed `vars/pipeline.groovy` to `vars/wat.groovy`, and guess what? It works... {code:java} node {stage("do stuff") {wat.doStuff() // works!}}{code} So my conclusion is that it must have something to do with either the name `pipeline.groovy`, or simply a variable named `pipeline` being implicitly defined in the global scope with newer Jenkins versions.I'm not sure which component exactly produces the error, so the ones I assigned are the most likely culprits for me.
[JIRA] (JENKINS-42893) Job-dsl-plugin support for parameterized scheduler plugin
Title: Message Title Andrew Hibbert created an issue Jenkins / JENKINS-42893 Job-dsl-plugin support for parameterized scheduler plugin Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin, parameterized-scheduler Created: 2017/Mar/17 6:02 PM Priority: Minor Reporter: Andrew Hibbert Hi, I would like to use parameterized scheduler plugin with job dsl plugin but this doesn't seem to be supported currently Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-s
[JIRA] (JENKINS-42892) Dynamic Choice Parameter support for jenkins-job-dsl
Title: Message Title Andrew Hibbert created an issue Jenkins / JENKINS-42892 Dynamic Choice Parameter support for jenkins-job-dsl Issue Type: Bug Assignee: Daniel Spilker Components: dynamicparameter-plugin, job-dsl-plugin Created: 2017/Mar/17 5:59 PM Priority: Minor Reporter: Andrew Hibbert Hi, I would like to be able to create jobs with Dynamic Choice Parameters, this currently does not seem to be supported by jenkins-job-dsl Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.
[JIRA] (JENKINS-41148) Jenkins Pipeline still uses --force=yes for Docker Pipeline plugin
Title: Message Title Jack Brooks commented on JENKINS-41148 Re: Jenkins Pipeline still uses --force=yes for Docker Pipeline plugin John Hovell, as the other posters point out, this is definitely still an issue, and- at least for me- isn't just a warning or the last message in the log. Hopefully Wojciech Duda's PR will get merged (with any needed changes). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42891) Using `vars/pipeline.groovy` causes script-security error starting with Jenkins 2.32.3
Title: Message Title Torben Knerr created an issue Jenkins / JENKINS-42891 Using `vars/pipeline.groovy` causes script-security error starting with Jenkins 2.32.3 Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin, script-security-plugin, workflow-cps-global-lib-plugin Created: 2017/Mar/17 5:58 PM Environment: Jenkins 2.32.3 LTS, with - script-security 1.27 - workflow-cps-global-lib 2.7 - pipeline-model-definition 1.1.1 Priority: Minor Reporter: Torben Knerr We are using a global lib with `vars/pipeline.groovy` in Jenkins 2.32.1 and everything works fine. When using the same lib with Jenkins 2.32.3 we suddenly get failing pipeline builds with this error: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter doTry org.jenkinsci.plugins.workflow.cps.CpsClosure2) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:183) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:117) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:103) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16) ...
[JIRA] (JENKINS-42152) Docker Pipeline causes build to fails because of use of --force=yes for tagging
Title: Message Title Jack Brooks commented on JENKINS-42152 Re: Docker Pipeline causes build to fails because of use of --force=yes for tagging Wojciech Duda, thanks for creating the PR! This is definitely still an issue. Hopefully we'll see that merged soon. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42829) [Regression] Jenkins pipeline start failing in on when/expression clause with custom method call with No such DSL method found among steps
Title: Message Title Andrew Bayer commented on JENKINS-42829 Re: [Regression] Jenkins pipeline start failing in on when/_expression_ clause with custom method call with No such DSL method found among steps I've added a fix for this to the PR for JENKINS-42753 at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/140 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42829) [Regression] Jenkins pipeline start failing in on when/expression clause with custom method call with No such DSL method found among steps
Title: Message Title Andrew Bayer updated JENKINS-42829 Jenkins / JENKINS-42829 [Regression] Jenkins pipeline start failing in on when/_expression_ clause with custom method call with No such DSL method found among steps Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42829) [Regression] Jenkins pipeline start failing in on when/expression clause with custom method call with No such DSL method found among steps
Title: Message Title Andrew Bayer started work on JENKINS-42829 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42777) Add more Declarative test coverage based on real-world usage
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-42777 Add more Declarative test coverage based on real-world usage Change By: Andrew Bayer For example, these were generously provided by [~stephendonner] and we should go through them to find usage that we don't test but do intend to continue to work:[https://github.com/mozilla/ Addon-Tests/blob/master/Jenkinsfile][https://github.com/mozilla/ socorro/blob/ master 7b12eadb62bbb33cfa5be7adeba85d81d6deacc8 /e2e-tests/Jenkinsfile][https://github.com/mozilla/ treeherder snippets -tests/blob/ master 3dcc6450feb3d3ffa9eb53650e329bbd043e649d /Jenkinsfile][https://github.com/mozilla -services / snippets go - tests bouncer /blob/ master f734f1d55140f36667325900cba2b096a3a9ba09 / tests/e2e/ Jenkinsfile][https://github.com/ mozilla stephendonner /mozillians-tests/blob/ master de22132dfa4a568d5ac28ab00e2b517c317d7d39 /Jenkinsfile] [https://github.com/mozilla-services/go-bouncer/blob/master/tests/e2e/Jenkinsfile] Shared libraries:[https://github.com/mozilla/fxtest-jenkins-pipeline] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-33561) BZ 87056 - Coverity plugin does not use Perforce env variables when adding SCM data
Title: Message Title Joel Briggs closed an issue as Fixed This was reported as resolved by internal customer issue (using plugin version 1.8.1) Jenkins / JENKINS-33561 BZ 87056 - Coverity plugin does not use Perforce env variables when adding SCM data Change By: Joel Briggs Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googl
[JIRA] (JENKINS-42856) Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel
Title: Message Title
Nick Jones updated an issue
Jenkins / JENKINS-42856
Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel
Change By:
Nick Jones
As a first step to being able to use the VMware plugin to spawn slaves automatically, I'm trying to get ssh slave connectivity to work. Normally I use Java Web Start for permanent slaves, which works fine, but I have no way to use that with a dynamic slave (without turning off the connect security and forgoing having a secret in the JNLP command).I've installed the Microsoft SSH port (Win32-OpenSSH) for sshd, and Cygwin to get the "true" utility that Jenkins expects to call, but my attempts to launch the agent fail almost immediately (after copying the slave.jar file), with the following log:{noformat}[03/16/17 14:35:26] [SSH] Opening SSH connection to myserver:22.[03/16/17 14:35:31] [SSH] Authentication successful.[03/16/17 14:35:34] [SSH] The remote users environment is:[03/16/17 14:35:36] [SSH] Starting sftp client.[03/16/17 14:35:39] [SSH] Copying latest slave.jar...[03/16/17 14:36:00] [SSH] Copied 717,563 bytes.Expanded the channel window size to 4MB[03/16/17 14:36:00] [SSH] Starting slave process: cd "C:\Jenkins" && "C:\Program Files\Java\jre1.8.0_121\bin\java" -jar slave.jar<===[JENKINS REMOTING CAPACITY]===><===[JENKINS REMOTING CAPACITY]===>ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins.hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:307) at hudson.remoting.Channel.terminate(Channel.java:888) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:92) at ..remote call to myserver(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:821) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:516) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:389) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:989) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:139) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:738) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:719) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.readShort(Unknown Source) at java.io.ObjectInputStream.readStreamHeader(Unknown Source) at java.io.ObjectInput
[JIRA] (JENKINS-32354) BZ 97113 - Provide support of Coverity runs from Workflow plugin
Title: Message Title Joel Briggs updated an issue Jenkins / JENKINS-32354 BZ 97113 - Provide support of Coverity runs from Workflow plugin Change By: Joel Briggs Summary: BZ 98977 97113 - Provide support of Coverity runs from Workflow plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42856) Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-42856 Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel Change By: Nick Jones Priority: Blocker Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42890) Could not find FROM instruction in Dockerfile.
Title: Message Title
Mateusz Kubaszek created an issue
Jenkins / JENKINS-42890
Could not find FROM instruction in Dockerfile.
Issue Type:
Bug
Assignee:
magnayn
Attachments:
Dockerfile, docker_error.png
Components:
docker-commons-plugin, docker-plugin
Created:
2017/Mar/17 5:28 PM
Environment:
Jenkins 2.49 on Ubuntu 16.04 on Azure VM. Docker Commons Plugin - 1.6 Docker Pipeline - 1.10
Priority:
Major
Reporter:
Mateusz Kubaszek
When building using pipeline definition as follows:
dir('src/MyProject') {
script {
def img = docker.build "mycompany/myproject:v0.0.${env.BUILD_NUMBER}"
docker.withRegistry('https://mycompany.azurecr.io/', 'mycompany.azurecr.io') {
img.push()
img.push 'latest'
}
}
}
The stage fails despite docker image built correctly.
[JIRA] (JENKINS-42856) Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-42856 Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel Change By: Nick Jones Summary: Unable to launch Windows slave with ssh slaves using Microsoft OpenSSH : Unexpected termination of the channel Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38624) BZ 101359 - MSBuild Projects no longer work after upgrading to 1.8.0
Title: Message Title Joel Briggs closed an issue as Fixed Fixed in 1.9.0 Jenkins / JENKINS-38624 BZ 101359 - MSBuild Projects no longer work after upgrading to 1.8.0 Change By: Joel Briggs Status: Reopened Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42889) Enable triggering of remote jobs in parallel
Title: Message Title Sylvia Qi created an issue Jenkins / JENKINS-42889 Enable triggering of remote jobs in parallel Issue Type: Improvement Assignee: Maurice W. Components: parameterized-remote-trigger-plugin Created: 2017/Mar/17 5:26 PM Priority: Major Reporter: Sylvia Qi I am trying to find a way to trigger multiple jobs running on a remote Jenkins server in parallel. Using the parameterized remote trigger plugin, I can only trigger them sequentially which takes very long. The parameterized trigger plugin allows jobs to be triggered in parallel by listing their names separated by commas. This is not allowed in parameterized remote trigger plugin. It would be useful to add this functionality. Another way to trigger remote jobs in parallel could potentially be done via the multijob plugin, but looks like the multijob plugin does not support triggering of remote jobs. Add Comment
[JIRA] (JENKINS-42856) Unable to launch Windows slave with ssh: Unexpected termination of the channel
Title: Message Title Nick Jones commented on JENKINS-42856 Re: Unable to launch Windows slave with ssh: Unexpected termination of the channel I switched to Cygwin's OpenSSH and got this working. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41138) Coverity - Job Failed
Title: Message Title Joel Briggs closed an issue as Fixed Fixed in 1.9.0 Jenkins / JENKINS-41138 Coverity - Job Failed Change By: Joel Briggs Status: Reopened Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42308) BZ 101359 - Command line parsing failed: Unclosed single-quoted string (with Gradle plugin)
Title: Message Title Joel Briggs closed an issue as Fixed Fixed in 1.9.0 Jenkins / JENKINS-42308 BZ 101359 - Command line parsing failed: Unclosed single-quoted string (with Gradle plugin) Change By: Joel Briggs Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/
[JIRA] (JENKINS-38694) BZ 96455 - Jenkins Coverity Plugin has arbitrary defect limit
Title: Message Title Joel Briggs closed an issue as Fixed Fixed in 1.9.0 Jenkins / JENKINS-38694 BZ 96455 - Jenkins Coverity Plugin has arbitrary defect limit Change By: Joel Briggs Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36097) BZ 91929 - coverity-plugin interaction with job-dsl-plugin
Title: Message Title Joel Briggs closed an issue as Fixed Fixed in 1.9.0 Jenkins / JENKINS-36097 BZ 91929 - coverity-plugin interaction with job-dsl-plugin Change By: Joel Briggs Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32672) Jenkins integration with Coverity caught Exception
Title: Message Title Joel Briggs closed an issue as Fixed Fixed in 1.9.0 Jenkins / JENKINS-32672 Jenkins integration with Coverity caught Exception Change By: Joel Briggs Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31508) Coverity results not displayed if "Perform Coverity build, analysis and commit" is not selected
Title: Message Title Joel Briggs closed an issue as Fixed Fixed in 1.9.0 Jenkins / JENKINS-31508 Coverity results not displayed if "Perform Coverity build, analysis and commit" is not selected Change By: Joel Briggs Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.
[JIRA] (JENKINS-33640) BZ 98963 - The coverity plug-in should be able to run for specific build steps only.
Title: Message Title Joel Briggs closed an issue as Fixed Fixed in 1.9.0 Jenkins / JENKINS-33640 BZ 98963 - The coverity plug-in should be able to run for specific build steps only. Change By: Joel Briggs Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optou
