Azure DevOps CICD Pipeline Project | Real-Time DevOps Project

Рет қаралды 8,471

Ай бұрын

Azure DevOps CICD Pipeline Project | Real-Time DevOps Project
𝗘𝗻𝗿𝗼𝗹 𝗧𝗼 𝗕𝗮𝘁𝗰𝗵-𝟱 | 𝗭𝗲𝗿𝗼 𝗧𝗼 𝗛𝗲𝗿𝗼 𝗗𝗲𝘃𝗦𝗲𝗰𝗢𝗽𝘀 & 𝗖𝗹𝗼𝘂𝗱 𝗗𝗲𝘃𝗢𝗽𝘀 𝗦𝘁𝗮𝗿𝘁𝗶𝗻𝗴 𝟭𝟴𝘁𝗵 𝗠𝗮𝘆:
www.devopsshack.com/courses/B...
Project: github.com/jaiswaladi246/Boar...
Doubt Clearing Group: t.me/+9roGPjX1YI42Yzdl
Instagram: / devopsshack
LinkedIn: / devops-shack

Пікірлер: 20

@devopsshack Ай бұрын

www.devopsshack.com/courses/Batch-5--Zero-To-Hero--DevSecOps--Cloud-DevOps-661d3ad119a57f6bb98a762f

@incrediblemanii Ай бұрын

One of the best videos for Azure Devops! Can we put in CV?

@RohitAlam-zr7on Ай бұрын

man you are the real handson helping hand for us

@saurabhpundir4048 5 күн бұрын

suutmunni intik po

@KunalGaming303 Ай бұрын

Osm

@prashishshirsat9214 Ай бұрын

Hi Aditya, very well explained. can you please teach security and networking CNI part, it will be very helpful. Thanks.

@GunShot109 10 күн бұрын

very informative

@SofiaParker777 14 күн бұрын

Good morning Sir, Can you please make a Azure Project which utilizes different Azure services Especially Databases, advanced networking, RBAC using Azure AD

@user-xe8ub5iq6c Ай бұрын

Hello Aditya, I hope you are doing well. Please try to explain the Dockerfile and YAML manifests you create for each project while making project videos. Thank you.

@imran-khan_fans8484 20 күн бұрын

Ask from GPT 4 .. they will be best explaination

@imran-khan_fans8484 20 күн бұрын

# Use an official Node.js runtime as the base image FROM node:14 # Set the working directory in the container to /app WORKDIR /app # Copy package.json and package-lock.json (if available) to the working directory # This step helps leverage Docker's caching mechanism for faster builds COPY package*.json ./ # Install dependencies specified in package.json RUN npm install # Copy the rest of the application code to the working directory COPY . . # Expose the port the application will run on # Replace 3000 with your application's port if different EXPOSE 3000 # Define the command to run the application # This usually matches the "start" script in your package.json CMD ["npm", "start"]

@NishankumarTripathy 6 күн бұрын

Sonarqube prepare configuration stage is failed, it is showing can not find location string for key

@saitejareddygurujala2534 Ай бұрын

Classic Pipelines , why not YAML

@devopsshack Ай бұрын

Probably will be teaching in future masterclaases. As of now its added in my courses

@profitstrading5513 Ай бұрын

This guy learning and as a practice he is promoting this video...Who is using Classic pipelines now....Its completely multi stage Yaml pipeline

@arnaudfrancktaptuekuate5367 Ай бұрын

Why are you using same tools. SonarQube, trivi . Why not snyk, Checkmarx and so on

@udaykumar-tb5kn Ай бұрын

U do video we all see

@roulniur2393 Ай бұрын

can i explain this project during an interview if asked

@roulniur2393 Ай бұрын

Kindly add time stamp

@iamthor1504 18 күн бұрын

INFO: Load plugins index (done) | time=49ms INFO: Load/download plugins (done) | time=148ms INFO: Process project properties INFO: Process project properties (done) | time=10ms INFO: Execute project builders INFO: Execute project builders (done) | time=2ms INFO: ------------------------------------------------------------------------ INFO: EXECUTION FAILURE INFO: ------------------------------------------------------------------------ INFO: Total time: 2.049s INFO: Final Memory: 8M/34M INFO: ------------------------------------------------------------------------ ##[error]ERROR: Error during SonarScanner execution ERROR: Validation of project failed: o To use the property "sonar.branch.name" and analyze branches, Developer Edition or above is required. See docs.sonarqube.org/latest/analyzing-source-code/branches/branch-analysis/ for more information. ERROR: ERROR: Re-run SonarScanner using the -X switch to enable full debug logging. ERROR: Error during SonarScanner execution ERROR: Validation of project failed: o To use the property "sonar.branch.name" and analyze branches, Developer Edition or above is required. See docs.sonarqube.org/latest/analyzing-source-code/branches/branch-analysis/ for more information. ERROR: ERROR: Re-run SonarScanner using the -X switch to enable full debug logging. ##[warning]LIB_ResourceFile does not exist ##[warning]Resource file haven't been set, can't find loc string for key: LIB_ProcessExitCode ##[warning]Error while executing SonarQube:Analyze task: LIB_ProcessExitCode /home/ubuntu/myagent/_work/_tasks/SonarQubeAnalyze_6d01813a-9589-4b15-8491-8164aeb38055/5.20.1/sonar-scanner/bin/sonar-scanner 2 ##[error]LIB_ProcessExitCode /home/ubuntu/myagent/_work/_tasks/SonarQubeAnalyze_6d01813a-9589-4b15-8491-8164aeb38055/5.20.1/sonar-scanner/bin/sonar-scanner 2 Finishing: Run Code Analysis getting error in run code analysis can you help @devopsshack in this or anyone