Archives for the category: Fisheye/Crucible

Introducing FishEye and Crucible 3.0 – Search, visualize and review code. Faster.

 

Meet FishEye and Crucible 3.0, a massive upgrade to our code search, visualization and review tools that will help development teams work faster, every day. This release provides developers with more powerful ways to track changes across all their code repositories, share knowledge, and accelerate collaboration cycles. Developers will find it easier to perform pre-commit reviews and benefit from huge indexing performance gains – especially for Subversion repositories. Come and meet the new FishEye and Crucible!

Try FishEye and Crucible 3.0 Now

Optimized performance

The FishEye and Crucible team have been laser-focused on improving dev speed for our users. Our aim is to optimize performance from the moment you start to index your repositories to when you close a code review. It’s important for us to continue to help you save valuable time in your development process.

In FishEye 2.8 we focused on improving load times on key pages like the activity streams and projects lists. Continuing our focus on performance in 2.9, we delivered improvements to shave off seconds for several common operations between JIRA, FishEye, and Crucible–specifically the source and review Tabs. Then in 2.10, we slashed server load and made every operation faster, especially for Enterprise teams: page loads, reviews and reports. We continue the performance theme in 3.0.

A newer, faster Subversion indexing engine

Take a deep breath Subversion users; you no longer have to wait for a full index of your Subversion repository in order to start using FishEye and Crucible. Our newest release uses intelligent indexing to make viewing your latest changesets and creating reviews available while the indexing is in still progress. Exhale!

Check out the difference from data tested on a load testing instance of FishEye and Crucible comparing index scanning times of 3.0 and 2.10.

The improvements bring these advantages to Subversion users:

  • Get productive ASAP: Viewing recent changesets and creating reviews is 10 times faster.
  • Understand progress: New progress screens give you a better understanding of how long it will take to index your repository.
  • Faster JIRA integration: Information in your JIRA source and review tabs is available while indexing is being performed
No more waiting on indexing! Large repositories (read: Enterprise
teams) can start improving their code quality quicker than ever.

Even more performance gains

We did not stop there. We want to make ensure FishEye and Crucible stay fast as you grow. A huge focus was put on improving concurrent performance. You will notice improvement across the common operations you use everyday like creating review and browsing commits.

  • Faster source browsing: we upgraded our internal database (to
    InfinityDB-3), this means greater concurrent access speeds and a better
    browsing experience
  • Quicker review creation: the techy details, we optimized some SQL
    statements when creating or modifying a review in Crucible. What it
    means to you, the time to create or modify a review is cut down to save
    you valuable time.

See some of the browsing improvements from a load testing server comparing FishEye and Crucible 3.0 to 2.10.

Streamlined pre-commit reviews

Simply put, a pre-commit (or patch) review means reviewing code
changes before they are checked-in to a repository. Typically, teams
adopt pre-commit reviews as part of their code review workflow for
reasons such as:

  • Catching defects earlyEnsure other developers on your team will not get affected by defects or bugs that can be found during a review.
  • Keeping code clean: Guarantee that all code that gets into the repository is of high quality.
  • Enforcing process: Make sure that reviews are not indefinitely postponed, or pile up to the point of never getting done.

Command line interface (CLI) pre-commit reviews

Until today, Crucible has been handling
pre-commit reviews by uploading patch files through the Crucible user
interface. We wanted to streamline this process so developers can stay
in the flow. Crucible 3.0 introduces the command line interface (CLI)
tool which allows you to generate pre-commit reviews, or update existing
ones from where you already are: the command line. No logging into
Crucible, no context-switching. This shaves off valuable time from the
review process, and keeps your coders coding.

The CLI pre-commit reviews works for all supported version control
systems including Subversion, Perforce, CVS, Mercurial, and Git.

Iterative pre-commit reviews

Code reviews are naturally iterative, and pre-commit reviews are no
different. Let’s face it: Almost all reviews find something that needs
to be re-factored or reworked, and it’s not unusual for reviews to
include several revisions. Crucible automatically tracks what you’ve
reviewed at the file and revision level, as well as comments. This
ensures that you’re presented with only the latest changes, and don’t
have to wade through the rest. Crucible 3.0 makes it simple to manage
reviews throughout the iterations:

  • Outdated files: Know when a new revision is available and include it in the review with a single click.
  • Tracking as you go: Crucible tracks which files and comments you’ve already covered, then resets them as new revisions or comments are added.

Iterative code review makes it simple for teams to collaborate around code changes in order to ensure the highest code quality.

A brand new experience

Following the lead of JIRA and Confluence, FishEye and Crucible 3.0 introduce a new user experience that follows the Atlassian Design Guidelines (ADG). The
goal is simple: Put key elements front and center, so developers can
stay in the flow and work faster. The improved design is just the
beginning of making it easier to navigate FishEye and Crucible.

New global header

When logging into FishEye and Crucible, one of the first things
you’ll notice is the new global header. Navigating FishEye and Crucible
is simpler with quick access to recent repositories, projects, reviews,
and people.

Application navigator

Many FishEye users connect to other Atlassian applications, like JIRA
or Bamboo. Users can now easily switch between FishEye and JIRA–or any
other Atlassian application–all from the FishEye and Crucible header. No
more bookmarks in your browser; we do the job for you.

JIRA source and review tab redesign

The key ingredient to any source code manager is its relationship to
issues. Many FishEye users link their source to JIRA, and close the loop
between code changes and the tasks that prompted them. We wanted to
simplify the experience but still give users the important information
they need to make decisions around their issues.

