From acdd840f848a58effbd5c6377ff2e99da2c89f58 Mon Sep 17 00:00:00 2001 From: lizrabuya <115472349+lizrabuya@users.noreply.github.com> Date: Fri, 6 Sep 2024 14:31:07 +1000 Subject: [PATCH 1/5] v0.0.0 --- package.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/package.json b/package.json index e8fb09a31f..a571387831 100644 --- a/package.json +++ b/package.json @@ -21,5 +21,6 @@ "dependencies": { "@docsearch/js": "3", "@hotwired/turbo-rails": "^7.3.0" - } + }, + "version": "0.0.0" } From 682bf41e21942cc1a877b43c5f81a3f50cd64f18 Mon Sep 17 00:00:00 2001 From: lizrabuya <115472349+lizrabuya@users.noreply.github.com> Date: Fri, 6 Sep 2024 14:48:40 +1000 Subject: [PATCH 2/5] Add info on how often a job expiry process is ran --- pages/pipelines/build_timeouts.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pages/pipelines/build_timeouts.md b/pages/pipelines/build_timeouts.md index 51dae6d375..ad6239dd56 100644 --- a/pages/pipelines/build_timeouts.md +++ b/pages/pipelines/build_timeouts.md @@ -38,3 +38,6 @@ By default, jobs are canceled when not picked up for 30 days. This will cause th You can override the default by setting a shorter value in your organization's [**Pipeline Settings**](https://buildkite.com/organizations/~/pipeline-settings) page. Scheduled job limits should not be confused with [scheduled builds](/docs/pipelines/scheduled-builds). A scheduled build's jobs will still go through the [build states](/docs/pipelines/defining-steps#build-states), and the timeout will apply once its individual jobs are in the scheduled state waiting for agents. + +> 📘 Delays in expiring a job +> A job's expiry process is run hourly at 5 minutes past. When the expiry process runs and the job's scheduled expiry was not over at that hour, it will only be expired until the next hour when the process is executed again. \ No newline at end of file From 18795c3822364bcb6418208a2019cd36280b1aeb Mon Sep 17 00:00:00 2001 From: lizrabuya <115472349+lizrabuya@users.noreply.github.com> Date: Fri, 6 Sep 2024 14:58:29 +1000 Subject: [PATCH 3/5] Fix lint errors --- pages/pipelines/build_timeouts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/pipelines/build_timeouts.md b/pages/pipelines/build_timeouts.md index ad6239dd56..13b21a2178 100644 --- a/pages/pipelines/build_timeouts.md +++ b/pages/pipelines/build_timeouts.md @@ -40,4 +40,4 @@ You can override the default by setting a shorter value in your organization's [ Scheduled job limits should not be confused with [scheduled builds](/docs/pipelines/scheduled-builds). A scheduled build's jobs will still go through the [build states](/docs/pipelines/defining-steps#build-states), and the timeout will apply once its individual jobs are in the scheduled state waiting for agents. > 📘 Delays in expiring a job -> A job's expiry process is run hourly at 5 minutes past. When the expiry process runs and the job's scheduled expiry was not over at that hour, it will only be expired until the next hour when the process is executed again. \ No newline at end of file +> A job's expiry process is run hourly at 5 minutes past. When the expiry process runs and the job's scheduled expiry was not over at that hour, it will only be expired until the next hour when the process is executed again. From b3fbf07edf0faca5be557d8efd7acfb5a50971e0 Mon Sep 17 00:00:00 2001 From: Lizette Rabuya <115472349+lizrabuya@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:40:48 +1100 Subject: [PATCH 4/5] Update pages/pipelines/build_timeouts.md Co-authored-by: Giles Gas --- pages/pipelines/build_timeouts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/pipelines/build_timeouts.md b/pages/pipelines/build_timeouts.md index 13b21a2178..efa4ce3605 100644 --- a/pages/pipelines/build_timeouts.md +++ b/pages/pipelines/build_timeouts.md @@ -39,5 +39,5 @@ You can override the default by setting a shorter value in your organization's [ Scheduled job limits should not be confused with [scheduled builds](/docs/pipelines/scheduled-builds). A scheduled build's jobs will still go through the [build states](/docs/pipelines/defining-steps#build-states), and the timeout will apply once its individual jobs are in the scheduled state waiting for agents. -> 📘 Delays in expiring a job -> A job's expiry process is run hourly at 5 minutes past. When the expiry process runs and the job's scheduled expiry was not over at that hour, it will only be expired until the next hour when the process is executed again. +> 📘 Delays in job expiration +> A job's expiration process is run hourly at 5 minutes past. When the expiration process runs and the job's scheduled expiration was not over at that hour, it will only be expired until the next hour when the process is executed again. From 19f160fbbe170dbeb9c9eb6108381dd8fb878f09 Mon Sep 17 00:00:00 2001 From: Giles Gas Date: Fri, 18 Oct 2024 11:58:51 +1100 Subject: [PATCH 5/5] Revert package.json --- package.json | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/package.json b/package.json index a571387831..e8fb09a31f 100644 --- a/package.json +++ b/package.json @@ -21,6 +21,5 @@ "dependencies": { "@docsearch/js": "3", "@hotwired/turbo-rails": "^7.3.0" - }, - "version": "0.0.0" + } }