Devops Unit 5
Devops Unit 5
Devops Unit-5
Step 8: Select the free plan. On the plan selection page, scroll
down to click the button for choosing a free plan. This will
immediately take you to your GitHub dashboard.
Repository:
Step 6: Now you will see that all of our files uploaded in our
github.
Branch:
A GitHub branch is used to work with different versions
of a repository at the same time.
By default a repository has a master branch (a
production branch).
Any other branch is a copy of the master branch (as it
was at a point in time).
New Branches are for bug fixes and feature work
separate from the master branch. When changes are
ready, they can be merged into the master branch. If you
make changes to the master branch while working on a
new branch, these updates can be pulled in.
Commits:
At GitHub, changes are called commits.
Each commit (change) has a description explaining why a
change was made.
Pull Requests :
Pull Requests are the heart of GitHub collaboration.
With a pull request you are proposing that your changes
should be merged (pulled in) with the master.
Pull requests show content differences, changes,
additions, and subtractions in colors (green and red).
As soon as you have a commit, you can open a pull
request and start a discussion, even before the code is
finished.
Git:
Git was created by Linus Torvalds in 2005 to develop
Linux Kernel
Git is an open-source distributed version control
system. It is designed to handle minor to major projects
with high speed and efficiency.
It is developed to co-ordinate the work among the
developers. The version control allows us to track and
work together with our team members at the same
workspace.
Organization:
All organizations must be manually created via the web portal. We don't support
automated creation of
Prerequisites:
Create an organization:
1. Sign in to Azure DevOps.
2. Select New
organi
z
ation.
Prerequisites:
Familiarity with forking and cloning a GitHub repo
Account requirements:
An Azure DevOps organization
o To use Microsoft-hosted agents, your Azure DevOps
organization must have access to Microsoft- hosted
parallel jobs. Check your parallel jobs and request a
free grant.
o You can use GitHub Codespaces to complete the
module, even if your Azure DevOps organization
doesn't have any parallel jobs.
A GitHub account
Software requirements:
If using GitHub Codespaces to complete the module,
there are no software requirements as all software is
included in the Codespace
https://github.com/MicrosoftDocs/pipelines-java
Create your first Java pipeline
1. Sign-in to your Azure DevOps organization and go to your project.
6.You might be redirected to GitHub to install the Azure Pipelines app. If so,
select Approve & install.
7.Azure Pipelines will analyze your repository and recommend the Maven
pipeline template.
8.When your new pipeline appears, take a look at the YAML to see what it
does. When you're ready, select Save and run.
If you want to watch your pipeline in action, select the build job.
You just created and ran a pipeline that we automatically created for you,
because your code appeared to be a good match for the Maven template.
10. When you're ready to make changes to your pipeline, select it in the
Pipelines page, and then Edit the azure-pipelines.yml file.
Select a pipeline to manage that pipeline and view the runs. Select the build
number for the last run to view the results of that build, select the branch name to
view the branch for that run, or select the context menu to run the pipeline and
perform other management actions.
You can choose to Retain or Delete a run from the context menu. For more information on run
retention, see Build and release retention policies.
pipeline.
Choose Edit to edit your pipeline. For more information, see YAML pipeline editor.
You can also edit your pipeline by modifying the azure-pipelines.yml file directly
in the repository that hosts the pipeline.
View pipeline run details
From the pipeline run summary you can view the status of your run, both while it
is running and when it is complete.
From the summary pane you can view job and stage details, download artifacts, and
navigate to linked commits, test results, and work Items From the summary pane you
can view job and stage details, download artifacts, and navigate to linked commits, test
results, and work items
steps view, you can review the status and details of eachstep. From the More
actions you can toggle timestamps or view a raw log of all steps in the
pipeline.
Now with the badge Markdown in your clipboard, take the following steps in
GitHub:
1. Go to the list of files and select Readme.md. Select the pencil icon to edit.
4.Notice that the status badge appears in the description of your repository.
Azure-Pipeline
• (https://dev.azure.com/{yourorganization}).
• Choose Edit.
• Make edits to your pipeline using Intellisense and the task assistant for
guidance.
YAML:Code
trigger:
- main
strategy:
matrix:
jdk10_linux:
imageName: "ubuntu-latest"
jdkVersion: "1.10"
jdk11_windows:
imageName: "windows-latest"
jdkVersion: "1.11"
maxParallel: 2
pool:
vmImage: $(imageName)
steps:
- task: Maven@4
inputs:
mavenPomFile: "pom.xml"
mavenOptions: "-Xmx3072m"
javaHomeOption: "JDKVersion"
jdkVersionOption: $(jdkVersion)
jdkArchitectureOption: "x64"
publishJUnitResults: true
testResultsFiles: "**/TEST-*.xml"
goals: "package"
Buildusingmultipleversions