Improve your dev speed with FishEye and Crucible 3.0

New to FishEye and Crucible? Start a free 30-day trial and get up and running in a matter of minutes.

Try FishEye and Crucible 3.0 Now

Already using FishEye and Crucible? Your upgrade to 3.0 is just a click away. Check out our full FishEye and Crucible release notes  to get started.

http://blogs.atlassian.com/2013/06/fisheye-crucible-30-faster-code-search-and-code-review/

Archives for the category: Fisheye/Crucible的更多相关文章

  1. django博客功能实现——标签功能

    标签功能添加流程 0.功能概括 标签作为文章中的分类标记,会显示出该文章是关于哪一方面的文章,比如是关于python的还是关于django的. 当我们点击该标签的时候,会出现该博客中所有属于该标签的文 ...

  2. 这些年常用的WEB开发工具和技术, 学会一半你找工作没问题

    前言: 技术选型并不是一成不变的,需要根据技术的发展.项目实际情况和人员技能构成实际考虑,在此列出的只是这些年常用的. 开发环境 1. 主要开发语言:Java7, HTML, Javascript等 ...

  3. [python] python django web 开发 —— 15分钟送到会用(只能送你到这了)

    1.安装python环境 1.1 安装python包管理器: wget https://bootstrap.pypa.io/get-pip.py sudo python get-pip.py   1. ...

  4. django学习笔记——搭建博客网站

    1. 配置环境,创建django工程 虚拟环境下建立Django工程,即创建一个包含python脚本文件和django配置文件的目录或者文件夹,其中manage.py是django的工程管理助手.(可 ...

  5. Atlassian In Action - (Atlassian成长之路)

    Atlassian是我工作过程中,使用过的最满意的研发团队管理套装.使用的主要软件包括Jira Software,Confluence,Fisheye/Crucible.理论上还可以再加上Bitbuc ...

  6. Jira 使用手册

    Date Revision version Description author 2018-06-14 V1.0.0 Isaac Zhang 2018-06-22 V1.0.1 1,添加git提交操作 ...

  7. centos7破解安装fisheye和Crucible

    背景介绍: Atlassian的东西相信大家都不陌生,JIRA.Confluence……虽然说这些产品都要收费,也可以申请试用: FishEye 可以方便地查看代码,而Crucible 则是进行Cod ...

  8. fisheye在centos上的安装

    目录 描述 部署过程 安装及配置 破解 添加存贮库 在jira上配置 描述 Fisheye 一个源代码库深度查看软件,它可以挖掘源代码库中的有用信息,呈现在Web浏览器界面上. Crucible是一个 ...

  9. category中重写方法?

    问:可以在category中重写方法吗? 答:代码上可以实现 在category中重写方法,但在实际开发中,不建议这样做.如果确实需要重写原有方法也建议使用子类进行重写. category是为了更方便 ...

随机推荐

  1. $.each()遍历Json对象

    1.遍历JavaScript数组对象: var json = [ //中括号起始 {"id":"1","tagName":"app ...

  2. Objective-c中的单例

    单例是指静态分配的实例,就是只开辟一块内存,不会重新开辟内存,而 iphone sdk 中全是这种实例,例如[UIApplication sharedApplication] 返回一个指向代表应用程序 ...

  3. sp.Net MVC4 + Oracle + EasyUI + Bootstrap2

    Asp.Net MVC4 + Oracle + EasyUI + Bootstrap 第二章   Asp.Net MVC4 + Oracle + EasyUI + Bootstrap 第二章 --使用 ...

  4. Performing User-Managed Database-18.4、Restoring Datafiles and Archived Redo Logs

    18.4.Restoring Datafiles and Archived Redo Logs 假定介质故障损坏的一个或多个数据文件,数据文件必须恢复损坏的文件之前恢复. 该位置是不是想恢复原来姿势. ...

  5. Appium Android Bootstrap源码分析之简介

    在上一个系列中我们分析了UiAutomator的核心源码,对UiAutomator是怎么运行的原理有了根本的了解.今天我们会开始另外一个在安卓平台上基于UiAutomator的新起之秀--Appium ...

  6. SQL点滴20—T-SQL中的排名函数

    原文:SQL点滴20-T-SQL中的排名函数 提到排名函数我们首先可能想到的是order by,这个是排序,不是排名,排名需要在前面加个名次序号的,order by是没有这个功能的.还可能会想到ide ...

  7. 【SSRS】入门篇(七) -- 报表发布

    原文:[SSRS]入门篇(七) -- 报表发布 完成[SSRS]入门篇(六) -- 分组和总计后,第一份简单的报表就已完成了,下面把报表发布到报表服务器上. (实际情况下,报表展示给用户未必是用报表服 ...

  8. ssis的script task作业失败(调用外部dll)

    原文 ssis的script task作业失败 我的ssis作业包里用了一个script task,会查询一个http的页面接口,获取json数据后解析然后做后续处理,其中解析json引用了本地目录下 ...

  9. AngularJS+requireJS项目的目录结构设想

    AngularJS+requireJS项目的目录结构设想 准备用AngularJS + require.js 作为新项目的底层框架,以下目录结果只是一个初步设想: /default    放页面,不过 ...

  10. innerText与innerHTML的区别

    innerText与innerHTML的区别:1.innerText将所有文本内容作为普通的文本2.innerHTML会识别文本内容中是否含有html标签,它能够把html标签的效果显示出来3.inn ...