User Documentation for Crucible 4.5 User Documentation for Crucible 4.5 2

Total Page:16

File Type:pdf, Size:1020Kb

User Documentation for Crucible 4.5 User Documentation for Crucible 4.5 2 User documentation for Crucible 4.5 User documentation for Crucible 4.5 2 Contents Crucible Documentation Home . 5 Getting Started . 5 Supported platforms . 5 Installing Crucible on Windows . 11 Installing Crucible on Linux and Mac . 13 Configuring JIRA Integration in the Setup Wizard . 17 Starting to use Crucible . 25 Installing and upgrading Git . 31 Using Crucible . 33 Using the Crucible screens . 34 Browsing all reviews . 36 Browsing source files . 38 Browsing projects . 40 Changing your User Profile . 41 Using favorites . 41 Using Wiki Markup in Crucible . 43 Using RSS feeds in Crucible . 48 Using keyboard shortcuts in Crucible . 48 Crucible icons . 49 The Crucible workflow . 54 Defining your workflow . 58 Roles and status classifications . 59 Creating a review . 60 Creating a review from JIRA . 63 Creating a review from a URL . 64 Creating a Snippet Review . 65 Creating reviews from the command line . 66 Adding content to the review . 68 Iterative reviews . 75 Creating patch files for pre-commit reviews . 78 Choosing reviewers . 84 Performing the review . 86 Starting a review . 87 Commenting on reviews . 88 Sending a review's comments via email . 92 Changeset discussions . 93 Flagging defects . 94 Viewing reports . 94 Review Coverage report . 96 Completing your review . 100 Using the Review History dialog . 102 Summarizing and closing the review . 103 Managing your reviews . 105 Using Review Reminders . 105 Moving a review to another project . 106 Using Progress Tracking . 107 Using Time Tracking . 109 Viewing people's statistics in Crucible . 110 Viewing Project Statistics . 114 Deleting a review . 116 Searching Crucible . 117 JIRA integration in Crucible . 122 Creating JIRA issues from the review . 126 Transitioning JIRA issues . 127 Administering Crucible . 128 Best practices for Crucible configuration . 129 Created by Atlassian in 2017. Licensed under a Creative Commons Attribution 2.5 Australia License. User documentation for Crucible 4.5 3 Crucible and FishEye . 129 Administering projects . 130 Creating a project . 131 Storing all revisions under review . 133 Enabling the moderator role . 134 Setting default review objectives . 134 Editing a project . 135 Configuring repositories . 138 Setting up a Git repository in Crucible . 138 Setting up a Perforce repository in Crucible alone . 141 Setting up a Subversion repository in Crucible alone . 142 Enabling reviews from the server file system in Crucible . 143 Setting up a repository via FishEye . 144 Configuring commit hooks . 144 Setting up users and security . ..
Recommended publications
  • Efficient Algorithms for Comparing, Storing, and Sharing
    EFFICIENT ALGORITHMS FOR COMPARING, STORING, AND SHARING LARGE COLLECTIONS OF EVOLUTIONARY TREES A Dissertation by SUZANNE JUDE MATTHEWS Submitted to the Office of Graduate Studies of Texas A&M University in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY May 2012 Major Subject: Computer Science EFFICIENT ALGORITHMS FOR COMPARING, STORING, AND SHARING LARGE COLLECTIONS OF EVOLUTIONARY TREES A Dissertation by SUZANNE JUDE MATTHEWS Submitted to the Office of Graduate Studies of Texas A&M University in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY Approved by: Chair of Committee, Tiffani L. Williams Committee Members, Nancy M. Amato Jennifer L. Welch James B. Woolley Head of Department, Hank W. Walker May 2012 Major Subject: Computer Science iii ABSTRACT Efficient Algorithms for Comparing, Storing, and Sharing Large Collections of Evolutionary Trees. (May 2012) Suzanne Jude Matthews, B.S.; M.S., Rensselaer Polytechnic Institute Chair of Advisory Committee: Dr. Tiffani L. Williams Evolutionary relationships between a group of organisms are commonly summarized in a phylogenetic (or evolutionary) tree. The goal of phylogenetic inference is to infer the best tree structure that represents the relationships between a group of organisms, given a set of observations (e.g. molecular sequences). However, popular heuristics for inferring phylogenies output tens to hundreds of thousands of equally weighted candidate trees. Biologists summarize these trees into a single structure called the consensus tree. The central assumption is that the information discarded has less value than the information retained. But, what if this assumption is not true? In this dissertation, we demonstrate the value of retaining and studying tree collections.
    [Show full text]
  • PETER STEPHENS Current Technical Pursuits: Agile Practices, Cloud
    PETER STEPHENS 512.778.6322 / cell 865.567.7173 1955 County Road 202 www.diligentsoftware.com/resume Liberty Hill, TX 78642 [email protected] Current Technical Pursuits: Agile Practices, Cloud Computing and Amazon Web Services, Cloud Automation, ASP.NET MVC, REST based web services, JavaScript and jQuery CURRENT SKILLS • Microsoft.NET Framework versions 1.0 – 4.5 » C#, LINQ, XML , Networking, Regular Expressions, Multithreading , Task Parallel Library, Encryption, etc. » Websites: ASP.NET WebForms and MVC » Thick Client: Windows Presentation Foundation (WPF) » Web Services: WCF, Web API (REST and RPC) , and OData • Cloud Computing » Amazon Web Services : EC2 , S3 , RDS , SQS, SNS, Cloud Formation, Route 53, etc. » Rackspace Cloud • Automation : Powershell, MSBuild, and T4 templating • Agile Practices : Continuous Integration with Team City and CruiseControl.NET, Test Driven Development (TDD ), NUnit, Rhino Mocks, MOQ, Autofac, and ReSharper • Microsoft SQL Server versions 7 – 2008. Extensive use of T-SQL , C# stored procedures, C# functions, management and database optimization • HTML , CSS , JavaScript , jQuery , HTTP, Web Design, SEO , and Microsoft Expression Studio, Report Viewer Control based RDLC reports • Domain Specific Languages: Irony • Deployment: WIX , InstallShield, and WebDeploy • Source Control : Git and Mercurial, Beyond Compare, KDIFF OPEN SOURCE AND SOCIAL • Stack Overflow: http://stackoverflow.com/users/72860/peter-stephens • Twitter: https://twitter.com/#!/peterastephens • Bitbucket: https://bitbucket.org/pstephens/
    [Show full text]
  • Bluej Teamwork Repository Configuration
    BlueJ Teamwork Repository Configuration Version 2.0 for BlueJ Version 2.5.0 (and 2.2.x) Davin McCall School of Engineering & IT, Deakin University 1 Introduction This document gives a brief description of how you might set up a version control repository for use with BlueJ’s teamwork features. It is intended mainly as a “quick start” guide and not as a complete reference – for that you should refer to the version control software documentation (i.e. the CVS manual or the Subversion manual) – but it does explain some BlueJ-specific concepts (such as how BlueJ supports the notion of student groups or teams). Setting up a repository usually requires a server to which you have “root” or administrator access. This may mean that you need to ask a Systems Administrator to set up the repository for you. Since BlueJ version 2.5.0, both Subversion and CVS are supported version control systems. BlueJ version 2.2.x supports only CVS. BlueJ versions prior to 2.2.0 did not support teamwork features. Chapters 2 and 3 explain how to set up and test a repository using CVS. Chapter 4 then covers the equivalent steps for using Subversion. 2 Setting up a simple single user CVS repository for testing the BlueJ teamwork features 2.1 Setting up the repository server On Unix / Linux / MacOS X: You must have the CVS software installed on the machine you intend to use as a server. There is a good chance that it is already installed, but if not, your vendor or distribution provider will almost certainly provide packages that can be installed.
    [Show full text]
  • User Documentation for Crucible 3.4 User Documentation for Crucible 3.4 2
    User documentation for Crucible 3.4 User documentation for Crucible 3.4 2 Contents Getting Started . 5 Supported platforms . 5 End of Support Announcements for Crucible . 7 End of Support Announcement for IBM ClearCase . 10 Installing Crucible on Windows . 11 Running Crucible as a Windows service . 13 Installing Crucible on Linux and Mac . 17 Configuring JIRA Integration in the Setup Wizard . 20 Starting to use Crucible . 27 Using Crucible . 35 Using the Crucible screens . 36 Using the Review Dashboard . 38 Browsing all reviews . 40 Browsing source files . 41 Crucible Icons . 42 Searching Crucible . 43 Viewing people's statistics in Crucible . 48 Browsing projects . 52 Viewing Project Statistics . 53 Changing your User Profile . 55 Using favourites . 55 Using Keyboard Shortcuts in Crucible . 57 The Crucible workflow . 58 Defining your workflow . 63 Roles and Status Classifications . 65 Creating a review . 66 Creating a review from FishEye . 70 Creating a review from JIRA . 71 Creating a review from a URL . 72 Creating a Snippet Review . 72 Creating reviews from the command line . 73 Adding content to the review . 75 Iterative reviews . 80 Creating patch files for pre-commit reviews . 83 Choosing reviewers . 90 Performing the review . 92 Starting a review . 93 Adding comments . 94 Changeset discussions . 96 Flagging defects . 97 Creating JIRA issues from the review . 98 Viewing reports . 99 Review Coverage report . 101 Completing your review . 105 Using the Review History Dialog . 107 Using RSS feeds in Crucible . 108 Using Wiki Markup in Crucible . 108 Tracking Crucible Review Metrics . 113 Using Progress Tracking . 113 Using Time Tracking . 115 JIRA integration in Crucible .
    [Show full text]
  • Homework 0: Account Setup for Course and Cloud FPGA Intro Questions
    Cloud FPGA Homework 0 Fall 2019 Homework 0 Jakub Szefer 2019/10/20 Please follow the three setup sections to create BitBucket git repository, install LATEX tools or setup Overleaf account, and get access to the course's git repository. Once you have these done, answer the questions that follow. Submit your solutions as a single PDF file generated from a template; more information is at end in the Submission Instructions section. Setup BitBucket git Repository This course will use git repositories for code development. Each student should setup a free BitBucket (https://bitbucket.org) account and create a git repository for the course. Please make the repository private and give WRITE access to your instructor ([email protected]). Please send the URL address of the repository to the instructor by e-mail. Make sure there is a README:md file in the repository (access to the repository will be tested by a script that tries to download the README:md from the repository address you share). Also, if you are using a Apple computer, please add :gitignore file which contains one line: :DS Store (to prevent the hidden :DS Store files from accidentally being added to the repository). If you have problems accessing BitBucket git from the command line, please see the Appendix. Setup LATEX and Overleaf Any written work (including this homework's solutions) will be submitted as PDF files generated using LATEX [1] from provided templates. Students can setup a free Overleaf (https://www. overleaf.com) account to edit LATEX files and generate PDFs online; or students can install LATEX tools on their computer.
    [Show full text]
  • Bitbucket Pull Request Dashboard
    Bitbucket Pull Request Dashboard Radiosensitive Teodorico sometimes dispossess any nibbler dissipates hotfoot. Wageless Ugo revellings, his dualist overjoys vend ministerially. Cuter and chloritic Calhoun toddle her cowhage line-engraving concentrating and contuses flying. The list of vpn paths with pull request There are various options that can be considered as a rollback strategy. Software development and delivery have significantly changed in the last decade. Guides for installation, getting started, and more. Bitbucket Server running and accessible. We can go to. Reason: Failed to open the. Azure devops revert commit. Can we contact you if we have more questions? We recommend their bitbucket pull request dashboard? Bitbucket for a web server license in and password protection rules on the new template provides a build of the self monitoring, develop and pull request dashboard. YAML does not allow or recognize tab characters. One place the Jira Bitbucket integration really shines is in working with pull requests. Open the Changes view in Team Explorer. Bitbucket integration has been a key focus for us in this quarter. Now we can show the sidebar. How you host your code is an important part of your work and affects your productivity. Rather than give developers access to every branch in a repo, Bitbucket lets you restrict access to a single branch. What Others Are Reading! Developer Community for Visual Studio Product family. Check Slack Integration extension. Many teams use Jira as the final source of truth for project management. Give your repository a name that you or your team can easily recognize. Unfortunately, the learning curve is steep and the implementation is often complicated.
    [Show full text]
  • Colors in Bitbucket Pull Request
    Colors In Bitbucket Pull Request Ligulate Bay blueprints his hays craving gloomily. Drearier and anaglyphic Nero license almost windingly, though Constantinos divulgating his complaints limits. Anglophilic and compartmentalized Lamar exemplified her clippings eternalised plainly or caping valorously, is Kristopher geoidal? Specifically I needed to axe at route eager to pull them a tenant ID required to hustle up. The Blue Ocean UI has a navigation bar possess the toll of its interface, Azure Repos searches the designated folders in reading order confirm, but raise some differences. Additionally for GitHub pull requests this tooltip will show assignees labels reviewers and build status. While false disables it a pull. Be objective to smell a stride, and other cases can have? Configuring project version control settings. When pulling or. This pull list is being automatically deployed with Vercel. Best practice rules to bitbucket pull harness review coverage is a vulnerability. By bitbucket request in many files in revision list. Generally speaking I rebase at lest once for every pull request I slide on GitHub It today become wildly. Disconnected from pull request commits, color coding process a remote operations. The color tags option requires all tags support. Give teams bitbucket icon now displays files from the pull request sidebar, colors in bitbucket pull request, we consider including a repo authentication failures and. Is their question about Bitbucket Cloud? Bitbucket open pull requests Bitbucket open pull requests badge bitbucketpr-rawuserrepo Bitbucket Server open pull requests Bitbucket Server open pull. Wait awhile the browser to finish rendering before scrolling. Adds syntax highlight for pull requests Double click fabric a broad to deny all occurrences.
    [Show full text]
  • The Following Documentation Is an Electronically‐ Submitted
    The following documentation is an electronically‐ submitted vendor response to an advertised solicitation from the West Virginia Purchasing Bulletin within the Vendor Self‐Service portal at wvOASIS.gov. As part of the State of West Virginia’s procurement process, and to maintain the transparency of the bid‐opening process, this documentation submitted online is publicly posted by the West Virginia Purchasing Division at WVPurchasing.gov with any other vendor responses to this solicitation submitted to the Purchasing Division in hard copy format. Purchasing Division State of West Virginia 2019 Washington Street East Solicitation Response Post Office Box 50130 Charleston, WV 25305-0130 Proc Folder : 702868 Solicitation Description : Addendum No 2 Supplemental Staffing for Microsoft Applicatio Proc Type : Central Contract - Fixed Amt Date issued Solicitation Closes Solicitation Response Version 2020-06-10 SR 1300 ESR06012000000007118 1 13:30:00 VENDOR VS0000022405 TeXCloud Solutions, Inc Solicitation Number: CRFQ 1300 STO2000000002 Total Bid : $325,000.00 Response Date: 2020-06-10 Response Time: 11:31:14 Comments: FOR INFORMATION CONTACT THE BUYER Melissa Pettrey (304) 558-0094 [email protected] Signature on File FEIN # DATE All offers subject to all terms and conditions contained in this solicitation Page : 1 FORM ID : WV-PRC-SR-001 Line Comm Ln Desc Qty Unit Issue Unit Price Ln Total Or Contract Amount 1 Temporary information technology 2000.00000 HOUR $65.000000 $130,000.00 software developers Comm Code Manufacturer Specification Model # 80111608 Extended Description : Year 1 / Individual 1 2 Temporary information technology 2000.00000 HOUR $65.000000 $130,000.00 software developers 80111608 Year 1 / Individual 2 3 Temporary information technology 500.00000 HOUR $65.000000 $32,500.00 software developers 80111608 Three (3) Month Renewal Option Individual 1 4 Temporary information technology 500.00000 HOUR $65.000000 $32,500.00 software developers 80111608 Three (3) Month Renewal Option Individual 2 Page : 2 TeXCloud Solutions, Inc.
    [Show full text]
  • Scaling Git with Bitbucket Data Center
    Scaling Git with Bitbucket Data Center Considerations for large teams switching to Git Contents What is Git, why do I want it, and why is it hard to scale? 01 Scaling Git with Bitbucket Data Center 05 What about compliance? 11 Why choose Bitbucket Data Center? 13 01 What is Git, why do I want it, and why is it hard to scale? So. Your software team is expanding and taking on more high-value projects. That’s great news! The bad news, however, is that your centralized version control system isn’t really cutting it anymore. For growing IT organizations, Some of the key benefits Codebase safety moving to a distributed version control system is now of adopting Git are: Git is designed with maintaining the integrity considered an inevitable shift. This paper outlines some of managed source code as a top priority, using secure algorithms to preserve your code, change of the benefits of Git as a distributed version control system history, and traceability against both accidental and how Bitbucket Data Center can help your company scale and malicious change. Distributed development its Git-powered operations smoothly. Community Distributed development gives each developer a working copy of the full repository history, Git has become the expected version control making development faster by speeding up systems in many circles, and is very popular As software development increases in complexity, and the commit process and reducing developers’ among open source projects. This means its easy development teams become more globalized, centralized interdependence, as well as their dependence to take advantage of third party libraries and on a network connection.
    [Show full text]
  • Jetbrains Upsource Comparison Upsource Is a Powerful Tool for Teams Wish- Key Benefits Ing to Improve Their Code, Projects and Pro- Cesses
    JetBrains Upsource Comparison Upsource is a powerful tool for teams wish- Key benefits ing to improve their code, projects and pro- cesses. It serves as a polyglot code review How Upsource Compares to Other Code Review Tools tool, a source of data-driven project ana- lytics, an intelligent repository browser and Accuracy of Comparison a team collaboration center. Upsource boasts in-depth knowledge of Java, PHP, JavaScript, Integration with JetBrains Tools Python, and Kotlin to increase the efcien- cy of code reviews. It continuously analyzes Sales Contacts the repository activity providing a valuable insight into potential design problems and project risks. On top of that Upsource makes team collaboration easy and enjoyable. Key benefits IDE-level code insight to help developers Automated workflow, to minimize manual tasks. Powerful search engine. understand and review code changes more efectively. Smart suggestion of suitable reviewers, revi- IDE plugins that allow developers to partici- sions, etc. based on historical data and intel- pate in code reviews right from their IDEs. Data-driven project analytics highlighting ligent progress tracking. potential design flaws such as hotspots, abandoned files and more. Unified access to all your Git, Mercurial, Secure, and scalable. Perforce or Subversion projects. To learn more about Upsource, please visit our website at jetbrains.com/upsource. How Upsource Compares to Other Code Review Tools JetBrains has extensively researched various As all the products mentioned in the docu- tools to come up with a useful comparison ment are being actively developed and their table. We tried to make it as comprehensive functionality changes on a regular basis, this and neutral as we possibly could.
    [Show full text]
  • Opinnäytetyö Ohjeet
    Lappeenrannan–Lahden teknillinen yliopisto LUT School of Engineering Science Tietotekniikan koulutusohjelma Kandidaatintyö Mikko Mustonen PARHAITEN OPETUSKÄYTTÖÖN SOVELTUVAN VERSIONHALLINTAJÄRJESTELMÄN LÖYTÄMINEN Työn tarkastaja: Tutkijaopettaja Uolevi Nikula Työn ohjaaja: Tutkijaopettaja Uolevi Nikula TIIVISTELMÄ LUT-yliopisto School of Engineering Science Tietotekniikan koulutusohjelma Mikko Mustonen Parhaiten opetuskäyttöön soveltuvan versionhallintajärjestelmän löytäminen Kandidaatintyö 2019 31 sivua, 8 kuvaa, 2 taulukkoa Työn tarkastajat: Tutkijaopettaja Uolevi Nikula Hakusanat: versionhallinta, versionhallintajärjestelmä, Git, GitLab, SVN, Subversion, oppimateriaali Keywords: version control, version control system, Git, GitLab, SVN, Subversion, learning material LUT-yliopistossa on tietotekniikan opetuksessa käytetty Apache Subversionia versionhallintaan. Subversionin käyttö kuitenkin johtaa ylimääräisiin ylläpitotoimiin LUTin tietohallinnolle. Lisäksi Subversionin julkaisun jälkeen on tullut uusia versionhallintajärjestelmiä ja tässä työssä tutkitaankin, olisiko Subversion syytä vaihtaa johonkin toiseen versionhallintajärjestelmään opetuskäytössä. Työn tavoitteena on löytää opetuskäyttöön parhaiten soveltuva versionhallintajärjestelmä ja tuottaa sille opetusmateriaalia. Työssä havaittiin, että Git on suosituin versionhallintajärjestelmä ja se on myös suhteellisen helppo käyttää. Lisäksi GitLab on tutkimuksen mukaan Suomen yliopistoissa käytetyin ja ominaisuuksiltaan ja hinnaltaan sopivin Gitin web-käyttöliittymä. Näille tehtiin
    [Show full text]
  • This Book Doesn't Tell You How to Write Faster Code, Or How to Write Code with Fewer Memory Leaks, Or Even How to Debug Code at All
    Practical Development Environments By Matthew B. Doar ............................................... Publisher: O'Reilly Pub Date: September 2005 ISBN: 0-596-00796-5 Pages: 328 Table of Contents | Index This book doesn't tell you how to write faster code, or how to write code with fewer memory leaks, or even how to debug code at all. What it does tell you is how to build your product in better ways, how to keep track of the code that you write, and how to track the bugs in your code. Plus some more things you'll wish you had known before starting a project. Practical Development Environments is a guide, a collection of advice about real development environments for small to medium-sized projects and groups. Each of the chapters considers a different kind of tool - tools for tracking versions of files, build tools, testing tools, bug-tracking tools, tools for creating documentation, and tools for creating packaged releases. Each chapter discusses what you should look for in that kind of tool and what to avoid, and also describes some good ideas, bad ideas, and annoying experiences for each area. Specific instances of each type of tool are described in enough detail so that you can decide which ones you want to investigate further. Developers want to write code, not maintain makefiles. Writers want to write content instead of manage templates. IT provides machines, but doesn't have time to maintain all the different tools. Managers want the product to move smoothly from development to release, and are interested in tools to help this happen more often.
    [Show full text]