Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix autoprune not exectuing for second resource #38 #364

Merged

Conversation

pradeepitm12
Copy link
Contributor

earlier resources["pipelinerun", "taskrun"] executes fine
but somehow resources ["taskrun", "pipelinrun"] do not execute
for the second resource.

problem: command created and passed was an array where each
item was treated as an arugement.

Now the commands are single string and seperated by ';'

Signed-off-by: Pradeep Kumar pradkuma@redhat.com

Changes

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Release Notes

earlier resources["pipelinerun", "taskrun"] executes fine
but somehow resources ["taskrun", "pipelinrun"] do not execute
for the second resource.

problem: command created and passed was an array where each
item was treated as an arugement.

Now the commands are single string and seperated by ';'

Signed-off-by: Pradeep Kumar <pradkuma@redhat.com>
@tekton-robot tekton-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Jul 14, 2021
@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jul 14, 2021
@pradeepitm12
Copy link
Contributor Author

cc: @nikhil-thomas @sm43

@@ -151,11 +151,11 @@ func getPruningContainers(resources, namespaces []string, keep uint, tknImage st
return containers
}

func deleteCommand(resources []string, keep uint, ns string) []string {
cmdArgs := []string{}
func deleteCommand(resources []string, keep uint, ns string) string {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is a diff uint and int with respect to the downstream.

@sm43
Copy link
Member

sm43 commented Jul 15, 2021

/lgtm
just one ques would tkn <res> delete cmd delete a running pr/tr?
if yes, then if user has kept for ex. keep 1 and right when the puner job is started there is a pipeline running
so would the job delete pr for it?

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 15, 2021
@pradeepitm12
Copy link
Contributor Author

pradeepitm12 commented Jul 15, 2021

/lgtm
just one ques would tkn <res> delete cmd delete a running pr/tr?
if yes, then if user has kept for ex. keep 1 and right when the puner job is started there is a pipeline running
so would the job delete pr for it?

Yes, it will delete a running pr/tr.
As keep=1 pruner would keep 1 pipelinerun which is latest and delete others, in this latest should be the one running.

@nikhil-thomas
Copy link
Member

@pradeepitm12 could you add an issue to track this case

/lgtm
just one ques would tkn <res> delete cmd delete a running pr/tr?
if yes, then if user has kept for ex. keep 1 and right when the puner job is started there is a pipeline running
so would the job delete pr for it?

Yes, it will delete a running pr/tr.
As keep=1 pruner would keep 1 pipelinerun which is latest and delete others, in this latest should be the one running.

/approve
/lgtm

@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nikhil-thomas

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 21, 2021
@tekton-robot tekton-robot merged commit 75bc3c0 into tektoncd:main Jul 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants