How to make build preview

JP-6279 0 Reputation points
2024-12-03T02:44:03.8166667+00:00

Hi,

Please find the docuements - https://learn.microsoft.com/en-us/azure/data-factory/continuous-integration-delivery-improvements

To use the build-preview, it is necessary to add build-preview to package.json. However, it does not give any clues how to configure this build-preview in the package.json.

Also, does the build includes the only stop/start triggers that are modified when building Artifact? It is pretty messy for this part in the documents.

Kind regards,

JP

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
10,968 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Smaran Thoomu 17,610 Reputation points Microsoft Vendor
    2024-12-03T11:55:19.78+00:00

    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 for build-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.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.