How to clear off all resource checks in concourse
up vote
0
down vote
favorite
I had a resource that kept triggering every few minutes and it created a queue of hundreds of pending jobs. I want to clear off all the old resource versions so that it stops trying to start new jobs. How can I do that without deleting and recreating the pipeline or impacting any other active pipelines?
concourse
add a comment |
up vote
0
down vote
favorite
I had a resource that kept triggering every few minutes and it created a queue of hundreds of pending jobs. I want to clear off all the old resource versions so that it stops trying to start new jobs. How can I do that without deleting and recreating the pipeline or impacting any other active pipelines?
concourse
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I had a resource that kept triggering every few minutes and it created a queue of hundreds of pending jobs. I want to clear off all the old resource versions so that it stops trying to start new jobs. How can I do that without deleting and recreating the pipeline or impacting any other active pipelines?
concourse
I had a resource that kept triggering every few minutes and it created a queue of hundreds of pending jobs. I want to clear off all the old resource versions so that it stops trying to start new jobs. How can I do that without deleting and recreating the pipeline or impacting any other active pipelines?
concourse
concourse
asked Nov 7 at 18:28
Alex Cohen
1,13211740
1,13211740
add a comment |
add a comment |
                                1 Answer
                                1
                        
active
oldest
votes
up vote
1
down vote
accepted
If I understand correctly you have something like:
> fly -t vm builds
id  pipeline/job       build  status    
25  queue-up/queue-up  25     started   
24  queue-up/queue-up  24     started   
23  queue-up/queue-up  23     started   
22  queue-up/queue-up  22     started   
21  queue-up/queue-up  21     started   
20  queue-up/queue-up  20     started   
19  queue-up/queue-up  19     started   
18  queue-up/queue-up  18     started   
17  queue-up/queue-up  17     succeeded 
where maybe some of the builds are pending instead than started.
There is no way to clear off the old resource versions without deleting the pipeline. On the other hand, you can always abort all or some of the builds:
> for i in (seq 24 18); fly -t vm abort-build --build $i; end
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
> fly -t vm builds
id  pipeline/job       build  status   
25  queue-up/queue-up  25     started  
24  queue-up/queue-up  24     aborted  
23  queue-up/queue-up  23     aborted  
22  queue-up/queue-up  22     aborted  
21  queue-up/queue-up  21     aborted  
20  queue-up/queue-up  20     aborted  
19  queue-up/queue-up  19     aborted  
18  queue-up/queue-up  18     aborted  
17  queue-up/queue-up  17     succeeded
add a comment |
                                1 Answer
                                1
                        
active
oldest
votes
                                1 Answer
                                1
                        
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
If I understand correctly you have something like:
> fly -t vm builds
id  pipeline/job       build  status    
25  queue-up/queue-up  25     started   
24  queue-up/queue-up  24     started   
23  queue-up/queue-up  23     started   
22  queue-up/queue-up  22     started   
21  queue-up/queue-up  21     started   
20  queue-up/queue-up  20     started   
19  queue-up/queue-up  19     started   
18  queue-up/queue-up  18     started   
17  queue-up/queue-up  17     succeeded 
where maybe some of the builds are pending instead than started.
There is no way to clear off the old resource versions without deleting the pipeline. On the other hand, you can always abort all or some of the builds:
> for i in (seq 24 18); fly -t vm abort-build --build $i; end
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
> fly -t vm builds
id  pipeline/job       build  status   
25  queue-up/queue-up  25     started  
24  queue-up/queue-up  24     aborted  
23  queue-up/queue-up  23     aborted  
22  queue-up/queue-up  22     aborted  
21  queue-up/queue-up  21     aborted  
20  queue-up/queue-up  20     aborted  
19  queue-up/queue-up  19     aborted  
18  queue-up/queue-up  18     aborted  
17  queue-up/queue-up  17     succeeded
add a comment |
up vote
1
down vote
accepted
If I understand correctly you have something like:
> fly -t vm builds
id  pipeline/job       build  status    
25  queue-up/queue-up  25     started   
24  queue-up/queue-up  24     started   
23  queue-up/queue-up  23     started   
22  queue-up/queue-up  22     started   
21  queue-up/queue-up  21     started   
20  queue-up/queue-up  20     started   
19  queue-up/queue-up  19     started   
18  queue-up/queue-up  18     started   
17  queue-up/queue-up  17     succeeded 
where maybe some of the builds are pending instead than started.
There is no way to clear off the old resource versions without deleting the pipeline. On the other hand, you can always abort all or some of the builds:
> for i in (seq 24 18); fly -t vm abort-build --build $i; end
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
> fly -t vm builds
id  pipeline/job       build  status   
25  queue-up/queue-up  25     started  
24  queue-up/queue-up  24     aborted  
23  queue-up/queue-up  23     aborted  
22  queue-up/queue-up  22     aborted  
21  queue-up/queue-up  21     aborted  
20  queue-up/queue-up  20     aborted  
19  queue-up/queue-up  19     aborted  
18  queue-up/queue-up  18     aborted  
17  queue-up/queue-up  17     succeeded
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
If I understand correctly you have something like:
> fly -t vm builds
id  pipeline/job       build  status    
25  queue-up/queue-up  25     started   
24  queue-up/queue-up  24     started   
23  queue-up/queue-up  23     started   
22  queue-up/queue-up  22     started   
21  queue-up/queue-up  21     started   
20  queue-up/queue-up  20     started   
19  queue-up/queue-up  19     started   
18  queue-up/queue-up  18     started   
17  queue-up/queue-up  17     succeeded 
where maybe some of the builds are pending instead than started.
There is no way to clear off the old resource versions without deleting the pipeline. On the other hand, you can always abort all or some of the builds:
> for i in (seq 24 18); fly -t vm abort-build --build $i; end
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
> fly -t vm builds
id  pipeline/job       build  status   
25  queue-up/queue-up  25     started  
24  queue-up/queue-up  24     aborted  
23  queue-up/queue-up  23     aborted  
22  queue-up/queue-up  22     aborted  
21  queue-up/queue-up  21     aborted  
20  queue-up/queue-up  20     aborted  
19  queue-up/queue-up  19     aborted  
18  queue-up/queue-up  18     aborted  
17  queue-up/queue-up  17     succeeded
If I understand correctly you have something like:
> fly -t vm builds
id  pipeline/job       build  status    
25  queue-up/queue-up  25     started   
24  queue-up/queue-up  24     started   
23  queue-up/queue-up  23     started   
22  queue-up/queue-up  22     started   
21  queue-up/queue-up  21     started   
20  queue-up/queue-up  20     started   
19  queue-up/queue-up  19     started   
18  queue-up/queue-up  18     started   
17  queue-up/queue-up  17     succeeded 
where maybe some of the builds are pending instead than started.
There is no way to clear off the old resource versions without deleting the pipeline. On the other hand, you can always abort all or some of the builds:
> for i in (seq 24 18); fly -t vm abort-build --build $i; end
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
build successfully aborted
> fly -t vm builds
id  pipeline/job       build  status   
25  queue-up/queue-up  25     started  
24  queue-up/queue-up  24     aborted  
23  queue-up/queue-up  23     aborted  
22  queue-up/queue-up  22     aborted  
21  queue-up/queue-up  21     aborted  
20  queue-up/queue-up  20     aborted  
19  queue-up/queue-up  19     aborted  
18  queue-up/queue-up  18     aborted  
17  queue-up/queue-up  17     succeeded
answered Nov 8 at 20:45
marco.m
2,9541634
2,9541634
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53195609%2fhow-to-clear-off-all-resource-checks-in-concourse%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown