Dumb Question Dept - how do I "delete" a public build from the list?
Scenario: I perform a team build as a "smoke" test and decide to mark it's quality as rejected. The team makes changes and the second "smoke" team build is successful. Since the changes are logged into Version Control, I don't need the first build hanging around.
How do I delete it? There doesn't seem to be anything in the beta help or menus that is apparent on how to remove the builds. I can remove the folders from the drop site, but the logs still remain in the system. Short of traversing the database myself, anything else I could do?
Regards,
Michael Shorten
Post Beta 2 we have added feature to delete a build. However as Marcel mentioned, some data will still be kept around for auditing purpose. The behavior of delete feature is -
1) It will delete the binaries etc from drop location
2) The build records will be deleted from operational store (provided it is already uploaded to warehouse). So essentially you will not be able to see that build in the reports.
The delete command will be available only in command line tool and not through the VS UI. Only person with "Administer Build" priviledges will be able to delete a build.
Is this what you were looking for? Will this work for you?
Thanks,
Gautam
Visual Studio Team System -> Team Build.
Apart from the cmd line tool, this feature required work on both the application tier and data tier. Hence, it is not easy to give you something that will work on Beta2 bits.
You can get your hands on these bits when our next customer preview bits are released. Unfortunately I don't have the dates for that yet.
Just to get you excited, the cmd line tool has 3 features -
1) Start a build (similar to UI)
2) Abort a build in progress (not there in UI)
3) Delete a completed build (not there in UI)
Thanks for the interest and feedback. Keep using VS and Team Build and send us your feedback.
Thanks,
Gautam
Visual Studio Team System | Team Build.
Gautam,
My Dad always said "Never hurts to ask." Thanks anyway for the reply.
Although that was almost cruel to tease us with those tidbits. ;)
I've got a ton of thoughts about the cmd line and the build process - I'm doing a real quick pass through its features but beyond the cmd line/schedule/delete stuff that you're already covering - be able to email or have the results of the build in an xml format for autoparsing/posting - or having an overview of the schema in the db so that we can do automated reporting on builds would be nice. To be honest, while the workitems and process stuff is fantastic, I see the integrated build and testing features being the lowest hanging fruit to pick for selling technical teams on VSTS.
Regards,
Michael Shorten
Olenick & Assoc.
Hi Michael,
Sorry I missed replying to this thread.
You can subscribe to get email notification on two events - on change in build status and on build complete. Change in build status will send mail on any change in build status while building and even post building. Build complete will be one time notification on build complete (pass or failed).
This email notification for build complete will have high level summary with a link to web page (aspx page). The web page will contain all the details - much the same as reports inside VS. If you want you can mail this URL to anyone having read access to application tier and it can be viewed over firewall also.
The above feature is there for other TF components also. Like you can subscribe to checkin notification or work item change notification also.
If needed, you can customize these notification also by writing your own code.
Thanks,
Gautam