proper configuration for a project
15 views
Skip to first unread message
pps78
Jan 15, 2015, 12:38:12 AM1/15/15
to jenkins...@googlegroups.com
At first I tried to use "Multi-configuration project", it appeared to be complete disaster in my case.
I use svn, at first it checked out 3.2GB into MyProject/workspace and then it checked out second copy into MyProject/workspace/default.
Then I selected "Emulate clean checkout by first deleting unversioned/ignored files, then 'svn update'", I also set it to use 1.8 svn format (WTF it uses 1.4 by default!?).
It was epic fail. It took more than an hour to make a single build, what some mysterious reason after spending close to an hour checking out full svn repo it would delete that entire svn repo and start new clean svn checkout from scratch (e.g. I didn't see that it was deleting unversioned/ignored files, it deleted everything). I tried to set sparce svn checkout, but jenkins would destroy the repo and check out new clean full 3.2GB repo.
In svn all the options completely failed for me. Everything feels excessively slow. I tried to use last "revert and svn update" option, but the revert step takes freaking years to do on absolutely clean svn copy. I had to settle with "Use 'svn update' as much as possible" and then run my batch script that starts with "svn revert -R .". Why is that these simple stuff cannot work at all? I wasted literally entire day trying to figure out why it was that slow (compared to regular cmd line).
Then, it totally didn't make sense why the hell it checks out second copy of my project into the first copy?! So, at the end I had to switch to "Freestyle project" with the simple "svn update" only option.
Now I have a question. My primary goal at the moment is to build multiple projects (or same project with different build params) and if build fails notify offenders. This part I figured out and it works with email notification (except ass broken skype plugin that sets mood tag lines and doesn't give an option to disable that behavior). Now, I need to build multiple projects, or the same project with different build params. All of them use some common code. If there is some compilation error in that common code, will jenkins end up spamming hard the offenders (because multiple projects will start failing the build)? How do I configure this part properly? Do I add multiple built steps and each of them will build a project, or do I add multiple items (but then it would checkout that same project MANY times). Or I simply need to write huge shell script that builds a project (or a custom config of a project and moves on to another one ony if previous has no errors)?
I use svn, at first it checked out 3.2GB into MyProject/workspace and then it checked out second copy into MyProject/workspace/default.
Then I selected "Emulate clean checkout by first deleting unversioned/ignored files, then 'svn update'", I also set it to use 1.8 svn format (WTF it uses 1.4 by default!?).
It was epic fail. It took more than an hour to make a single build, what some mysterious reason after spending close to an hour checking out full svn repo it would delete that entire svn repo and start new clean svn checkout from scratch (e.g. I didn't see that it was deleting unversioned/ignored files, it deleted everything). I tried to set sparce svn checkout, but jenkins would destroy the repo and check out new clean full 3.2GB repo.
In svn all the options completely failed for me. Everything feels excessively slow. I tried to use last "revert and svn update" option, but the revert step takes freaking years to do on absolutely clean svn copy. I had to settle with "Use 'svn update' as much as possible" and then run my batch script that starts with "svn revert -R .". Why is that these simple stuff cannot work at all? I wasted literally entire day trying to figure out why it was that slow (compared to regular cmd line).
Then, it totally didn't make sense why the hell it checks out second copy of my project into the first copy?! So, at the end I had to switch to "Freestyle project" with the simple "svn update" only option.
Now I have a question. My primary goal at the moment is to build multiple projects (or same project with different build params) and if build fails notify offenders. This part I figured out and it works with email notification (except ass broken skype plugin that sets mood tag lines and doesn't give an option to disable that behavior). Now, I need to build multiple projects, or the same project with different build params. All of them use some common code. If there is some compilation error in that common code, will jenkins end up spamming hard the offenders (because multiple projects will start failing the build)? How do I configure this part properly? Do I add multiple built steps and each of them will build a project, or do I add multiple items (but then it would checkout that same project MANY times). Or I simply need to write huge shell script that builds a project (or a custom config of a project and moves on to another one ony if previous has no errors)?
Reply all
Reply to author
Forward
0 new messages