Explanation
You can create a service hook for Azure DevOps Services and TFS with Jenkins.
However, the service subscription event should use the code pushed event, is triggered when the code is pushed to a Git repository.

Explanation

Step 1: Create a YAML file.
If your AKS cluster is RBAC-enabled, you must create a service account and role binding for use with Tiller.
To create a service account and role binding, create a file named rbac-virtual-kubelet.yaml Step 2: Run kubectl apply.
Apply the service account and binding with kubectl apply and specify your rbac-virtual-kubelet.yaml file.
Step 3: Run helm init.
Configure Helm to use the tiller service account:
helm init --service-account tiller
You can now continue to installing the Virtual Kubelet into your AKS cluster.
References: https://docs.microsoft.com/en-us/azure/aks/virtual-kubelet

Explanation
Pipeline artifacts are a way to persist build outputs, test results, and other files generated during a pipeline run.
They allow you to share data between stages, jobs, and pipelines, and to persist data for longer than the lifetime of a pipeline run. While artifacts can be useful for sharing data between pipeline runs and reducing the time required to download dependencies, they are not a solution for reducing the time required to install JavaScript packages from npm during a pipeline run.
The solution of reducing the pipeline execution time could be achieved by using package caching, which allows you to store and reuse npm packages from previous pipeline runs. There are several package caching options available for Azure Pipelines, including the npm task, the npm cache task, and the npm ci task. All of these options allow you to configure caching for your npm packages, which can significantly reduce the time required to install packages during subsequent pipeline runs.
Another solution could be using a dedicated agent that has those packages already installed, this way the pipeline doesn't have to install them again.
You can find more information on package caching by following this link
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/package/npm-cache?view=azure-devops

Explanation
Instead use implement continuous integration.
Note: WhiteSource is the leader in continuous open source software security and compliance management.
WhiteSource integrates into your build process, irrespective of your programming languages, build tools, or development environments. It works automatically, continuously, and silently in the background, checking the security, licensing, and quality of your open source components against WhiteSource constantly-updated denitive database of open source repositories.
Reference:
https://azuredevopslabs.com/labs/vstsextend/whitesource/

Explanation
Multi-stage builds are a new feature requiring Docker 17.05 or higher on the daemon and client. Multistage builds are useful to anyone who has struggled to optimize Dockerfiles while keeping them easy to read and maintain.
References: https://docs.docker.com/develop/develop-images/multistage-build/