[Issue 4722] New - Hudson serializes AccuRev pops

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[Issue 4722] New - Hudson serializes AccuRev pops

sowens01
https://hudson.dev.java.net/issues/show_bug.cgi?id=4722
                 Issue #|4722
                 Summary|Hudson serializes AccuRev pops
               Component|hudson
                 Version|current
                Platform|All
              OS/Version|All
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P1
            Subcomponent|accurev
             Assigned to|statlor
             Reported by|sowens01






------- Additional comments from [hidden email] Tue Oct 27 03:31:43 +0000 2009 -------
I was checking on a number of builds that I have just converted over to hudson.
The code base is quite large (3 GB), so it takes quite a while to get the code
from AccuRev. From the hudson main page it looked as though all the builds had
started, but when I actually check the build directories, only one was being
populated. Checking the job logs, the one that was being populated had a log
file that showed content being populated in the directories. One of the other
jobs was at the "populating workspace" message in the log, and the other was at
the "Authenticating" message.

I waited a number of minutes for the first job to finish populating. Shortly
after completion of the first populate, one of the other jobs started populating
the build directory. Once that one completed populating, the last job started
populating the directory.

All the jobs are set up to poll AccuRev at the same time using the same user,
and build the code if changes in the selected stream are found (also the same
across all the jobs).

Is there any reason why the populating of the workspace is done in a serial
fashion? I had these set up as a cron job before converting to hudson, with the
same configuration (same user populating different directories at the same time,
etc) and never had to serialize the builds.

Given the size of the code base, this could have a negative impact on the
performance of our already lengthy builds.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 4722] Hudson serializes AccuRev pops

statlor
https://hudson.dev.java.net/issues/show_bug.cgi?id=4722






------- Additional comments from [hidden email] Tue Nov  3 20:51:16 +0000 2009 -------
Thanks for the information. I will look into the issue and see what I can find
out. I am not the original developer of the plugin, so I'm not sure yet what the
rationale is for serializing pops.

Question for you - are you using AccuRev workspaces on these jobs or no?

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 4722] Hudson serializes AccuRev pops

sowens01
In reply to this post by sowens01
https://hudson.dev.java.net/issues/show_bug.cgi?id=4722






------- Additional comments from [hidden email] Tue Nov  3 23:51:32 +0000 2009 -------
Not at the moment. We're using the custom workspace option, which apparently
does an 'accurev pop -R -O'.

Let me know if I can be of any help. I was thinking about downloading the code
just to read it: both to see how plugins work and to see how the AccuRev plugin
specifically works.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]