You'll have to do some housekeeping anyway....Otherwise you'll run out of
memory very fast.
By archiving all the artefacts generated(mainly needed for release steps or
similar) on your own you'll be able to keep your jenkins workspace very slim.
This is an advantage and practicable.
Keeping Console Output by simply archiving is possible. I do so on the
following way:
-Use Log Parser Plugin which generates a Log.txt or similar in your project on
slave workspace and include it as post build step('Console output(build
log)parsing')
-Get your Console Output from slaves by scp/ssh or similar e.g.
Original Message processed by david®
Re: Re-4: Copy files from remote Jenkins workspace (14-Nov-2016 10:41)
From: Eran Yanay
To:[email protected]
Discarding older builds means it discards my console output of these builds as
well, I wish to keep it.
On Mon, Nov 14, 2016 at 11:40 AM, Jovan Jevric <[email protected]> wrote:
Do archive the artefacts elsewhere by running a post-build job, as you
proposed. And simply parametrize your job that way, that elder jobs on your
host are being deleted automatically. In other words - simply discard old
builds, doing that is very simple.
Original Message processed by david®
Re: Re-2: Copy files from remote Jenkins workspace (14-Nov-2016 10:15)
From: buddy123
To:Jenkins Users
I'll look into pipeline, though it seems very complicated.
Regarding artifacts, I've thought about it, but I cant figure out how to delete
the artifacts once I finished the job, otherwise my disk space will get empty
very quickly.
Is it possilble to mark files as artifacts, pull them from slave, and then
erase them?
I want to keep the console output of every build though, just dont care about
the artifacts because I store them elsewhere
On Monday, November 14, 2016 at 11:12:08 AM UTC+2, jje wrote:
What about archiving artefacts. On that way all output marked as artefacts
could be found on master so far, couldn't it?
Original Message processed by david®
Re: Copy files from remote Jenkins workspace (13-Nov-2016 15:39)
From: Baptiste Mathus
To:[email protected]
Look for pipeline jobs. Might be far easier to achieve that.
https://jenkins.io/pipeline/getting-started-pipelines/[jenkins.io]
2016-11-13 11:23 GMT+01:00 buddy123 <[email protected]>:
down votefavorite[stackoverflow.com] Im trying to create a cross-compilation
job, that will build my code for both Windows & Linux. I have set up Windows &
Linux jenkins nodes, and configured two jobs, one with 'windows' label to run
on my Windows machine and the other with 'linux' label to run on my linux
machine. I installed MultiJob plugin, and wrapped both jobs to run in parallel
When both finishes successfully, I want to copy all the generated files and do
operations on them In other words I want to copy the files from both jobs
remote workspaces for further operations Can anyone suggest a way how to do it?
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/05639dc0-fce6-4ce7-9cc1-c39e95ca7498%40googlegroups.com[groups.google.com].
For more options, visit https://groups.google.com/d/optout[groups.google.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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6i%3DXazsb%3DzYyQ_21PXnJSQN5gNpBmJJycUZrOnwZXTaA%40mail.gmail.com[groups.google.com].
For more options, visit https://groups.google.com/d/optout[groups.google.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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/d70bc939-7416-4d89-9265-7b2d8631d301%40googlegroups.com[groups.google.com].
For more options, visit https://groups.google.com/d/optout[groups.google.com].
--
You received this message because you are subscribed to a topic in the Google
Groups "Jenkins Users" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-users/1OChk_e4A6Y/unsubscribe[groups.google.com].
To unsubscribe from this group and all its topics, send an email to
[email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/DIIE.0000228E0093FFA4%4010.11.0.23[groups.google.com].
For more options, visit https://groups.google.com/d/optout[groups.google.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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CABz3omUiTCaB%3DHmJ%2BJbBj_tST9ST3jYkO4Mzf5TDK3tYVL09Xg%40mail.gmail.com[groups.google.com].
For more options, visit https://groups.google.com/d/optout[groups.google.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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/DIIE.000021EC00940142%4010.11.0.23.
For more options, visit https://groups.google.com/d/optout.
