Upsource 2.5 is released

Posted on by Maria Khalusova

Today we are excited to share with you the latest Upsource release: please give a warm welcome to Upsource 2.5.

This is a free upgrade for all existing commercial customers, and even if you’re not using Upsource so far, remember that a 10-user plan is free of charge.

Here’s what we’ve included in Upsource 2.5:

  • Smarter email notifications: Upsource bundles notifications and sends them as a single email so you have less in your inbox to go through. We’ve also added the ability to reply to comments via email.
  • Redesigned Review page: Based on your feedback we have thoroughly revised the Review page UI, and gave it a completely new look.
  • Discussion labels: Labels can be applied to discussions to denote priority, category, or any other information that you find useful.
  • Branches page: See the activity across branches on the brand-new Branches page.
  • Open in IDE: It is now possible to open a review (or a piece of code) in the IDE by clicking a link in the browser.
  • Numerous IDE Plugin Improvements and more!

You can learn more about new features and improvements in Upsource 2.5. Alternatively, here’s a video that sums up most of the changes:

https://youtu.be/Plx7FEhCiUg

Download Upsource 2.5 and follow these instructions to safely upgrade your instance.

Yours truly,
The Upsource Team

Comments below can no longer be edited.

27 Responses to Upsource 2.5 is released

  1. Artem says:

    November 18, 2015

    Unfortunately i couldn’t get the upsource service started on windows (upgrading 2.0.3682 to 2.5.4934).
    I always get the following error:

    [Upsource Cluster Initialize Service Error] log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.FileAppender.
    [Upsource Cluster Initialize Service Error] log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.FileAppender.
    [Upsource Cluster Initialize Service Error] [2015-11-18 12:54:50,305] WARN APP-WRAPPER] Proxy 1 datastax.driver.core.NettyUtil – Found Netty’s native epoll transport, but not running on linux-based operating system. Using NIO instead.
    [Upsource Cluster Initialize Service Error] Core version mismatch. Database update not possible
    Upsource Cluster Initialize Service failed to start

    Is there a solution for this?

    • Maria Khalusova says:

      November 18, 2015

      You need to follow instructions for the major upgrade mentioned in the post:
      http://upsource-support.jetbrains.com/hc/en-us/articles/205018542-How-to-upgrade-your-Upsource-installation-

      • Jordan Petersen says:

        November 18, 2015

        I followed the major upgrade instructions and I get the same error as Artem.

        • Jordan Petersen says:

          November 18, 2015

          Please ignore. I copied data and conf from the previous install rather than from the backup.

        • Maria Khalusova says:

          November 18, 2015

          That is strange. Can you contact our support to help us figure out what went wrong?
          upsource-support@jetbrains.com

          • Tammo Schülke says:

            November 18, 2015

            Just like Jordan, I stumbled upon step 6 because the wording is even worse here, as it lacks the “” hint, and that’s what a google search for “upsource upgrade” offers first:

            “Copy data and conf folder from the Upsource.old/backup directory to the new .”

            https://www.jetbrains.com/upsource/help/2.5/upgrade.html

            Also, the upgrade process and packaging of Upsource differs from the other JetBrains products.

            • Tammo Schülke says:

              November 18, 2015

              “date_of_backup” was stripped from my comment.

            • Maria Khalusova says:

              November 18, 2015

              We see that the upgrade process is indeed confusing, and we will automate it as much as possible with the next version to avoid these issues. Sorry about the trouble.

            • Javier Z. McFigglestein says:

              November 18, 2015

              It’s also confusing how the update section references upgrading to Upsource 2.5.2 which doesn’t even exist yet.

  2. Даниил Водопьян says:

    November 18, 2015

    At what languages does Upsource support code navigation? Does that already work for Kotlin? Thanks

    • Maria Khalusova says:

      November 18, 2015

      Yes, code insight works for Kotlin as well.

  3. Damian says:

    November 18, 2015

    I’m upgrading from build 2.0.3682 and Cassandra won’t start.

    2015-11-18T10:19:04,301 [MemtableFlushWriter:1] ERROR o.a.c.service.CassandraDaemon – Exception in thread Thread[MemtableFlushWriter:1,5,main]
    java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native

    [root@672206-dev-tools cassandra]# java -version
    openjdk version “1.8.0_51”
    OpenJDK Runtime Environment (build 1.8.0_51-b16)
    OpenJDK 64-Bit Server VM (build 25.51-b03, mixed mode)

  4. Yury V. Zaytsev says:

    November 19, 2015

    So, with the redesigned review page, is it somehow possible to also see the complete diff, not just per-file diffs? I generally like the new design, and it makes sense in most of the cases, but I still want to have the possibility to view the complete diff as well. Am I correct that this is only possible if one disables the new design and uses the old one?

    Also, re. UP-5679, is it possible to turn this commit to review adding “intelligence” off? I understood from UP-4808 that there must be a project level option somewhere, but, unfortunately, I can’t seem to be able to find it…

    • Maria Khalusova says:

      November 19, 2015

      Yes, you are correct. If you want to see all changes one after another on the same page, you need to switch off master-detail view in your personal settings.
      Regarding UP-5679 and UP-4808, it is not possible to switch it off.
      We are very careful about adding commits though.

      • Yury V. Zaytsev says:

        November 19, 2015

        > If you want to see all changes one after another on the same page, you need to switch off master-detail view in your personal settings.

        Okay, thank you for the confirmation, but this is my only issue with the new design, and it’s a bit cumbersome to switch to the old one to see the complete diff and then switch back again.

        I think it would be great if one could build in a button in the new design “show complete diff on the right side”, which can be clicked only when needed by the reviewer. In this case, I would completely switch over and not use the old design anymore.

        Is there a ticket for that, or I should create one?

        P.S. I somehow posted the last message as a new comment instead of replying to yours, sorry about that.

        • Maria Khalusova says:

          November 19, 2015

          Can you please create a ticket?

          • Yury V. Zaytsev says:

            November 24, 2015

            See UP-5722 Make it possible to optionally continuously scroll through the diff in the new “master-detail” review page!

  5. Yury V. Zaytsev says:

    November 19, 2015

    > Regarding UP-5679 and UP-4808, it is not possible to switch it off. We are very careful about adding commits though.

    Well, obviously, not careful enough (merge commits that close the branch are added to the review if they contain the review identifier), such that my workflow is now completely broken.

    Do you have any hints on how to solve the problem for me, if it’s not possible to disable this feature? The only thing that I can think of is to stop using review identifiers in the merge commits :-/

    • Maria Khalusova says:

      November 19, 2015

      You can not mention review ID, if you don’t want it attached. May I ask why are you using them in commit messages, if the commit is not related to the review?

      • Yury V. Zaytsev says:

        November 19, 2015

        > May I ask why are you using them in commit messages, if the commit is not related to the review?

        Sure, here is a workflow:

        1) Create topic branch
        2) Create a review from this branch
        (Optional: Add more commits, they would get attached because it’s a branch review, no matter if you mention the review ID or not, but in this case, the intelligence at least doesn’t bother anyone)
        3) Review is completed, reviewers have given their thumbs up
        5) Merge the branch into master, mentioning the review ID in the merge commit

        Here the merge commit is added to the review by Upsource intelligence, which is undesired.

        The reason why I would like to mention review IDs in the merge commits is that this makes it clear that the merged branch has been reviewed (and in which review) and one can easily jump to the review directly from browsing the merge history.

        However, the merge commit itself is in a different branch and has nothing to do with the review, the review ID is just mentioned there to keep the provenance clear, so I don’t want it to be added to the review.

        P.S. In UP-5679, it was established that the commits are not added if the review is closed. This is a good thing, but it’s very tedious to make sure you always close the review before the merge. At least, it’s a workaround for my case.

  6. Vitaly Litvak says:

    November 19, 2015

    Is it possible to edit/delete custom discussion label?

    P.S. thank you for a great job done!

  7. Ian Ross says:

    November 25, 2015

    I am a new user and have just installed Upsource 2.5 on a 64-bit Windows 7 system. On starting, the Upsource Cluster Initialize Service always fails to start:

    [Upsource Cluster Initialize Service Error] log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.FileAppender.
    [Upsource Cluster Initialize Service Error] log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.FileAppender.
    [Upsource Cluster Initialize Service Error] [2015-11-25 16:12:14,956] WARN APP-WRAPPER] Proxy 1 datastax.driver.core.NettyUtil – Found Netty’s native epoll transport, but not running on linux-based operating system. Using NIO instead.
    [Upsource Cluster Initialize Service Error] [2015-11-25 16:12:23,582] ERROR IU-144.530, eap:true .xslt.impl.XsltConfigImpl[IDE] –
    [Upsource Cluster Initialize Service Error] java.lang.NullPointerException
    [Upsource Cluster Initialize Service Error] at org.intellij.lang.xpath.xslt.impl.XsltConfigImpl.initComponent(XsltConfigImpl.java:72)
    [Upsource Cluster Initialize Service Error] at com.intellij.openapi.components.impl.ComponentManagerImpl$ComponentConfigComponentAdapter.getComponentInstance(ComponentManagerImpl.java:518)
    [Upsource Cluster Initialize Service Error] at com.intellij.openapi.components.impl.ComponentManagerImpl.createComponents(ComponentManagerImpl.java:123)
    [Upsource Cluster Initialize Service Error] at com.intellij.openapi.application.impl.ApplicationImpl.access$801(ApplicationImpl.java:90)
    [Upsource Cluster Initialize Service Error] at com.intellij.openapi.application.impl.ApplicationImpl$12.run(ApplicationImpl.java:496)
    [Upsource Cluster Initialize Service Error] at com.intellij.openapi.application.impl.ApplicationImpl.createComponents(ApplicationImpl.java:502)
    [Upsource Cluster Initialize Service Error] at com.intellij.openapi.components.impl.ComponentManagerImpl.init(ComponentManagerImpl.java:107)
    [Upsource Cluster Initialize Service Error] at com.intellij.openapi.application.impl.ApplicationImpl.load(ApplicationImpl.java:454)
    [Upsource Cluster Initialize Service Error] at com.intellij.openapi.application.impl.ApplicationImpl.load(ApplicationImpl.java:446)
    [Upsource Cluster Initialize Service Error] at com.jetbrains.upsource.backend.server.psi.IdeaApplicationFactory.create(IdeaApplicationFactory.java:153)
    [Upsource Cluster Initialize Service Error] at com.jetbrains.upsource.backend.server.facade.UpsourceApplicationEnvironment.(UpsourceApplicationEnvironment.java:143)
    [Upsource Cluster Initialize Service Error] at com.jetbrains.upsource.ClusterInitService.start(ClusterInitService.java:44)
    [Upsource Cluster Initialize Service Error] at com.jetbrains.launcher.AppProxy$4.call(AppProxy.java:83)
    [Upsource Cluster Initialize Service Error] at com.jetbrains.launcher.AppProxy$4.call(AppProxy.java:81)
    [Upsource Cluster Initialize Service Error] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    [Upsource Cluster Initialize Service Error] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    [Upsource Cluster Initialize Service Error] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    [Upsource Cluster Initialize Service Error] at java.lang.Thread.run(Thread.java:745)
    [Upsource Cluster Initialize Service Error] com.intellij.ide.plugins.PluginManager$StartupAbortedException: com.intellij.diagnostic.PluginException: [Plugin: org.jetbrains.kotlin]
    Upsource Cluster Initialize Service failed to start

  8. Alexander says:

    January 25, 2016

    Hi,
    I’m not sure about is this right place to ask such question, but anyway: we are investigating possibility to use Upsource in a project with up to 100 users.
    What system requirments would be enough to provide good user experience ?
    Based on my last experience playing with Upsource2 I faced with bad performance when I run it with 6 GB (couldn’t provide more due to VM limitations.)
    Would 16GB be enough, or we need to provide more – for example 24,32? What about disk space requirments?

    Thanks

Subscribe

Subscribe for updates