stride3d / stride3d/stride-website
CDN cache not purged as part of build
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 15
- Forks
- 34
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Description
Teamcity still tries to clean up StackPath CDN cache but we recently moved to Azure Frontdoor.
At the same time, we likely want to take this opportunity to move purge cache action from a teamcity build step to a script in the stride-website repo so that it's easier to version/change (i.e. in case of changing services or how it's purged) without touching teamcity config.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the TeamCity build step that still targets StackPath and the build instructions in the stride-website repository. Confirm how Azure Front Door cache purging should be invoked, then move the purge action into a versioned repository script so the website build purges the current CDN; done means StackPath is no longer used and Azure Front Door is purged during builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- build-system, cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100