Posts to do with setup and maintenance for Repositories, builds, etc.
View All Tags
Today, we took a major step toward automating the deployment of this site, eliminating manual steps and reducing the risk of errors.
Now, every pull request (PR) generates a preview build, and every merge to the
main branch automatically triggers a production deployment. This new setup
speeds up the process, ensures consistency, and minimizes the chances of
mistakes.
Today, we focused on streamlining our automated preview deployment process for PRs, ensuring that each pull request includes a live preview of the Docusaurus site, Storybook components, and test reports.
The main goal was to automate the deployment of a fully functional preview for every PR, complete with Docusaurus builds, Storybook, and test results. This meant dealing with dynamic URLs, managing build artifacts, and ensuring everything worked in harmony.
Automating the preview process means changes to the site are instantly available for review, speeding up development and reducing the chance of bugs. This allows us to deliver updates faster while keeping quality high.
As part of our commitment to ensuring high-quality code, we've set up an automated testing and reporting workflow using Vitest, Istanbul, and XUnit Viewer. Here’s a quick overview of how we made that happen.
We opted for:
It's been a few days since I posted. That's not because I haven't been busy, it's because setting up unit testing turned out to be much harder than I anticipated.
To be fair, I was trying to achieve a somewhat complex setup.