If the artifacts are not rebuilt, they should still be available in the
workspace, and you could archive them. If they are not present in the
workspace, you could add a build step to copy them from the last
successful build, and then archive them. This would have the drawback of
increasing the disk space used by saved artifacts, depending on how long
you keep past builds and artifacts around.
The other thing would be to use a repository manager such as Nexus to
store your artifacts, which would integrate well with Maven builds.
Eric
On 1/22/2014 8:12 AM, starwarsfan wrote:
Hi
I have a huge maven project which produces a bunch of *.ear and *.zip
artifacts. These artifacts where archived at the end of job run using
the appropriate step on the Post-Build section to make them available
on the job overview page. To increase the speed of build I activated
the incremental build option, which works as a charm. But now I step
into a problem: There are only these artifacts available on the job
overview page, which where build on the last run! That's a problem
because there are some artifacts with a very low amount of changes, so
they will be build rarely. But they must be available on the job
overview page too! Any ideas on how to achieve this?
Kind regards,
Yves
--
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.
