You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Kratix-docs CircleCI job is setup to run the build & deploy stages in a single job and the job is only configured to run on the main branch. This results in poor development feedback loops as yarn build is not run in CI until deploy time on main. yarn build should run on all development branches as it gives development time verifications of things like broken links and broken dependencies.
The text was updated successfully, but these errors were encountered:
cghsystems
changed the title
chore: Split build-and-deploy job and run on all branches
chore: Split build-and-deploy job and run build on all branches
Jul 1, 2024
instead of splitting, consider adding a job that runs on all branches but main that just runs the yarn build step, while the existing ci remains as is; i think the overall pipeline may be simpler this way 🤔
The Kratix-docs CircleCI job is setup to run the build & deploy stages in a single job and the job is only configured to run on the main branch. This results in poor development feedback loops as
yarn build
is not run in CI until deploy time on main.yarn build
should run on all development branches as it gives development time verifications of things like broken links and broken dependencies.Tasks are:
build
job on all branchesdeploy
should still only run on main)The text was updated successfully, but these errors were encountered: