[JIRA] Created: (JENKINS-11241) AccuRev: reduce load and increase speed for SCM polling

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

[JIRA] Created: (JENKINS-11241) AccuRev: reduce load and increase speed for SCM polling

JIRA noreply@jenkins-ci.org
AccuRev: reduce load and increase speed for SCM polling
-------------------------------------------------------

                 Key: JENKINS-11241
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11241
             Project: Jenkins
          Issue Type: Improvement
          Components: accurev
         Environment: Jenkins v1.432, AccuRev Plugin v0.6.18
            Reporter: robsimon
            Assignee: Scott Tatum


This should feature should be usable per job setting so that each job/project can either use the old style or this style because not every project likes to have the extra stream.

-- -- -- -- --

Here is a suggestion for a more effective AccuRev polling to decide whether a CI build should be started.

1) One time only: Create a sub-stream of Project named Project_Last_CI and set time-basis to "now"
accurev mkstream -s Project_Last_CI -b Project -t now

2) On each polling cycle, check to see if there are any changes in Project (promotes into Project, its parent, its grandparent, any xlinks, etc.)
accurev diff -a -i -v Project -V Project_Last_CI

3) If the accurev diff command produces any output, it is time to kick off a CI build
a) Update Last_CI stream time-basis
accurev chstream -s Project_Last_CI -t now
b) Perform regular hist information being done today to capture transactions
c) workspace update
d) build

Because the diff command normally takes just 4-5 seconds, even for a large stream, this will create a significant load reduction. It should actually enable the project to run the polling more frequently while simultaneously creating less load on the AccuRev server.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Updated: (JENKINS-11241) AccuRev: reduce load and increase speed for SCM polling

JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-11241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

robsimon updated JENKINS-11241:
-------------------------------

    Description:
This feature should be usable per job setting so that each job/project can either use the old style or this style because not every project likes to have the extra required stream.

-- -- -- -- --

Here is a suggestion for a more effective AccuRev polling to decide whether a CI build should be started.

1) One time only: Create a sub-stream of Project named Project_Last_CI and set time-basis to "now"
accurev mkstream -s Project_Last_CI -b Project -t now

2) On each polling cycle, check to see if there are any changes in Project (promotes into Project, its parent, its grandparent, any xlinks, etc.)
accurev diff -a -i -v Project -V Project_Last_CI

3) If the accurev diff command produces any output, it is time to kick off a CI build
a) Update Last_CI stream time-basis
accurev chstream -s Project_Last_CI -t now
b) Perform regular hist information being done today to capture transactions
c) workspace update
d) build

Because the diff command normally takes just 4-5 seconds, even for a large stream, this will create a significant load reduction. It should actually enable the project to run the polling more frequently while simultaneously creating less load on the AccuRev server.

  was:
This should feature should be usable per job setting so that each job/project can either use the old style or this style because not every project likes to have the extra stream.

-- -- -- -- --

Here is a suggestion for a more effective AccuRev polling to decide whether a CI build should be started.

1) One time only: Create a sub-stream of Project named Project_Last_CI and set time-basis to "now"
accurev mkstream -s Project_Last_CI -b Project -t now

2) On each polling cycle, check to see if there are any changes in Project (promotes into Project, its parent, its grandparent, any xlinks, etc.)
accurev diff -a -i -v Project -V Project_Last_CI

3) If the accurev diff command produces any output, it is time to kick off a CI build
a) Update Last_CI stream time-basis
accurev chstream -s Project_Last_CI -t now
b) Perform regular hist information being done today to capture transactions
c) workspace update
d) build

Because the diff command normally takes just 4-5 seconds, even for a large stream, this will create a significant load reduction. It should actually enable the project to run the polling more frequently while simultaneously creating less load on the AccuRev server.


> AccuRev: reduce load and increase speed for SCM polling
> -------------------------------------------------------
>
>                 Key: JENKINS-11241
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11241
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: accurev
>         Environment: Jenkins v1.432, AccuRev Plugin v0.6.18
>            Reporter: robsimon
>            Assignee: Scott Tatum
>
> This feature should be usable per job setting so that each job/project can either use the old style or this style because not every project likes to have the extra required stream.
> -- -- -- -- --
> Here is a suggestion for a more effective AccuRev polling to decide whether a CI build should be started.
> 1) One time only: Create a sub-stream of Project named Project_Last_CI and set time-basis to "now"
> accurev mkstream -s Project_Last_CI -b Project -t now
> 2) On each polling cycle, check to see if there are any changes in Project (promotes into Project, its parent, its grandparent, any xlinks, etc.)
> accurev diff -a -i -v Project -V Project_Last_CI
> 3) If the accurev diff command produces any output, it is time to kick off a CI build
> a) Update Last_CI stream time-basis
> accurev chstream -s Project_Last_CI -t now
> b) Perform regular hist information being done today to capture transactions
> c) workspace update
> d) build
> Because the diff command normally takes just 4-5 seconds, even for a large stream, this will create a significant load reduction. It should actually enable the project to run the polling more frequently while simultaneously creating less load on the AccuRev server.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] [accurev] (JENKINS-11241) AccuRev: reduce load and increase speed for SCM polling

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: Joshua Sherwood (04/Apr/14 9:00 PM)
Assignee: Scott Tatum Joshua Sherwood
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.