Upsource 2017.2

Posted on by Maria Khalusova

Good news, everyone – Upsource 2017.2 is here! It comes with a number of highly anticipated features, brings some fun elements into your daily routine and, as usual, enhances the existing functionality. Here’s a quick recap.

  • External Inspection Engines

    Running SonarQube inspections? Or ReSharper/IntelliJ Inspections on TeamCity? Now you can see the results straight in Upsource. This makes a reviewer’s job even easier than before, especially if you’re working on a .NET project!
    ReSharper Code Inspections in Upsource
  • Python Support
    Code insight functionality is now also available to teams using Python. As for other supported languages this includes code-aware navigation, static code analysis, Find Usages and Usages diff.
    Python support
  • Reactions
    When there’s no need for an elaborate answer, give your feedback in a fast and compact form using a reaction.
    Reactions
  • GitLab Support
    We’ve received a number of requests to support GitLab merge requests, so you’ll be pleased to know that you can now perform code review for your GitLab merge requests in Upsource.
  • NPM Support
    To improve “Go to declaration” and “Find usages” in JavaScript code, we install dependencies listed in your package.json file using npm or yarn (whichever is required).
    NPM support
  • Suggested Revisions in Reviews
    We have employed advanced statistical analysis to suggest revisions that should be added to a review. Similar to the reviewer suggestions that were implemented several releases ago, this is another powerful tool that helps you review code more efficiently.
    Suggested Revisions in a Review
  • Achievements
    To make it easier to discover new features and to add some fun to your interactions with Upsource, we are introducing an achievements/badges system. So far we’ve added only a few basic achievements but that’s just the beginning!
    Achievements

That’s not all of it! If you’d like to learn more about the new Upsource 2017.2 features, please check out the What’s New page. See the complete list of changes in our issue tracker.

To try Upsource 2017.2 download the build and don’t forget to backup your current instance!

Comments below can no longer be edited.

8 Responses to Upsource 2017.2

  1. tiger-seo says:

    July 14, 2017

    Wow! Cool! Thank you, guys!

  2. Hazge says:

    July 18, 2017

    Hello.
    Is there any GitLab connection manual?
    Because a don’t see any Merge Request features in my projects or review space.
    Thanks.

    • Maria Khalusova says:

      July 18, 2017

      It doesn’t require any additional configuration. You should be able to see the merge requests on the Branches page, and you can create reviews for them from this page. If you don’t, please contact our support – upsource-support@jetbrains.com

      • krandobas says:

        July 28, 2017

        Could you tell me please, How can I configure automatic branch rewiew creation for merge requests?

        • Maria Khalusova says:

          August 1, 2017

          Hi!
          In your project’s settings go to Custom Workflows. There, you can add a trigger to create a review automatically, and there specify Merge Request * as a pattern in the Branches field.
          Upsource sees GitLab merge requests as branches, so you can automate review creation as if it was a branch.
          Hope it helps!

          • Artur Eshenbrener says:

            October 9, 2017

            Is there any way to tell GitLab that review of MR is finished and it is good to merge?

  3. Ivano says:

    December 18, 2017

    Hello,
    I am trying to set up the SonarQube analysis integration in upsource.
    By following what is written in the documentation (https://www.jetbrains.com/help/upsource/external-inspections-support.html)
    I configured TeamCity to run sonarQube analysis (whose results are correctly shown in the SonarQube server) and configured the way SonarQube analysis results are published to Upsource. (the project id, the upsource server url, the git revision id and the token generated in Upsource)

    I also enabled Code intelligence and Rune Code inspections in upsource (is this needed btw?), but all I can see in terms of code analysis are the one run from Upsource itself, and not the one from SonarQube.

    Am I missing something?

  4. Roman says:

    January 15, 2018

    We need a lot more achievements! Could you tell me when will there be an update with new challenges?

Subscribe

Subscribe for updates