The document outlines the use of Microsoft Azure Pipelines for building, testing, and deploying applications across platforms, specifically detailing tasks, secret variables, and AWS S3 integration. It mentions the use of Jekyll as a static site builder and the implementation of Docker for deployment. Additionally, it includes FAQs and contact information for Tarun Jangra, the CTO at Ginvoicing.

1. Microsoft Azure
Pipeline
Build, Test and Deploy to
any platform.

2. Tarun Jangra
CTO at GInvoicing
+91-9888300750
tarun.jangra@hotmail.com
Happy Devops
Solution architect, Serial Entrepreneur, DevOps
@jangratarun
@tarunjangra

3. Overview
1. Azure pipeline. “Build, Test and Deploy to any Platform”.
2. Azure Tasks.
3. Docker Task.
4. Secret Variables.
5. Access of AWS S3.
6. Github, an external repository.
7. Demo.
8. FAQs.

4. Build, Test and Deploy to any platform.
1. Static site builder “Jekyll”.
2. Github, An external git repository.
3. Ruby language to make test and deployment tasks.
4. Docker image “jekyll/builder:latest”.
5. Deploy it on AWS S3 Which can be further connected to AWS CloudFront
to leverage amazing performance.

5. Azure tasks.
A task is the building block for defining automation in a build pipeline, or in a
stage of a release pipeline. A task is simply a packaged script or procedure that
has been abstracted with a set of inputs.
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/?view=azure-
devops

7. Docker task

9. Secret variables.
1. Encrypted 2048-bit RSA.
2. Masked with “*”.
3. Reference in azure-pipeline.yml with $(variable-name).
4. AWS Secret key and access key.

13. AWS S3 Access

14. Access to S3 - Create user.

15. Access to S3 - Set Permissions

16. Access to S3 - Credentials

17. S3 - After deployment

18. Github as an external repository.

19. Source code@Github

20. Demo - http://azure-pipeline.s3-website.ap-south-1.amazonaws.com/

21. Tarun Jangra
Happy Devops FAQs
CTO at GInvoicing
+91-9888300750
tarun.jangra@hotmail.com
@jangratarun
@tarunjangra