Upsource 2017.3 Help

Warning: "This file is binary or is too large to be displayed"

This warning may be shown when you're viewing revisions or reviews containing large or binary files. If you must see all of the changes, the limit can be raised.

Solution

To raise the limit in the ZIP installation:

  1. Stop Upsource: <upsource_home>/bin/upsource.sh stop

  2. Open the configuration file upsource-frontend.jvmoptions located in the <upsource_home>/conf/upsource-frontend directory. If the file does not exist, create it.

  3. Add the following lines to that file:

    frontend.view.filesize.limit=XXXX frontend.diff.filesize.limit=YYYY

    where XXXX is the maximum file size (2000000 by default) and YYYY is the maximum length of the diff (1000 lines by default).

  4. Save and close the file.
  5. Start Upsource.

To raise the limit in the Docker installation::

  1. Stop Upsource: docker exec <containerId> stop

  2. Open the configuration file upsource-frontend.jvmoptions. The file is located in the <path to conf directory>/conf/upsource-frontend/. If the file does not exist, create it.

  3. Add the following lines to that file:

    frontend.view.filesize.limit=XXXX frontend.diff.filesize.limit=YYYY

    where XXXX is the maximum file size (2000000 by default) and YYYY is the maximum length of the diff (1000 lines by default).

  4. Save and close the file.

  5. Start Upsource: docker start <containerId>.

Last modified: 28 February 2018
Error: "Some services registered by Product are not valid in target Hub"Warning: "The full diff is too big to be displayed, showing the first 200 changed files"