Skip to content

WIP: Resolve "Add Gulp to External Pipeline"

Lauren Barker requested to merge 5323-implement-external-pipeline-3 into master

This adds Gulp 4 to the existing frontend external pipeline.

Introduces Gulp 4 to external pipeline

When the existing frontend external_pipeline for middleman is activated, it now includes a command to run yarn gulp production. Gulp process the source/assets directory and puts finished files in tmp/frontend/

When pipeline.sh executes, it now runs three commands:

yarn install
yarn gulp production // Fires Gulp to process JS and SCSS
yarn run bundle "${@}"

Moves stylesheets directory

By default, Middleman will process any scss located at /source/stylehssets. By moving our scss to source/assets/stylesheets, middleman no longer process stylesheets. Final destination of .css files remains the same.

Moves javascripts direcotry

By default, Middleman will process any javascript files located at /source/javascript. By moving our javascript to source/assets/javascript, middleman no longer process javascript files. Final destination of .js files remains the same.

Relieves Middleman from building scss and js

Middleman no longer builds css or js files during the build. This reduces the build_branch CI process down from XX to XX

Faster livereload of stylesheets and javascript

Developers can now use gulp development locally to see live reloading of scss and js changes. This is faster than middlemans native livereload feature.

related #5323 (closed)

Edited by Lauren Barker

Merge request reports