Build Notification Applet
Upcoming SlideShare
Loading in...5
×
 

Build Notification Applet

on

  • 4,251 views

This is an annotated storyboard for the build notification applet we are planning to release as a power tool for Team Foundation Server Orcas.

This is an annotated storyboard for the build notification applet we are planning to release as a power tool for Team Foundation Server Orcas.

Statistics

Views

Total Views
4,251
Views on SlideShare
3,872
Embed Views
379

Actions

Likes
0
Downloads
127
Comments
0

6 Embeds 379

http://blogs.msdn.com 368
http://luca-foto.blogspot.com 5
http://luca-foto.blogspot.it 3
https://s3.amazonaws.com 1
http://www.slideshare.net 1
http://luca-foto.blogspot.ca 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Build Notification Applet Build Notification Applet Presentation Transcript

  • Continuous Integration — Build Notification Applet Team Build Program Manager User Education Jim Lamb Sirkku Willie Development Lead User Experience Buck Hodges Kristoffer Schultz Test Lead International Jason Barile Aldo Donetti June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 1/15
  • Continuous Integration — Build Notification Applet Microsoft Corporation Technical Documentation License Agreement (Standard) READ THIS! THIS IS A LEGAL AGREEMENT BETWEEN MICROSOFT CORPORATION (quot;MICROSOFTquot;) 3. These Materials may contain preliminary information or inaccuracies, and may not correctly AND THE RECIPIENT OF THESE MATERIALS, WHETHER AN INDIVIDUAL OR AN ENTITY (quot;YOUquot;). IF represent any associated Microsoft Product as commercially released. All Materials are provided YOU HAVE ACCESSED THIS AGREEMENT IN THE PROCESS OF DOWNLOADING MATERIALS entirely quot;AS IS.quot; To the extent permitted by law, MICROSOFT MAKES NO WARRANTY OF ANY KIND, (quot;MATERIALSquot;) FROM A MICROSOFT WEB SITE, BY CLICKING quot;I ACCEPTquot;, DOWNLOADING, USING OR DISCLAIMS ALL EXPRESS, IMPLIED AND STATUTORY WARRANTIES, AND ASSUMES NO LIABILITY TO PROVIDING FEEDBACK ON THE MATERIALS, YOU AGREE TO THESE TERMS. IF THIS AGREEMENT IS YOU FOR ANY DAMAGES OF ANY TYPE IN CONNECTION WITH THESE MATERIALS OR ANY ATTACHED TO MATERIALS, BY ACCESSING, USING OR PROVIDING FEEDBACK ON THE ATTACHED INTELLECTUAL PROPERTY IN THEM. MATERIALS, YOU AGREE TO THESE TERMS. 4. If You are an entity and (a) merge into another entity or (b) a controlling ownership interest in You 1. For good and valuable consideration, the receipt and sufficiency of which are acknowledged, You changes, Your right to use these Materials automatically terminates and You must destroy them. and Microsoft agree as follows: 5. You have no obligation to give Microsoft any suggestions, comments or other feedback (a) If You are an authorized representative of the corporation or other entity designated below (quot;Feedbackquot;) relating to these Materials. However, any Feedback you voluntarily provide may be used (quot;Companyquot;), and such Company has executed a Microsoft Corporation Non-Disclosure Agreement in Microsoft Products and related specifications or other documentation (collectively, quot;Microsoft that is not limited to a specific subject matter or event (quot;Microsoft NDAquot;), You represent that You Offeringsquot;) which in turn may be relied upon by other third parties to develop their own Products. have authority to act on behalf of Company and agree that the Confidential Information, as defined in Accordingly, if You do give Microsoft Feedback on any version of these Materials or the Microsoft the Microsoft NDA, is subject to the terms and conditions of the Microsoft NDA and that Company Offerings to which they apply, You agree: (a) Microsoft may freely use, reproduce, license, distribute, will treat the Confidential Information accordingly; and otherwise commercialize Your Feedback in any Microsoft Offering; (b) You also grant third parties, without charge, only those patent rights necessary to enable other Products to use or (b) If You are an individual, and have executed a Microsoft NDA, You agree that the Confidential interface with any specific parts of a Microsoft Product that incorporate Your Feedback; and (c) You Information, as defined in the Microsoft NDA, is subject to the terms and conditions of the Microsoft will not give Microsoft any Feedback (i) that You have reason to believe is subject to any patent, NDA and that You will treat the Confidential Information accordingly; or copyright or other intellectual property claim or right of any third party; or (ii) subject to license terms (c) If a Microsoft NDA has not been executed, You (if You are an individual), or Company (if You which seek to require any Microsoft Offering incorporating or derived from such Feedback, or other are an authorized representative of Company), as applicable, agrees: (a) to refrain from disclosing or Microsoft intellectual property, to be licensed to or otherwise shared with any third party. distributing the Confidential Information to any third party for five (5) years from the date of 6. Microsoft has no obligation to maintain confidentiality of any Microsoft Offering, but otherwise the disclosure of the Confidential Information by Microsoft to Company/You; (b) to refrain from confidentiality of Your Feedback, including Your identity as the source of such Feedback, is governed reproducing or summarizing the Confidential Information; and (c) to take reasonable security by Your NDA. precautions, at least as great as the precautions it takes to protect its own confidential information, but no less than reasonable care, to keep confidential the Confidential Information. You/Company, 7. This agreement is governed by the laws of the State of Washington. Any dispute involving it must however, may disclose Confidential Information in accordance with a judicial or other governmental be brought in the federal or state superior courts located in King County, Washington, and You waive order, provided You/Company either (i) gives Microsoft reasonable notice prior to such disclosure and any defenses allowing the dispute to be litigated elsewhere. If there is litigation, the losing party must to allow Microsoft a reasonable opportunity to seek a protective order or equivalent, or (ii) obtains pay the other party’s reasonable attorneys’ fees, costs and other expenses. If any part of this written assurance from the applicable judicial or governmental entity that it will afford the agreement is unenforceable, it will be considered modified to the extent necessary to make it Confidential Information the highest level of protection afforded under applicable law or regulation. enforceable, and the remainder shall continue in effect. This agreement is the entire agreement Confidential Information shall not include any information, however designated, that: (i) is or between You and Microsoft concerning these Materials; it may be changed only by a written subsequently becomes publicly available without Your/Company’s breach of any obligation owed to document signed by both You and Microsoft. Microsoft; (ii) became known to You/Company prior to Microsoft’s disclosure of such information to You/Company pursuant to the terms of this Agreement; (iii) became known to You/Company from a source other than Microsoft other than by the breach of an obligation of confidentiality owed to Microsoft; or (iv) is independently developed by You/Company. For purposes of this paragraph, quot;Confidential Informationquot; means nonpublic information that Microsoft designates as being confidential or which, under the circumstances surrounding disclosure ought to be treated as confidential by Recipient. quot;Confidential Informationquot; includes, without limitation, information in tangible or intangible form relating to and/or including released or unreleased Microsoft software or hardware products, the marketing or promotion of any Microsoft product, Microsoft's business policies or practices, and information received from others that Microsoft is obligated to treat as confidential. 2. You may review these Materials only (a) as a reference to assist You in planning and designing Your product, service or technology (quot;Productquot;) to interface with a Microsoft Product as described in these Materials; and (b) to provide feedback on these Materials to Microsoft. All other rights are retained by Microsoft; this agreement does not give You rights under any Microsoft patents. You may not (i) duplicate any part of these Materials, (ii) remove this agreement or any notices from these Materials, or (iii) give any part of these Materials, or assign or otherwise provide Your rights under this agreement, to anyone else. June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 2/15
  • Continuous Integration — Build Notification Applet Build Notification ? View Build Status Check Now Volunteer to Fix Odyssey Continuous Queue New Build... Tahoe Continuous Show Notifications Options Exit Team Build Notifications To configure notifications for your team builds, click this balloon. Inbox – Microsoft Out... Build Explorer – Orcas... 11:33 AM June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 3/15
  • Continuous Integration — Build Notification Applet Configuring Build Notifications Build Notification Options Search Select the build definitions to monitor: TKBGITVSTFAT01 Whidbey Odyssey Continuous Odyssey Nightly Orcas Tahoe Continuous Tahoe Nightly Rosario Cayenne Continuous Cayenne Nightly Show notifications for the following events: Build Queued Build Started Build Finished Show notifications for builds triggered or queued by: Anyone Me only OK Cancel Clear All Select All June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 4/15
  • Continuous Integration — Build Notification Applet Anatomy of a Build Notification Window Tahoe Continuous_20070405.1 Build succeeded Triggered by BuckH 1/3 View Work Items | Open Drop Folder June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 5/15
  • Continuous Integration — Build Notification Applet Notifications View Build Details Open Drop Folder Open Log View Changesets View Work Items Set Priority Stop Postpone Retain Indefinitely Delete Build… Show Build Notifications Options… Tahoe Continuous_20070405.1 Build succeeded Triggered by BuckH 1/3 View Work Items | Open Drop Folder June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 6/15
  • Continuous Integration — Build Notification Applet Notifications Build Queued Tahoe Continuous_20070405.1 Build queued Triggered by BuckH, position 2/3 1/1 Postpone Build | Cancel Build Build Started Tahoe Continuous_20070405.1 Build started on TFDGBBLDSVR2 Triggered by BuckH 1/1 Stop Build June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 7/15
  • Continuous Integration — Build Notification Applet Build Succeeded Tahoe Nightly_20070405 Build succeeded Requested by BuckH 1/1 View Work Items | Open Drop Folder Build Failed Tahoe Continuous_20070405.1 Build broken Broken by JimLamb 1/1 View Changesets | Volunteer to Fix Tahoe Continuous_20070405.2 Build broken Broken for 35 minutes 1/1 View Changesets | Volunteer to Fix Tahoe Nightly_20070404 Build broken Broken for 1 day 1/1 View Changesets | Volunteer to Fix June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 8/15
  • Continuous Integration — Build Notification Applet Volunteer to Fix When someone volunteers... Tahoe Continuous_20070405.1 BuckH volunteered to fix Broken for 15 minutes 1/1 View Changesets When someone fixes the build... Tahoe Continuous_20070405.2 Build fixed by BuckH 18 minutes to fix 1/1 View Work Items | Open Drop Folder June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 9/15
  • Continuous Integration — Build Notification Applet Build Notification Flow June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 10/15
  • Continuous Integration — Build Notification Applet Build Status Window Current Build Status Context Menu Command State Team Foundation Build Current Build Status Options View Build Details Open Drop Folder Broken (1) Open Log Tahoe Nightly_20070405 View Changesets 11 hours ago View Work Items Building (2) Queue New Build… Cayenne Continuous_20070405.3 Getting sources Set Priority Tahoe Continuous__20070405.5 Stop/Cancel Generating list of changesets and work items Postpone Succeeded (2) Retain Indefinitely Cayenne Nightly_20070405 30 minutes ago Delete Build… Odyssey Continuous_20070405.2 3 hours ago June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 11/15
  • Continuous Integration — Build Notification Applet Build Status Window Completed Builds Team Foundation Build Completed Builds Failed (1) Tahoe Nightly_20070405 Build failure message Succeeded (2) Cayenne Continuous_20070405.3 30 minutes ago Cayenne Nightly_20070405 3 hours ago Odyssey Continuous_20070405.2 15 minutes ago Tahoe Continuous_20070405.5 1 hour ago June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 12/15
  • Continuous Integration — Build Notification Applet Build Status Window Last Known Good Builds Team Foundation Build Last Known Good Builds Available (4) Cayenne Continuous_20070405.3 30 minutes ago Cayenne Nightly_20070405 Yesterday Odyssey Continuous_20070405.2 48 minutes ago Odyssey Nightly_20070405 2 days ago Unavailable (1) Tahoe Nightly_20070405 Failed 11 hours ago June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 13/15
  • Continuous Integration — Build Notification Applet View Changesets Changesets – Tahoe Continuous_20070405.2 Changeset User Comment 194214 jimlamb Checking in new MSBuild project and response files. June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 14/15
  • Continuous Integration — Build Notification Applet Exiting Exiting Team Build Notifications Do you want to permanently close Team Build Notifications? You can close the Team Build Notifier temporarily (until the next time you log on) or permanently (until the next time you choose to run it) Close for now (recommended) Remove Team Build Notifier from the system notification area until the next time you log on. Close permanently Remove Team Build Notifier from the system notification area and do not start it automatically the next time you log on. Cancel June 21, 2007 Microsoft Visual Studio – Team Foundation Server | Team Build 15/15