Commit 7e17aca

You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and Visual Studio.

You can integrate your {% data variables.product.product_name %} personal account or organization with third-party project management tools, such as Jira or Slack.

You can integrate Jira Cloud with your personal or organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues. For more information, visit the [Jira integration app](https://github.com/marketplace/jira-software-github) in the marketplace.

You can integrate Slack with your personal or organization account to subscribe for notifications, close or open issues, and provide rich references to issues and pull requests without leaving Slack. For more information, visit the [Slack integration app](https://github.com/marketplace/slack-github) in the marketplace.

{% link_in_list /running-codeql-code-scanning-in-a-container %}

title: 'Running CodeQL code scanning in a container'

shortTitle: '{% data variables.product.prodname_code_scanning_capc %} in a container'

intro: 'You can run {% data variables.product.prodname_code_scanning %} in a container by ensuring that all processes run in the same container.'

product: '{% data reusables.gated-features.code-scanning %}'

versions:

free-pro-team: '*'

enterprise-server: '>=2.22'

{% data reusables.code-scanning.beta %}

If you're setting up {% data variables.product.prodname_code_scanning %} for a compiled language, and you're building the code in a containerized environment, the analysis may fail with the error message "No source code was seen during the build." This indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code as it was compiled.

You must run {% data variables.product.prodname_codeql %} in the same container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. If you're using the {% data variables.product.prodname_codeql_runner %}, run it in the container where your code builds. For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system)." If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."

You may have difficulty running {% data variables.product.prodname_code_scanning %} if the container you're using is missing certain dependencies (for example, Git must be installed and added to the PATH variable). If you encounter dependency issues, review the list of software typically included on {% data variables.product.prodname_dotcom %}'s virtual environments. For more information, see the version-specific `readme` files in these locations:

* Linux: https://github.com/actions/virtual-environments/tree/main/images/linux

* MacOS: https://github.com/actions/virtual-environments/tree/main/images/macos

* Windows: https://github.com/actions/virtual-environments/tree/main/images/win

This sample workflow uses {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_codeql %} analysis in a containerized environment. The value of `container.image` identifies the container to use. In this example the image is named `codeql-container`, with a tag of `f0f91db`. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)."

``` yaml

name: "{% data variables.product.prodname_codeql %}"

on:

push:

branches: [main]

pull_request:

branches: [main]

schedule:

- cron: '0 0 * * 0'

jobs:

analyze:

name: Analyze

runs-on: ubuntu-latest

strategy:

fail-fast: false

matrix:

language: [java]

# Specify the container in which actions will run

container:

image: codeql-container:f0f91db

steps:

- name: Checkout repository

uses: actions/checkout@v2

- name: Initialize {% data variables.product.prodname_codeql %}

uses: github/codeql-action/init@v1

with:

languages: {% raw %}${{ matrix.language }}{% endraw %}

- name: Build

run: |

- name: Perform {% data variables.product.prodname_codeql %} Analysis

uses: github/codeql-action/analyze@v1

* Running your build process in a separate container to {% data variables.product.prodname_codeql %}. For more information, see "[Running CodeQL code scanning in a container](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container)."

* Building using a distributed build system external to GitHub Actions, using a daemon process.

* {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using.

You can submit your request to remove sensitive data via our [contact form](https://support.github.com/contact?tags=docs-sensitive-data). Please include a plain-text version of your request in the body of your message. Sending your request in an attachment may result in processing delays.

Holders of registered trademarks can report possible trademark policy violations to GitHub via our [contact form](https://support.github.com/contact?tags=docs-trademark). Please submit trademark-related requests using your company email address and include all the information requested below to help expedite our response. Also be sure to clearly describe to us why the account may cause confusion with your mark or how the account may dilute or tarnish your mark.

A job matrix can generate a maximum of 256 jobs per workflow run. This limit also applies to self-hosted runners.