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. 将已有的工程项目添加到Xcode到Git管理中

    在Xcode中创建工程的时候,我们很容易的可以将新创建的工程添加到Git中,如图: 但是如果是本地已经有的工程,那该如何添加到Git中呢? 首先终端进入到该工程的目录. 然后: git init gi ...

  2. MVC验证02-自定义验证规则、邮件验证

    原文:MVC验证02-自定义验证规则.邮件验证 本文体验MVC自定义验证特性,来实现对邮件的验证.对于刚写完的自定义验证特性,起初只能支持后端验证.如果要让前端jquery支持,还必须对jquery的 ...

  3. s2sh三大框架整合过程(仅供参考)

    三大框架顾名思义就是非常有名的Struts2 ,Hibernate,Spring, 框架整合的方法很多,现在我写一个非常简单的整合过程,相信大家一看就会! 这里使用的struts-2.2.1.1.hi ...

  4. 用javascript把扑克牌理理顺!

    打扑克的人都知道,比如斗地主! 我们一般都会按照顺序把随机摸过来的牌从小到大的顺序在手上理整齐(记得小时候打牌两副牌手都抓不过来),这篇随笔就是想通过实现这个功能来熟悉下js中排序数组等相关知识. 用 ...

  5. 调试javascript

    Chrome 控制台 如何调试javascript 上面的文章已经大致介绍了一下console对象具体有哪些方面以及基本的应用,下面简单介绍一下如何利用好chrome控制台这个神器好好调试javasc ...

  6. MUI初始化滚动区域

    mui(".mui-scroll-wrapper").scroll().refresh(); 如果不是MUI对象,需要转一下才可 mui($("#areaDiv" ...

  7. windows下架设SVN服务器并设置开机启动

    原文:windows下架设SVN服务器并设置开机启动 1.安装SVN服务器,到http://subversion.apache.org/packages.html上下载windows版的SVN,并安装 ...

  8. Maven包装过程中跳过测试

    在具体项目,步骤需要跳过假设检验,应采取skipTests此属性设置为true. <pre name="code" class="html">< ...

  9. MVC 5 - 查询Details和Delete方法

    MVC 5 - 查询Details和Delete方法 在这部分教程中,接下来我们将讨论自动生成的Details和Delete方法. 查询Details和Delete方法 打开Movie控制器并查看De ...

  10. 用户故事(User Story)

    用户故事(User Story)       用户故事是描述对用户有价值的功能,好的用户故事应该包括角色.功能和商业价值三个要素.用户故事通常的格式为:作为一个<角色>, 我想要<功 ...