English
No results found.

Explore by product

GitHub Actions
  • Get started
  • Account and profile
  • Authentication
  • Repositories
  • GitHub
  • Enterprise administrators
  • Billing and payments
  • Organizations
  • Code security
  • GitHub Issues
  • GitHub Actions
  • GitHub Codespaces
  • GitHub Packages
  • Search on GitHub
  • Developers
  • REST API
  • GraphQL API
  • GitHub CLI
  • GitHub Discussions
  • GitHub Sponsors
  • Building communities
  • GitHub Pages
  • Education
  • GitHub Desktop
  • Atom
  • Electron
  • CodeQL
  • npm
    • English
  • English
  • 简体中文 (Simplified Chinese)
  • 日本語 (Japanese)
  • Español (Spanish)
  • Português do Brasil (Portuguese)

    • This version of GitHub Enterprise was discontinued on 2021-09-23. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

    Article version

    In this article

    Enabling debug logging

    If the workflow logs do not provide enough detail to diagnose why a workflow, job, or step is not working as expected, you can enable additional debug logging.

    Note: GitHub Actions was available for GitHub Enterprise Server 2.22 as a limited beta. The beta has ended. GitHub Actions is now generally available in GitHub Enterprise Server 3.0 or later. For more information, see the GitHub Enterprise Server 3.0 release notes.


    Note: GitHub-hosted runners are not currently supported on GitHub Enterprise Server. You can see more information about planned future support on the GitHub public roadmap.

    These extra logs are enabled by setting secrets in the repository containing the workflow, so the same permissions requirements will apply:

    • To create secrets for a user account repository, you must be the repository owner. To create secrets for an organization repository, you must have admin access.

    • To create secrets at the organization level, you must have admin access.

    • To create secrets using the REST API, you must have write access to the repository or admin access to the organization. For more information, see "GitHub Actions secrets API."

    For more information on setting secrets, see "Creating and using encrypted secrets."

    Enabling runner diagnostic logging

    Runner diagnostic logging provides additional log files that contain information about how a runner is executing a job. Two extra log files are added to the log archive:

    • The runner process log, which includes information about coordinating and setting up runners to execute jobs.
    • The worker process log, which logs the execution of a job.

    1. To enable runner diagnostic logging, set the following secret in the repository that contains the workflow: ACTIONS_RUNNER_DEBUG to true.

    2. To download runner diagnostic logs, download the log archive of the workflow run. The runner diagnostic logs are contained in the runner-diagnostic-logs folder. For more information on downloading logs, see "Downloading logs."

    Enabling step debug logging

    Step debug logging increases the verbosity of a job's logs during and after a job's execution.

    1. To enable step debug logging, you must set the following secret in the repository that contains the workflow: ACTIONS_STEP_DEBUG to true.

    2. After setting the secret, more debug events are shown in the step logs. For more information, see "Viewing logs to diagnose failures".