|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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/d/optout.
The whole idea is to 1) save space and 2) save time
I have 50 jobs all using the same stream.
Each time a job is running on a new executor it does a full sync (e.g. 10minutes vs 10s if an incremental sync could be done) and a new workspace is created.
So for a slave of 16 executors: i will have 16x50 copies of the same source code.
Now i want to run the same jobs on a second stream or 3 third stream or have 200 jobs.
It just doesn't scale unless you have a massive amount of disk space and don't mind the sync time or P4 server overhead of managing all the have lists.
So I have a working Jenkins system and i understand how all the bits work.
I can just see that in 3 months we are going to run out of disk space.....