Vault Update

Posted by Jeff Clausius Sat, 27 Aug 2011 21:59:00 GMT

As I sit down to this entry, Hurricane Irene is 90 miles from Cape Hatteras. For those of you on the East Coast, heed all evacuation orders, and please take all precautions to remain safe.

It’s been busy for us on the Vault Dev team since my last post, and I wanted to update you on our work. We’ve made excellent progress on the cornerstone features for Vault 6. The foundational framework has been coded for both Find in Files as well as Vault Notifications, and we are now working on the UI.

For those unaware, Find in Files allows searching for a string of text within text based files stored within the repository. As a file’s data will be indexed in its own database, searches will be more efficient than keeping or GETting files to disk and running recursive greps against those files. In regards to Vault Notifications, this feature will provide a central location for you to see various source code and work item events generated by your team’s activity. Need to know when when a file has its lock released? No problem. Set a notification. Need to know when a change set is committed or a change made to a bug in a project, set a notification. Like before, the Notification service can also be configured to send email for these events.

Oh, there is also one other HUGE announcement. (OK, at least I think it’s huge.) However, I don’t want to ruin the surprise. We’ll be updating the Vault 6 road map with this info very, very soon. Please stay tuned!

Let’s switch gears a bit and talk Vault 5. We haven’t been idle here these past few months, and are tentatively planning a Vault 5.1.2 release sometime this September. Coding is just about complete, and early builds are already in the hands of our QA department as well as a few select customers. In this maintenance release we’ve addressed some nuisances as well as tried to streamline a few areas. Some highlights of this release include:

  • A new option named “Use check box as selection.” This option allows users to control the check box selection for items in the Pending Change Set list as well as items in the Search Results. When the option is unchecked, check boxes are not used, and operations are based on the selected items. When the option is checked, check boxes are visible, but the behavior of the check box is used to select the item. This behavior is similar to the Windows Explorer option of the same name found in Windows Vista/7. Also, this change allowed the “Commit” command to be placed back in the context menu for the Pending Change Set.
  • Changes in the OnTime Integration Component to account for Axosoft’s change in authentication for OnTime 2011. Axosoft made a slight change with OnTime 2011 that broke compatibility with Vault’s Integration Component. Vault 5.1.2 addresses this problem as well as allow access for OnTime user’s configured with Windows Authentication to access Defects from within the Vault GUI client.
  • A new option in the Vault Import tool which allows user’s to skip importing labels and/or keep the import running after a label error. The VSS Import tool needed to take certain liberties with the restrictions on labels when creating VSS data within the Vault repository. Unfortunately, these labels would not allow VSS imported repositories to be exported/imported correctly to other Vault repositories. This option within the Vault Import tool allows the export/import of VSS created repositories to other Vault repositories.

That about wraps up this entry, and you’re now up to date. We appreciate everyone’s enthusiasm around Vault, and as always, if you have any questions, please don’t hesitate to ask.

-Jeff Clausius Vault Dev Team

Posted in  | 2 comments