Difference between revisions of "InContext Installation"

From Lingoport Wiki
Jump to: navigation, search
(Chrome Extension Configuration)
(Chrome Extension Configuration)
Line 38: Line 38:
 
* Click on the 'Option' icon (☰) of the dialog.
 
* Click on the 'Option' icon (☰) of the dialog.
 
* Fill in the data, using the username and token
 
* Fill in the data, using the username and token
  +
[[File:incontext_configuration.png|300px]]
 
** Jenkins URL
 
** Jenkins URL
 
** Jenkins user name
 
** Jenkins user name

Revision as of 21:41, 24 July 2018

Pre-Requisites

In order to use Lingoport InContext QA, the user must have access to the Google Chrome browser. Lingoport InContext QA is based off a Chrome extension and other browsers do not have the same capability. Firefox or Internet Explorer can not be used as the browser in this situation.

  • LRM must be installed and
  • the G11n Continuous System's Jenkins server must be accessible from the reviewer's system.

The reviewer needs to have the following information which should be set up by the Jenkins administrator:

  • The Jenkins URL
  • A Jenkins username and password.
  • To get the API token and verify the Jenkins account:
    • Log in to Jenkins using the reviewer username and password.
    • Select the pull down next to username at the top of the window and select Configure.
      • Under API Token, Show API Token.... Copy the token.


In addition, the reviewer will need:

  • Their email address

Chrome Extension Installation

From within the Google Chrome Browser:

Google.png
  • click on Add to Chrome Extension

You should see the Lingoport swirl Swirl.png at the top of the Chrome browser window.

  • Select the three vertical dots on the top right side of the Chrome browser window. In the menu, select Settings
Chrome customize.png
  • On the Settings page, select the three horizontal lines (Main Menu) and select Extensions. There should be an entry for Lingoport InContext QA. Slide Developer Mode button to ON.
  • Select DETAILS in the Lingoport InContext QA entry. Slide on the choice for Allow access to file URLs

Note: If you are using multiple screens, you may want to invoke Chrome the following way:

  • "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" /high-dpi-support=1 /force-device-scale-factor=1. --allow-file-access-from-files

Chrome Extension Configuration

  • Before configuring the Chrome InContext extension, a username needs to be created in Jenkins.
  • Click on the Lingoport swirl Swirl.png for the Chrome Extension (top right corner of your Chrome)
  • Click on the 'Option' icon (☰) of the dialog.
  • Fill in the data, using the username and token

300px

    • Jenkins URL
    • Jenkins user name
    • Jenkins user API Token
    • Reviewer's email address
  • Click on 'Save Credentials'