On 31/07/2013 21:36, Eric Pyle wrote:
Hi Chris,
You can get a shell script as a post-build action by using Flexible
Publish or PostBuildScript plugins.
Which version of PostBuildScript plugin works with 1.480.3?
I tried to upgrade to 1.509.2 but got this heinous error:
https://issues.jenkins-ci.org/browse/JENKINS-19031
Regarding the main problem you are having, does the user running Jenkins
have that /coredumps path available?
Yes, the jenkins user can list, create and delete files in that directory.
cheers,
Chris
Eric
On 7/31/2013 1:11 PM, Chris Withers wrote:
Hi All,
We've noticed that some of our jobs are leaving core files in
/coredumps and we'd like to archive those as artifacts when that happens.
So, how do we do that?
If I put "/coredumps/*" in as a "Pattern for files to be deleted" the
workspace cleanup plugin silently does nothing. Why is that?
Okay, so work around that with a "rm -f /coredumps/*" at the start of
the jobs.
So, setting /coredumps/** as a "Files to archive" pattern doesnt work:
- if there are core files there, they're ignored and I get an error
"No artifacts that match the file pattern "/coredump/**". Why is that?
- if there are no core files, I get the same error, but for a
different reason.
So, to work around that, what I'd *like* to do is:
tar czf $WORKSPACE/coredumps.tgz /coredumps
...but where do I put this? core dumps are, you know, most likely when
a build has failed ;-)
How can I get a shell command to execute as a post-build action?
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--
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.
