How do I update the license?
General settingsin the side bar to display the current license details.
- Click Browse to display a file selection dialog box.
- Locate the license file and select it.
- Click Open to confirm the selection and close the dialog box.
- Click Upload to load the new license file.
Can LGTM analyze private projects from cloud-based services?
Yes, LGTM Enterprise supports private repositories for all cloud-based host systems for which there is an authorization provider. These include Azure DevOps Service (previously called VSTS), Bitbucket Cloud, GitHub.com, and GitLab.com—see System integrations. The authorization provider ensures that the access rights to such projects, configured in the host system, are respected in LGTM Enterprise.
How do I add a project that LGTM can't build?
Some codebases are so large, or have such complex build environments, that it doesn't make sense to create specialized LGTM worker hosts to build them. In these cases, it's often best to use your existing infrastructure to create a QL snapshot. Then you can use the rest API to create an LGTM project with the special upload analysis mode and upload the snapshot for analysis. For more information, see Using upload analysis.
Projectsin the side bar to display the project pages.
- Find the project you're interested in.
- Click the project name to display detailed information.
- The External immutable ID is shown on the Info tab under Basic information.
You should be able to display the full log file for any of the jobs run by LGTM (for details, see Exploring work pool logs). If you click a link and the log file can't be displayed, there are two possible reasons:
- Routine housekeeping tasks have deleted the file.
- Your external URL is misconfigured, so the link to the log file is wrong.
If the file has been deleted, you cannot retrieve it. If the log file was for a failed attempt-build job, then you can retry the build to rerun the job.
It is always worth checking that your external URL is correctly configured. If this is wrong, you may also have problems uploading a license, logging in with an external authentication provider, or analyzing pull requests. In addition, any links included in emails sent to users will be wrong. You can check the external URL on the
LGTM polls each repository once every 24 hours to find out if there are any new commits to analyze. Poll jobs are scheduled to be spread evenly across the 24-hour period, with the poll job for a specific repository occurring at roughly the same time every day. The result is that LGTM does not start to analyze a new commit until after the repository has been polled, which may be up to 24 hours after the code change was merged.
If someone needs to see analysis results more quickly, you can trigger a manual poll job. Go to Projects > <project name> > Repository and click Poll repository. Better still, if you enable automated code review for a project, LGTM alerts are reported in your repository host system when developers raise a pull request. That way they can fix issues before the code is merged into the repository. For more information, see Managing automated code review in the user help.
You have added a new repository provider and then added projects from that repository. The projects have been added successfully in the
The issue may be that the projects are private. Check the authorization provider used in the repository provider settings (see Defining an external repository provider). If this is set to Private, no one will see the project in the main interface unless they are explicitly given FULL access in the settings page for an individual user in the administration interface (see Overriding authorization for all projects associated with a repository provider). By default, users can only see a very restricted amount of data relating to projects added from a repository that uses the Private authorization provider. For more information, see Restricted authorization.
You have added an issue tracker provider but no issue tickets have been raised for some projects. There are several possible reasons for this.
- No new analysis yet—LGTM Enterprise polls repositories once a day for changes to each project and then analyzes any revisions. No issue tracking updates will be made until the daily poll job has been performed. If you want to force LGTM Enterprise to poll for changes to a project, go to Projects > <project name> > Repository and click Poll repository.
- Query filter too restrictive—The query filter you have defined for the issue tracker provider may be too restrictive to match any alerts. Try modifying the filter on the provider's settings page. For information about the syntax of query filters, see Configuring issue tracking.
- No new alerts—By default, issue tickets are only raised for new alerts, identified by LGTM Enterprise after you added the issue tracker integration. If you want to raise issue tickets for all existing alerts, clear the Only create issues for new alerts check box on the provider's settings page.
- Issue tracker integration turned off—Issue tracking integration can be turned off for specific projects. In the administration interface, go to Projects > <project name> > Analysis settings and check that the Create tickets for alerts in this project check box is selected.