ci: Skip WebsiteAutoDeployment on scheduled builds - #2492
Conversation
The nightly scheduled build runs with always: true, meaning it triggers even when there are no new commits. The WebsiteAutoDeployment job redeploys the exact same website content every night, adding ~21 min of build time and introducing unnecessary failure points that mask real test failures. Skip this job on scheduled builds since push triggers (merges to master) already handle website deployment when content actually changes.
|
Hey Brendan Walsh (@BrendanWalsh) 👋! We use semantic commit messages to streamline the release process. Examples of commit messages with semantic prefixes:
To test your commit locally, please follow our guild on building from source. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2492 +/- ##
==========================================
- Coverage 84.28% 84.24% -0.04%
==========================================
Files 335 335
Lines 17781 17781
Branches 1592 1592
==========================================
- Hits 14987 14980 -7
- Misses 2794 2801 +7 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
2 participants
Summary
Skip the
WebsiteAutoDeploymentjob on nightly scheduled builds.Problem
The nightly scheduled build runs with
always: true, meaning it triggers even when there are no new commits on master. TheWebsiteAutoDeploymentjob redeploys the exact same website content every night, which:Fix
Add
ne(variables['Build.Reason'], 'Schedule')to the job condition so it only runs on push/PR triggers, which already handle website deployment when content actually changes.Testing
This is a pipeline condition change — no code logic affected. Website deployment will still run on every merge to master and on manual/tag-triggered builds.