You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md
+14
Original file line number
Diff line number
Diff line change
@@ -37,5 +37,19 @@ If any dependencies are missing, check the log files for errors. If any package
37
37
38
38
## Viewing {% data variables.product.prodname_dependabot %} log files
39
39
40
+
{% ifversion dependabot-job-log %}
41
+
42
+
{% data reusables.dependabot.dependabot-jobs-log-access %}
43
+
44
+
To view the full logs files for a particular job, to the right of the log entry you are interested in, click **view logs**.
45
+
46
+
47
+
48
+
For more information, see "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/viewing-dependabot-job-logs)."
49
+
50
+
{% else %}
51
+
40
52
1. On the **{% data variables.product.prodname_dependabot %}** tab, click **Last checked _TIME_ ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates.
41
53
1. Optionally, to rerun the version check, click **Check for updates**.
Copy file name to clipboardexpand all lines: content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md
+13-5
Original file line number
Diff line number
Diff line change
@@ -60,16 +60,24 @@ If an error blocked {% data variables.product.prodname_dependabot %} from creati
60
60
61
61
## Investigating errors with {% data variables.product.prodname_dependabot_version_updates %}
62
62
63
-
When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to update a dependency in an ecosystem, it posts the error icon on the manifest file. The manifest files that are managed by {% data variables.product.prodname_dependabot %} are listed on the {% data variables.product.prodname_dependabot %} tab. To access this tab, on the **Insights** tab for the repository click **Dependency graph**, and then click the **{% data variables.product.prodname_dependabot %}** tab.
63
+
When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to update a dependency in an ecosystem, {% ifversion dependabot-job-log %} you can view the job logs list to find out more about the error {% else %} it posts the error icon on the manifest file{% endif %}.
64
64
65
-
65
+
{% ifversion dependabot-job-log %}
66
+
67
+
{% data reusables.dependabot.dependabot-jobs-log-access %}
68
+
69
+
To view the full logs files for a particular job, to the right of the log entry you are interested in, click **view logs**.
66
70
67
-
{% ifversion fpt or ghec %}
71
+
68
72
69
-
To see the log file for any manifest file, click the **Last checked TIME ago** link. When you display the log file for a manifest that's shown with an error symbol, any errors are also displayed.
73
+
For more information, see "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/viewing-dependabot-job-logs)."
70
74
71
75
{% else %}
72
76
77
+
The manifest files that are managed by {% data variables.product.prodname_dependabot %} are listed on the {% data variables.product.prodname_dependabot %} tab. To access this tab, on the **Insights** tab for the repository click **Dependency graph**, and then click the **{% data variables.product.prodname_dependabot %}** tab.
78
+
79
+
80
+
73
81
To see the logs for any manifest file, click the **Last checked TIME ago** link, and then click **View logs**.
74
82
75
83
{% endif %}
@@ -177,7 +185,7 @@ For more information on how to configure groups for {% data variables.product.pr
177
185
178
186
### {% data variables.product.prodname_dependabot %} fails to update one of the dependencies in a grouped pull request
179
187
180
-
**Version updates only.**{% data variables.product.prodname_dependabot %} will show the failed update in your logs, as well as in the job summary at the end of your logs. You should use the `@dependabot recreate` comment on the pull request to build the group again. For more information, see "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
188
+
**Version updates only.**{% data variables.product.prodname_dependabot %} will show the failed update in your logs, as well as in the job summary at the end of your logs. You should use the `@dependabot recreate` comment on the pull request to build the group again. For more information, see "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
181
189
182
190
If the dependency still fails to update, you should use the `exclude-patterns` configuration so that the dependency is excluded from the group. {% data variables.product.prodname_dependabot %} will then raise a separate pull request to update the dependency.
intro: 'To support debugging of {% data variables.product.prodname_dependabot %} pull requests, {% data variables.product.product_name %} provides logs of all {% data variables.product.prodname_dependabot %} jobs.'
4
+
shortTitle: Viewing Dependabot logs
5
+
versions:
6
+
feature: dependabot-job-log
7
+
type: how_to
8
+
topics:
9
+
- Dependabot
10
+
- Troubleshooting
11
+
- Errors
12
+
- Security updates
13
+
- Dependencies
14
+
---
15
+
16
+
## About {% data variables.product.prodname_dependabot %} job logs
17
+
18
+
Whenever a {% data variables.product.prodname_dependabot %} job runs, the details of the job are captured in the job logs list, which is accessibile from the dependency graph.
19
+
20
+
For each manifest file, the job logs record the most recent runs of {% data variables.product.prodname_dependabot %}, with each log entry displaying the job type, job ID, timestamp, and, where necessary, a link to the pull request(s) associated with the job.
21
+
22
+
You may find that the log entry contains a short error message, which can be useful for debugging issues with a particular pull request or run. If you need to troubleshoot further, you can click **view logs** to access the full log files for a specific run.
23
+
24
+
You will see the following job types recorded in the log list:
25
+
-**Version update** - refers to a {% data variables.product.prodname_dependabot_version_updates %} run.
26
+
-**Security update** - refers to a {% data variables.product.prodname_dependabot_security_updates %} run.
27
+
-**Rebase update** - refers to a run where {% data variables.product.prodname_dependabot %} has automatically rebased the pull request to resolve a conflict with the target branch. This update could apply to a pull request from a {% data variables.product.prodname_dependabot_version_updates %} job, or a {% data variables.product.prodname_dependabot_security_updates %} job.
28
+
29
+
## Viewing {% data variables.product.prodname_dependabot %} job logs
30
+
31
+
The {% data variables.product.prodname_dependabot %} job logs list is accessible from the dependency graph tab in your repository.
32
+
33
+
{% data reusables.repositories.navigate-to-repo %}
34
+
{% data reusables.repositories.accessing-repository-graphs %}
35
+
{% data reusables.repositories.click-dependency-graph %}
36
+
{% data reusables.dependabot.click-dependabot-tab %}
37
+
1. To the right of the name of manifest file that you're interested in, click **Recent update jobs**.
38
+
1. Optionally, to see the full logs files for a particular job, click **view logs**.
39
+
40
+
The job logs list is accessible from the dependency graph of a repository. From the dependency graph, click the **{% data variables.product.prodname_dependabot %}** tab, then to the right of the affected manifest file, click **Recent update jobs**.
0 commit comments