does anyone has an idea how to change the build template that is used? or how to customize our pom to support it?
On Tuesday, July 19, 2016 at 3:18:01 PM UTC+3, [email protected] wrote: > > Hi, > i've noticed that the regular Jenkins build of our plugin on the cloudbees > service for Jenkins CI fails. > I guess the issue is due to Jenkins node based on Linux while the pom > requires windows path for .Net framework files. > > What's the best solution for cases such as this? > > I'm attaching the build log. > > The errors can be seen at the end - > >> ERROR] Failed to execute goal >> org.codehaus.mojo:exec-maven-plugin:1.4.0:exec (clean >> HPToolsLauncher) on project hp-application-automation-tools-plugin: >> Command execution >> failed. Cannot run program >> "C:/Windows/Microsoft.NET/Framework/v4.0.30319/msbuild.exe" >> (in directory >> "/scratch/jenkins/workspace/plugins/hp-application-automation-toolsplugin/ >> HpToolsLauncher"): error=2, No such file or directory -> [Help 1] >> > > the link to the build is: > > https://jenkins.ci.cloudbees.com/job/plugins/job/hp-application-automation-tools-plugin/ > > (it compiles well on our windows based build Jenkins nodes) > > Thanks ahead, > Fima. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6d8f22f0-cb85-45af-b137-970852bdf14d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
