On Thu, Oct 10, 2013 at 10:17 AM, D Soa <usoa...@gmail.com> wrote:
> The workspace is for source files, not output. Yes, the source from the SCM
> is shared between builds, but each build gets its own output (build) folder.
Does jenikins have anything to do with that part?
> I figured out how to do this by creating an output folder in the project
> directory. The compile output goes there as well as the dependency info
> which is then used by subsequent builds to only compile what is required
> after the next source change. The actual deployment artifacts are built to
> the individual build folder. So it is doing exactly what I want now.
I'd think that would be the normal case. But, if you'd like jenkins
to archive the artifacts on the master you could use the copy-artifact
plugin to retrieve them from the previous build so they would appear
even if the build happens on a different slave.
--
Les Mikesell
lesmikes...@gmail.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.
> For more options, visit https://groups.google.com/groups/opt_out.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
