Pipeline support [Fixes JENKINS-26948]

[mdkf]

[pavelpikta]

@marshall777 could you review this changes ?

[burtonr]

Gentle ping to ask for this feature to be merged :smile:

[marcus-sonestedt]

Ping here too

[DamonStamper]

@marshal777's last commit to github was Jan 11, 2018 (over 1.5 years ago). Is there anybody else able to review this? Looking at https://github.com/jenkinsci/msbuild-plugin/graphs/contributors it looks like this plugin is dead.

[moshavnik]

is this pr about to be merged in the near future?

[x86]

Bump.

[MarkEWaite]

Closing this because a bat, powershell, or pwsh step should be used to call msbuild from Pipeline rather than creating special case logic inside this plugin. I agree with the observations from @jglick in https://github.com/jenkinsci/msbuild-plugin/pull/36#discussion_r340092182

[minfrin]

Closing this because a bat, powershell, or pwsh step should be used to call msbuild from Pipeline rather than creating special case logic inside this plugin.

Does this not mean we have to create special logic inside the jenkinsfile instead, which means the implementation details of a particular node are bleeding into the project source code?

I am setting this up right now and surprised at how difficult this appears to be.

[MarkEWaite]

Does this not mean we have to create special logic inside the jenkinsfile instead, which means the implementation details of a particular node are bleeding into the project source code?

I am setting this up right now and surprised at how difficult this appears to be.

https://github.com/jenkinsci/msbuild-plugin/pull/36#discussion_r340159871 describes a technique that uses a Jenkins tool installer for each msbuild configuration and then references that tool from the Pipeline script. The Jenkins tool installer definitions are managed on the Jenkins controller. Other alternatives are discussed in that comment thread.