Re: Pipeline powershell

I have add the support info inside the following bug https://issues.jenkins-ci.org/browse/JENKINS-42988 As far as the mini repro project, I cannot reproduce it with a strip down pipeline file that does the same bat command on the same repos checkout. So it look like (not sure yet, only 5 build

Re: Pipeline powershell

Hi James, I will try to install the plugin and provide more information (I was giving the dump and the system info, but I may generate even more with this it seem). As for JENKINS-34150 goes it definitely did not fix everything, since many

Re: Pipeline powershell

Given you can reliably reproduce if can you open a new ticket with the minimum steps to reproduce (this likely includes an msbuild project) and include your plugin versions, build logs and a stack trace then it is more likely to get fixed - if you can attach a support bundle

Re: Pipeline powershell

I'm not alone into this situation and this have been a problems for many times for some: - https://issues.jenkins-ci.org/browse/JENKINS-28759 - https://issues.jenkins-ci.org/browse/JENKINS-33164 - https://issues.jenkins-ci.org/browse/JENKINS-42988 And I probably miss some other,

Re: Pipeline powershell

There are many many people using Jenkins with no issues, so perhaps you could give some more information to help solve your problem rather than just leaving for something else. On Tue, Jul 4, 2017 at 6:05 AM Jérôme Godbout wrote: > Not even 3 triggered build did terminate,

Re: Pipeline powershell

Not even 3 triggered build did terminate, it's still hanging itself. So the powershell is no better then batch into this regard. This is getting ridiculous, a CI system who hang is worthless. I guess it's time to find an alternative. [image: bodycad] Jerome Godbout

Re: Pipeline powershell

You can you use powershell natively in pipeline now. https://issues.jenkins-ci.org/browse/JENKINS-34581 -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: Pipeline powershell

You're right, I was looking at the tool descriptor having an @Symbol. On Fri, Jun 30, 2017 at 12:45 PM wrote: > unless I'm mistaken or I missed the feature, MsBuild plugin is not > pipeline compatible ( >

Re: Pipeline powershell

unless I'm mistaken or I missed the feature, MsBuild plugin is not pipeline compatible ( https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md seem to agree on that, not sure if this up to date). If I'm wrong I will totally up to use it. I was using batch because the plugin

Re: Pipeline powershell

Why not use the msbuild plugin to launch msbuild? https://wiki.jenkins.io/display/JENKINS/MSBuild+Plugin?focusedCommentId=67568742 On Fri, Jun 30, 2017 at 12:35 PM wrote: > So far I can execute the following into a powershell: > $msbuild = "C:\Program Files

Re: Pipeline powershell

def psScript = """ \$msbuild = "${bcad.msbuild_current}" \$options = "${bcad.msbuild_solution_name} ${bcad.msbuild_default_arg. replace('"', '`"').replace('%CD%', '$PSScriptRoot')} /t:Build" Invoke-Expression "& '\$msbuild' \$options" """; powershell returnStatus: false, script: psScript is doing

Re: Pipeline powershell

So far I can execute the following into a powershell: $msbuild = "C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe" $options = "BodyCad.sln /m /p:Configuration=Release;Platform=x64;SolutionDir=`" + $PSScriptRoot + `"\ /t:Clean;Build" Invoke-Expression "& '$msbuild' $options" But I cannot

Pipeline powershell

Hi, I just realized that the powershell is not part of pipeline script. I'm no powershell guru. So I wonder how one can use it properly to launch something like msbuild (I known I can launch it with the bat but this often hang like many jenkins issues have already show the problems). So I hope