Hi Yves,
You would need to use the Copy Artifact and Conditional Build Step
plugins. Add a conditional build step that runs after all your artifacts
have been built, with the condition that the rarely changed artifact
file does not exist in the workspace. When the condition is satisfied,
copy that rarely changed artifact from the last successful build of this
job. This way, you will always have a copy of all artifacts in the
workspace, whether or not they were built by the current build, and you
can archive all of them.
Regards,
Eric
On 1/22/2014 9:40 AM, starwarsfan wrote:
Hi Eric,
thx for your response.
Am Mittwoch, 22. Januar 2014 14:30:18 UTC+1 schrieb Eric Pyle:
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.
Can you explain this in detail? I already use the artifact archiver
but it only stores the artifacts which were built during the current
run and so there are no links to the "older" artifacts from previous
builds on the job main page.
The other thing would be to use a repository manager such as Nexus to
store your artifacts, which would integrate well with Maven builds.
We already use Nexus but this is some kind of a special use case where
we explicitly not want to store these artifacts on Nexus for different
reasons.
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 [email protected].
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
