...@googlegroups.com
> *Sent:* Wednesday, March 27, 2013 1:06 PM
> *Subject:* Re: Jenkins, Git, Windows and Line Feeds
>
> William, just saw your post. That is exactly what I had to figure out.
>
> Mark, I would definitely like to have different steps in my build run on
> different
those artifacts in the final
build result.
Mark Waite
>
> From: David Brossard
>To: jenkinsci-users@googlegroups.com
>Sent: Wednesday, March 27, 2013 1:06 PM
>Subject: Re: Jenkins, Git, Windows and Line Feeds
>
>
>William, just saw your po
You need to assign labels ('windows', 'linux', etc.) to your slaves and then
indicate in your jobs what labels are required for that job to run.
- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Mar 27 2013 15:07:36
William, just saw
William, just saw your post. That is exactly what I had to figure out.
Mark, I would definitely like to have different steps in my build run on
different machines, however I still haven't solved the problem that if I
have an MSBuild step anywhere in my config, it tries to find that on my
linux
I found an answer to my own question.
- Set the Jenkins Slave service to run as a specific user on the local
system.
- login as that user and run in a command prompt "git config --global
core.autocrlf input"
- Clear out the Jenkins workspace on that slave so it will do a full gi
I can't tell if you are talking about files created during the build or files
checked out for the build but if it is files checked out for the build perhaps
your git line endings are set wrong. If the git repo is for windows and git
then you need it set to use linux line endings. Check out thi
Could you split your build into two parts, running the part which involves
Linux components on a Linux machine, and the part which requires MSBuild (and
Windows) on your Windows machine, with one of those jobs publishing its build
results as an artifact which the next build takes and includes in
