SSWConsulting / SSWConsulting/SSW.Rules
DevOps - Shortening build times for content changes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
@pierssinclairssw @adamcogan @bradystroud @wicksipedia
Hi,
As per my conversation with Piers and Adam, we are looking at methods to reduce the build time for content changes. In theory, only a few files should have changed when a content change is merged. However, the build process takes approximately 9 minutes. The 'yarn build:incremental' step in the build process only takes approximately 3.5 minutes of this.
Note: There is an issue to migrate SSW Rules to Azure Static Web Hosting and use GitHub Actions which could make this issue redundant. See #628
- Investigate the deployment process of SSW Rules to understand what happens when a deployment is triggered
- Discuss findings with @wicksipedia
- Create issues to implement any changes arising from this investigation
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 tracing the deployment process and the yarn build:incremental step mentioned in the issue, then compare the approach with the possible Azure Static Web Hosting and GitHub Actions migration in #628. Discuss the findings with @wicksipedia; done means documenting the bottleneck and creating follow-up implementation issues for the agreed changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- build-system, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100