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.
# 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"]
Question Can we moved release level Test plans to any folder, /Archive Need to hide previous TestPlans not to show every time when I present I know how to filter
Good morning Sir, Can you please make a Azure Project which utilizes different Azure services Especially Databases, advanced networking, RBAC using Azure AD
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
www.devopsshack.com/courses/Batch-5--Zero-To-Hero--DevSecOps--Cloud-DevOps-661d3ad119a57f6bb98a762f
man you are the real handson helping hand for us
This is brilliant! Keep up the good work.
One of the best videos for Azure Devops! Can we put in CV?
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.
Ask from GPT 4 .. they will be best explaination
# 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"]
Sonarqube prepare configuration stage is failed, it is showing can not find location string for key
I hope you will do it in Self Azure DevOps agent
Question
Can we moved release level Test plans to any folder, /Archive
Need to hide previous TestPlans not to show every time when I present
I know how to filter
Clear content.Thankyou very much
Why are you using same tools. SonarQube, trivi . Why not snyk, Checkmarx and so on
Hi Aditya,
very well explained.
can you please teach security and networking CNI part, it will be very helpful.
Thanks.
I am working in that A company and have migrated 100s of servers/apps on cloud
Can u give training pls
He used Classic Pipeline ?
A means AT&T?
Good morning Sir,
Can you please make a Azure Project which utilizes different Azure services
Especially Databases, advanced networking, RBAC using Azure AD
very informative
Osm
Classic Pipelines , why not YAML
Probably will be teaching in future masterclaases.
As of now its added in my courses
This guy learning and as a practice he is promoting this video...Who is using Classic pipelines now....Its completely multi stage Yaml pipeline
444th like
can i explain this project during an interview if asked
Kindly add time stamp
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