[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title Vladimir Eremeev commented on JENKINS-60153 Re: NullPointerException in Build failure analyzer No, I was wrong. This bug still exists in 1.25.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.203018.1573630888000.1569.1580890440187%40Atlassian.JIRA.
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title Vladimir Eremeev commented on JENKINS-60153 Re: NullPointerException in Build failure analyzer Updated the plugin to version 1.25.0, the issue is 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.203018.1573630888000.3651.1579683360212%40Atlassian.JIRA.
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title Vladimir Eremeev updated an issue Jenkins / JENKINS-60153 NullPointerException in Build failure analyzer Change By: Vladimir Eremeev Environment: Jenkins version 2.190.2OS: Ubuntu 18 16 .04 with all recent updatesBuild failure analyzer version: 1.24.1 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.203018.1573630888000.1534.1573803000241%40Atlassian.JIRA.
[JIRA] (JENKINS-57008) Jenkins declarative-linter does not handle missing variables
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-57008
Jenkins declarative-linter does not handle missing variables
Change By:
Vladimir Eremeev
Following pipeline with errors is successfully validated.{ { code} pipeline {agent anystages {stage('Build') {steps {script {println missing_variable}} } } {code } }} { { code} ssh -p 18122 username@jenkins declarative-linter < jfJenkinsfile successfully validated. {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
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-60153
NullPointerException in Build failure analyzer
Change By:
Vladimir Eremeev
NPE on click on failed build , instead of showing failure causes .Stack trace:{code:java}org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.190.2.jar!/hudson/model/AbstractBuild/index.jelly:110:84: java.lang.NullPointerException at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-60153
NullPointerException in Build failure analyzer
Change By:
Vladimir Eremeev
NPE on click on failed build.Stack trace:{code:java}org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.190.2.jar!/hudson/model/AbstractBuild/index.jelly:110:84: java.lang.NullPointerException at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-60153
NullPointerException in Build failure analyzer
Change By:
Vladimir Eremeev
NPE on click on failed build : . Stack trace: {code :java } Stack traceStack traceorg org .apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.190.2.jar!/hudson/model/AbstractBuild/index.jelly:110:84: java.lang.NullPointerException at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title Vladimir Eremeev created an issue Jenkins / JENKINS-60153 NullPointerException in Build failure analyzer Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2019-11-13 07:41 Environment: Jenkins version 2.190.2 OS: Ubuntu 18.04 with all recent updates Build failure analyzer version: 1.24.1 Priority: Minor Reporter: Vladimir Eremeev NPE on click on failed build: Stack traceStack traceorg.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.190.2.jar!/hudson/model/AbstractBuild/index.jelly:110:84: java.lang.NullPointerException at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-57123) Script Security Plugins latests version caused Jenkins 2.173 failed to start
Title: Message Title Vladimir Eremeev edited a comment on JENKINS-57123 Re: Script Security Plugins latests version caused Jenkins 2.173 failed to start Same situation here. Jenkins version 2.176.3Script Security plugin version 1.64 After routine plugin update Jenkins has started crashing on startup and showing exception, similar to one, provided in the bug description. I've searched for the errors and have found this bug report. Tried removing script-security plugin, and Jenkins has started.Then, I've tried installing script-security plugin version 1.64 and crashes appeared again. Update.Actually, crashes were caused by Active-choice plugin. It was recently updated from 2.1 to 2.2 I've found this by rolling back script-security plugin. All versions from 1.64 back to 1.50 have caused crash. That suggested that the cause was somewhere 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.198873.1555704698000.4746.1568700360340%40Atlassian.JIRA.
[JIRA] (JENKINS-57123) Script Security Plugins latests version caused Jenkins 2.173 failed to start
Title: Message Title Vladimir Eremeev commented on JENKINS-57123 Re: Script Security Plugins latests version caused Jenkins 2.173 failed to start Updating Active choice to 2.2.1 has solved the issue https://issues.jenkins-ci.org/browse/JENKINS-59389 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.198873.1555704698000.4261.1568637060381%40Atlassian.JIRA.
[JIRA] (JENKINS-59389) Active choices plugin causes Jenkins to crash on startup
Title: Message Title Vladimir Eremeev commented on JENKINS-59389 Re: Active choices plugin causes Jenkins to crash on startup I've manually downloaded 2.2.1 from https://updates.jenkins.io/download/plugins/uno-choice/ Now it works. cd $JENKINS_HOME/plugins sudo rm -rf uno-choice* sudo wget https://updates.jenkins.io/download/plugins/uno-choice/2.2.1/uno-choice.hpi sudo systemctl stop jenkins sudo systemctl start jenkins 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.201945.1568634852000.4258.1568637060324%40Atlassian.JIRA.
[JIRA] (JENKINS-59389) Active choices plugin causes Jenkins to crash on startup
Title: Message Title Vladimir Eremeev updated an issue Jenkins / JENKINS-59389 Active choices plugin causes Jenkins to crash on startup Change By: Vladimir Eremeev Comment: How can I get it?Jenkins update center shows only 2.2 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.201945.1568634852000.4247.1568636760164%40Atlassian.JIRA.
[JIRA] (JENKINS-59389) Active choices plugin causes Jenkins to crash on startup
Title: Message Title Vladimir Eremeev commented on JENKINS-59389 Re: Active choices plugin causes Jenkins to crash on startup How can I get it? Jenkins update center shows only 2.2 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.201945.1568634852000.4235.1568636580684%40Atlassian.JIRA.
[JIRA] (JENKINS-59389) Active choices plugin causes Jenkins to crash on startup
Title: Message Title Vladimir Eremeev created an issue Jenkins / JENKINS-59389 Active choices plugin causes Jenkins to crash on startup Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: jenkins-crashlog.log Components: active-choices-plugin Created: 2019-09-16 11:54 Environment: Jenkins version 2.176.3 OS: Ubuntu 16.04.6 LTS Priority: Minor Reporter: Vladimir Eremeev After recent update of the Active Choices plugin from version 2.1 to version 2.2 Jenkins crashes on startup. It shows following error in the browser: Error java.lang.IllegalStateException: Expected 1 instance of hudson.PluginManager$PluginUpdateMonitor but got 0 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:2188) at hudson.maven.PluginImpl.init(PluginImpl.java:58) Caused: java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) Caused: java.lang.Error at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at
[JIRA] (JENKINS-57123) Script Security Plugins latests version caused Jenkins 2.173 failed to start
Title: Message Title Vladimir Eremeev edited a comment on JENKINS-57123 Re: Script Security Plugins latests version caused Jenkins 2.173 failed to start Same situation here. Jenkins version 2.176.3Script Security plugin version 1.64 After routine plugin update Jenkins has started crashing on startup and showing exception, similar to one, provided in the bug description. I've searched for the errors and have found this bug report. Tried removing script-security plugin, and Jenkins has started.Then, I've tried installing script-security plugin version 1.64 and crashes appeared again. Update.Actually, crashes were caused by Active-choice plugin. It was recently updated from 2.1 to 2.2 I've found this by rolling back script-security plugin. All versions from 1.64 back to 1.50 have caused crash. 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.198873.1555704698000.4204.1568634000311%40Atlassian.JIRA.
[JIRA] (JENKINS-57123) Script Security Plugins latests version caused Jenkins 2.173 failed to start
Title: Message Title Vladimir Eremeev edited a comment on JENKINS-57123 Re: Script Security Plugins latests version caused Jenkins 2.173 failed to start Same situation here. Jenkins version 2.176.3 Script Security plugin version 1.64 After routine plugin update Jenkins has started crashing on startup and showing exception, similar to one, provided in the bug description. I've searched for the errors and have found this bug report. Tried removing script-security plugin, and Jenkins has started.Then, I've tried installing script-security plugin version 1.64 and crashes appeared 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.198873.1555704698000.4196.1568632260235%40Atlassian.JIRA.
[JIRA] (JENKINS-57123) Script Security Plugins latests version caused Jenkins 2.173 failed to start
Title: Message Title Vladimir Eremeev commented on JENKINS-57123 Re: Script Security Plugins latests version caused Jenkins 2.173 failed to start Same situation here. Jenkins version 2.176.3 After routine plugin update Jenkins has started crashing on startup and showing exception, similar to one, provided in the bug description. I've searched for the errors and have found this bug report. Tried removing script-security plugin, and Jenkins has started. Then, I've tried installing script-security plugin version 1.64 and crashes appeared 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.198873.1555704698000.4184.1568631840235%40Atlassian.JIRA.
[JIRA] (JENKINS-57502) Cmake arguments sometimes are added to path in parallel build
Title: Message Title Vladimir Eremeev commented on JENKINS-57502 Re: Cmake arguments sometimes are added to path in parallel build The problem has gone. Jenkins version was updated to 2.176.1 Cmake plugin version is 2.6.1 Cmake program version is 3.13 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199365.1557999255000.1586.1562225520155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57502) Cmake arguments sometimes are added to path in parallel build
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-57502
Cmake arguments sometimes are added to path in parallel build
Change By:
Vladimir Eremeev
I'm trying to simulate matrix build using PipelinePipeline snippet { { code:java} def cmake_tasks(os_labels, configs, DL_on_off) {tasks = [:]def DL_dir_labels = ['ON': 'DL', 'OFF': 'noDL']for(int i = 0; i < os_labels.size(); i++) {def os = os_labels[i] for (int j = 0; j < configs.size(); j++) {for (int k = 0; k < DL_on_off.size(); k++) {def config = configs[j]def DL = DL_on_off[k]def DL_dir_label = DL_dir_labels["${DL}"] def generator = "Ninja"def steps = [[withCmake: true]]def cmakeArgs = "-Dsomevar=somevalue" def cmake_inst = 'InSearchPath' tasks["${os}/${config}/${DL_dir_label}"] = {node("build && ${os}") { stage("${os}/${config}/${DL_dir_label}") { if (os == "windows") { bat """ // does not matter ${env.WORKSPACE } \\DL\\test\\support\\configure.cmd ${config} build_${config}_${DL_dir_label} ${DL} ninja """ } else { cmakeBuild(buildDir: "build_${config}_${DL_dir_label}", buildType: config, cleanBuild: true, cmakeArgs: cmakeArgs, generator: generator, installation: cmake_inst, sourceDir: ".", steps: steps) } }}}}}}return tasks}pipeline {agent none parameters {string(defaultValue: 'develop',description: 'Commit ID or branch name to build', name: 'branch', trim: false)} stages {stage(' Checkout') {steps {script {// checkout on windows and linux}}}stage(' Configure & Build') {steps {script {def OSes = ["windows", "linux"]def configs = ["Release", "Debug"]def DL_inc = ["ON", "OFF"]parallel cmake_tasks(OSes, configs, DL_inc) }}}}} {code } } Sometimes I see failed steps with the following output similar to the following (please, note that "CMAKE_BUILD_TYPE=Debug" is concatenated with a path) : { { code:java} Cleaning build dir /jenkins/workspace/project@7/build_Debug_DL ... [build_Debug_DL] $ cmake -G Ninja -D CMAKE_BUILD_TYPE=Debug -Dsomevar=somevalue /jenkins/workspace/project@7CMake Error: The source directory
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title Vladimir Eremeev updated an issue Jenkins / JENKINS-57501 cmakeBuild does not set environment variables in Windows when run in Pipeline Change By: Vladimir Eremeev Comment: After careful studying of this discussion, as well as a web-page of snippet generator, it became clear for me that envVars, passed to cmakeBuild, has nothing to do with my issue.And the issue itself is invalid, since I've incorrectly passed arguments to cmake.Closing.Thanks for the help. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.8355.1558514040495%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title Vladimir Eremeev updated JENKINS-57501 After careful studying of this discussion, as well as a web-page of snippet generator, it became clear for me that envVars, passed to cmakeBuild, has nothing to do with my issue. And the issue itself is invalid, since I've incorrectly passed arguments to withEnv. Thanks for the help. Jenkins / JENKINS-57501 cmakeBuild does not set environment variables in Windows when run in Pipeline Change By: Vladimir Eremeev Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title Vladimir Eremeev edited a comment on JENKINS-57501 Re: cmakeBuild does not set environment variables in Windows when run in Pipeline After careful studying of this discussion, as well as a web-page of snippet generator, it became clear for me that envVars, passed to cmakeBuild, has nothing to do with my issue.And the issue itself is invalid, since I've incorrectly passed arguments to cmake.Closing. Thanks for the help. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.8351.1558513980218%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title Vladimir Eremeev commented on JENKINS-57501 Re: cmakeBuild does not set environment variables in Windows when run in Pipeline After careful studying of this discussion, as well as a web-page of snippet generator, it became clear for me that envVars, passed to cmakeBuild, has nothing to do with my issue. And the issue itself is invalid, since I've incorrectly passed arguments to cmake. Closing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.8349.1558513980196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev edited a comment on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
{quote} Anyway, you do not need to pass envvars to BuildToolStep to configure *cmake*. These varaibles are passed to the *build tool* (make or nija).{quote}Now I see why my attempts failed. It seems, the only way to pass environment variables to cmake is using withEnv.{quote} The online help for _Build tool | Env. Variables_*has* an example that shows how to set multiple variables.{quote}Sorry, I cannot figure out where it is, and how I should use it in a pipeline script.Here is what I've entered in pipeline snippet generator: !image-2019-05-22-10-36-53-131.png!And here is the generated code:{code:java}cmakeBuild buildDir: '${build_dir}', buildType: '${config}', cleanBuild: true, generator: 'Ninja', installation: 'InSearchPath', sourceDir: '${env.WORKSPACE}', steps: [[envVars: '''A=BC=D''', withCmake: true]]{code}Code sample in the issue description does exactly this. It generates a string in the form "NAME=VALUENAME=VALUE"), and CMake does not see these variables. I've found two links: [https://javadoc.jenkins.io/plugin/cmakebuilder/index.html?hudson/plugins/cmake/BuildToolStep.html] and [https://javadoc.jenkins.io/plugin/cmakebuilder/hudson/plugins/cmake/BuildToolStep.html]They don't contain examples either.I've also studied sources on GitHub but failed to find how `BuildToolStep` processes `this.vars`, set in `setEnvVars`.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.8329.1558512900365%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev edited a comment on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
{quote}The online help for _Build tool | Env. Variables_*has* an example that shows how to set multiple variables.{quote}Sorry, I cannot figure out where it is, and how I should use it in a pipeline script.Here is what I've entered in pipeline snippet generator: !image-2019-05-22-10-36-53-131.png!And here is the generated code:{code:java}cmakeBuild buildDir: '${build_dir}', buildType: '${config}', cleanBuild: true, generator: 'Ninja', installation: 'InSearchPath', sourceDir: '${env.WORKSPACE}', steps: [[envVars: '''A=BC=D''', withCmake: true]]{code}Code sample in the issue description does exactly this (variable names and values differ) . It generates a string in the form "NAME=VALUE NAME=VALUE"), and CMake does not see these variables. I've found two links: [https://javadoc.jenkins.io/plugin/cmakebuilder/index.html?hudson/plugins/cmake/BuildToolStep.html] and [https://javadoc.jenkins.io/plugin/cmakebuilder/hudson/plugins/cmake/BuildToolStep.html]They don't contain examples either.I've also studied sources on GitHub but failed to find how `BuildToolStep` processes `this.vars`, set in `setEnvVars`.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.8324.1558512660101%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev edited a comment on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
{quote}The online help for _Build tool | Env. Variables_*has* an example that shows how to set multiple variables.{quote}Sorry, I cannot figure out where it is, and how should I should use it in a pipeline script.Here is what I've entered in pipeline snippet generator: !image-2019-05-22-10-36-53-131.png!And here is the generated code:{code:java}cmakeBuild buildDir: '${build_dir}', buildType: '${config}', cleanBuild: true, generator: 'Ninja', installation: 'InSearchPath', sourceDir: '${env.WORKSPACE}', steps: [[envVars: '''A=BC=D''', withCmake: true]]{code}Code sample in the issue description does exactly this (variable names and values differ). It generates a string in the form "NAME=VALUE NAME=VALUE"), and CMake does not see these variables. I've found two links: [https://javadoc.jenkins.io/plugin/cmakebuilder/index.html?hudson/plugins/cmake/BuildToolStep.html] and [https://javadoc.jenkins.io/plugin/cmakebuilder/hudson/plugins/cmake/BuildToolStep.html]They don't contain examples either.I've also studied sources on GitHub but failed to find how `BuildToolStep` processes `this.vars`, set in `setEnvVars`.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.8321.1558512601562%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev edited a comment on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
{quote}The online help for _Build tool | Env. Variables_*has* an example that shows how to set multiple variables.{quote}Sorry, I cannot figure out where it is, and how should I use it in a pipeline script.Here is what I've entered in pipeline snippet generator: !image-2019-05-22-10-36-53-131.png!And here is the generated code:{code:java}cmakeBuild buildDir: '${build_dir}', buildType: '${config}', cleanBuild: true, generator: 'Ninja', installation: 'InSearchPath', sourceDir: '${env.WORKSPACE}', steps: [[envVars: '''A=BC=D''', withCmake: true]]{code}Code sample in the issue description does exactly this (variable names and values differ). It generates a string in the form "NAME=VALUE NAME=VALUE"), and CMake does not see these variables. I've found two links: [https://javadoc.jenkins.io/plugin/cmakebuilder/index.html?hudson/plugins/cmake/BuildToolStep.html] and [https://javadoc.jenkins.io/plugin/cmakebuilder/hudson/plugins/cmake/BuildToolStep.html]They don't contain examples either. I've also studied sources on GitHub but failed to find how `BuildToolStep` processes `this.vars`, set in `setEnvVars`.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.8318.1558512300122%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev edited a comment on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
{quote}The online help for _Build tool | Env. Variables_*has* an example that shows how to set multiple variables.{quote}Sorry, I cannot figure out where it is, and how should I use it in a pipeline script.Here is what I've entered in pipeline snippet generator: !image-2019-05-22-10-36-53-131.png!And here is the generated code:{code:java}cmakeBuild buildDir: '${build_dir}', buildType: '${config}', cleanBuild: true, generator: 'Ninja', installation: 'InSearchPath', sourceDir: '${env.WORKSPACE}', steps: [[envVars: '''A=BC=D''', withCmake: true]]{code}Code sample in the issue description does exactly this (variable names and values differ). It generates a string in the form "NAME=VALUE NAME=VALUE"), and CMake does not see these variables. I've found two links: [https://javadoc.jenkins.io/plugin/cmakebuilder/index.html?hudson/plugins/cmake/BuildToolStep.html] and [https://javadoc.jenkins.io/plugin/cmakebuilder/hudson/plugins/cmake/BuildToolStep.html]They don't contain examples either.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.8315.1558511280115%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev edited a comment on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
{quote}The online help for _Build tool | Env. Variables_*has* an example that shows how to set multiple variables.{quote}Sorry, I cannot figure out where it is, and how should I use it in a pipeline script.Here is what I've entered in pipeline snippet generator: !image-2019-05-22-10-36-53-131.png!And here is the generated code:{code:java}cmakeBuild buildDir: '${build_dir}', buildType: '${config}', cleanBuild: true, generator: 'Ninja', installation: 'InSearchPath', sourceDir: '${env.WORKSPACE}', steps: [[envVars: '''A=BC=D''', withCmake: true]]{code}Code sample in the issue description does exactly this (variable names and values differ). It generates a string in the form "NAME=VALUE NAME=VALUE"), and CMake does not see these variables. I've found two links: [https://javadoc.jenkins.io/plugin/cmakebuilder/index.html?hudson/plugins/cmake/BuildToolStep.html] and [https://javadoc.jenkins.io/plugin/cmakebuilder/hudson/plugins/cmake/BuildToolStep.html]They don't contain examples either.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.8312.1558511040209%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev commented on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
The online help for Build tool | Env. Variableshas an example that shows how to set multiple variables.
Sorry, I cannot figure out where it is, and how should I use it in a pipeline script. Here is what I've entered in pipeline snippet generator: And here is the generated code:
cmakeBuild buildDir: '${build_dir}', buildType: '${config}', cleanBuild: true, generator: 'Ninja', installation: 'InSearchPath', sourceDir: '${env.WORKSPACE}', steps: [[envVars: '''A=B
C=D''', withCmake: true]]
Code sample in the issue description does exactly this (variable names and values differ). It generates a string in the form "NAME=VALUE NAME=VALUE"), and CMake does not see these variables.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.8304.1558510920382%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title Vladimir Eremeev updated an issue Jenkins / JENKINS-57501 cmakeBuild does not set environment variables in Windows when run in Pipeline Change By: Vladimir Eremeev Attachment: image-2019-05-22-10-36-53-131.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.8298.1558510620200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev edited a comment on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
Yes, indeed. Changing argument of withEnv to {code:java}vars = ["INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ","LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...","LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;","PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc]{code}does the trick.Tried adding the same to the "steps" argument of cmakeBuild:{code:java}def steps = [[withCmake: true, envVars: ["INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ", "LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...", "LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;", "PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc] ]]{code}got error:{code:java}"java.lang.ClassCastException: class hudson.plugins.cmake.BuildToolStep.setEnvVars() expects class java.lang.String but received class java.util.ArrayList"{code} I see following issues.1. Manual of withEnv is not clear (I understand that this is not related to current issue)2. Processing of envVars by cmakeBuild is not consistent with one, done by "withEnv" (Though, I understand that different authors could have different ideas about user interface. But consistency is good).3. Description of envVars is misleading. I've come from Python, and sentence "key-value pairs" suggests that this argument should be a dictionary (or a map), not a string. It is not said, how these pairs must be separated, if they are wrapped in a string.4. Both documentation pieces, for withEnv and for envVars, miss examples on how to set multiple variables, they only show just one how to set a single variable, a very rare case, IMHO .
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev edited a comment on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
Yes, indeed. Changing argument of withEnv to {code:java}vars = ["INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ","LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...","LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;","PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc]{code}does the trick.Tried adding the same to the "steps" argument of cmakeBuild:{code:java}def steps = [[withCmake: true, envVars: ["INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ", "LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...", "LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;", "PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc] ]]{code}got error:{code:java}"java.lang.ClassCastException: class hudson.plugins.cmake.BuildToolStep.setEnvVars() expects class java.lang.String but received class java.util.ArrayList"{code} I see following issues.1. Manual of withEnv is not clear (I understand that this is not related to current issue)2. Processing of envVars by cmakeBuild is not consistent with one, done by "withEnv" (Though, I understand that different authors could have different ideas about user interface . But consistency is good ).3. Description of envVars is misleading too . I've come from Python, and sentence "key-value pairs" suggests that this argument should be a dictionary (or a map), not a string. It is not said, how these pairs must be separated. 4. Both documentation pieces, for withEnv and for envVars, miss examples on how to set multiple variables, they show just one.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev edited a comment on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
Yes, indeed. Changing argument of withEnv to {code:java}vars = ["INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ","LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...","LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;","PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc]{code}does the trick.Tried adding the same to the "steps" argument of cmakeBuild:{code:java}def steps = [[withCmake: true, envVars: ["INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ", "LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...", "LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;", "PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc] ]]{code}got error:{code:java}"java.lang.ClassCastException: class hudson.plugins.cmake.BuildToolStep.setEnvVars() expects class java.lang.String but received class java.util.ArrayList"{code} I see following issues.1. Manual of withEnv is not clear (I understand that this is not related to current issue)2. Processing of envVars by cmakeBuild is not consistent with one, done by "withEnv" (Though, I understand that different authors could have different ideas about user interface. But consistency is good).3. Description of envVars is misleading. I've come from Python, and sentence "key-value pairs" suggests that this argument should be a dictionary (or a map), not a string. It is not said, how these pairs must be separated , if they are wrapped in a string .4. Both documentation pieces, for withEnv and for envVars, miss examples on how to set multiple variables, they show just one.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev edited a comment on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
Yes, indeed. Changing argument of withEnv to {code:java}vars = ["INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ","LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...","LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;","PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc]{code}does the trick.Tried adding the same to the "steps" argument of cmakeBuild:{code:java}def steps = [[withCmake: true, envVars: ["INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ", "LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...", "LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;", "PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc] ]]{code}got error:{code:java}"java.lang.ClassCastException: class hudson.plugins.cmake.BuildToolStep.setEnvVars() expects class java.lang.String but received class java.util.ArrayList"{code} I see following issues.1. Manual of withEnv is not clear (I understand that this is not related to current issue)2. Processing of envVars by cmakeBuild is not consistent with one, done by "withEnv" (Though, I understand that different authors could have different ideas about user interface) . 3. Description of envVars is misleading too. I've come from Python, and sentence "key-value pairs" suggests that this argument should be a dictionary (or a map), not a string.Both documentation pieces, for withEnv and for envVars, miss examples on how to set multiple variables, they show just one.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev edited a comment on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
Yes, indeed. Changing argument of withEnv to {code:java}vars = ["INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ","LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...","LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;","PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc]{code}does the trick.Tried adding the same to the "steps" argument of cmakeBuild:{code:java}def steps = [[withCmake: true, envVars: ["INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ", "LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...", "LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;", "PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc] ]]{code}got error:{code:java}"java.lang.ClassCastException: class hudson.plugins.cmake.BuildToolStep.setEnvVars() expects class java.lang.String but received class java.util.ArrayList"{code} I see following issues.1. Manual of withEnv is not clear (I understand that this is not related to current issue)2. Processing of envVars by cmakeBuild is not consistent with one, done by "withEnv" (Though, I understand that different authors could have different ideas about user interface).3. Description of envVars is misleading too. I've come from Python, and sentence "key-value pairs" suggests that this argument should be a dictionary (or a map), not a string. 4. Both documentation pieces, for withEnv and for envVars, miss examples on how to set multiple variables, they show just one.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev edited a comment on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
Yes, indeed. Changing argument of withEnv to {code:java}vars = ["INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ","LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...","LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;","PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc]{code}does the trick.Tried adding the same to the "steps" argument of cmakeBuild:{code:java}def steps = [[withCmake: true, envVars: [ " INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ", "LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...", "LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;", "PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc] ]]{code}got error:{code:java}"java.lang.ClassCastException: class hudson.plugins.cmake.BuildToolStep.setEnvVars() expects class java.lang.String but received class java.util.ArrayList"{code} I see following issues.1. Manual of withEnv is not clear (I understand that this is not related to current issue)2. Processing of envVars by cmakeBuild is not consistent with one, done by "withEnv". Description is misleading too. I've come from Python, and sentence "key-value pairs" suggests that this argument should be a dictionary (or a map), not a string.Both documentation pieces, for withEnv and envVars, miss examples on how to set multiple variables, they show just one.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title Vladimir Eremeev commented on JENKINS-57501 Re: cmakeBuild does not set environment variables in Windows when run in Pipeline Yes, indeed. Changing argument of withEnv to vars = ["INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ", "LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...", "LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;", "PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc ] does the trick. Tried adding the same to the "steps" argument of cmakeBuild: def steps = [[ withCmake: true, envVars: [INCLUDE=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE; . ", "LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64; ...", "LIBPATH=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;", "PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;...", // etc ] ]] got error: "java.lang.ClassCastException: class hudson.plugins.cmake.BuildToolStep.setEnvVars() expects class java.lang.String but received class java.util.ArrayList" I see following issues. 1. Manual of withEnv is not clear (I understand that this is not related to current issue) 2. Processing of envVars by cmakeBuild is not consistent with one, done by "withEnv". Description is misleading too. I've come from Python, and sentence "key-value pairs" suggests that this argument should be a dictionary (or a map), not a string. Both documentation pieces, for withEnv and envVars, miss examples on how to set multiple variables, they show just one. Add Comment
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-57501
cmakeBuild does not set environment variables in Windows when run in Pipeline
Change By:
Vladimir Eremeev
ipeline Jenkins pipeline snippet : {code:java}def cmake_tasks() {def tasks=[:] def steps = [[withCmake: true]]def os = "windows" def config = "Debug" def generator = "Ninja"// addidional env vars def vars="""LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\ATLMFC\\LIB\\amd64;C:\\Program Files (x86)\\Windows Kits\\10\\lib\\10.0.17763.0\\ucrt\\x64;C:\\Program Files (x86)\\Windows Kits\\NETFXSDK\\4.6.1\\lib\\um\\x64;C:\\Program Files (x86)\\Windows Kits\\10\\lib\\10.0.17763.0um\\x64;PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\binamd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319;C:\\Windows\\Microsoft.NET\\Framework64;C:\\Program Files (x86)\\Windows Kits\\10\\binx64;C:\\Program Files (x86)\\Windows Kits\\10\\binx86;C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v10.0A\\bin\\NETFX 4.6.1 Tools\\x64;C:\\Program Files (x86)\\Common Files\\Oracle\\Java\\javapath;C:\\ProgramData\\Oracle\\Java\\javapath;C:\\CMake\\bin;c:\\windows\\system32;C:\\ Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v7.0bin;C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v7.0libnvvp;g:\\Bin;"""// another variant, also does not affect CMake// vars = bat returnStdout: true, script: """//@call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64//set//"""// third variant, also doesn't work//bat """call c:\Path\to\Visual\Studio\vcvarsall.bat // set > build.props"""//var = readFile("build.props") def cmakeArgs = "-DARG=VALUE" def cmake_inst = 'InSearchPath' steps.add([envVars: vars]) cmakeArgs = cmakeArgs + " -DCMAKE_C_COMPILER=cl -DCMAKE_CXX_COMPILER=cl -DCMAKE_MAKE_PROGRAM=g:\\Bin\\ninja" tasks["${os}"] = { node("${os}"){ stage("${os}/${config}") { withEnv([vars]){ if (os == "windows"){ bat "set | sort" println vars println steps } cmakeBuild(buildDir: "build_${config}", buildType: config, cleanBuild: true, cmakeArgs: cmakeArgs, generator: generator, installation: cmake_inst, sourceDir: ".", steps: steps) } } } } return tasks} pipeline {agent none stages{ stage('Configurte') { steps{ script { parallel cmake_tasks() }} } }} {code} Snippet of
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-57501
cmakeBuild does not set environment variables in Windows when run in Pipeline
Change By:
Vladimir Eremeev
ipeline snippet {code:java}def cmake_tasks() {def tasks=[:] def steps = [[withCmake: true]]def os = "windows" def config = "Debug" def generator = "Ninja"// addidional env vars def vars="""LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\ATLMFC\\LIB\\amd64;C:\\Program Files (x86)\\Windows Kits\\10\\lib\\10.0.17763.0\\ucrt\\x64;C:\\Program Files (x86)\\Windows Kits\\NETFXSDK\\4.6.1\\lib\\um\\x64;C:\\Program Files (x86)\\Windows Kits\\10\\lib\\10.0.17763.0um\\x64;PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\binamd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319;C:\\Windows\\Microsoft.NET\\Framework64;C:\\Program Files (x86)\\Windows Kits\\10\\binx64;C:\\Program Files (x86)\\Windows Kits\\10\\binx86;C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v10.0A\\bin\\NETFX 4.6.1 Tools\\x64;C:\\Program Files (x86)\\Common Files\\Oracle\\Java\\javapath;C:\\ProgramData\\Oracle\\Java\\javapath;C:\\CMake\\bin;c:\\windows\\system32;C:\\ Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v7.0bin;C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v7.0libnvvp;g:\\Bin;"""// another variant, also does not affect CMake// vars = bat returnStdout: true, script: """//@call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64//set//""" // third variant, also doesn't work//bat """call c:\Path\to\Visual\Studio\vcvarsall.bat // set > build.props"""//var = readFile("build.props") def cmakeArgs = "-DARG=VALUE" def cmake_inst = 'InSearchPath' steps.add([envVars: vars]) cmakeArgs = cmakeArgs + " -DCMAKE_C_COMPILER=cl -DCMAKE_CXX_COMPILER=cl -DCMAKE_MAKE_PROGRAM=g:\\Bin\\ninja" tasks["${os}"] = { node("${os}"){ stage("${os}/${config}") { withEnv([vars]){ if (os == "windows"){ bat "set | sort" println vars println steps } cmakeBuild(buildDir: "build_${config}", buildType: config, cleanBuild: true, cmakeArgs: cmakeArgs, generator: generator, installation: cmake_inst, sourceDir: ".", steps: steps) } } } } return tasks} pipeline {agent none stages{ stage('Configurte') { steps{ script { parallel cmake_tasks() }} } }} {code} Snippet of CMakeLists.txt{code:java}cmake_minimum_required(VERSION
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title Vladimir Eremeev commented on JENKINS-57501 Re: cmakeBuild does not set environment variables in Windows when run in Pipeline Actually, that code was in the original snippet, but it was corrupted by Jira. I've learned about the code tag and fixed original issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.5159.1558339260171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-57501
cmakeBuild does not set environment variables in Windows when run in Pipeline
Change By:
Vladimir Eremeev
Pipeline ipeline snippet { { code:java} def cmake_tasks() { }} {{ def tasks=[:] }} {{ def steps = [[withCmake: true]] }}{{ def os = "windows" }} {{ def config = "Debug" }} {{ def generator = "Ninja" }} {{ // addidional env vars def vars=""" }} {{ LIB=C: \\ Program Files (x86) \\ Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;C: \\ Program Files (x86) \\ Microsoft Visual Studio 14.0\\VC\\ATLMFC\\LIB\\amd64;C: \\ Program Files (x86) \\ Windows Kits\\10\\lib\\10.0.17763.0\\ucrt\\x64;C: \\ Program Files (x86) \\ Windows Kits\\NETFXSDK\\4.6.1\\lib\\um\\x64;C: \\ Program Files (x86) \\ Windows Kits\\10\\lib\\10.0.17763. 0 0um \\ um x64; }} {{ PATH=C: \\ Program Files (x86)\\MSBuild\\14.0\\ bin\\amd64 binamd64 ;C: \\ Program Files (x86) \\ Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319;C:\\Windows\\Microsoft.NET\\Framework64 \\ ;C: \\ Program Files (x86) }} {{ \\ Windows Kits\\10\\ bin\\x64 binx64 ;C: }}{{ \\ Program Files (x86) }}{{ \\ Windows Kits\\10\\ bin\\x86 binx86 ;C: }}{{ \\ Program Files (x86) }}{{ \\ Microsoft SDKs\\Windows\\v10.0A\\bin }}{{ \\ NETFX 4.6.1 Tools\\x64 }}{{ ;C: }} {{ \\ Program Files (x86) }}{{ \\ Common Files\\Oracle\\Java\\javapath;C:\\ProgramData\\Oracle\\Java\\javapath;C:\\CMake\\bin;c:\\windows\\system32;C: }} \\ {{ Program Files }} {{ \\ NVIDIA GPU Computing Toolkit\\CUDA\\v7. 0\\bin 0bin ;C: }}{{ \\ Program Files }}{{ \\ NVIDIA GPU Computing Toolkit\\CUDA\\v7. 0\\libnvvp 0libnvvp ;g: }}{{ \\ Bin; }} """// another variant, also does not affect CMake// vars = bat returnStdout: true, script: """//@call "C: \ {{ Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat " amd64//set// "" }} " {{ def cmakeArgs = "-DARG=VALUE" }} {{ def cmake_inst = 'InSearchPath' }}{{ steps.add([envVars: vars]) }} {{ cmakeArgs = cmakeArgs + " -DCMAKE_C_COMPILER=cl -DCMAKE_CXX_COMPILER=cl -DCMAKE_MAKE_PROGRAM=g:\\Bin }}{{ \\ ninja" }} {{ tasks["${os}"] = { }} {{ node("${os}"){ }} {{ stage("${os}/${config}") { }} {{ withEnv([vars]){ }} {{ if (os == "windows") }} { \{{}} bat "set | sort" println vars println steps {\{ } }} {\{ cmakeBuild(buildDir: "build_${config}", }} \{{ buildType: config, }} \{{ cleanBuild: true, }} \{{ cmakeArgs: cmakeArgs, }} \{{ generator: generator, }} \{{ installation: cmake_inst, }} \{{ sourceDir: ".", }} {{
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-57501
cmakeBuild does not set environment variables in Windows when run in Pipeline
Change By:
Vladimir Eremeev
Pipeline snippet{{def cmake_tasks() {}}{{ def tasks=[:]}}{{ def steps = [[withCmake: true]]}}{{def os = "windows"}}{{ def config = "Debug"}}{{ def generator = "Ninja"}} {{ def vars="""}}{{ LIB=C: \\ Program Files (x86) \\ Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;C: \\ Program Files (x86) \\ Microsoft Visual Studio 14.0\\VC\\ATLMFC\\LIB\\amd64;C: \\ Program Files (x86) \\ Windows Kits\\10\\lib\\10.0.17763.0\\ucrt\\x64;C: \\ Program Files (x86) \\ Windows Kits\\NETFXSDK\\4.6.1\\lib\\um\\x64;C: \\ Program Files (x86) \\ Windows Kits\\10\\lib\\10.0.17763.0\\um \\ x64;}}{{ PATH=C: \\ Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C: \\ Program Files (x86) \\ Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319;C:\\Windows\\Microsoft.NET\\Framework64\\;C: \\ Program Files (x86)}}{{Windows Kits\\10\\bin\\x64;C: \\ }}{{ Program Files (x86) \\ }}{{ Windows Kits\\10\\bin\\x86;C: \\ }}{{ Program Files (x86) \\ }}{{ Microsoft SDKs\\Windows\\v10.0A\\bin \\ }}{{ NETFX 4.6.1 Tools\\x64 \\ }}{{ ;C:}}{{Program Files (x86) \\ }}{{ Common Files\\Oracle\\Java\\javapath;C:\\ProgramData\\Oracle\\Java\\javapath;C:\\CMake\\bin;c:\\windows\\system32;C: \\ }}{{ Program Files}}{{NVIDIA GPU Computing Toolkit\\CUDA\\v7.0\\bin;C: \\ }}{{ Program Files \\ }}{{ NVIDIA GPU Computing Toolkit\\CUDA\\v7.0\\libnvvp;g: \\ }}{{ Bin;}} \ {{ """}}{{ def cmakeArgs = "-DARG=VALUE"}}{{ def cmake_inst = 'InSearchPath'}}{{steps.add([envVars: vars])}}{{ cmakeArgs = cmakeArgs + " -DCMAKE_C_COMPILER=cl -DCMAKE_CXX_COMPILER=cl -DCMAKE_MAKE_PROGRAM=g:\\Bin \\ }}{{ ninja"}}{{ tasks["${os}"] = {}}{{ node("${os}"){}}{{ stage("${os}/${config}") {}}{{ withEnv([vars]){}}{{ if (os == "windows")}}{ \ {{}} bat "set | sort" println vars println steps{ \ { }}}{ \ { cmakeBuild(buildDir: "build_${config}", }} \ {{ buildType: config, }} \ {{ cleanBuild: true, }} \ {{ cmakeArgs: cmakeArgs, }} \ {{ generator: generator, }} \ {{ installation: cmake_inst, }} \ {{ sourceDir: ".", }}{{ steps: steps)}}{{ }}}{{ }}} \ {{ }}}{{ }}}{{ return tasks}} \ {{ }}} {{pipeline {}}{{ agent none}}{{ stages{}}{{ stage('Configurte') {}}{{ steps}}{ \ {{}}{{ script {}}{ \ { parallel cmake_tasks() }}{ \ { }}}{ \ { }}} \ {{ }}}{{ }}} \ {{ }}}Snippet of CMakeLists.txt
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev commented on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
Also, it would be good to handle call of "vcvarsall.bat" inside cmakeBuild. Currently I've made a workaround: bat """ call c:\Path\to\Visual\Studio\vcvarsall.bat set > build.props """ var = readFile("build.props") ... cmakeBuild steps: [envVars : vars]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.581.1558081440092%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-57501
cmakeBuild does not set environment variables in Windows when run in Pipeline
Change By:
Vladimir Eremeev
Pipeline snippet{{def cmake_tasks() { }} {{ def tasks=[:] }} {{ def steps = [[withCmake: true]] }}{{ def os = "windows" }} {{ def config = "Debug" }} {{ def generator = "Ninja" }}{{ def vars=""" }} {{ LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\ATLMFC\\LIB\\amd64;C:\\Program Files (x86)\\Windows Kits\\10\\lib\\10.0.17763.0\\ucrt\\x64;C:\\Program Files (x86)\\Windows Kits\\NETFXSDK\\4.6.1\\lib\\um\\x64;C:\\Program Files (x86)\\Windows Kits\\10\\lib\\10.0.17763.0\\um\\x64; }} {{ PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319;C:\\Windows\\Microsoft.NET\\Framework64\\;C:\\Program Files (x86) \\ }}{{ Windows Kits\\10\\bin\\x64;C:\\Program Files (x86)\\Windows Kits\\10\\bin\\x86;C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v10.0A\\bin\\NETFX 4.6.1 Tools\\x64\\;C: \\ }}{{ Program Files (x86)\\Common Files\\Oracle\\Java\\javapath;C:\\ProgramData\\Oracle\\Java\\javapath;C:\\CMake\\bin;c:\\windows\\system32;C:\\Program Files \\ }}{{ NVIDIA GPU Computing Toolkit\\CUDA\\v7.0\\bin;C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v7.0\\libnvvp;g:\\Bin; }} {{ """ }} {{ def cmakeArgs = "-DARG=VALUE" }} {{ def cmake_inst = 'InSearchPath' }}{{ steps.add([envVars: vars]) }} {{ cmakeArgs = cmakeArgs + " -DCMAKE_C_COMPILER=cl -DCMAKE_CXX_COMPILER=cl -DCMAKE_MAKE_PROGRAM=g:\\Bin\\ninja" }} {{ tasks["${os}"] = { }} {{ node("${os}"){ }} {{ stage("${os}/ Debug ${config} ") { }} {{ withEnv([vars]){ }} {{ if (os == "windows") }} { {{}} bat "set | sort" println vars println steps {{ } }} {{ cmakeBuild(buildDir: "build_${config}",}}{{ buildType: config,}}{{ cleanBuild: true,}}{{ cmakeArgs: cmakeArgs,}}{{ generator: generator,}}{{ installation: cmake_inst,}}{{ sourceDir: ".",}}{{ steps: steps) }} {{ } }} {{ } }} {{ } }} {{
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title Vladimir Eremeev commented on JENKINS-57501 Re: cmakeBuild does not set environment variables in Windows when run in Pipeline Yes, this duplicates JENKINS-51060 with addition of ignorance of "envVars" in steps. According to last comment in that issue, added 2 months after it was closed, the bug was not fixed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.553.1558077060129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57502) Cmake arguments sometimes are added to path in parallel build
Title: Message Title
Vladimir Eremeev created an issue
Jenkins / JENKINS-57502
Cmake arguments sometimes are added to path in parallel build
Issue Type:
Bug
Assignee:
Martin Weber
Components:
cmakebuilder-plugin
Created:
2019-05-16 09:34
Environment:
Jenkins version 2.164.3 cmake plugin version 2.6.1
Priority:
Blocker
Reporter:
Vladimir Eremeev
I'm trying to simulate matrix build using Pipeline Pipeline snippet {{def cmake_tasks(os_labels, configs, DL_on_off) { tasks = [:] def DL_dir_labels = ['ON': 'DL', 'OFF': 'noDL'] for(int i = 0; i < os_labels.size(); i++) { def os = os_labels[i] for (int j = 0; j < configs.size(); j++) { for (int k = 0; k < DL_on_off.size(); k++) { def config = configs[j] def DL = DL_on_off[k] def DL_dir_label = DL_dir_labels["${DL}"] def generator = "Ninja" def steps = [[withCmake: true]] def cmakeArgs = "-Dsomevar=somevalue" def cmake_inst = 'InSearchPath' tasks["${os}/${config}/${DL_dir_label}"] = { node("build && ${os}") { stage("${os}/${config}/${DL_dir_label}") { if (os == "windows") { bat """ ${env.WORKSPACE}\\DL\\test\\supportconfigure.cmd ${config} build_${config}_${DL_dir_label} ${DL} ninja """ } else { cmakeBuild(buildDir: "build_${config}_${DL_dir_label}", buildType: config, cleanBuild: true, cmakeArgs: cmakeArgs, generator: generator, installation: cmake_inst, sourceDir: ".", steps: steps) } } } } } } } return tasks } pipeline { agent none parameters { string(defaultValue: 'develop', description: 'Commit ID or branch name to build', name: 'branch', trim: false) } stages { stage('Checkout') { steps { script { // checkout on windows and linux } } } stage('Configure & Build') { steps { script { def OSes = ["windows", "linux"] def configs = ["Release", "Debug"] def DL_inc = ["ON", "OFF"] parallel cmake_tasks(OSes,
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev created an issue
Jenkins / JENKINS-57501
cmakeBuild does not set environment variables in Windows when run in Pipeline
Issue Type:
Bug
Assignee:
Martin Weber
Components:
cmakebuilder-plugin
Created:
2019-05-16 08:14
Environment:
Jenkins ver. 2.164.3 Cmake plugin version 2.6.1 Jenkins slave running on windows machine as a service.
Priority:
Blocker
Reporter:
Vladimir Eremeev
Pipeline snippet {{def cmake_tasks() { def tasks=[:] def steps = [[withCmake: true]] def os = "windows" def config = "Debug" def generator = "Ninja" def vars=""" LIB=C:Program Files (x86)Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;C:Program Files (x86)Microsoft Visual Studio 14.0\\VC\\ATLMFC\\LIB\\amd64;C:Program Files (x86)Windows Kits\\10\\lib\\10.0.17763.0\\ucrt\\x64;C:Program Files (x86)Windows Kits\\NETFXSDK\\4.6.1\\lib\\um\\x64;C:Program Files (x86)Windows Kits\\10\\lib\\10.0.17763.0\\umx64; PATH=C:Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:Program Files (x86)Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319;C:\\Windows\\Microsoft.NET\\Framework64\\;C:Program Files (x86)Windows Kits\\10\\bin\\x64;C:Program Files (x86)Windows Kits\\10\\bin\\x86;C:Program Files (x86)Microsoft SDKs\\Windows\\v10.0A\\binNETFX 4.6.1 Tools\\x64\\;C:Program Files (x86)Common Files\\Oracle\\Java\\javapath;C:\\ProgramData\\Oracle\\Java\\javapath;C:\\CMake\\bin;c:\\windows\\system32;C:Program FilesNVIDIA GPU Computing Toolkit\\CUDA\\v7.0\\bin;C:Program FilesNVIDIA GPU Computing Toolkit\\CUDA\\v7.0\\libnvvp;g:Bin; """ def cmakeArgs = "-DARG=VALUE" def cmake_inst = 'InSearchPath' steps.add([envVars: vars]) cmakeArgs = cmakeArgs + " -DCMAKE_C_COMPILER=cl -DCMAKE_CXX_COMPILER=cl -DCMAKE_MAKE_PROGRAM=g:\\Binninja"
[JIRA] (JENKINS-57008) Jenkins declarative-linter does not handle missing variables
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-57008
Jenkins declarative-linter does not handle missing variables
Change By:
Vladimir Eremeev
Following pipeline with errors is successfully validated.{{ pipeline {agent anystages {stage('Build') {steps {script { println missing_variable }} } } } }} {{ ssh -p 18122 username@jenkins declarative-linter < jf Jenkinsfile successfully validated. }}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57008) Jenkins declarative-linter does not handle missing variables
Title: Message Title
Vladimir Eremeev created an issue
Jenkins / JENKINS-57008
Jenkins declarative-linter does not handle missing variables
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-04-15 09:38
Environment:
Jenkins ver. 2.164.2 Pipeline plugin version 2.6
Priority:
Major
Reporter:
Vladimir Eremeev
Following pipeline with errors is successfully validated. {{ pipeline { agent any stages { stage('Build') { steps { script { println missing_variable } } } } } }} {{ ssh -p 18122 username@jenkins declarative-linter < jf Jenkinsfile successfully validated. }}
Add Comment
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Vladimir Eremeev commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines I see this error on Jenkins 2.164.1 One my pipeline job started failing today with unclear reason. Both successful jobs and failed jobs contain "Terminated" in console logs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56193) Warnings-ng plugin cannot parse messages from MSBuild with relative paths
Title: Message Title Vladimir Eremeev updated an issue Jenkins / JENKINS-56193 Warnings-ng plugin cannot parse messages from MSBuild with relative paths Change By: Vladimir Eremeev Attachment: consoleText.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56193) Warnings-ng plugin cannot parse messages from MSBuild with relative paths
Title: Message Title Vladimir Eremeev commented on JENKINS-56193 Re: Warnings-ng plugin cannot parse messages from MSBuild with relative paths Yes, similar. What about letting user to specify path mapping? Valgrind plugin does so. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56193) Warnings-ng plugin cannot parse messages from MSBuild with relative paths
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-56193
Warnings-ng plugin cannot parse messages from MSBuild with relative paths
Change By:
Vladimir Eremeev
I use CMake to generate Visual Studio solution in a separate directory ([out of source build|https://cgold.readthedocs.io/en/latest/tutorials/out-of-source.html])For example:{{ {{ mkdir build}} }} {{cd build}}{{cmake .. -GNinja}}Compiler prints warnings in the following format:{{ {{ [14/139] Building C object modules\Lib\CMakeFiles\Lib.dir\file.c.obj}} }} {{ ..\modules\Lib\file.c(608): warning C4101: 'i': unreferenced local variable}}{{ ..\modules\Lib\file.c(725): warning C4267: '=': conversion from 'size_t' to 'int', possible loss of data}}And the Warnings-NG plugin, called at the post-build step, cannot find these files and outputs errors:{{ {{ [MSBuild] [ERROR] Can't resolve absolute paths for some files:}} }} {{[MSBuild] [ERROR] - ../modules/Lib/file.c}}{{ ...}}{{[MSBuild] [ERROR] Can't create fingerprints for some files:}}{{[MSBuild] [ERROR] - '../modules/Lib/file.c', IO exception has been thrown: java.nio.file.NoSuchFileException: ..\modules\Lib\file.c}}{{ ...}}{{[MSBuild] [ERROR] Can't create blame requests for some affected files:}}{{[MSBuild] [ERROR] - Skipping non-workspace file ../modules/Lib/file.c}}{{ ...}}h2. Suggestion:Add option for path mapping, relative to workspace root.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56193) Warnings-ng plugin cannot parse messages from MSBuild with relative paths
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-56193
Warnings-ng plugin cannot parse messages from MSBuild with relative paths
Change By:
Vladimir Eremeev
I use CMake to generate Visual Studio solution in a separate directory ([out of source build|https://cgold.readthedocs.io/en/latest/tutorials/out-of-source.html])For example:{{ {{ mkdir build}} }} {{ cd build }}{{ cmake .. -GNinja}}Compiler prints warnings in the following format:{{ {{ [14/139] Building C object modules\Lib\CMakeFiles\Lib.dir\file.c.obj}} }} {{ ..\modules\Lib\file.c(608): warning C4101: 'i': unreferenced local variable}}{{ ..\modules\Lib\file.c(725): warning C4267: '=': conversion from 'size_t' to 'int', possible loss of data}}And the Warnings-NG plugin, called at the post-build step, cannot find these files and outputs errors:{{ {{ [MSBuild] [ERROR] Can't resolve absolute paths for some files:}} }} {{ [MSBuild] [ERROR] - ../modules/Lib/file.c}}{{ ...}}{{ [MSBuild] [ERROR] Can't create fingerprints for some files:}}{{ [MSBuild] [ERROR] - '../modules/Lib/file.c', IO exception has been thrown: java.nio.file.NoSuchFileException: ..\modules\Lib\file.c}}{{ ...}}{{ [MSBuild] [ERROR] Can't create blame requests for some affected files:}}{{ [MSBuild] [ERROR] - Skipping non-workspace file ../modules/Lib/file.c}}{{ ...}}h2. Suggestion:Add option for path mapping, relative to workspace root.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56193) Warnings-ng plugin cannot parse messages from MSBuild with relative paths
Title: Message Title
Vladimir Eremeev created an issue
Jenkins / JENKINS-56193
Warnings-ng plugin cannot parse messages from MSBuild with relative paths
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-02-19 08:30
Environment:
Versions: Jenkins: 2.150.3 Warnings NG: 5.0.1
Priority:
Major
Reporter:
Vladimir Eremeev
I use CMake to generate Visual Studio solution in a separate directory (out of source build) For example: mkdir build {{ cd build }} {{ cmake .. -GNinja}} Compiler prints warnings in the following format: [14/139] Building C object modules\Lib\CMakeFiles\Lib.dir\file.c.obj {{ ..\modules\Lib\file.c(608): warning C4101: 'i': unreferenced local variable}} {{ ..\modules\Lib\file.c(725): warning C4267: '=': conversion from 'size_t' to 'int', possible loss of data}} And the Warnings-NG plugin, called at the post-build step, cannot find these files and outputs errors: [MSBuild] [ERROR] Can't resolve absolute paths for some files: {{ [MSBuild] [ERROR] - ../modules/Lib/file.c}} {{ ...}} {{ [MSBuild] [ERROR] Can't create fingerprints for some files:}} {{ [MSBuild] [ERROR] - '../modules/Lib/file.c', IO exception has been thrown: java.nio.file.NoSuchFileException: ..\modules\Lib\file.c}} {{ ...}} {{ [MSBuild] [ERROR] Can't create blame requests for some affected files:}} {{ [MSBuild] [ERROR] - Skipping non-workspace file ../modules/Lib/file.c}} {{ ...}} Suggestion: Add option for path mapping, relative to workspace root.
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Vladimir Eremeev commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent Peter Vohmann: Thank you, I've obtained one more key with ssh-keyscan, having ssh-rsa in it, and the slave now launches fine. Michael Clarke: I think, more information in the help message will be useful. I mean the following: - this is a help on the slave configuration page. It says nothing about supported key encodings. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Vladimir Eremeev updated an issue Jenkins / JENKINS-42959 Failed known_hosts verification for SSH agent Change By: Vladimir Eremeev Attachment: J42959.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Vladimir Eremeev edited a comment on JENKINS-42959 Re: Failed known_hosts verification for SSH agent How can I change it? Looks like SSH settings are default. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Vladimir Eremeev commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent How can I change it? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-42959
Failed known_hosts verification for SSH agent
Change By:
Vladimir Eremeev
SSH agent isn't launched after the latest update, complaining about missing records in the known hosts file.Nevertheless, the records do exist. I've tried to connect manually with ssh, everything was fine, ssh reports that it has found the host in known_hosts.Probable reason is the hashed host name in known_hosts.Here is the log from the Jenkins slave launch page:{noformat}[03/21/17 11:40:34] [SSH] Opening SSH connection to xxx.xxx.xxx.xxx:22[03/21/17 11:40:34] [SSH] WARNING: No entry currently exists in the Known Hosts file for this host. Connections will be denied until this new host and its associated key is added to the Known Hosts file. Key exchange was not finished, connection is closed. java.io.IOException: There was a problem while connecting to xxx.xxx.xxx.xxx:22 at com.trilead.ssh2.Connection.connect(Connection.java:818) at com.trilead.ssh2.Connection.connect(Connection.java:687) at com.trilead.ssh2.Connection.connect(Connection.java:601) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1265) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:790) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:785) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Key exchange was not finished, connection is closed. at com.trilead.ssh2.transport.KexManager.getOrWaitForConnectionInfo(KexManager.java:93) at com.trilead.ssh2.transport.TransportManager.getConnectionInfo(TransportManager.java:230) at com.trilead.ssh2.Connection.connect(Connection.java:770) ... 9 more Caused by: java.io.IOException: The server hostkey was not accepted by the verifier callback at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:591) at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:777) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:489) ... 1 more [03/21/17 11:40:34] Launch failed - cleaning up connection [03/21/17 11:40:34] [SSH] Connection closed.{noformat}And this is the debug output from ssh, showing that it has found a record in the seknown_hosts second line of known_hosts .{noformat} $ sudo -u jenkins -g jenkins ssh -v jenk...@xxx.xxx.xxx.xxxOpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014debug1: Reading configuration data /etc/ssh/ssh_configdebug1: /etc/ssh/ssh_config line 19: Applying options for *debug1: Connecting to xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx] port 22.debug1: Connection established.debug1: identity file /var/lib/jenkins/.ssh/id_rsa type 1...debug1: sending SSH2_MSG_KEX_ECDH_INITdebug1: expecting SSH2_MSG_KEX_ECDH_REPLY
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-42959
Failed known_hosts verification for SSH agent
Change By:
Vladimir Eremeev
SSH agent isn't launched after the latest update, complaining about missing records in the known hosts file.Nevertheless, the records do exist. I've tried to connect manually with ssh, everything was fine, ssh reports that it has found the host in known_hosts.Probable reason is the hashed host name in known_hosts.Here is the log from the Jenkins slave launch page:{noformat}[03/21/17 11:40:34] [SSH] Opening SSH connection to xxx.xxx.xxx.xxx:22[03/21/17 11:40:34] [SSH] WARNING: No entry currently exists in the Known Hosts file for this host. Connections will be denied until this new host and its associated key is added to the Known Hosts file. Key exchange was not finished, connection is closed. java.io.IOException: There was a problem while connecting to xxx.xxx.xxx.xxx:22 at com.trilead.ssh2.Connection.connect(Connection.java:818) at com.trilead.ssh2.Connection.connect(Connection.java:687) at com.trilead.ssh2.Connection.connect(Connection.java:601) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1265) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:790) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:785) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Key exchange was not finished, connection is closed. at com.trilead.ssh2.transport.KexManager.getOrWaitForConnectionInfo(KexManager.java:93) at com.trilead.ssh2.transport.TransportManager.getConnectionInfo(TransportManager.java:230) at com.trilead.ssh2.Connection.connect(Connection.java:770) ... 9 more Caused by: java.io.IOException: The server hostkey was not accepted by the verifier callback at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:591) at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:777) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:489) ... 1 more [03/21/17 11:40:34] Launch failed - cleaning up connection [03/21/17 11:40:34] [SSH] Connection closed.{noformat}And this is the debug output from ssh, showing that it has found a record in the seknown_hosts.{noformat} $ sudo -u jenkins -g jenkins ssh -v jenk...@xxx.xxx.xxx.xxxOpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014debug1: Reading configuration data /etc/ssh/ssh_configdebug1: /etc/ssh/ssh_config line 19: Applying options for *debug1: Connecting to xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx] port 22.debug1: Connection established.debug1: identity file /var/lib/jenkins/.ssh/id_rsa type 1...debug1: sending SSH2_MSG_KEX_ECDH_INITdebug1: expecting SSH2_MSG_KEX_ECDH_REPLYdebug1: Server host key: ECDSA
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Vladimir Eremeev created an issue Jenkins / JENKINS-42959 Failed known_hosts verification for SSH agent Issue Type: Bug Assignee: Stephen Connolly Components: ssh-credentials-plugin, ssh-slaves-plugin Created: 2017/Mar/21 10:19 AM Environment: Versions: Jenkins: 2.51 SSH Agent Plugin: 1.14 SSH Credentials plugin: 1.13 SSH Slaves Plugin : 1.15 Ubuntu 14.04, 16.04 Priority: Major Reporter: Vladimir Eremeev SSH agent isn't launched after the latest update, complaining about missing records in the known hosts file. Nevertheless, the records do exist. I've tried to connect manually with ssh, everything was fine, ssh reports that it has found the host in known_hosts. Probable reason is the hashed host name in known_hosts. Here is the log from the Jenkins slave launch page: [03/21/17 11:40:34] [SSH] Opening SSH connection to xxx.xxx.xxx.xxx:22 [03/21/17 11:40:34] [SSH] WARNING: No entry currently exists in the Known Hosts file for this host. Connections will be denied until this new host and its associated key is added to the Known Hosts file. Key exchange was not finished, connection is closed. java.io.IOException: There was a problem while connecting to xxx.xxx.xxx.xxx:22 at com.trilead.ssh2.Connection.connect(Connection.java:818) at com.trilead.ssh2.Connection.connect(Connection.java:687) at com.trilead.ssh2.Connection.connect(Connection.java:601) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1265) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:790) at
