►
Description
With Azure DevOps, you have the option to use only the features you need. For instance you already have your own system for work item tracking or source control, you can still use those along with Azure Pipelines.
In this video, Abel and Jeremy walk us through the first class integration that Azure DevOps has with GitHub. You will learn how to connect your GitHub repo to Azure boards and also see how to create a new Azure Pipeline from the GitHub Marketplace
[01:35] - Linking Azure Boards to GitHub
[03:28] - Referencing a work item in a commit
[06:40] - Create a CI/CD pipeline from GitHub
[09:40] - Inspecting the YAML build definition
Github and Azure Boards - https://docs.microsoft.com/azure/devops/boards/github/index?view=azure-devops&WT.mc_id=ondotnet-c9-cxa
DevOps with ASP.NET. Core and Azure ebook - https://docs.microsoft.com/aspnet/core/azure/devops?WT.mc_id=OnDotNet-c9-cephilli
Start with Azure DevOps for Free: http://dev.azure.com
Create a Free Azure Account: https://aka.ms/c9-azurefree
A
Hey
everyone
Donovan
Brown
here
welcome
to
the
DevOps
for
asp.net
developer
series,
as
your
DevOps
allows
you
to
use
as
much
or
as
little
as
you
like.
Thanks
to
the
numerous
integration
options,
you
don't
have
to
rip
and
replace
what
you
have
today
to
start
using
Azure
DevOps,
for
example.
If
your
code
is
already
in
github,
you
can
leave
it
there
and
start
using
just
the
features
you
need
from
Azure
DevOps.
Let's
see
how
Abel
and
Jeremy
integrate
as
your
DevOps
and
github.
B
Abell
we've
talked
about
a
bunch
of
different
ways
that
we
can
share
or
store
source
code
with
Azure
DevOps
right
and
in
Azure
DevOps.
We
have
options
to
do
distributed
and
non
distributed.
Source
control
right,
but
I
think
what
intrigues
me
the
most
is.
The
ability
to
plug
in
to
other
source
control
repositories
like
github
and
github
is
so
important,
because
so
many
open
source
projects
are
on
github
and
I
understand.
There's
direct
integrations
between
github
and
Azure
DevOps
yeah.
C
We
really
wanted
to
build
a
first-class
experience
between
github
and
Azure
DevOps
so
that
there
really
is
no
type
of
gap
right
if
you're
using
github.
It
should
make
perfect
sense
that
you
want
to
use
Azure
DevOps
as
your
DevOps
tool,
like
very
cool
yeah,
so,
like
I,
said,
first-class
integration
and
the
way
that
we've
done,
that
is,
we've
built
integration
between
Asscher
boards.
The
way
that
we
track
our
work
with
github
and
also
we've
integrated
our
pipelines
are
building
release
pipelines
with
github
as
well.
C
So
let's
go
ahead
and
check
it
out
and
see
what
I'm
get
all
right.
So
on
my
screen
right
now,
what
you
see
is
a
sample
of
an
azure
board.
Right
we've
talked
about
this
as
well.
Inside
of
azure
boards.
You
have
the
ability
to
track
any
unit
of
work
in
your
software
project.
Now
in
github
there
are
issues
right,
Brad
can
track,
but
that's
not
very
powerful
right
if
you're,
just
tracking
issues
that
make
sense.
C
B
C
C
B
C
So
you've
already
created
your
Azure
DevOps
project.
You
have
your
board
and
from
here
you
go
into
your
project,
settings
and
you'll
go
into
underneath
boards.
There's
a
github
connections
and
from
here
we'll
go
ahead
and
click
on
it.
Let's
connect
to
our
github
account
now
I've
already
authenticated
otherwise
you'd
have
to
type
in
your
username
and
password
and
two-factor
authentication
and
all
that
stuff.
And
now
it's
gonna
want
you
to
connect
up
to
your
github
repo,
okay,
here's
a
list
of
all
of
my
repos
we'll
go
ahead
and
just
grab
one
of
them.
C
My
able
tail
in
front
end,
that's
good
enough!
We'll
click
on
save
and
literally
that's
all
you
need
to
do
now
now.
My
asher
board
is
connected
with
that
specific
github
repo
okay.
So
let
me
show
you
what
I
mean,
let's
jump
back
to
our
boards
and
let's
go
into
our
Kanban
board
and
for
this
demo
let
me
go
ahead
and
move
this
over
to
the
side.
C
C
Let's
go
ahead
and
hit
enter
and
then
we'll
go
ahead
and
push
this
back
up
to
github.
Now
the
magic
is
where
I
say,
fixes
a
be
pound
right,
because
by
doing
that,
I
just
saw
a
move,
yes
method
by
doing
that.
It
linked
that
check
in
to
this
particular
work
item.
So
now
any
work
that
you
do
in
github
as
long
as
you
flag
it
with
a
be
pound.
C
Whatever
the
number
is,
it's
gonna
automatically
link
it
to
that
particular
work
item,
including
using
verbs
like
fixes,
which
takes
it
from
an
active
to
a
resolved
State.
Now,
if
we
jump
into
the
work
item
itself,
you'll
be
able
to
see
the
work
that
we
did
is
now
tracked
underneath
development,
and
this,
of
course,
is
a
deep
link
back
into
github.
So
if
I
jump
in
here
and
click
on
it,
it
takes
me
into
github
into
the
work
into
the
the
change
set
and
you
can
see
exactly
what
changes
were
made
Thanks.
C
Let's
say
we
update
my
readme
file
for
some
reason:
let's
go
ahead
and
update
this
really
quickly,
we'll
make
a
change
and
from
here
we
have
to
wait
for
my
screen
to
refresh
and
or
add
something
now,
if
we
come
in
here
check
this
out,
if
I
say
fix
for
demo,
maybe
pound
or
let's
do
a
pound
just
like
that,
all
of
a
sudden,
it's
gonna
start
showing
us
all
of
the
work
items,
that's
already
linked
to
our
Asscher
boards.
Okay,.
B
C
B
C
C
Other
thing
that
I
wanted
to
show
you
as
well
is:
this
is
great
for
tracking
our
work
right,
but
what
about
build
and
release
pipelines
from
github?
How
easy
is
it
for
me
to
create
and
build
and
release
pipeline,
and
the
answer
is
it's
actually
super
easy?
Let
me
jump
back
to
my
repo
again
and
from
my
repo.
What
you
need
to
do
to
create
your
CI
CD
pipelines
and
Azure
pipelines.
Is
you
have
to
install
the
github
marketplace
extension
for
Azure
pipelines
and
that's.
C
Github
so
from
github
right,
let's
go
to
the
marketplace
and
from
github
x'
marketplace
we'll
go
ahead
and
search
for
ash.
Your
pipelines
and
here
we'll
be
able
to
see
the
extension
that
we
need
to
install
now.
I've
already
installed
this
so
we'll
just
go
ahead
and
jump
in
and
configure
it.
But
when
you
configure
it
it's
pretty
simple.
First,
its
gonna
ask
you
for
your
password.
Then
it's
going
to
ask
you
which
repo
do
you
want
to
create
your
pipelines?
C
We'll
just
go
ahead
and
you
can
select
which
repository
you
want,
click
on
save
and
then
it's
going
to
now
redirect
you
and
take
you
back
into
Azure
pipelines
where
you
have
to
login
and
after
you
login
it's
going
to
ask
you
which
subscription
do
you
want
to
use
which
project
you
want
to
use
so
we'll
go
ahead
and
do
that.
So,
while.
B
You're
doing
that,
what's
key
for
people
who
are
running
open
source
projects,
is
we
provide
the
pipeline
service
free?
So
if
I
have
an
open
source,
dotnet
project
on
github
and
I
want
to
automate
my
build
process,
I
can
go
in.
Take
these
steps
and
at
no
extra
cost
to
me.
I've
got
automated
builds.
Yes,.
C
Absolutely
right,
so
even
for
your
open
source
projects,
you
can
have
really
complex,
powerful,
CI,
CD
pipelines
as
well
right.
So
you
select
your
subscription,
so
you
go
ahead
and
select
your
project
we'll
go
ahead
and
click
on
continue,
and
now
it
takes
me
into
my
azure
dev
ops
subscription
and
you
will
be
able
to
see
all
the
repositories
and
from
here
we
can
go
ahead
and
say
you
know
what
for
this,
let's
go
ahead
and
create
my
build
pipeline
for
me.
C
So
the
first
thing
that
it
does
is:
it
goes
and
actually
examines
that
repo
figures
out
what's
in
the
repo
based
on
the
technologies
and
suggests
some
type
of
install
or
some
type
of
built
right
using
a
yamo
build.
So
then
we
can
go
ahead
and
save
this
and
right
for
that
we're
ready
to
go
now.
You
have
your
building
with
these
pipeline
all
set
and.
B
C
C
B
C
I
really
love
yamo
builds
precisely
for
that
reason,
right
so
a
yamo
build.
Is
you
have
your
build
definition,
but
you
describe
it.
You
describe
your
a
build
definition
using
a
gamma
file
and
that
same
yamo
file
is
checked
into
your
source
code,
repo
right
alongside
your
code.
So
now,
you're
Bill
definition
is
versioned
right
alongside
your
code,
which
makes
it
super
powerful,
because
if
somebody
Forks
your
repo
like
you're
saying
or
maybe
clones
your
repo,
not
only
do
they
get
your
source
code.
They're
gonna
get
your.
C
Which
is
nice,
which
is
really
really
nice,
and
not
only
do
they
inherit
your
build
at
that
moment,
it's
the
build
for
that
version
right.
So,
even
if
your
build
definition,
changes
as
time
goes
on
its
version
right
alongside
your
code.
So
as
long
as
you
do
a
get
from
your
repo,
your
build
definition
and
your
source
code,
that's
always
going
to
be
in
sync.
That's.
B
C
All
right,
so
there
you
go
right:
super
powerful
integration
between
github
and
Azure
DevOps,
so,
like
I,
said
before,
what
we
wanted
to
make
sure
is,
even
if
you're,
using
github
for
your
open
source
projects
or
your
social
projects.
We
want
to
give
you
first-class
DevOps
tools
by
using
Azure
DevOps.
That's.
B
Awesome
and
speaking
of
Azure
DevOps,
this
has
been
a
multi-part
series.
We've
sat
here
and
gone
through
all
phases
of
azure,
DevOps
I
just
want
to
say
for
dotnet
developers.
Abel
said
it
before:
there's
no
excuse
not
to
have
continuous
integration,
continuous
deployment,
all
of
the
tools
are
available
straightforward
and
easy,
and
we
hope
that
this
series
has
not
only
introduced
you
to
what's
available
and
what
you're
capable
of
doing,
but
also
has
made
it
easy
to,
regardless
of
whether
you're
looking
at
source
control.
Automated
builds
testing
unit
testing,
we
had
release
pipelines.