[JIRA] (JENKINS-60174) To be able to inform test version executed
Title: Message Title Roy Lu edited a comment on JENKINS-60174 Re: To be able to inform test version executed Hi [~scuenca],There's no test version concept in ALM. As the test result will be parsed to ALM test set, test and run. What would you like the test version belong to? I mean should it be a field of ALM test set or ALM test or ALM run?Per my understanding, different versions for Junit test may be different tests for ALM test. Correct me if I'm wrong. Or the test version just indicates the version of Junit? BR,Roy Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203134.1573743302000.3069.1574150460133%40Atlassian.JIRA.
[JIRA] (JENKINS-60174) To be able to inform test version executed
Title: Message Title Roy Lu edited a comment on JENKINS-60174 Re: To be able to inform test version executed Hi [~scuenca],There's no test version concept in ALM. As the test result will be parsed to ALM test set, test and run. What would you like the test version belong to? I mean should it be a field of ALM test set or ALM test or ALM run?Per my understanding, different versions for Junit test may be different tests for ALM test. Correct me if I'm wrong. Or the test version just indicates the version of Junit? BR,Roy Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203134.1573743302000.3071.1574150520295%40Atlassian.JIRA.
[JIRA] (JENKINS-60208) I am trying to deploy the code using AWScodedeploy via jenkins . I am getting error while provide the Iam role ARN , which is associated to my instance .Connection test failed w
Title: Message Title kumari Nitu created an issue Jenkins / JENKINS-60208 I am trying to deploy the code using AWScodedeploy via jenkins . I am getting error while provide the Iam role ARN , which is associated to my instance .Connection test failed with error: Unable to execute HTTP request: sts.amazonaws.com Issue Type: Task Assignee: Jan Roehrich Components: amazon-ecs-plugin Created: 2019-11-19 08:01 Priority: Critical Reporter: kumari Nitu Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Yves Schumann commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head We've spot the same today, all our nightly pipelines break with this error: 04:02:41 04:02:40,990 INFO JettyHandler:43 - Got request: /status.xml. Sender is 10.1.53.1:40440 Creating placeholder flownodes because failed loading originals. java.io.IOException: Tried to load head FlowNodes for execution Owner[RT-Jobs/RT-Nightly/9:RT-Jobs/RT-Nightly #9] but FlowNode was not found in storage for head id:FlowNodeId 1:526 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:679) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:716) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:662) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:526) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:501) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:483) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:381) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:899) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:910) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:995) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233) Finished: UNSTABLE Quite annoying as it follows Murphy's Law: Occurs in the exact worst moment... :-/ Add Comment
[JIRA] (JENKINS-57912) Jenkins build fail with emulator issue
Title: Message Title Dragana Stojanovikj commented on JENKINS-57912 Re: Jenkins build fail with emulator issue Same happens to me on CentOS 6.5 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199880.1559914841000.3101.1574152740341%40Atlassian.JIRA.
[JIRA] (JENKINS-58201) com.amazonaws.SdkClientException: Unable to execute HTTP request: sts.amazonaws.com
Title: Message Title kumari Nitu commented on JENKINS-58201 Re: com.amazonaws.SdkClientException: Unable to execute HTTP request: sts.amazonaws.com Can you please tell me what changes you had done Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200257.1561509851000.3124.1574154121524%40Atlassian.JIRA.
[JIRA] (JENKINS-60208) I am trying to deploy the code using AWScodedeploy via jenkins . I am getting error while provide the Iam role ARN , which is associated to my instance .Connection test failed w
Title: Message Title kumari Nitu commented on JENKINS-60208 Re: I am trying to deploy the code using AWScodedeploy via jenkins . I am getting error while provide the Iam role ARN , which is associated to my instance .Connection test failed with error: Unable to execute HTTP request: sts.amazonaws.com Without giving IAM role ARN I am getting Connection test failed with error: Unable to execute HTTP request: s3bucketname.s3.amazonaws.com Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203180.1574150519000.3126.1574154480137%40Atlassian.JIRA.
[JIRA] (JENKINS-60209) jCasC-Groovy not expanding variables
Title: Message Title
Cyril Marin created an issue
Jenkins / JENKINS-60209
jCasC-Groovy not expanding variables
Issue Type:
Improvement
Assignee:
Tomasz Szandała
Components:
configuration-as-code-groovy-plugin
Created:
2019-11-19 09:25
Environment:
Jenkins 2.176.4 OpenJDK Runtime Environment 11.0.5+10-LTS Linux 3.10.0-957.27.2.el7.x86_64 configuration-as-code-groovy-plugin 1.1 Running on OpenShift container platform.
Labels:
plugin jcasc configuration-as-code
Priority:
Minor
Reporter:
Cyril Marin
jCasC-Groovy plugin is not expanding variables from definitions because the feature is not implemented yet. Example:
// Variables not expanded, in the case of jCasC defined variables
groovy:
- url: https://${USER}:${PASS}@web.site.com/path/of/my/resource
groovy:
- script: println("${MY_VARIABLE}")
I made a Pull Request on Github project ==> https://github.com/jenkinsci/configuration-as-code-groovy-plugin/pull/3
[JIRA] (JENKINS-58360) Enabling Permissive Script Security Plugin causes pipelines to appear empty
Title: Message Title Jasmine Nouriel commented on JENKINS-58360 Re: Enabling Permissive Script Security Plugin causes pipelines to appear empty Seeing the same issue in our env: Jenkins 2.190.2 Permissive script plugin 0.5 Is there any workaround/fix for this issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200475.1562331517000.3134.1574155921730%40Atlassian.JIRA.
[JIRA] (JENKINS-58201) com.amazonaws.SdkClientException: Unable to execute HTTP request: sts.amazonaws.com
Title: Message Title kumari Nitu commented on JENKINS-58201 Re: com.amazonaws.SdkClientException: Unable to execute HTTP request: sts.amazonaws.com Failed CodeDeploy post-build step; exception follows. Unable to execute HTTP request: codedeploy.us-east-1.amazonaws.com com.amazonaws.SdkClientException: Unable to execute HTTP request: codedeploy.us-east-1.amazonaws.com at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleRetryableException(AmazonHttpClient.java:1116) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1066) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200257.1561509851000.3143.1574156521159%40Atlassian.JIRA.
[JIRA] (JENKINS-58201) com.amazonaws.SdkClientException: Unable to execute HTTP request: sts.amazonaws.com
Title: Message Title kumari Nitu commented on JENKINS-58201 Re: com.amazonaws.SdkClientException: Unable to execute HTTP request: sts.amazonaws.com Failed CodeDeploy post-build step; exception follows. Unable to execute HTTP request: codedeploy.us-east-1.amazonaws.com com.amazonaws.SdkClientException: Unable to execute HTTP request: codedeploy.us-east-1.amazonaws.com at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleRetryableException(AmazonHttpClient.java:1116) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1066) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200257.1561509851000.3150.1574156761387%40Atlassian.JIRA.
[JIRA] (JENKINS-57727) ConcurrentModificationException from lock step
Title: Message Title James Withers commented on JENKINS-57727 Re: ConcurrentModificationException from lock step Getting the same issue for Jenkins 2.190.2 and Lockable Resources Plugin2.7. Has happened a few times and seems to be happening when many jobs have started at the same time and they are all trying to use the lock step. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199670.155908000.3146.1574156761080%40Atlassian.JIRA.
[JIRA] (JENKINS-60210) Whitelist all java.util.Collections methods
Title: Message Title Hari Dara created an issue Jenkins / JENKINS-60210 Whitelist all java.util.Collections methods Issue Type: Improvement Assignee: Hari Dara Components: script-security-plugin Created: 2019-11-19 09:49 Priority: Minor Reporter: Hari Dara We currently only have Collections.sort whiltelisted, but every method in this class is a static utility method that is safe. Also need to whitelist a couple of Throwable.printStackTrace variations. JENKINS-57344 already whitelisted a few java.io methods to make it possible to write to a StringWriter, so together this will make it possible to log more detailed error messages that include exception stacktraces and make it easier to troubleshoot some issues. Add Comment
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Thomas M commented on JENKINS-50429 Re: Shell command are really slower than before The PR applies to a specific plugin. I can't pin it down to a specific plugin. https://github.com/jenkinsci/kubernetes-plugin/pull/425/files seems to use reflection to make a general change to the java runtime. I would like to try that, but I don't know how to apply it. Do I have to develop a dummy plugin or can I otherwise hook into the runtime? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189484.1522154059000.3154.1574157120598%40Atlassian.JIRA.
[JIRA] (JENKINS-60210) Whitelist all java.util.Collections methods
Title: Message Title Hari Dara commented on JENKINS-60210 Re: Whitelist all java.util.Collections methods PR: https://github.com/jenkinsci/script-security-plugin/pull/280 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203182.1574156994000.3170.1574157302426%40Atlassian.JIRA.
[JIRA] (JENKINS-60210) Whitelist all java.util.Collections methods
Title: Message Title Hari Dara updated JENKINS-60210 Jenkins / JENKINS-60210 Whitelist all java.util.Collections methods Change By: Hari Dara Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203182.1574156994000.3172.1574157303109%40Atlassian.JIRA.
[JIRA] (JENKINS-60210) Whitelist all java.util.Collections methods
Title: Message Title Hari Dara started work on JENKINS-60210 Change By: Hari Dara Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203182.1574156994000.3171.1574157302940%40Atlassian.JIRA.
[JIRA] (JENKINS-59952) Whitelist request for regex.MatchResult methods
Title: Message Title Hari Dara closed an issue as Fixed I see a new release (1.67) after the merge, so assuming that this is now released and so can be closed. Jenkins / JENKINS-59952 Whitelist request for regex.MatchResult methods Change By: Hari Dara Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202756.1572184004000.3173.1574157600477%40Atlassian.JIRA.
[JIRA] (JENKINS-37557) Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs
Title: Message Title Francois Ferrand updated JENKINS-37557 Jenkins / JENKINS-37557 Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs Change By: Francois Ferrand Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173669.1471622564000.3184.1574158082926%40Atlassian.JIRA.
[JIRA] (JENKINS-37557) Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs
Title: Message Title
Francois Ferrand updated JENKINS-37557
Solution available in repo 1.10 release, by explicitely specifying the 'extraEnvVars' argument:
sshAgent(['gerrit-ssh-credentials-id']) {
checkout([$class: 'RepoScm', manifestRepositoryUrl: 'ssh://server/project',
extraEnvVars: getContext(hudson.EnvVars)])
}
Jenkins / JENKINS-37557
Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs
Change By:
Francois Ferrand
Status:
Open Fixed but Unreleased
Assignee:
Francois Ferrand
Resolution:
Fixed
Released As:
https://github.com/jenkinsci/repo-plugin/releases/tag/repo-1.11.0
Add Comment
[JIRA] (JENKINS-58201) com.amazonaws.SdkClientException: Unable to execute HTTP request: sts.amazonaws.com
Title: Message Title vanchinathan lokanathan commented on JENKINS-58201 Re: com.amazonaws.SdkClientException: Unable to execute HTTP request: sts.amazonaws.com Hi kumari Nitu, Actually there was AWS credentials in the Jenkins server that was referred in the 'Jenkinsfile', which caused this issue. After setting the correct user credentials this problem was gone. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200257.1561509851000.3192.1574158560990%40Atlassian.JIRA.
[JIRA] (JENKINS-47337) More than one PrimaryOwner
Title: Message Title Alexander Ukhanov commented on JENKINS-47337 Re: More than one PrimaryOwner This case can be solved by setting a secondary owner with the same as PrimaryOwner rights. But for more flexibility it would be nice to implement item-specific security on folders (https://issues.jenkins-ci.org/browse/JENKINS-47595) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185766.1507494955000.3203.1574159280162%40Atlassian.JIRA.
[JIRA] (JENKINS-38479) Grade Plugin: Fix Documentation of the "Root Build script" attribute
Title: Message Title Stefan Wolf updated JENKINS-38479 Jenkins / JENKINS-38479 Grade Plugin: Fix Documentation of the "Root Build script" attribute Change By: Stefan Wolf Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174661.1474685886000.3223.1574161860585%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Steffen Seckler commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline from what I see, the files in the json test directory can give very good hints: https://github.com/jenkinsci/pipeline-model-definition-plugin/tree/master/pipeline-model-definition/src/test/resources/json/matrix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3244.1574165281071%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Serhii Shepel commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Ah right! Thanks Steffen Seckler Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3278.1574165461474%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Denis Dudarev commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Thank you for great feature! I could only see 2 axis cases in tests and json files. Is this a limit for there? Anyway I need better instructions to check it out. For example - sample Jenkinsfile with 3axis build would be very useful. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3326.1574165581025%40Atlassian.JIRA.
[JIRA] (JENKINS-58201) com.amazonaws.SdkClientException: Unable to execute HTTP request: sts.amazonaws.com
Title: Message Title kumari Nitu commented on JENKINS-58201 Re: com.amazonaws.SdkClientException: Unable to execute HTTP request: sts.amazonaws.com I don't have access and secret key. In that case what can be the issue , I have created IAM role and attached to the instance where I want to deploy with s3 and Ec2 full access. I trying for Deploy using code deploy via s3 bucket. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200257.1561509851000.3360.1574165760951%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Denis Dudarev commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Hm. I've reviewed json file more detailed. It seems to be quite agile implementation, covering most of cases above. So what I need (and most users I believe) is a Jenkinsfile example, to review end-user syntax. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3363.1574165821332%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Andrew Bayer commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline https://github.com/jenkinsci/pipeline-model-definition-plugin/tree/master/pipeline-model-definition/src/test/resources/matrix has a whole bunch of Jenkinsfile examples/test cases. =) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3396.1574167200820%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Denis Dudarev commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Got it, thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3453.1574167860979%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Denis Dudarev commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Results of my humble review: It seems to be usable, it covers user cases Excludes syntax is quite huge, but I have no fast good idea for much compact one without imperative expressions from original matrix functionality, it could be very annoying to avoid all uninterested combinations with axis count >2, especially in cases where *most* of combinations are uninterested (e.g. at the start of a project) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3486.1574168401398%40Atlassian.JIRA.
[JIRA] (JENKINS-60175) To be able to define test cases in hierarchy folder
Title: Message Title Sergio Cuenca commented on JENKINS-60175 Re: To be able to define test cases in hierarchy folder Hi Roy!! Let’s imagine we have this structure in the test plan (this structure has been created manually, defining test folders and test cases): · Automated tests/ o Module 1/ § Module 1_Test A § Module 1_Test B o Module 2/ § Module 2_Test C o Module 3/ § Module 3_Test D Each test case has been correctly defined inside ALM manually, and all of them have their steps and all the required atributes. Then, I use this XML file to load a test execution done with an external tool: 9.0020 Module 1 Test A false 0 36.0010 Module 1 Test B false 0 0.576 When tests executions are loaded in ALM, the test plan folder have the following structure: · Automated tests/ o Module 1_Test A o Module 1_Test B o Module 1/ § Module 1_Test A § Module 1_Test B o Module 2/ § Module 2_Test C o Module 3/ § Module 3_Test D Module 1_Test A and Module 1_Test B are duplicated within the Test Plan structure and this is a problem for us. We want that the plugin recognizes that they already exist inside folder Automated tests / Module 1.
[JIRA] (JENKINS-60071) [JenkinsPlugin][MC3.3][UFT14.03]The UFT cannot be launched
Title: Message Title Maria Narcisa Galan updated an issue Jenkins / JENKINS-60071 [JenkinsPlugin][MC3.3][UFT14.03]The UFT cannot be launched Change By: Maria Narcisa Galan Labels: UFTM Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202905.1573021329000.3520.1574168820250%40Atlassian.JIRA.
[JIRA] (JENKINS-59989) Cannot Run Tests from ALM after upgrading to 5.8
Title: Message Title Maria Narcisa Galan updated an issue Jenkins / JENKINS-59989 Cannot Run Tests from ALM after upgrading to 5.8 Change By: Maria Narcisa Galan Labels: UFT Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202796.1572457328000.3523.1574168880426%40Atlassian.JIRA.
[JIRA] (JENKINS-60174) To be able to inform test version executed
Title: Message Title Sergio Cuenca commented on JENKINS-60174 Re: To be able to inform test version executed We use the field “Version Number” of the Test Case which is a OOB field (TS_VC_VERSION_NUMBER). It indicates the version of the test case. Our scenario is: 1. Let’s imagine we have a test case, called Test X. The test X has 3 versions (it has been modified through the time to modify steps, add more steps, or remove some steps, I don’t care). 2. Then, we have the version 2.0 automated in an external automation tool. 3. We execute the version 2.0 of the test in the external automation tool and we want to load these results in ALM. 4. Currently, when we load the results, the “Version Number” inside the Test Instance, is empty, So we don’t know to which version of the test case this execution corresponds to. 5. So, what we need is to be able to spcify the Version Number inside the XML and load this information. Something like that: XML result Changes file Changes Test Set 2.293 8.293 ChangesManagement List changes 2.0 false 0 0.576
[JIRA] (JENKINS-49707) Auto retry for elastic agents after channel closure
Title: Message Title Andrey Babushkin commented on JENKINS-49707 Re: Auto retry for elastic agents after channel closure We use kubernetes plugin with our bare-metal kubernetes cluster and the problem is that pipeline can run indefinitely if agent inside pod were killed/underlying node was restarted. Is there any option to tweak such behavior, e.g. some timeout settings (except explicit timeout step)? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188646.1519349293000.3530.1574169602160%40Atlassian.JIRA.
[JIRA] (JENKINS-60211) Jenkins slave is showining offline mode
Title: Message Title siva prasad created an issue Jenkins / JENKINS-60211 Jenkins slave is showining offline mode Issue Type: Bug Assignee: Unassigned Components: slave-status-plugin Created: 2019-11-19 13:31 Priority: Critical Reporter: siva prasad We are using one master server two slaves one slave it is working fine while try to launch second slave we are facing error please find error below. Thanks, Siva Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60211) Jenkins slave is showining offline mode
Title: Message Title siva prasad updated an issue Jenkins / JENKINS-60211 Jenkins slave is showining offline mode Change By: siva prasad Attachment: slave error1.PNG Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203184.157417026.3572.1574170380236%40Atlassian.JIRA.
[JIRA] (JENKINS-60211) Jenkins slave is showining offline mode
Title: Message Title siva prasad updated an issue Jenkins / JENKINS-60211 Jenkins slave is showining offline mode Change By: siva prasad Attachment: slave error.PNG Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203184.157417026.3571.1574170380154%40Atlassian.JIRA.
[JIRA] (JENKINS-60211) Jenkins slave is showining offline mode
Title: Message Title siva prasad updated an issue Jenkins / JENKINS-60211 Jenkins slave is showining offline mode Change By: siva prasad We are using one master server two slaves one slave it is working fine while try to launch second slave we are facing error please find error below . Please find attachments !image-2019-11-19-18-57-11-510.png|width=450,height=103! !image-2019-11-19-18-59-34-627.png|width=495,height=122! Thanks, Siva Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203184.157417026.3580.1574170860075%40Atlassian.JIRA.
[JIRA] (JENKINS-60211) Jenkins slave is showing offline mode
Title: Message Title siva prasad updated an issue Jenkins / JENKINS-60211 Jenkins slave is showing offline mode Change By: siva prasad Summary: Jenkins slave is showining showing offline mode Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203184.157417026.3581.1574170980201%40Atlassian.JIRA.
[JIRA] (JENKINS-60212) Unstash pipeline step hangs intermittently
Title: Message Title Megan Smith created an issue Jenkins / JENKINS-60212 Unstash pipeline step hangs intermittently Issue Type: Bug Assignee: Jie Shen Components: azure-artifact-manager-plugin Created: 2019-11-19 14:26 Priority: Blocker Reporter: Megan Smith Jenkins: 2.190.1 Azure Artifact Manager plugin: 2.121.3 Running a build with several parallel steps the unstash step for an Azure-stored artifact hangs indefinitely. This blocks the usage of this plugin, at least in out case. Stack traces after aborting one of the jobs: 16:56:32 java.lang.InterruptedException16:56:32 java.lang.InterruptedException16:56:32 at java.lang.Object.wait(Native Method)16:56:32 at hudson.remoting.Request.call(Request.java:177)16:56:32 at hudson.remoting.Channel.call(Channel.java:956)16:56:32 at hudson.FilePath.act(FilePath.java:1072)16:56:32 at hudson.FilePath.act(FilePath.java:1061)16:56:32 at hudson.FilePath.untarFrom(FilePath.java:800)16:56:32 at com.microsoft.jenkins.artifactmanager.AzureArtifactManager.unstash(AzureArtifactManager.java:281)16:56:32 at org.jenkinsci.plugins.workflow.flow.StashManager.unstash(StashManager.java:158)16:56:32 at org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:76)16:56:32 at org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:63)16:56:32 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)16:56:32 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)16:56:32 at java.util.concurrent.FutureTask.run(FutureTask.java:266)16:56:32 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)16:56:32 at java.util.concurrent.ThreadPoolExecuto
[JIRA] (JENKINS-60212) Unstash pipeline step hangs frequently
Title: Message Title Megan Smith updated an issue Jenkins / JENKINS-60212 Unstash pipeline step hangs frequently Change By: Megan Smith Summary: Unstash pipeline step hangs intermittently frequently Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203185.1574173604000.3591.1574173680167%40Atlassian.JIRA.
[JIRA] (JENKINS-41805) Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace.
Title: Message Title Alexander Samoylov commented on JENKINS-41805 Re: Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace. Baptiste Mathus wrote: "Not a bug by the way, more an improvement." I strongly disagree. Jenkins creates the @tmp automatically and stores there temporary files. Therefore it should be removed also automatically by Jenkins. Each tool that produces temporary data should be responsible for its removal. It is easy as ABC. Following your logic, memory leaks are also "not a bugs"... +1 for the fix (which must be trivial) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178650.1486474486000.3679.1574176323618%40Atlassian.JIRA.
[JIRA] (JENKINS-60188) Windows JNLP Agent SSLException
Title: Message Title Ram krish closed an issue as Fixed Jenkins / JENKINS-60188 Windows JNLP Agent SSLException Change By: Ram krish Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203151.157383253.3681.1574176560334%40Atlassian.JIRA.
[JIRA] (JENKINS-41805) Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace.
Title: Message Title Alexander Samoylov edited a comment on JENKINS-41805 Re: Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace. [~batmat] wrote: "Not a bug by the way, more an improvement."I strongly disagree. Jenkins creates the @tmp automatically and stores there temporary files. Therefore it should be removed also automatically by Jenkins.Each tool that produces temporary data should be responsible for its removal. It is easy as ABC.Following your logic, memory leaks are also "not a bugs"...+1 for the fix (which must be trivial) Update: I confirm that the workaround dir() { deleteDir() } is working. Luckily it does not create the nested @tmp@tmp. Thank you, [~vanaken]. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178650.1486474486000.3683.1574177641848%40Atlassian.JIRA.
[JIRA] (JENKINS-41805) Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace.
Title: Message Title Alexander Samoylov edited a comment on JENKINS-41805 Re: Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace. [~batmat] wrote: "Not a bug by the way, more an improvement."I strongly disagree. Jenkins creates the @tmp automatically and stores there temporary files. Therefore it should be removed also automatically by Jenkins.Each tool that produces temporary data should be responsible for its removal. It is easy as ABC.Following your logic, memory leaks are also "not a bugs"...+1 for the fix (which must be trivial)Update: I confirm that the workaround dir(+ '@tmp' ) { deleteDir() } is working. Luckily it does not create the nested @tmp@tmp. Thank you, [~vanaken]. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178650.1486474486000.3833.1574177646038%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title
James Bateman created an issue
Jenkins / JENKINS-60213
P4 environment variables non-reentrant
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2019-11-19 16:14
Priority:
Minor
Reporter:
James Bateman
Version 1.10.6 of the p4-plugin causes issues when multiple jobs are ran in parallel. The result is that the p4 created environment variables of one job can corrupt those in another job that is running at the same time. This bug wasn't in 1.10.5 Steps to reproduce issue:
Create a new Jenkins test job with the following settings
General:
Execute concurrent builds if necessary
Use custom workspace
Directory
/tmp/${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title James Bateman updated an issue Jenkins / JENKINS-60213 P4 environment variables non-reentrant Change By: James Bateman Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203186.1574180065000.3835.1574180580340%40Atlassian.JIRA.
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title James Bateman updated an issue Jenkins / JENKINS-60142 ConnectionHelper.java constructors call connectionRetry() Change By: James Bateman Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203003.1573562093000.3837.1574180580518%40Atlassian.JIRA.
[JIRA] (JENKINS-60141) Excessive number of "login -s" requests
Title: Message Title James Bateman updated an issue Jenkins / JENKINS-60141 Excessive number of "login -s" requests Change By: James Bateman Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203002.157355793.3840.1574180640359%40Atlassian.JIRA.
[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title
Eugene Koval commented on JENKINS-59636
Re: timestamper shows wrong time on [View as plain text] link
+1 I guess the plain text log (shown by "View as plaint text" button) just shows the UTC time, while my Jenkins server system time is UTC+2. I understand the need to store one universal time (which then can be displayed differently for different users in different timezones), but that universal time has really got to be the Jenkins server system time, not UTC time. Reason: Jenkins time at least makes sense to Jenkins admins and has a chance of being intuitive for users ("this timestamp is wrong! => why? => maybe it's server time, not my time"), while UTC is meaningless for anyone who does not happen to live in UTC+0 timezone just by chance. Jenkins: 2.190.2 Timestamper plugin: 1.10
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202318.1570086045000.3844.1574181300246%40Atlassian.JIRA.
[JIRA] (JENKINS-60147) Artifactory Plugin doesn't run in a freestyle job with a Maven Build Step.
Title: Message Title Jed Jacobs closed an issue as Not A Defect User error – sorry. Jenkins / JENKINS-60147 Artifactory Plugin doesn't run in a freestyle job with a Maven Build Step. Change By: Jed Jacobs Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https:/
[JIRA] (JENKINS-60188) Windows JNLP Agent SSLException
Title: Message Title Jeff Thompson commented on JENKINS-60188 Re: Windows JNLP Agent SSLException Ram krish, did you figure out your problem here? If it's a configuration issue others may encounter it might help if you could describe the situation and resolution in case others run into it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203151.157383253.3856.1574182920143%40Atlassian.JIRA.
[JIRA] (JENKINS-41377) Polling has not run yet, although received push event
Title: Message Title Tim Tippens commented on JENKINS-41377 Re: Polling has not run yet, although received push event Is the necessary manual trigger of the first job considered a bug or a "feature" we will have to document and live with for the foreseeable future? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178159.148527334.3862.1574184780600%40Atlassian.JIRA.
[JIRA] (JENKINS-49500) In every pipeline build with triggers, a new trigger is created and the old one is stopped
Title: Message Title Liam Newman commented on JENKINS-49500 Re: In every pipeline build with triggers, a new trigger is created and the old one is stopped Now https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/365 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188392.1518430561000.3874.1574185080290%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title Karl Wirth commented on JENKINS-60213 Re: P4 environment variables non-reentrant Hi James Bateman - Thanks for letting us know. This looks like a freestyle job. Is that correct? Please also attach the code you are using to display the variables. Thanks in advance, Karl Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203186.1574180065000.3877.1574185200141%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Mark Waite commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Olivier Lamy is this likely a result of the upgrade to Jetty 9.4.22? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203169.1574080196000.3880.1574186820281%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules If shallow clone for the submodule is activated this error happens on my side. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3886.1574188860258%40Atlassian.JIRA.
[JIRA] (JENKINS-58539) Tool always exits with value of 1
Title: Message Title Natasha Stopa updated JENKINS-58539 Jenkins / JENKINS-58539 Tool always exits with value of 1 Change By: Natasha Stopa Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200688.1563427958000.3887.1574189940097%40Atlassian.JIRA.
[JIRA] (JENKINS-60214) Plugin installation manager does not work with Cloudbees update site
Title: Message Title leemeador created an issue Jenkins / JENKINS-60214 Plugin installation manager does not work with Cloudbees update site Issue Type: Improvement Assignee: leemeador Components: plugin-installation-manager-tool Created: 2019-11-19 19:01 Labels: plugin-manager Priority: Minor Reporter: leemeador I've found that jenkins-plugin-manager-1.0.1 fails when used against the Cloudbees update center because that site has no update-center.actual.json file available there. There is an update-center.json. The actual file has pure json content while the non-actual file has a wrapper around the json "updateCenter.post( ... json goes here ... );" Someone said that has to do with allowing the file to be more easily compatible with browsers use of _javascript_. I don't know if the best thing is to get Cloudbees to add the non-actual file or change the code to remove the wrapper text in in the non-actual file and use it. Add Comment
[JIRA] (JENKINS-60215) Show ssh public keys in ssh key editing ui
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60215 Show ssh public keys in ssh key editing ui Issue Type: New Feature Assignee: Unassigned Components: core Created: 2019-11-19 19:01 Priority: Minor Reporter: Josh Soref visit http://jenkins/credentials/store/system/domain/_/ click the wrench for a SSH Username with private key item Actual results: Scope ID Description Username Private Key Enter directly Key Concealed for Confidentiality [Replace] Passphrase Expected results: Private Key should be Key, and under Enter directly, there should be a Public Key showing the current calculated Public Key. The item currently labeled as Key should be renamed Private Key. See also JENKINS-56940
[JIRA] (JENKINS-60202) Error when --Jenkins-update-manager value has trailing slash
Title: Message Title Natasha Stopa updated an issue Jenkins / JENKINS-60202 Error when --Jenkins-update-manager value has trailing slash Change By: Natasha Stopa Labels: newbie-friendly plugin-manager Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203173.1574098577000.3891.1574190120498%40Atlassian.JIRA.
[JIRA] (JENKINS-59173) Add Compatibility with Java 11
Title: Message Title Natasha Stopa updated an issue Jenkins / JENKINS-59173 Add Compatibility with Java 11 Change By: Natasha Stopa Labels: newbie-friendly plugin-manager Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201610.156736835.3892.1574190120543%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules If shallow clone for the submodule is activated this error happens on my side. It has to be a clean build. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3894.1574190360170%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60204 git plugin 4.0.0 can not shallow clone a submodule Change By: Mark Waite Summary: git plugin 4.0.0 can not handle submodules shallow clone a submodule Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3900.1574190720218%40Atlassian.JIRA.
[JIRA] (JENKINS-60202) Error when --Jenkins-update-manager value has trailing slash
Title: Message Title Natasha Stopa assigned an issue to leemeador Jenkins / JENKINS-60202 Error when --Jenkins-update-manager value has trailing slash Change By: Natasha Stopa Assignee: Natasha Stopa leemeador Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203173.1574098577000.3902.1574190720248%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Mark Waite commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule René Scheibe was shallow clone for submodules an area that you submitted in 4.0.0, or was that someone else? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3904.1574190840123%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule If shallow clone for the submodule is activated this error happens on my side. It has to be a clean build. Additionally: If i activate shallow clone and the build fails the submodule-folder has just a .git. If i deactivate shallow clone again it will still fail, until i wipe the workspace again. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3906.1574191980140%40Atlassian.JIRA.
[JIRA] (JENKINS-49707) Auto retry for elastic agents after channel closure
Title: Message Title Jesse Glick commented on JENKINS-49707 Re: Auto retry for elastic agents after channel closure Andrey Babushkin that should have already been fixed—see linked PRs. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188646.1519349293000.3908.1574192041032%40Atlassian.JIRA.
[JIRA] (JENKINS-60216) Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-60216
Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible
Change By:
Devin Nusbaum
The Pipeline {{build}} step does not validate that the types of parameters passed to the step match the parameter types defined on the downstream job. This leads to situations like users passing a string parameter ("true") when a boolean parameter is expected, or a string parameter where a password is expected, etc. Parameterized-trigger plugin made a change long ago to automatically convert some kinds of parameter type mismatches, see https://github.com/jenkinsci/parameterized-trigger-plugin/pull/62.The {{build}} step should be updated to perform the same conversion logic, and log a warning when such a conversion occurs.In some cases, a conversion is not possible/sensible (i.e. converting a password parameter to a boolean parameter). The {{build}} step does not currently attempt to prevent these kinds of mismatches, and this issue is not about changing that behavior (but perhaps it would make sense to fail the build or log a warning when that happens, perhaps hidden behind an option or system property).
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60216) Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible
Title: Message Title
Devin Nusbaum created an issue
Jenkins / JENKINS-60216
Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible
Issue Type:
Improvement
Assignee:
Devin Nusbaum
Components:
pipeline-build-step-plugin
Created:
2019-11-19 20:07
Priority:
Minor
Reporter:
Devin Nusbaum
The Pipeline build step does not validate that the types of parameters passed to the step match the parameter types defined on the downstream job. This leads to situations like users passing a string parameter ("true") when a boolean parameter is expected, or a string parameter where a password is expected, etc. Parameterized-trigger plugin made a change long ago to automatically convert some kinds of parameter type mismatches, see https://github.com/jenkinsci/parameterized-trigger-plugin/pull/62. The build step should be updated to perform the same conversion logic, and log a warning when such a conversion occurs. In some cases, a conversion is not possible/sensible (i.e. converting a password parameter to a boolean parameter). The build step does not currently attempt to prevent these kinds of mismatches, and this issue is not about changing that behavior (but perhaps it would make sense to fail the build or log a warning when that happens, perhaps hidden behind an option or system property).
[JIRA] (JENKINS-60216) Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible
Title: Message Title Devin Nusbaum started work on JENKINS-60216 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203189.1574194043000.3956.1574194207681%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title René Scheibe commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule Benjamin Brummer can you reproduce this error with a) only a specific private git repository or b) also with an open source one from GitHub? Can you provide the full XML of the configured job here (maybe with redacted repository URL and credentials)? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3955.1574194207660%40Atlassian.JIRA.
[JIRA] (JENKINS-60216) Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible
Title: Message Title Devin Nusbaum updated JENKINS-60216 Jenkins / JENKINS-60216 Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203189.1574194043000.3957.1574194207711%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title René Scheibe edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule [~benbrummer] can you reproduce this error with a) only a specific private git repository or b) also with an open source one from GitHub?Can you provide the full XML of the configured job here and a stripped down Jenkinsfile (maybe with redacted repository URL and credentials)? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3959.1574195040390%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Mark Waite commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule René Scheibe I have enabled shallow clone for the parent repository and for the submodule update in my JENKINS-60204 check job. It works as expected and does not show any failure. I still am unable to duplicate the problem as reported by Benjamin Brummer. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3963.1574195940166%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer updated an issue Jenkins / JENKINS-60204 git plugin 4.0.0 can not shallow clone a submodule Change By: Benjamin Brummer Attachment: works.xml Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3966.1574196000212%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule I tried to reproduce it with a public repo without success, so a) only private repo. works.xml fail.xml Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3970.1574196060963%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer updated an issue Jenkins / JENKINS-60204 git plugin 4.0.0 can not shallow clone a submodule Change By: Benjamin Brummer Attachment: fail.xml Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3969.1574196060888%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule I tried to reproduce it with a public repo without success, so a) only private repo.[^works.xml][^fail.xml] ^[^fail.log]^ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3975.1574196420150%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title René Scheibe commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule Mark Waite yes I have been involved in the shallow submodule update - see https://github.com/jenkinsci/git-plugin/pull/610 https://github.com/jenkinsci/git-plugin/pull/614 I also cleaned up the original parallel submodule update implementation - see https://github.com/jenkinsci/git-client-plugin/pull/352 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3977.1574197560158%40Atlassian.JIRA.
[JIRA] (JENKINS-59115) When condition for Branch build with comparator
Title: Message Title Victor Martinez resolved as Fixed Jenkins / JENKINS-59115 When condition for Branch build with comparator Change By: Victor Martinez Status: Open Resolved Resolution: Fixed Released As: 1.4.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201541.1566975845000.3979.1574197800225%40Atlassian.JIRA.
[JIRA] (JENKINS-60217) When condition for Changeset with comparator
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-60217 When condition for Changeset with comparator Change By: Victor Martinez Released As: 1.4.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203190.157419779.3982.1574197860215%40Atlassian.JIRA.
[JIRA] (JENKINS-60217) When condition for Changeset with comparator
Title: Message Title
Victor Martinez created an issue
Jenkins / JENKINS-60217
When condition for Changeset with comparator
Issue Type:
New Feature
Assignee:
Victor Martinez
Components:
pipeline-model-definition-plugin
Created:
2019-11-19 21:09
Priority:
Minor
Reporter:
Victor Martinez
https://issues.jenkins-ci.org/browse/JENKINS-48523 added support to the tag when condition with the comparator. At the moment, the branch when condition does support GLOB, but no REGEXP patterns. Let's standardize the branch condition format as done with the tag condition.
when {
branch "release-*"
}
when {
branch pattern: "release-*", comparator: "GLOB"
}
when {
branch pattern: "release-\\d+", comparator: "REGEXP"
}
Add Comment
[JIRA] (JENKINS-60217) When condition for Changeset with comparator
Title: Message Title
Victor Martinez updated an issue
Jenkins / JENKINS-60217
When condition for Changeset with comparator
Change By:
Victor Martinez
https://issues.jenkins-ci.org/browse/JENKINS-48523 added support to the tag when condition with the comparator. At the moment, the branch changeset when condition does support GLOB, but no REGEXP patterns. Let's standardize the branch changeset condition format as done with the tag condition.{code:java} when { branch changeset " release- * */*.java "}when { branch changeset pattern: " release- * */*.java ", comparator: "GLOB"} when { branch changeset pattern: " release- .* \\ d+ .java ", comparator: "REGEXP"} {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule I checked the submodule again updated it to a different commit already and now i removed it, added it again => it looks like it is working now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3985.1574198581476%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule I checked the submodule again updated it to a different commit already and now .Now i removed it, added it again => it looks like it is working now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3988.1574198700193%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule I checked the submodule again updated it to a different commit already.Now i removed it, added it again => it looks like it is working now. No clue what is going on. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3991.1574198880148%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title René Scheibe commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule I was first with confused by the the description that shallow submodule updates are used but the logged command didn't contain --depth=1. I guess it was edited somehow. > git submodule update --remote impl/tool_protec # timeout=10 The provided fail.log contains the proper command logged > git submodule update --remote --reference C:\jenkins\repo\submodule.git --depth=1 tool_protec # timeout=10 The reported git issue is not an issue of the new git-plugin 4.0.0. hudson.plugins.git.GitException: Command "git submodule update --remote --reference C:\jenkins\repo\submodule.git --depth=1 tool_protec" returned status code 1: stdout: stderr: Cloning into 'C:/jenkins/workspace/submoduletest/master/tool_protec'... fatal: Needed a single revision Unable to find current origin/development revision in submodule path 'tool_protec' You should also be able to reproduce it on the command line without Jenkins and this plugin involved. It's due to the fact that only fetching a single commit from the submodule repository but wanting to resolve the "origin/development" revision which is I guess not the latest commit. You can find plenty of such failed updates reported when searching the Internet for "git submodule update Unable to find current revision in submodule path". The other issue reported in the logs is I guess due to some invalid usage in the Jenkinsfile. Please double check this. Error when executing always post condition: org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing Does this sound reasonable to you Benjamin Brummer?
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title
René Scheibe edited a comment on JENKINS-60204
Re: git plugin 4.0.0 can not shallow clone a submodule
I was first with confused by the the description that shallow submodule updates are used but the logged command didn't contain {{--depth=1}}. I guess it was edited somehow or some intermediate setup while trying to reproduce the relevant job settings .{code :java } > git submodule update --remote impl/tool_protec # timeout=10{code} The provided fail.log contains the proper command logged{code :java } > git submodule update --remote --reference C:\jenkins\repo\submodule.git --depth=1 tool_protec # timeout=10{code} The reported git issue is not an issue of the new git-plugin 4.0.0.{code :java }hudson.plugins.git.GitException: Command "git submodule update --remote --reference C:\jenkins\repo\submodule.git --depth=1 tool_protec" returned status code 1:stdout:stderr: Cloning into 'C:/jenkins/workspace/submoduletest/master/tool_protec'...fatal: Needed a single revisionUnable to find current origin/development revision in submodule path 'tool_protec'{code}You should also be able to reproduce it on the command line without Jenkins and this plugin involved. It's due to the fact that only fetching a single commit from the submodule repository but wanting to resolve the "origin/development" revision which is I guess not the latest commit. You can find plenty of such failed updates reported when searching the Internet for "git submodule update Unable to find current revision in submodule path".The other issue reported in the logs is I guess due to some invalid usage in the Jenkinsfile. Please double check this.{code :java }Error when executing always post condition:org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing{code} Does this sound reasonable to you [~benbrummer]?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule The missing "–depth=1" in the first log is caused, by running first with shallow clone on the submodule which leaves a somehow broken submodule directory behind. The next build was than not a clean build i guess. None of the above errors happen when i downgrade to git plugin 3.12.1 with the exact same job configuration. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4000.1574200680185%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule The missing "–depth=1" in the first log is caused, by running first with shallow clone on the submodule which leaves a somehow broken submodule directory behind. The next build was than not a clean build i guess. [comment|https://issues.jenkins-ci.org/browse/JENKINS-60204?focusedCommentId=380228&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-380228] None of the above errors happen when i downgrade to git plugin 3.12.1 with the exact same job configuration. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4003.1574200740169%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title
René Scheibe edited a comment on JENKINS-60204
Re: git plugin 4.0.0 can not shallow clone a submodule
I was first with confused by the description that shallow submodule updates are used but the logged command didn't contain {{--depth=1}}. I guess it was edited somehow or some intermediate setup while trying to reproduce the relevant job settings.{code:java}> git submodule update --remote impl/tool_protec # timeout=10{code}The provided fail.log contains the proper command logged{code:java}> git submodule update --remote --reference C:\jenkins\repo\submodule.git --depth=1 tool_protec # timeout=10{code}The reported git issue is not an issue of the new git-plugin 4.0.0.{code:java}hudson.plugins.git.GitException: Command "git submodule update --remote --reference C:\jenkins\repo\submodule.git --depth=1 tool_protec" returned status code 1:stdout:stderr: Cloning into 'C:/jenkins/workspace/submoduletest/master/tool_protec'...fatal: Needed a single revisionUnable to find current origin/development revision in submodule path 'tool_protec'{code}You should also be able to reproduce it on the command line without Jenkins and this plugin involved. It's due to the fact that only fetching a single commit from the submodule repository but wanting to resolve the "origin/development" revision which is I guess not the latest commit. You can find plenty of such failed updates reported when searching the Internet for "git submodule update Unable to find current revision in submodule path".The other issue reported in the logs is I guess due to some invalid usage in the Jenkinsfile. Please double check this. {code:java}Error when executing always post condition:org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing{code} From the fail.log I can only see that you are using a declarative pipeline with scripted block and parallel inside. I guess you might have missed to allocate a node in there as suggested.Please double check this. Does this sound reasonable to you [~benbrummer]?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title Bradley Wangia commented on JENKINS-59752 Re: Add support for ephemeral OS disk Stefan Scherer Jie Shen can I get review on the PR for this? https://github.com/jenkinsci/azure-vm-agents-plugin/pull/173 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202475.1570808392000.4009.1574201040200%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule The missing "–depth=1" in the first log is caused, by running first with shallow clone on the submodule which leaves a somehow broken submodule directory behind. The next build was than not a clean build i guess. [ comment |https://issues.jenkins-ci.org/browse/JENKINS-60204?focusedCommentId=380228&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-380228] None of the above errors happen when i downgrade to git plugin 3.12.1 with the exact same job configuration. When i switch between the original submodule and the readded submodule commit i can reproducible make the build fail/succeed.I will test on commandline and report back. But i assume somehow the submodules where added in a strange way. Although i can not tell what is wrong and why it worked until this update. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4013.1574201220793%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title René Scheibe commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule git-plugin 3.12.1 didn't yet provide the shallow submodule update feature. After a downgrade of the plugin from 4.0.0 to 3.12.1 you should therefore see an entry in the "old data" section in Jenkins. Jenkins is clever enough to just ignore unknown settings. Therefore after the downgrade a git submodule update without the -- depth parameter is performed, always fetching all revisions of a submodule repository. Therefore "origin/development" can also be resolved. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4015.1574201340143%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule So it looks like a layer 8 problem on my side combined with inconsistent submodule handling in our company. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4019.1574202060153%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title
Benjamin Brummer edited a comment on JENKINS-60204
Re: git plugin 4.0.0 can not shallow clone a submodule
So it looks like a layer 8 problem on my side combined with inconsistent submodule handling in our company. We always get this error when something is wrong with git.{code:java}Error when executing always post condition:org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing. Suppressed: org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missingPerhaps you forgot to surround the code with a step that provides this, such as: node{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4022.1574202300191%40Atlassian.JIRA.
[JIRA] (JENKINS-60215) Show ssh public keys in ssh key editing ui
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-60215 Show ssh public keys in ssh key editing ui Change By: Josh Soref Component/s: ssh-credentials-plugin Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203188.157419007.4023.1574202900072%40Atlassian.JIRA.
