[JIRA] (JENKINS-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström commented on JENKINS-40712 Re: Exception when using mavenSettingsConfig Have now set up an environment to be able to build the plugin. Once installed I could see a difference in the behaviour. First of all, the config files I have setup now appears in the "Snippet Generator" and it all looks good. However, when running the script it can't find 'mvn' any more. Despite one of the arguments being passed to 'withMaven(maven: 'maven333') ' for the maven version to use in Jenkins it can not find it anymore. I can see the workaround and just add the path to the $PATH and or manually set the $MAVEN_HOME but the question I ask myself is, why does it not find maven anymore? This is an excerpt from the log: [Pipeline] } [Pipeline] // stage [Pipeline] withMaven 00:00:16.758 $ /bin/sh -c "which mvn" [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline ERROR: Could not find maven executable, please set up a Maven Installation or configure MAVEN_HOME environment variable Finished: FAILURE Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-40712) Exception when using mavenSettingsConfig
Title: Message Title
Kent Granström updated an issue
Jenkins / JENKINS-40712
Exception when using mavenSettingsConfig
Change By:
Kent Granström
Comment:
Have now set up an environment to be able to build the plugin. Once installed I could see a difference in the behaviour. First of all, the config files I have setup now appears in the "Snippet Generator" and it all looks good. However, when running the script it can't find 'mvn' any more. Despite one of the arguments being passed to 'withMaven(maven: 'maven333') ' for the maven version to use in Jenkins it can not find it anymore. I can see the workaround and just add the path to the $PATH and or manually set the $MAVEN_HOME but the question I ask myself is, why does it not find maven anymore? This is an excerpt from the log:{code:java}[Pipeline] }[Pipeline] // stage[Pipeline] withMaven00:00:16.758 $ /bin/sh -c "which mvn"[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // timestamps[Pipeline] End of PipelineERROR: Could not find maven executable, please set up a Maven Installation or configure MAVEN_HOME environment variableFinished: FAILURE{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are
[JIRA] (JENKINS-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström commented on JENKINS-40712 Re: Exception when using mavenSettingsConfig Have now set up an environment to be able to build the plugin. Once installed I could see a difference in the behaviour. First of all, the config files I have setup now appears in the "Snippet Generator" and it all looks good. However, when running the script it can't find 'mvn' any more. Despite one of the arguments being passed to 'withMaven(maven: 'maven333') ' for the maven version to use in Jenkins it can not find it anymore. I can see the workaround and just add the path to the $PATH and or manually set the $MAVEN_HOME but the question I ask myself is, why does it not find maven anymore? This is an excerpt from the log: [Pipeline] } [Pipeline] // stage [Pipeline] withMaven 00:00:16.758 $ /bin/sh -c "which mvn" [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline ERROR: Could not find maven executable, please set up a Maven Installation or configure MAVEN_HOME environment variable Finished: FAILURE Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström edited a comment on JENKINS-40712 Re: Exception when using mavenSettingsConfig Off work now. Will have a go on monday. Happy new year to you all you guys doing such a GREAT job Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström edited a comment on JENKINS-40712 Re: Exception when using mavenSettingsConfig Off work now. Will a go on måndag monday . Hoppas Happy new year to you all you guds guys doing suck such a GREAT job Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-40712 Exception when using mavenSettingsConfig Change By: Kent Granström Comment: Will have a go on Monday... Arrrgggh K9... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40745) Kubernetes plugin mkdirs error when configuring a persistent volume claim for /home/jenkins on slave
Title: Message Title
Jesse Redl commented on JENKINS-40745
Re: Kubernetes plugin mkdirs error when configuring a persistent volume claim for /home/jenkins on slave
Well...I was able to workaround this error but i'm not entirely sure why this fixed the issue. Rather than using inheritFrom I specified the containerTemplate for the jnlp slave and it worked just fine?
#!groovy
podTemplate(label: 'build', containers: [
containerTemplate(
name: 'jnlp',
image: 'jenkinsci/jnlp-slave/',
args: '${computer.jnlpmac} ${computer.name}',
resourceRequestCpu: '.5',
resourceLimitCpu: '1',
resourceRequestMemory: '500Mi',
resourceLimitMemory: '1Gi',
),
containerTemplate(
name: 'build-dependencies',
image: 'myorg/build-dependencies',
ttyEnabled: true,
command: 'cat',
alwaysPullImage: true,
resourceRequestCpu: '4',
resourceLimitCpu: '4',
resourceRequestMemory: '8Gi',
resourceLimitMemory: '8Gi'
)],
volumes: [
persistentVolumeClaim(mountPath: '/home/jenkins', claimName: 'jenkins-slaves', readOnly: false)
]) {
node('build') {
stage("Checkout") {
checkout scm
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message
[JIRA] (JENKINS-40638) Undo not capturing values within steps properly
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40638 Undo not capturing values within steps properly Change By: James Dumay Sprint: christmas Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40747) Last Build is ignored when specifying "Pin build at Perforce Label"
Title: Message Title boris avney created an issue Jenkins / JENKINS-40747 Last Build is ignored when specifying "Pin build at Perforce Label" Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2017/Jan/01 10:59 PM Environment: Jenkins 1.641 Priority: Minor Reporter: boris avney When specifying "Pin build at Perforce Label" in order to get the changes up to specific revision, the "summary of changes" includes way more checking than it should be from last build. Add Comment
[JIRA] (JENKINS-40740) Blue ocean branches page crashes when branch does not have a last run date
Title: Message Title James Dumay assigned an issue to Ivan Meredith Jenkins / JENKINS-40740 Blue ocean branches page crashes when branch does not have a last run date Change By: James Dumay Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40740) Blue ocean branches page crashes when branch does not have a last run date
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40740 Blue ocean branches page crashes when branch does not have a last run date Change By: James Dumay Sprint: kraken christmas Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40746) Tests failures on the test module of the core on Windows
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-40746 Tests failures on the test module of the core on Windows Change By: Baptiste Mathus Labels: testing windows Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40746) Tests failures on the test module of the core on Windows
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-40746 Tests failures on the test module of the core on Windows Change By: Baptiste Mathus Labels: failure testing windows Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40290) unit tests failures in core on windows
Title: Message Title Baptiste Mathus commented on JENKINS-40290 Re: unit tests failures in core on windows Created JENKINS-40746 to followup on the failures on that module and not mix discussions (though there's still probably a link). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40746) Tests failures on the test module of the core on Windows
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-40746 Tests failures on the test module of the core on Windows Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Jan/01 8:47 PM Priority: Minor Reporter: Baptiste Mathus This is somehow a followup on JENKINS-40290. I created a separated issue to segregate and clarify work, and the issue reported there by James was only originally on the core module. Test Result (66 failures ) hudson.PluginManagerTest.uploadDependencyResolution hudson.PluginManagerTest.prevalidateConfig hudson.model.RunTest.getLogReturnsAnRightOrder org.jvnet.hudson.test.BuildTriggerTest.testSomething hudson.ProcStarterTest.testNonInitializedEnvsNPE hudson.ProcTest.remoteProcOutputSync hudson.ProcTest.ioPumpingWithRemoteLaunch hudson.ProcTest.ioPumpingWithLocalLaunch hudson.cli.AbstractBuildRangeCommand2Test.dummyRangeShouldSuccessEvenTheBuildIsStuckInTheQueue hudson.cli.AbstractBuildRangeCommand2Test.dummyRangeShouldSuccessEvenTheBuildIsRunning hudson.cli.AbstractBuildRangeCommandTest.dummyRangeNumberMultiShouldSuccess hudson.cli.AbstractBuildRangeCommandTest.dummyRangeNumberMultiShouldSuccessIfSomeBuildDoesNotExist hudson.cli.AbstractBuildRangeCommandTest.dummyRangeNumberSingleShouldSuccessIfBuildNumberIsZero hudson.cli.AbstractBuildRangeCommandTest.dummyRangeNumberSingleShouldSuccess hudson.cli.AbstractBuildRangeCommandTest.dummyRangeRangeMultiShouldSuccess hudson.cli.AbstractBuildRangeCommandTest.dummyRangeNumberSingleShouldSuccessIfBuildNumberIsComma hudson.cli.AbstractBuildRangeCommandTest.dummyRangeNumberSingleShouldSuccessIfBuildNumberIsEmpty hudson.cli.AbstractBuildRangeCommandTest.dummyRangeRangeSingleShouldSuccess hudson.cli.AbstractBuildRangeCommandTest.dummyRangeRangeSingleShouldSuccessIfSomeBuildDoesNotExist
[JIRA] (JENKINS-40523) Include Jenkins Project Name in Log message
Title: Message Title Boguslaw Klimas started work on JENKINS-40523 Change By: Boguslaw Klimas Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40735) Gradle filling up /tmp folder
Title: Message Title wolfs commented on JENKINS-40735 Re: Gradle filling up /tmp folder Are you sure this issue is caused by the Gradle plugin? The two files sound more like the Artifactory plugin (for Gradle and/or Jenkins). What are you using? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40290) unit tests failures in core on windows
Title: Message Title Baptiste Mathus commented on JENKINS-40290 Re: unit tests failures in core on windows James Nord Working on ^ I saw there's actually a few failures in the test module of the core. Can you run it too and confirm? (I'm saying "a few" because 60+ is quite high, but still small compared to 9173 ). Thanks 19:03:20 [windows] Tests run: 9173, Failures: 53, Errors: 11, Skipped: 34, Flakes: 3 19:03:20 [windows] 19:03:20 [windows] [ERROR] There are test failures. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40290) unit tests failures in core on windows
Title: Message Title Baptiste Mathus commented on JENKINS-40290 Re: unit tests failures in core on windows Filed https://github.com/jenkinsci/jenkins/pull/2689 against the Jenkinsfile to also build the core on Windows. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40745) Kubernetes plugin mkdirs error when configuring a persistent volume claim for /home/jenkins on slave
Title: Message Title Jesse Redl created an issue Jenkins / JENKINS-40745 Kubernetes plugin mkdirs error when configuring a persistent volume claim for /home/jenkins on slave Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2017/Jan/01 7:59 PM Environment: kubernetes 1.4.4 jenkins 2.32.1 kubernetes-plugin 0.10 slave image jenkinsci/jnlp-slave Labels: kubernetes Priority: Major Reporter: Jesse Redl I'm attempting to create a persistent volume claim at /home/jenkins for my build container so that I can get the working directory off of the kubernetes node. I'm running into kubernetes eviction errors due to the size of the container / source code that is being checked out on the node. However, I'm running into a permissions error it looks like when hitting the checkout step. Any thoughts on what to try here? java.io.IOException: Failed to mkdirs: /home/jenkins/workspace/vendasta_AA_develop-IEOQWSXH4FZN4YOLA4GNTUPEHK5V6WLUSFSBDOOPY2CKPWC5MHVQ at hudson.FilePath.mkdirs(FilePath.java:1169) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:736) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1088) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83) at
[JIRA] (JENKINS-40744) Null Pointer Exception in Folder Pipeline Lib Property when there is no SCM API
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-40744 Null Pointer Exception in Folder Pipeline Lib Property when there is no SCM API Issue Type: Bug Assignee: Unassigned Attachments: Folder Config [Jenkins].pdf Components: workflow-cps-global-lib-plugin Created: 2017/Jan/01 7:21 PM Priority: Minor Reporter: Oleg Nenashev See the attachment. I have one "Legacy" SCM plugin and Workflow Global CPS lib installed without Pipeline aggregator. SCM source does not show up, and maybe it's the root cause Add Comment
[JIRA] (JENKINS-40743) FilesystemSCM plugin does not work as Pipeline Library source
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-40743 FilesystemSCM plugin does not work as Pipeline Library source Change By: Oleg Nenashev Labels: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40743) FilesystemSCM plugin does not work as Pipeline Library source
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-40743 FilesystemSCM plugin does not work as Pipeline Library source Issue Type: Bug Assignee: samngms Attachments: Screen Shot 2017-01-01 at 19.19.37.png Components: filesystem_scm-plugin Created: 2017/Jan/01 6:23 PM Priority: Major Reporter: Oleg Nenashev I would like to perform local development of Pipeline libraries. In order to do it I wanted to use the Filesystem SCM plugin, but it appears the plugin is not compatible with Folder's library source. 1) The UI seems to be broken (fields are always expanded) 2) The configuration is not being saved to the disk after save() 3) After the reopening of the configuration, it is missing Add Comment
[JIRA] (JENKINS-40743) FilesystemSCM plugin does not work as Pipeline Library source
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-40743 FilesystemSCM plugin does not work as Pipeline Library source Change By: Oleg Nenashev Assignee: samngms Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40743) FilesystemSCM plugin does not work as Pipeline Library source
Title: Message Title Oleg Nenashev started work on JENKINS-40743 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40703) Support injection of maven-gpg-plugin:sign config params in Maven Settings files
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-40703
Support injection of maven-gpg-plugin:sign config params in Maven Settings files
Change By:
Cyrille Le Clerc
When signing artifacts with GPG, Maven apps usually rely on the [Maven GPG Plugin|http://maven.apache.org/plugins/maven-gpg-plugin] and thus store secrets in Maven settings.xml.These secrets should be handled by the Jenkins Config File Provider Plugin.Key configuration parameters that should be handled by the Config File Provider Plugin:http://maven.apache.org/plugins/maven-gpg-plugin/sign-mojo.html* *gpg.keyname*: The "name" of the key to sign with. Passed to gpg as --local-user.* *gpg.passphrase*: The passphrase to use when signing. If not given, look up the value under Maven settings using server id at 'passphraseServerKey' configuration.* *gpg.passphraseServerId*: Server id to lookup the passphrase under Maven settings.* *gpg.useagent*: Server id to lookup the passphrase under Maven settings.* *gpg.homedir** *gpg.publicKeyring*: The path to a public keyring to add to the list of keyrings. By default, only the pubring.gpg from gpg's home directory is considered. Use this option (and defaultKeyring if required) to use a different public key. Note: Relative paths are resolved against gpg's home directory, not the project base directory.* *gpg.secretKeyring*: The path to a secret keyring to add to the list of keyrings. By default, only the secring.gpg from gpg's home directory is considered. Use this option (in combination with publicKeyring and defaultKeyring if required) to use a different secret key. Note: Relative paths are resolved against gpg's home directory, not the project base directory.gpg.useagent: Passes --use-agent or --no-use-agent to gpg. If using an agent, the passphrase is optional as the agent will provide it. For gpg2, specify true as --no-use-agent was removed in gpg2 and doesn't ask for a passphrase anymore.* *gpg.defaultKeyring*: Whether to add the default keyrings from gpg's home directory to the list of used keyrings.* *gpg.homedir*: The directory from which gpg will load keyrings. If not specified, gpg will use the value configured for its installation, e.g. ~/.gnupg or %APPDATA%/gnupg.Maybe we should also consider http://kohsuke.org/pgp-maven-plugin but I'm not sure that this plugin is widely adopted and actively maintained. References:* https://www.gnupg.org/documentation/manuals/gnupg/GPG-Configuration.html** {{~/.gnupg}} This is the default home directory which is used if neither the environment variable GNUPGHOME nor the option --homedir is given. ** {{~/.gnupg/pubring.gpg}} : The public keyring.** {{~/.gnupg/pubring.gpg}}: The public keyring.** {{~/.gnupg/trustdb.gpg}} The trust database. There is no need to backup this file; it is better to backup the ownertrust values (see option --export-ownertrust).
[JIRA] (JENKINS-40703) Support injection of maven-gpg-plugin:sign config params in Maven Settings files
Title: Message Title Cyrille Le Clerc commented on JENKINS-40703 Re: Support injection of maven-gpg-plugin:sign config params in Maven Settings files Maybe it makes more sense to offer this feature through the credentials binding plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40687) "Automatic Cleanup and Sync" does not delete non-versioned folders, only files
Title: Message Title boris avney stopped work on JENKINS-40687 Change By: boris avney Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40687) "Automatic Cleanup and Sync" does not delete non-versioned folders, only files
Title: Message Title boris avney started work on JENKINS-40687 Change By: boris avney Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40742) local variable in parallel threads behaves like global variables
Title: Message Title
Shai Kubitsky created an issue
Jenkins / JENKINS-40742
local variable in parallel threads behaves like global variables
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2017/Jan/01 1:27 PM
Priority:
Minor
Reporter:
Shai Kubitsky
running this pipeline: def do_i(p) { return { echo "$p" for (i = 0; i < 10; i++) { echo "i: $i" } } } stage('i') { parallel( "x" : do_i('xx'), "y" : do_i('yy') ) } produces this output: [Pipeline] stage [Pipeline] { [Pipeline] parallel [Pipeline] [x] { (Branch: x) [Pipeline] [y] { (Branch: y) [Pipeline] [x] echo [x] xx [Pipeline] [y] echo [y] yy [Pipeline] [x] echo [x] i: 0 [Pipeline] [y] echo [y] i: 1 [Pipeline] [x] echo [x] i: 2 [Pipeline] [y] echo [y] i: 3 [Pipeline] [x] echo [x] i: 4 [Pipeline] [y] echo [y] i: 5 [Pipeline] [x] echo [x] i: 6 [Pipeline] [y] echo [y] i: 7 [Pipeline] [x] echo [x] i: 8 [Pipeline] [y] echo [y] i: 9 [Pipeline] [y] } [Pipeline] [x] echo [x] i: 10 [Pipeline] [x] } [Pipeline] // parallel [Pipeline] } [Pipeline] // stage [Pipeline] End of Pipeline Note how i is incremented as if both threads were referring to the same variable i. If I modify the for loop to: for (int i = 0; i < 10; i++) then it works as I expect, where each thread has its own i variable: [Pipeline] stage [Pipeline] { [Pipeline] parallel [Pipeline] [x] { (Branch: x) [Pipeline] [y] { (Branch: y) [Pipeline] [x] echo [x] xx [Pipeline] [y] echo [y] yy [Pipeline] [x] echo [x] i: 0 [Pipeline] [y] echo [y] i: 0 [Pipeline] [x] echo [x] i: 1 [Pipeline] [y] echo [y] i: 1 [Pipeline] [x] echo [x] i: 2 [Pipeline] [y] echo [y] i: 2 [Pipeline] [x] echo [x] i: 3 [Pipeline] [y] echo [y] i: 3 [Pipeline] [x] echo [x] i: 4 [Pipeline] [y] echo [y] i: 4 [Pipeline] [x] echo [x] i: 5 [Pipeline] [y] echo [y] i: 5 [Pipeline] [x] echo [x] i: 6 [Pipeline] [y] echo [y] i: 6 [Pipeline] [x] echo [x] i: 7 [Pipeline] [y] echo [y] i: 7 [Pipeline] [x] echo [x] i: 8 [Pipeline] [y] echo [y] i: 8 [Pipeline] [x] echo [x] i: 9 [Pipeline] [x] }
[JIRA] (JENKINS-40647) With Env not working after .10 k8 plugin update
Title: Message Title
Lars Lawoko edited a comment on JENKINS-40647
Re: With Env not working after .10 k8 plugin update
{code: groovy java }runEnv = []runEnv.add('JAVA_OPTS=-Xmx6g')runEnv.add('npm_config_registry=http://nexus.default.svc.cluster.local:8081/repository/npm/')withEnv(runEnv) { try { sh './gradlew --stacktrace --parallel jenkinsBuild' } catch (Exception e) { junit allowEmptyResults: true, testResults: '**/build/test-results/**/*.xml' step([$class: 'CheckStylePublisher', canComputeNew: false, defaultEncoding: '', healthy: '', pattern: '**/main.xml,**/test.xml', unHealthy: '']) throw e }{code}Adding a {code: groovy java }sh 'printenv'{code}Shows the env is not populatedP.s it is inside a container which contains JDK 7 & gcloud{code: :groovy java } node('JavaPod') {container('gcloud-jdk7') {{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40647) With Env not working after .10 k8 plugin update
Title: Message Title
Lars Lawoko commented on JENKINS-40647
Re: With Env not working after .10 k8 plugin update
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
runEnv = []
runEnv.add('JAVA_OPTS=-Xmx6g')
runEnv.add('npm_config_registry=http://nexus.default.svc.cluster.local:8081/repository/npm/')
withEnv(runEnv) {
try {
sh './gradlew --stacktrace --parallel jenkinsBuild'
} catch (Exception e) {
junit allowEmptyResults: true, testResults: '**/build/test-results/**/*.xml'
step([$class: 'CheckStylePublisher', canComputeNew: false, defaultEncoding: '', healthy: '', pattern: '**/main.xml,**/test.xml', unHealthy: ''])
throw e
}
Adding a
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
sh 'printenv'
Shows the env is not populated P.s it is inside a container which contains JDK 7 & gcloud
Unable to find source-code formatter for language: :groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
node('JavaPod') {
container('gcloud-jdk7') {
[JIRA] (JENKINS-40693) badMessage: 400 Bad Host header for HttpChannelOverHttp
Title: Message Title olamy commented on JENKINS-40693 Re: badMessage: 400 Bad Host header for HttpChannelOverHttp fix backported to jetty-9.2.x branch. 9.2.21-SNAPSHOT deployed to https://oss.sonatype.org/content/repositories/jetty-snapshots let me know how it works with the fix. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
