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
Currently, in our GitHub Actions workflow, we build the site files for each job independently. This approach may lead to redundancy and slower build times, especially when dealing with the "static" content.
Proposal:
We could optimize the workflow by building the "static" content once and then reusing it across all jobs. This would potentially reduce build times and overall resource consumption.
Additional Notes:
If the build speed is already satisfactory, we might not need to implement this optimization.
As of now, the entire CI process completes in less than a minute.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Discussion base on: #614 (comment)
Problem:
Currently, in our GitHub Actions workflow, we build the site files for each job independently. This approach may lead to redundancy and slower build times, especially when dealing with the "static" content.
Proposal:
We could optimize the workflow by building the "static" content once and then reusing it across all jobs. This would potentially reduce build times and overall resource consumption.
Additional Notes:
If the build speed is already satisfactory, we might not need to implement this optimization.
As of now, the entire CI process completes in less than a minute.
Beta Was this translation helpful? Give feedback.
All reactions