Let's build all en-us docs every 6h instead of 24h
See original GitHub issueAt the moment, in prod-build.yml
the cron job runs every 24h. It takes about 50min each time. I believe if you only do mdn/content (aka. only the en-us) it only takes about 15min. The translated-content very rarely changes. It will change once we unfreeze it but even then it might be worth keep that stuff to every 24h.
What we could do instead is to build the en-us content every 6h and the whole everything every 24h.
This way, the time between a merged mdn/content PR and getting it into production will be reduced. We still have the CDN cache which might hold on to a page “too long” but if it’s a new edit, the chances are better.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:9 (6 by maintainers)
Top Results From Across the Web
NGU Idle Guide
As you fight and defeat bosses, you will unlock more menus/features. ... Boosts drop in the itopod at a flat 16% (roughly 1...
Read more >Known issues with Google Meet
Google is aware of this issue. Tip: When you add a meeting room in a different time zone, schedule the event for 24...
Read more >Customizing date formats in Amazon QuickSight
Example Description Token
99 or 21 A 2‑digit representation of a year. YY
1999 or 2021 A full, 4‑digit numeric representation of a year. YYYY
1–12...
Read more >Scheduling and sending dashboards | Looker
Looker lets you schedule immediate or recurring deliveries of dashboards with the Schedule delivery dashboard menu option. Depending on how your Looker admin ......
Read more >Assisted Living Resources and Frequently-Asked ...
All information related to the application process is available on the ... Are there any documents related to services the provider must give...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@schalkneethling I don’t think it’s worth the effort right now, because of my earlier comment, but I think it’s worth considering in the future when there’s time to make the changes necessary to the deployer code.
This still sounds like a good idea, what do you think @escattone?