Choose the Best Fitting for Your DevOps Plumbing: Red Hat OpenShift CI/CD Pipelines with JFrog Artifactory and Xray
This repository contains the code for the Choose the Best Fitting for Your DevOps Plumbing: Red Hat OpenShift CI/CD Pipelines with JFrog Artifactory and Xray SwampUp 2021 Session. This session is jointly presented by Red Hat and JFrog and discusses how to develop a CI/CD pipeline with OpenShift and the JFrog Platform. It contains a npm application, dockerfile and openshift pipeline/tekton pipelines, resources and tasks to build and deploy the application.
The build and deployment of our DevOps pipelines is achieved through the use of OpenShift Pipelines (Tekton) for CI/CD and the JFrog CLI. The JFrog CLI is used to build and upload the artifacts and the build information. Openshift Pipelines is used to automate this process. The pipeline and the tasks that use the JFrog CLI are defined in pipeline.yaml.
- Apply the project-clusterrolebinding to allow OpenShift Pipelines to use the default ServiceAccount to create K8s resources.
kubectl apply -f project-clusterrolebinding.yaml -n demo
- Apply the pipeline YAML with the following command to create the Task and Pipeline resources.
kubectl apply -f pipeline.yaml -n demo
- Then create the PipelineRun resource to execute the pipeline. You can use the pipeline-run.yaml as an demo and apply it.
kubectl apply -f pipeline-run.yaml -n demo
or you can use the OpenShift Pipeline UI to create the PipelineRun resource via Pipeline > Start.
- The pipeline creates a K8s Deployment and a Service to deploy the application. To view the application, create an OpenShift Route under Networking > Routes. Specify the service as seen here.
- Click on the URL to view your application!
This project was generated with Angular CLI version 10.1.7.
$ docker build -t demo-app .
$ docker run -p 443:443 -p 80:80 docker.io/library/demo-app
Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.
Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.
Run ng test to execute the unit tests via Karma.
Run ng e2e to execute the end-to-end tests via Protractor.
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.