A while ago I wrote two articles about how you can automate the publishing process of your SharePoint Framework scripts and solution package via custom gulp tasks.
These gulp tasks are already a great step forward but still, requires you to manually launch these gulp commands to push everything to your environments. For publishing, this requires you to execute the following steps: bundle, package, upload scripts, and package.
A couple of weeks ago, when I was setting up a build pipeline for another project, I saw that the gulp and npm build tasks became available in preview on Azure DevOps. These tasks are a great way to automate the deployment process. So, that you only have to commit and push your code (if you use Git of course).
Something else which is great about it is that you can set up multiple builds and release pipelines which allow you to target various environments (development, test, production, …).
Here is an example of the build process:
In my case, when I push a new release to Git, the build process automatically picks it up and executes the following tasks:
- Get all files
- Get all dependencies via the npm install command
- Update the CDN URL in the manifests JSON file. For this, I created a simple gulp tasks. That way you can change the URL per build task. Here is the code snippet of the task:
- Bundle the project via the
gulp bundle --shipcommand
- Package the project via the
gulp package-solution --shipcommand
- When the project is bundled and the solution package is created, everything will be zipped and published ready for release.
Once the build process is completed, the release task will automatically start the continuous deployment feature.
Info: if you want you can configure everything in the build pipeline, but when you are working with multiple environments. You would most probably like it to set it up via a release pipeline.
Here you can see the output of my production deployment:
It is not as fancy as the build output, but it does the following tasks:
- Retrieve the zip package (this is done automatically, so you do not have to configure it)
- Extract the files from the retrieved package
- Upload the SharePoint Framework project bundle files to the SharePoint CDN library
- Upload the app package to SharePoint
Info: for the upload gulp tasks to SharePoint I made use of the approach I explained in the two articles about automation for SPFx. Only a small change has been made to allow you to make use of gulp arguments. That way, it is not done from a configuration file in your project, but via variables in the build and release pipeline instead.
In the next article, I will explain how you can configure the build and release pipelines yourself.