Skip to content

Commit e81d6d8

Browse files
authored
Merge pull request #2667 from buildkite/ivannalisetska/doc-64660-cron-job-permission
Cron Job Permission Considuration
2 parents 9bc41ff + 423db48 commit e81d6d8

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

pages/pipelines/scheduled_builds.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,21 @@ You can create and manage schedules in the Schedules section of your Pipeline Se
88

99
You can also create and manage schedules using the [Buildkite GraphQL API](/docs/apis/graphql-api).
1010

11+
## Cron job permission consideration
12+
13+
When setting up a cron job in your parent pipeline, it's important to ensure that the same team has been assigned to the corresponding child pipeline. Failure to match the team between the parent and child pipelines may result in an error with the following message:
14+
15+
**Error:**
16+
17+
_Could not find a matching team that includes both pipelines, each having a minimum "Build" access level._
18+
19+
This error is indicative of a mismatch in team assignments and highlights the importance of maintaining consistent team configurations across interconnected pipelines to avoid permission-related issues.
1120

1221
## Schedule intervals
1322

1423
The interval defines when the schedule will create builds. Schedules run in UTC time by default, and can be defined using either predefined intervals or standard crontab time syntax.
1524

16-
>🚧 Interval granularity
25+
> 🚧 Interval granularity
1726
> Buildkite only guarantees that scheduled builds run within 10 minutes of the scheduled time, and therefore does not support intervals less than 10 minutes.
1827
1928
### Predefined intervals

0 commit comments

Comments
 (0)