-
Notifications
You must be signed in to change notification settings - Fork 4
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
Support galasactl runs delete --name U52
#1210
Comments
We are looking at enhancing the command-line tool so that tasks such as this could be automated more easily... See https://ibm.box.com/s/fsc4bwxsb9pb8jdcymk30ay7vsf7l8fq The scope of this request is covered if we implement these plans. |
galasactl runs delete --name U52
@jt-nti Thinking we need a new chapter or something for admins, to cover administering the Galasa service ? Also we have a script which might be useful here: galasa-dev/cli#278 |
See galasa-dev/projectmanagement#1210 Signed-off-by: James Taylor <[email protected]>
See galasa-dev/projectmanagement#1210 Signed-off-by: James Taylor <[email protected]>
# Original Text from @jasonrhughes
Over time, local test runs build up and the local RAS directory content grows accordingly.
We could manually trim the directory contents (if this doesn't upset Galasa) but a more elegant solution might be to right click results (or group of results) in the Galasa Results view and delete them from there - which would also clear them from the RAS.
(I would personally not want this to be automatically time-based - i.e., delete test runs older than a certain age - but rather to be able to prune manually.)
I notice it's possible to do this from the Galasa Runs view but the very few runs contained there don't correspond to those in the Galasa Results view.
Story
As a user of galasa, I want to be able to delete test runs which have completed in the past, so that they don't take up space in my Galasa system.
Background
galasactl runs get --age 6w:1w
--format raw
makes it easy to get the names of the runs out using a script.galasactl runs delete --name xxx
command to allow individual runs to be removed.The Rest API changes
DELETE /ras/runs/{id}
Does not take a body. Ignores it.
Status codes:
200 OK (same if the property was deleted, or it doesn't exist).
401 Unauthorised. Invalid JWT token, or you don't have permissions.
400 Bad request : The run is currently active. Cancel if first.
Assumptions: We have done the story which always makes sure that Finished state is reached when a test run is cancelled. Story #1775
Once complete, we can try as script like this:
Tasks
add a delete method into the RAS extensions APIdiscard
already exists on theIRunResult
interfaceand the default implementation (can be a no-op)and the couchdb implementationThe text was updated successfully, but these errors were encountered: