Hi @JP-6279
Thank you for reaching out to Microsoft Q&A and sharing your query. Let me provide some clarity on the questions you've raised:
Configuring build-preview
in package.json
The documentation refers to enabling the build-preview
feature for Azure Data Factory CI/CD pipelines. To include build-preview
in your package.json
, you can follow these steps:
- Open your
package.json
file. - Add or update the
scripts
section to include a command forbuild-preview
. For example:{ "scripts": { "build-preview": "npm run build -- --preview" } }
- This configuration enables you to use the
build-preview
command during your CI/CD pipeline execution. - If you are using Azure DevOps, ensure your pipeline script invokes this command during the build step.
Artifacts and Stop/Start Triggers
Regarding your question about whether the build includes only the modified stop/start triggers:
Yes, the build process in build-preview
mode is optimized.
- It captures changes to triggers, pipelines, datasets, and other ADF components based on the updates you’ve made.
- Triggers that have been modified are included in the artifacts. If triggers are unchanged, they may not be part of the generated artifacts.
- However, if your triggers are not behaving as expected or are excluded unintentionally, you can force their inclusion by verifying the build configuration in your CI/CD pipeline.
If the documentation seems unclear or incomplete, feel free to leave feedback directly on the Microsoft Docs page. You can find the option at the bottom. This helps improve the guidance for everyone.
Hope this helps. Do let us know if you any further queries.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.