Am 19.02.2016 um 12:39 schrieb Philip Pemberton:
> I've been given the job of automating the build of some new-ish code
> for a crusty old system which uses a cranky old build system which
> depends on hard-coded paths. Essentially, all input source files must
> be in the same directory, my build script has to copy the source into
> that directory from the Jenkins workspace, then the outputs it
> produces are zipped and archived.
>
> Sadly I have two independent projects which depend in this little
> horror of a compiler.
What about running both projects on different slaves?
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 1596666 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/56C70CAA.7000902%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
