Webinar recording: What’s New in Upsource 3.0

The recording of our webinar “What’s New in Upsource 3.0” is available on JetBrains YouTube channel.

In this webinar recording Maria Khalusova goes over the major features introduced in the latest release, Upsource 3.0, such as:

  • Code insight for PHP projects
  • Code analysis summary
  • Build Status from CI server
  • Automated Workflows
  • GitHub Integration and Pull Requests support
  • Custom notifications
  • Webhooks
  • https://www.youtube.com/watch?v=9kbUn5ikhNo

    This webinar is geared towards developers of different proficiency regardless of programming language of choice.

    Maria Khalusova_webinar
    Maria is a JetBrains’ veteran and has participated in various projects since 2006: IntelliJ IDEA, TeamCity, AppCode. Currently she is a Product Marketing Manager in Upsource team. Maria is passionate about productivity tools, sharing knowledge and photography.

Comments below can no longer be edited.

7 Responses to Webinar recording: What’s New in Upsource 3.0

  1. Avatar

    आलोक says:

    May 18, 2016

    What’s the json payload format for upsource webhooks?
    We have set them up but they don’t seem to work.
    If it makes any difference it’s for integration with slack.

  2. Avatar

    Artem says:

    May 18, 2016

    Hi There,

    There should be an example of a json in the webhooks doc located here:


    Could you please share with us webhooks trigger(s) settings you have configured?

  3. Avatar

    आलोक says:

    May 18, 2016

    Thanks. The triggers are pretty simple:

    1 On new revision : post to a single (slack) url
    2 On On comment added/ On review created/ On review closed or reopened/On review accepted or concern raised : post to another single (slack) url

    From the doc you provided, the issue could be owing to the fact that slack expects certain name value pairs, and they are not available in the json that upsource generates.
    But that’s just a hunch. Is it possible to view the POST payload data that upsource sends and the status code it received from the integrated service in some audit or access logs?

    What slack expects, from their documentation:
    payload={“text”: “A very important thing has occurred! for details!”}

    • Avatar

      Kirill Kononov says:

      May 19, 2016


      The POST payload data that Upsource sends is not shown in logs. However, a payload structure is fully described in the doc that Artem has mentioned. There is also an example of a payload shown on that page.

      The results of webhook requests are reflected in logs as the following messages:
      “Successful webhook POST to URL
      “Unsuccessful webhook POST to URL, response code: statusCode

      Obviously, there should be an intermediate entity between Upsource and Slack for the described integration to work, since the json formats are not compatible directly. We will probably provide Slack integration out of the box in the future, but for now there is no such feature.

      • Avatar

        Rajiv Nair says:

        August 4, 2016

        We’ve done a quick n’ dirty node service to sit between slack and upsource. It supports notifications when reviews are opened, closed, participants or comments are added etc. Feel free to extend or re-use as you see fit.
        Have a look: https://github.com/rajivrnair/upsource-slack-api-adapter

  4. Avatar

    Rodislav Moldovan says:

    May 19, 2016

    pull requests are working only with github ?
    can I create pull request with thirdparty repositories ? for example for repos from Stash from Atlassian, so when everything is accepted Upsource will merge all the changes to the original repos from stash 🙂