►
From YouTube: S206 - Azure DevOps for .NET Teams - Martin Woodward
Description
DevOps is about people, process, and products. Getting it all right requires effort, but the benefits to your organization and customers can be huge. It's also important to know that you don't have to get everything right straight away, DevOps is about continually getting better in delivering value to your customers. Microsoft has a fantastic set of products that can help you get the most out of the cloud and help in deploying .NET to any platform. In this demo-heavy session, Martin shows you how to go from "zero to DevOps" and help you see how to begin the transformation of your team.
A
Hey
everybody
Martin
Woodward
here
today,
I'm
going
to
talk
to
you
about
dotnet
DevOps,
so
how
to
do
DevOps
with
dotnet.
My
name
is
Martin
Woodward
at
Martin
Woodward
on
Twitter.
If
you
want
to
send
some
questions
through
and
obviously
use
the
hashtag
dotnet
Kampf
I
work
on
the
azure
DevOps
team,
the
newly
announced
as
a
DevOps
team
and
I'm
going
to
go
through
some
stuff
today.
So
let's
get
started
right
then.
What
do
we
think
DevOps?
Is
it's
useful
to
level
set
on
this?
A
First
of
all,
DevOps
is
not
a
product;
DevOps
isn't
technology
DevOps
is
the
whole
process
is
about
people
process
and
products,
allowing
you
to
give
continuous
delivery
of
value
to
your
end-users,
the
people
and
the
process
right
there,
the
hard
bit
the
people
are
always
the
hard
bit,
especially
when
you're
trying
to
drive
culture
change
in
your
organization
bringing
process
in
to
support
those
people
is
also
you
know
what
you
need
to
do
and
then
the
tools
to
support
support
the
processes.
Now
we
have
tools,
you
can
get
tools
open
source.
A
You
get
tools
from
other
people,
it's
about
that
continual
flow
of
value.
We
find
that
teams
that
are
doing
DevOps
are
actually
delivering
quicker
delivering
faster.
So
if
we
look
in
the
market,
there's
a
the
state
of
DevOps
report,
that's
just
out
now.
If
we
look
at
that,
we
actually
see
around
about
a
forty
six
times
quicker
deployment.
You
look
at
the
Stack
Overflow
survey
from
2017-2018.
A
You
actually
see
that
developers
who
ship
more
a
happier-
and
it
makes
sense
really.
You
know
if
you're
shipping,
frequently
to
your
to
your
customers,
you're
getting
live
feedback
from
your
customers.
Then
you're
gonna
be
a
lot
happier
of
your
results.
You
know,
you're
gonna
know
that
what
you're
doing
is
the
right
thing
to
do
in
it.
You
need
to
get
your
team's.
A
You
need
to
try
and
remove
all
these
obstacles
and
get
them
shipping
quickly
and
get
them
shipping
to
your
customers
and
making
sure
you
can
then
learn
from
your
customers
as
to
what
happens
and
if
it's
good
or
not
have
you
made
it
better
or
worse.
The
key
thing
that
DevOps
is
to
be
doing
incremental
changes
the
whole
time
slowly
and
iteratively
improving
or
quickly,
and
it's
really
improving
really
so,
when
you're
trying
to
learn
and
improve
and
deploy
quicker
and
learn
quickly
from
your
your
customers.
A
What
sort
of
the
key
technologies
you
need
to
be
on
the
lookout
for
to
help
you
do
that?
It's
no
good!
Just
you
know
having
your
application,
pressing
f5
from
Visual
Studio
and
then
it'd
be
a
real,
complex
process
to
get
what
you've
built
out
into
the
hands
of
your
customers.
It.You
know
that
the
harder
it
is
to
do
that
then
the
the
least
often
you
do
it
and
the
longer
it
takes,
and
that
slows
down
the
flow
of
value
to
your
customers,
so
some
key
technologies
to
look
out
for
around
continuous
integration.
A
Hopefully
most
people
are
doing
this
now
continuous
integration
with
say,
Jenkins
or
with
Azure
pipelines
or
wave
team
city.
You
know
any
kind
of
CI
build
server
or
really
help
you
do
your
builds
automatically
and
make
sure
your
builds
are
of
high
quality
all
the
time.
We
then
have
continuous
deployments,
so
that's
being
able
to
take
what
built
did
it
work?
Is
it
good
and
actually
take
that
package
and
ship
it
to
your
end-users?
A
Now
that's
easy
easy
when
you're
doing
it
when
you're
shipping
to
the
cloud
when
you
just
you
know
deploying
web
apps
and
things
like
that.
We'll
talk
a
little
bit
today
about
how
to
do
continuous
deployment.
We
have
desktop
applications
as
well
and
then,
finally,
it's
no
good
having
all
this
stuff
helping
you
ship
faster
if
you're,
not
learning
at
the
same
time,
if
you're
constantly
just
shipping
quicker
constantly
just
you
know
shipping
fast
to
your
customers.
A
How
do
you
know
if
it's
better
or
worse
or
not,
if
you're
not
looking
and
monitoring,
and
seeing
what
they're
doing
and
seeing
if
you're,
making
it
better
or
worse,
you
might
just
go
off
in
the
wrong
direction,
a
lot
quicker.
So
it's
very
important
that
you
build
monitoring
in
and
build
learning
into
your
DevOps
pipelines
early
on,
so
you
can
tell
have
I
made
this
better
or
worse
are
users
using
my
software
easier?
Are
they
are
they
deploying
quicker?
Are
they
able
to
make
the
changes
they
need
to
do?
A
Are
they
able
to
find
the
functionality?
Are
they
running
into
any
errors,
those
sorts
of
things
and
being
able
to
get
confidence
by
what
your
users
are
doing
in
production?
That
allows
you
to
then
move
on
to
do
anything
like
testing
in
production
and
being
able
to
have
real
users,
use
your
system
for
real
and
actually
get
them.
You
know:
get
live
data
from
real
usage
on
your
customers.
A
Now
on
Tuesday
well,
Monday
we
announced
on
the
blog
post,
but
then
Tuesday
in
the
studio.
Here
we
had
a
live
stream
talking
all
about
the
new
Azure
devops
services.
So
what
we've
done,
if
you,
if
you're
a
V,
STS
customer
if
you're
familiar
with
VSS
we've
taken
the
core
functionality
within
that
and
we've
broken
it
into
a
set
of
services
and
they
complement
the
existing
services
in
Azure
to
help
you
do
DevOps
with
your
teams.
A
So
we've
got
as
your
boards,
which
helps
you
do
planning
pipelines
for
build
and
release
repos
for
doing
source
control,
test
plans
and
artifacts.
So
we've
taken
one
service
and
we've
taken
it
up
and
we've
broken
up
into
five
services
called
as
your
pipelines
as
your
boards
as
your
repos,
and
they
complement
the
existing
other
services
that
are
out
there
today.
If
we
take
a
look
getting
started
with
a
continuous
integration,
continuous
deployment
process,
there's
actually
a
cool
little
feature
built
straight
into
the
azure
portal
called
Azure
DevOps
projects.
A
You
can
very
very
quickly
and
easily
come
in
and
set
up
a
full
end-to-end
pipeline
that
uses
the
azure
devops
services
and
plumbs
them
all
together
for
you
and
gives
you
a
skeleton,
and
then
you
can
take
that
and
customize
it.
So
let's
have
a
quick
play
and
show
you
how
that
works.
It's
really
easy
to
get
started
so
I'm
going
to
come
in
here
and
just
go
to
the
azure
portal
and
Here
I
am
and
u
s--
noticed.
You've
got
DevOps
projects,
I've
got
it
pinned
to
the
top,
because
I
do
this
a
lot.
A
A
There
we
go
let's
clear
some
subscriptions
out
here
and
then
we
go
I'm
gonna
load
this
up
and
I'm
going
to
quickly
create
a
new
DevOps
project
and
then
within
my
DevOps
project,
I'm
going
to
say
what
do
I
want
to
do
I'm
here
at
dotnet
of
comp,
so
you
know
don't
need
to
do
any
of
this
stuff.
Any
of
those
Python
go
and
all
that
I'm
gonna
go
with
dotnet.
That's
the
way
to
go.
A
That's
the
only
true
way,
so
we're
gonna
come
in
and
then
say
what
type
of
dotnet
application
we
want
to
do.
I
want
to
try
out
if
I'm
gonna
do
all
this
DevOps,
goodness
I'm
gonna
go
with
a
fancy,
shiny,
brand-new
asp.net,
core
application,
but
you
know
I
want
a
real
one:
I,
don't
just
want
a
hello
world,
so
I
actually
want
a
sequel
database
back-end
that
I'm
gonna
do
some
real
work
with
get
that
all
set
up
for
me
and
do
the
hard
work
of
plumbing
the
database.
A
You
know
doing
all
the
deployment
scripts
that
sort
of
thing
hit
next
and
then.
Finally,
how
do
you
want
to
deploy
it?
So
do
you
want
to
do
a
web
app?
Do
you
want
to
do
a
VM
in
the
future?
There'll
be
more
options
here
around
you
know,
docker
izing
deploying
it
to
aks
that
sort
of
thing,
so
I'm
gonna
just
her
as
a
web
app
and
then
I'm
going
to
use
an
existing
as
your
DevOps
subscription
so
being
on.
A
This
is
this
is
really
handy,
so
I'm
going
to
come
up
here
and
I'm
going
to
go,
deploy
it
to
West
Europe,
because
that
happens
to
be
close
to
where
I
live
normally
and
then
just
tell
everyone,
I'm
gonna
hit
done
and
that's
going
to
do
all
the
hard
work
now
of
getting
a
basic
project
set
up
setting
up
a
simple
C
icd
pipeline
for
you
actually
creating
all
the
resources,
energy.
You
need
to
be
able
to
deploy
it
to
so
in
Asia
where
that
site.
A
You
know
as
a
sequel
database
and
then
get
the
application,
build
it
deploy
it
and
have
you
a
skeleton
application
to
run
to
so.
While
that's
running
it's
going
to
give
me
a
little
notification
people
who
are
following
the
live
stream.
If
they
want
to
try,
you
know:
pinging
Netcom
18,
your
website's
net,
it'll
it'll,
be
there
eventually
it'll
start
to
pop
up,
but
while
we're
waiting
for
it
to
appear,
you
can
see
here
it's
the
deployment
starting
for
me.
A
Well,
this
is
all
waiting,
I'm
gonna
jump
over
and
show
you
what
an
existing
one
looks
like
when
it's
created.
So
if
I
come
in
and
I
just
look
at
this
dotnet
core
one
I
did
last
night,
we
can
see
it's
currently
running.
We
can
see
my
CI
CD
pipeline,
so
the
code
we
can
see
the
bill,
that's
that
last
succeeded
and
the
last
deployment
into
the
dev
environment
and
then
we're
to
go.
Look
at
that
application.
A
So
if
you
wanted
to
go
look
at
this
live,
you
know
you
can
just
come
in
here
and
browse
the
application
and
you
can
see
it'll
say
hello
world
once
it
comes
up
and
you
just
hammer
that
there
we
go
the
power
of
the
cloud
and
then,
if
I
come
in
here,
we
can
actually
go
look
at
the
code
that
it's
part
of
this.
So
let's
just
do
that.
Let's
just
go
straight
in
and
jump
into
the
code.
A
This
is
stored
in
my
azure
dev
ops
account
in
my
in
Azure
repos,
so
I'm
going
to
come
in
and
I'm
going
to
do
dotnet
core
project,
and
this
is
what
the
new
looking
for
your
haunts
have
logged
in.
This
is
what
the
new
look
and
feel
is
like
for
Azure
DevOps
services.
Now
so
you
see
you've
got
you
know,
it
all
looks
shiny.
It's
a
lot
faster.
It
looks
very
different
to
the
old
VST
s
and
what's
also
quite
interesting,
is
these
services
here
you
don't
have
to
have
all
these
ons.
A
So
if
you're
using
say
JIRA
with
you,
know
github,
but
you
using
as
your
pipelines
to
do
deployment
you
can
just
have
as
your
pipelines
enabled
you
know,
you
don't
need
to
confuse
people
with
all
this
functionality.
You
don't
use.
So
if
I
come
in
and
do
my
project
settings,
you
know
maybe,
for
this
particular
one
not
using
I'm,
not
using
my
artifact
service
I'm,
not
using
the
test
plan
service,
but
I
do
want
boards,
repos
and
pipelines.
So
I
can
just
switch
those
off
there.
A
Go
back
to
my
project
and
it'll
show
you
it'll
it'll
just
see
you
know
the
things
that
I
want
to
see
and
not
show
you
anything.
That's
going
to
confuse
people
and
one
of
the
things
we've
done
with
Azure
DevOps
is
actually
taken.
The
individual
services
that
you
might
be
using
and
make
them
a
lot
more
pluggable.
A
lot
more.
You
know
configurable.
A
So
if
I
show
you
the
code,
that's
currently
here,
you
know:
we've
got,
we've
got
boards,
which
is
the
work
tracking
system
and
I
can
quickly
come
in
and
just
create
a
new
work
item,
I'm
going
to
say,
create
a
bug
and
if
I
look
at
this
website,
you
know
HelloWorld
is
no
good.
I
want
to
come
in
and
say
you
know
this
is
dotnet
Kampf.
A
You
know
we
want
to
be
saying
hello
to
the
world
net
Kampf,
so
we'll
come
in
here
yet
create
a
new
work
item
say
this
is
dot
net
comp,
that's
book
173!
If
we
wanted
to,
we
could
come
and
plan
that
work
out
in
our
backlogs.
We
can
use
our
odd
job
dashboards
to
try
and
take
that
work
and
create
new
tasks,
and
you
know,
update
homepage
is
a
story.
We
can
make
that
story
there
and
we'll
say.
Actually.
No,
it's
active
and
I
can
use
my
my
finger
mice.
A
My
screen
and
I
actually
move
these
cards
around,
live
on
the
screen
as
well,
and
do
all
that
sort
of
thing.
So
there
we
go
move
that
around
there
to
resolved,
but
it's
not
yet
I'm
going
to
make
it
active.
So
you've
got
Kanban
boards,
work,
item
tracking
and
look
over
here
in
source
code.
This
is
a
source
code
that
was
created
when
I
created
an
azure
devops
project
and
we
can
see
there's
a
straightforward
application
in
here
with
a
database
project,
a
website,
a
web
app
and
some
unit
tests
and
some
functional
tests.
A
If
I
go
into
the
main
application
and
then
let's
just
go
look
at
let's
take
the
main
view
and
we'll
go
to
the
home
page
and
index.html.
If
you're
looking
around
you
notice,
I
can
actually
now
hide
these.
You
know
the
nav
bar
if
I've
got
a
limited
screen
space
like
I.
Do
when
I'm
presenting
you
know
I'm
showing
you
it
in
big
screen,
so
it's
limited
and
I
can
come
in
and
if
I
wanted
to
I,
don't
even
need
to
clone
this
source
code
down
and
edit
it
inside
a
visual
studio.
A
I
can
actually
come
in
here
and
live
edit
in
master
I.
Wouldn't
particularly
advise
this
I
can
just
come
in
here,
live
at
it
and
say
hello,
dr.
Khan,
exclamation
mark
awesome
and
I'm
gonna
commit
that
change
directly
into
master
I'm
gonna
associate
it
with
my
work
item.
I
was
just
on.
This
is
done
at
comp
and
I'm
gonna
commit
that,
and
it's
going
to
make
that
change.
Now
now
I've
made
that
change
in
my
application.
A
If
I
go
over
and
look
into
my
builds,
I
can
actually
see
already
a
CIA
build,
has
been
configured
for
me
and
is
already
running
and
executing
to
run
that
build
in
the
cloud.
Microsoft
have
cloud-hosted
build
service
for
you
that
you
can
use
and
you
can
have
them
work
on
Mac,
Linux
and
Windows
builds
all
in
the
cloud.
You
get
8
1,800
minutes
of
bill
minutes
for
free
for
a
team
of
five.
If
you're
doing
open
source,
she
actually
get
unlimited,
build
minutes
to
be
able
to
do
your
application.
So
it's
pretty
awesome.
A
It's
a
question
here
from
Raymond
Dillon
is
asking
hey
Raymond
nice
to
see
you.
Can
I
integrate
azure
devops
with
Microsoft
teams
to
get
notifications
of
build?
Yes?
Actually,
if
you
go
into
the
team's
marketplace,
there
is
an
extension
for
Azure
DevOps
to
go,
integrate
that
into
teams
and
into
your
team.
Channel
I'll
see
if
I
get
a
chance
to
show
you
that
in
a
bit
I'm
a
bit
worried
what
will
pop
up
because
I
don't
have
don't
have
a
demo
channel
kicking
around
so
but
yeah.
A
That
definitely
is
there
and
we
use
that
all
the
time.
So
thanks
thanks
Raymond
good
to
join
us
on
on
live
stream
today,
so
we've
come
in
here
and
then
where
was
it
yeah
we'd?
So
we're
watching
the
bill?
That's
happening
and
the
build
is
just
coming
along
here
and
you
can
actually
see
it.
Running
live
if
I
was
looking
at
this
from
the
azure
portal.
A
So
if
I'm
a
you
know,
not
a
dev
but
I
may
be
on,
you
know
the
ops
side
of
the
same
team
I
can
come
in
and
I
can
hit
refresh
I'm
gonna
just
refresh
the
portal.
It
does
update,
live
as
we
come
in,
but
let's
just
see
if
we
see
it
running-
and
we
now
should
be
able
to
see
here
once
it
refreshes
for
us
yep,
it's
currently
running
a
build.
The
current
builds
in
progress
and
then
it's
going
to
be
deploying
to
dev
in
a
minute.
A
So
Jonnie
has
asked
the
question:
azure
devops
sounds
more
like
azure
devops,
only
no
multi-cloud
projects,
so
why
are
they
stay
mning?
That's
a
great
question
and
one
I've
seen
on
the
on
Beth's
net
comp
hash
tag.
Quite
a
lot
lately
so
feel
free
to
mention
that
on
me,
rather
than
the
Beth,
because
it's
probably
my
fault,
but
it's
called
this
name
not
best.
So
the
it's
a
suite
of
services
like
as
your
repos
and
Azure
pipelines,
or
a
suite
to
services
to
help
you
do
it
that
are
in
Asia
Asia
is
completely
multi-cloud.
Today.
A
If
you
want
to
use
you
know,
monitoring
as
your
application
insights
and
use
that
to
actually
monitor
an
application,
that's
in
any
cloud
or
on
Prem,
you
know,
so
you
can
monitor
your
on-prem
resources.
You
can
monitor
resources
in
AWS
TCP
if
you
want
to,
and
you
can
monitor
them
already
inside
of
azure
at
the
azure
devops
services
are
exactly
the
same
and
it's
a
great
question,
actually
one
that
is
worth
pointing
out
to
people,
but
it's
not
just
for
Asha.
It's
not
just
to
deploy
projects
to
Azure.
A
So
if
I,
if
I
wanted
to,
if
I
go
back
to
my
project,
it's
currently
building
I'm,
just
going
to
open
up
a
new
tab
if
I
was
to
create
a
new
release,
that's
just
to
a
new
build
just
to
show
you
some
of
the
power
here.
If
I
come
in
and
I'm
going
to
do,
new
bill
pipeline
and
I'm
gonna
say:
where
do
I
want
to
pull
the
code
from
repos
or
github
all
that
sort
of
stuff?
A
You
know
you
see
it's
instantly
a
lot
more
pluggable,
so
you
can
plug
into
whatever
provider
you
want
and
right
now
we
don't
have
it
available
for
you.
But
if
you
want
to
talk
to
subversion,
you
want
to
talk
to
bitbucket.
You
want
to
talk
to
get
lab.
You
can
just
go
and
do
that
as
it
is.
But
what
I
wanted
to
show
was
actually,
if
I
could
do
it
as
a
release.
That
would
be
quicker.
A
I'll
leave
this
page
here
and
I'm
going
to
come
in
I'm
just
going
to
create
a
new
release
pipeline
and
I'm
gonna
just
say
start
with
an
empty
empty
table,
okay,
cool
and
then,
if
I,
look
at
the
tasks
that
are
available
to
me,
so
I'm
gonna,
say
I
want
to
add
a
task
you
can
come
in
and
if
I
type
AWS,
for
example,
I
can
come
here
and
deploy
my
dotnet
workloads
to
AWS
I
can
do
the
same
with
Google
with
TCP.
You
can
deploy
anywhere
if
I
want
to
deploy
on
premise.
A
I
just
want
to
run
a
shell
script,
for
example.
You
can
also
do
that.
So
we'll
talk
more
about
that.
In
a
little
bit
so
Ash's
multi-cloud
aja
is
hybrid
cloud
of
the
holo-badges,
so
hence
the
name
I
know
a
few
people,
especially
Visual
Studio.
You
is
who
were
like.
Well,
you
know,
I'm
an
I'm,
an
AWS
dev
like
this
seems
weird
to
me.
Azure
is
multi-cloud.
All
of
it
is
so
I,
don't
you
know
it
isn't
weird.
We
have
a
lot
of
customers
that
also
have
innovated
Java
developers
or
Linux.
A
A
sad
min
and
a
product
called
visual
studio
team
services
to
those
people
wasn't
particularly
welcoming
either.
So
it's
the
trade-off
on,
but
on
both
sides
of
the
house.
But
it's
the
service
that
completely
runs
in
Asia.
It's
a
service,
that's
integrated
with
all
the
azure
services
for
doing
operations
and
management.
So
it
makes
sense
so
hopefully
that
that
answers
the
question
but
feel
free
to
shout
at
me
at
smart
in
Woodward.
A
If
you,
if
you
disagree
strongly-
and
we
can
have
a
discussion
on
Twitter
after
this
okay,
so
away
from
the
naming
controversy
if
I
come
in
and
I,
look
that
actually
that
build
is
currently
in
progress.
So
I'm
just
going
to
jump
back
in
here
again
and
actually
see
where
we
are
yep.
So
it's
now
finished
and
if
I
look
at
my
release,
pipelines
I
should
hopefully
see
a
new
release
is
being
configured
while
I
was
talking
about
yet
there
we
go
about
naming
so
there.
A
The
dev
release
is
currently
deploying,
and
we
see
we've
got
other
releases
here
that
have
come
in
and,
and
you
know
been
deployed
previously,
so
we
can
go
look
at
our
previous
versions,
but
we're
currently
looking
at
that
release.
That's
deploying
into
production.
If
I
look
at
that
release
here
and
actually
show
I'm
currently
running
four
out
of
eight
tasks,
I
mean
I
did
that
drop.
So
if
I
go
back
to
that
drop
and
actually
see
what
what
was
I
building.
This
is
the
thing
that
I
built
so
I.
A
All
my
unit
tests
passed
I
had
a
whopping
three
unit
tests.
All
my
code
coverage
was
done
all
that
sort
of
thing
and
you
notice
there
was
only
one
change
associated
with
this
build
so
you're
getting
end-to-end
traceability
between
what's
deploying
what's
deployed,
and
then
what
actually
is
in
that
new
deployment?
And
then,
if
we
look,
we
can
see
that
it
was
associated
with
bug
173.
A
So
not
only
are
you
seeing
what's
deployed
where
to
which
environment,
what
changes
are
in
that
environment,
but
also
why
you
know
why
was
that
change
put
into
production
so
I'm,
hoping
now
if
I
go
back
into
my
releases?
Just
have
a
quick
look
here
from
that.
It
is
currently
still
in
employment,
so
there
we
go
and
if
you
want
to
go,
live
to
doc,
petticord
or
as
your
Webster
core.
Sorry
to
add
your
websites,
dotnet
I'm,
hoping
we're
gonna
get
a
we're.
Gonna
get
a
new
website
coming
up
here
soon.
A
This
is
quite
cool
and
we
can
use
that
app
in
sites
he's
built
in
to
our
DevOps
portal
for
us
as
well.
So
we
can
actually
see
how
many
people
are
live
hitting
this
so
go
on.
Everybody
on
the
livestream
hit
dotnet
core
to
dodge
your
websites
net.
Give
that
a
try
for
me
and
then
we'll
actually
look
here
and
we'll
watch
the
server
requests.
You
know
peek
up
and
down,
and
that's
traffic.
That's
coming
now
off
a
live
stream,
which
is
pretty
awesome
thanks
for
doing
that.
A
That's
so
cool
right,
so
it's
currently
doing
a
release.
Still,
let's
come
in
here,
I'm
gonna
hit
refresh
just
to
check
and
I'm
gonna
come
over
here
and
see
how
this
release
is
going.
How
long
we
got
left
to
go,
we're
gonna,
we're
maybe
come
back
for
this.
It's
currently
been
doing
it
for
two
minutes,
which
seems
pretty
slow,
but
we'll
see
what
happens.
Oh
there
we
go
if
I
come
back,
it's
just
a
quick
refresh,
see
what
happens
so.
A
Seven
eighths
asks
testing
always
do
been
doing
the
testing.
Now
that's
awesome,
but
you
can
see
it's
already
updated.
It's
already
deployed
the
website.
Now
it's
running
all
the
unit
tests
against
it,
which
is
pretty
cool,
so
there
we
go
and
if
we
have
a
look,
how
many
people
have
seen
that
that's
happening?
Well,
quite
a
few!
No
failed
requests
yet
awesome,
it's
all
working
perfect.
So
that's
that
there
watch
this
come
through
and
wait
wait
for
it
to
finish
right.
Well,
that's
finishing
off!
A
Should
we
see
if,
let's
see,
if
they're
over
DevOps
project,
we
created
the
I'm
gonna
just
come
in
and
go
up
to
my
home
page
and
I'm
gonna,
say
dotnet
comp
18
there
we
go
so
there's
the
dotnet
Kampf
18
pipeline
that
I
created
earlier
for
me
and
we
actually
see
the
same
sort
of
files.
We
can
see
it's
created
the
builds
and
the
releases
just
to
quickly
show
you
what
the
build
is
that
it
creates
I'm,
not
gonna,
dwell
on
this
too
much.
But
if
I
come
in
here
and
I
edit
the
build
definition.
A
This
is
the
default
one,
but
you
can
learn
a
lot
from
this.
It's
you
know
basic.net
core
stuff.
So
do
a
dollar
you
know
donate,
restore,
don't
let
build
on
a
test
on
it.
Publish
do
some
arm
stuff
copy
the
database
files
over
that's
what
it's
actually
doing
is
looking
for
any
sequel,
scripts
copying
them
over
and
then
putting
them
into
a
drop
location.
A
A
So
it's
going
to
run
all
that
stuff
to
actually
deploy
out
to
Azure,
but
then,
if
I
wanted
to
come
in
and
make
it
so
as
well
as
doing
maybe
not
just
a
CI
trigger,
maybe
I
wanted
to
add
a
new
artifact.
So
rather
than
listening
to
builds
happening,
it
was
maybe
listening
to
a
Jenkins
build
happening,
or
maybe
it's
listening
to
a
github
action
occurring.
You
know
you
can
configure
all
these
things.
A
Maybe
when
something
arrives
in
your
a
K
in
your
Azure
container
registry
or
your
docker
hub
then
actually
go
deploy
it
and
push
it
out
into
production.
So
it's
very
flexible,
very
pluggable,
but
I
might
well
also
can
come
in
here
and
say
on
a
schedule.
Do
nightly
deployments
do
weekly.
You
know
daily
deployments:
whatever
you
want
to
do.
You've
got
all
that
configuration.
We
then
have
the
Deb
environment
if
I
wanted
to
clone
this
environment
and
now
create
a
production
environment.
I
can
just
come
in
and
do
that
so
prod
or
whatever
or
staging.
A
We
can
call
it
and
then
I
can
customize
my
tasks
to
do
what
I
want
to
do.
I
can
set
properties,
which
is
what
you
normally
do
to
actually
define
your
properties
between.
You
know,
staging
and
production.
What's
different
and
I
can
actually
come
in
here
and
set
a
pre
deployment
condition,
so
I
won't
deploy
into
production,
and
so
maybe
I've
got
an
approver
from.
Maybe
you
know,
I've
approved
it
or
I'll
do
it.
I
can
have
it.
So
that's
the
approvers
I
just
wish
that
often
you
see
a
bit
better.
A
I
can
have
what's
called
a
release
gate
so
I
can
have
it
delay
the
deployment
by
five
minutes.
You
know
so
don't
deploy
directly
to
production,
leave
it
in
one
environment.
First,
let
it
settle
make
sure
it's!
Okay
and
no
no
fire
alarms
have
gone
off.
No
screaming's
happened
on
twitter
and
then
deploy
it
to
the
next
environment,
but
what
I
might
want
to
do
actually
is
say
hook
it
up
to
work
items,
don't
allow
me
to
deploy
into
production
if
somebody
has
created
a
defect,
a
burg
or
a
work
item
recently.
A
Don't
allow
me
to
deploy
into
production
if,
as
your
application
insights
is
telling
me,
production
isn't
healthy,
those
things
are
build
up
a
box.
You
can
just
invoke
any
random
as
your
function
and
one
of
my
buddies
actually
wrote
it
as
a
function
which
looks
at
Twitter
sentiment
analysis,
and
it
can
tell
you
know
if
your
Twitter
sentiment
is
good
or
bad
and
using
magic,
cognitive
services
and
doesn't
do
a
production
deploy
if
the
Twitter
sentiment
was
bad,
for
example.
A
So
you
know
if
we
had
a
the
config
change
to
do
the
rename
and
the
Twitter
sentiment
was
low
and
it
wouldn't
allow
the
production
in
it
wouldn't
allow
it
into
the
next
ring,
which
is
quite
cool
right,
so
I'm,
just
gonna
leave
that
and
I'll
bother
saving
it
okay,
so
there
we
go
and
then
yep
that's
good
right.
I
signal
for
that
sort
of
stuff:
let's
jump
back
in
I.
Just
answer
a
couple
of
quick
questions.
Now,
while
I
can,
if
we
I'm
switching
back
into
slides,
excuse
me
so
calm
pronounce
the
handles.
A
Sorry,
it's
LIC
j,
AP,
OD
ACA
has
asked
how
easy
is
it
to
migrate
from
TFS,
though
the
on-premises
version
of
azure
dev
ups
out
into
the
cloud
as
a
DevOps
services,
we
have
a
service
to
help.
You
do
that
it.
Actually
you
can
do
it
with
full
fidelity.
Migration
go
from
your
on-prem
instance
to
the
cloud
and
that
works
it.
You
know
you
need
to
be
on
a
recent
issue
of
TFS
to
be
able
to
do
that
migration.
A
You
can't
go
straight
from,
say:
TFS
2013,
all
the
way
into
the
latest
Azure
DevOps,
because
what
it's
doing
is
it
actually
takes
a
copy
of
your
TFS.
Your
on-prem
database
pushes
it
up
into
the
cloud
and
then
hooks
up
into
a
new
into
an
Asscher
devops
organization.
So
it
is
good.
You
wanted
practice.
Do
a
couple
of
test
runs
first,
and
you
also
need
to
do
your
TFS
upgrade
first
and
Vanessa's
asked
we
setup
manual
test
bans
in
cases
so
great
question
with
actually
he's
talking
about
Azure
DevOps
and
to
DevOps
services.
A
A
However,
load
testing
doesn't
come
as
part
of
the
standard
account.
So
if
I'm
just
going
to
quickly
jump
over
here,
for
you
sure
comm
whack
DevOps,
so
that's
how
you
go
and
learn
more
about
agile
devops.
If
I
go
into
the
pricing
page,
you
can
see
for
free,
you
get
the
standard
services,
the
pipeline's
board
repos
for
for
up
to
five
users,
and
then
you
can
pay
per
user.
It's
around
about
six
books,
a
user
you
pay,
but
then,
if
I
want
I
can
add
additional
parallel
build
job.
A
So
I
can
I
can
have
like
you
know.
Ten
or
five
builds
happening
at
the
same
time,
if
a
one
so
I
can
pay
for
those.
You
can
also
pay
an
additional
fifty
two
books
to
get
the
test
plan
infrastructure
so
and
gives
vinash.
If
you
want
test
buns,
you
actually
have
to
pay
additional
for
that,
and
then
it
becomes
available
into
your
account.
If
you
have
a
Visual
Studio
Enterprise
subscription,
then
that
comes
with
a
free
license
for
as
your
test
plans
and
as
your
artifacts
as
well
right.
A
Sorry,
I'm,
gonna,
jump
back
into
slides
again
and
I'll
answer
some
more
questions
in
a
sec
right
then,
when
you're
trying
to
do
DevOps
in
your
team's
DevOps
remembers
about
continuously
improving
continuously
getting
better
and
removing
those
impediments
delivering
the
flow
value
to
your
team's.
What
you
want
to
do
is
figure
out
where
your
biggest
pain
is
is
the
biggest
pain
right
now
in
your
process
that
nobody
knows
what
we're
supposed
to
be
delivering.
A
You
know,
I
have
no
idea
like
what
the
current
single
you
know
of
current
sort
of
point
of
truth
is
in
terms
of
what
features
the
developers
should
be
building.
Is
your
problem
work
prioritization?
If
it
is,
then
planning
and
tracking
is
kind
of
where
you
want
to
be
focusing,
you
know
if
the
problems
are
around
your
development
processes.
A
Often,
today
you
know
people
are
getting
more
sophisticated
as
time
goes
on
when
I
first
started
doing
this
sort
of
thing,
source
control
was
either
saw
safe
or
just
copying
zip
files
around.
You
know
it's
got
a
lot
better.
Most
people
are
using
source
control.
Now,
thankfully,
90%
of
people
are
using
git
as
well,
so
build
and
test
is
an
area
where
people
have
started
to
do
investments,
and
you
know
they're
doing
continuous
integration.
Continuous
integration
is
not
DevOps.
Devops
is
the
whole
process.
A
Bringing
your
team
close
together
and
focusing
on
the
flow
of
value
to
your
end
customers.
It's
not
just
builds
ok,
so,
but
people
often
forget
that
and
just
focus
on
CI
CD.
We
call
that
Asia
pipelines.
That's
the
feature
that
provides
this
part
so
mate.
What's
most
common
and
I
see
when
I'm
talking
to
most
customers
is
actually
deployment
getting
bits
into
production.
A
That's
a
scary
thing
that
requires
you
know
somebody
who
knows
how
to
like
get
on
to
the
live
boxes
or
knows
how
to
get
things
done
or
maybe,
if
you're
doing
a
desktop
application.
You
know
it's
a
massive
process
that
requires
years
to
get
you
users
to
upgrade
like
deployment
is
frequently
where
I
see
today,
most
people
having
lots
of
lag
time
and
issues,
and
so
that's
an
area
where
we've
invested
heavily
with
the
Azure
pipeline
service
to
actually
come
in
and
be
able
to
sort
of
help.
A
Some
of
those
things
running
your
servers,
you
know
getting
things.
Actually
all
your
servers
up
and
running.
Do
they
go
down
or
a
time
have
you
got
the
monitoring
in
place?
Do
you
know
what's
what's
good?
What's
bad,
that
is
that
the
main
problem
that's
happening
for
you
right
now
and
then,
finally,
as
I
say,
do
you
know
if
you've
made
it
your
changes
have
made
it
better
or
worse.
A
All
too
often
I
talk
to
teams,
and
they
talk
about
this
amazing
new
feature
they've
deployed
into
production,
but
what
they're
not
doing
is
you
know
how
many
people
are
using
it?
How
many
people
are
having
success?
Taking
that
feature
you
think's
awesome
and
getting
it
and
actually
making
use
of
it.
People
aren't
using
it.
If
people
don't
understand
your
UI,
it's
a
bit
like
a
joke.
If
you
have
to
explain
the
joke,
then
it
doesn't
work.
If
you
have
to
explain
your
system
to
people,
it
doesn't
work,
you
know
it's
not
working.
So
we'll.
A
Actually
look
at
usage
and
monitor
usage
to
see
is
this:
is
this
application
being
successful
for
our
customers?
How
quickly
are
they
able
to
do
the
activity?
What's
their
what's
their
phone
or
what's
their
drop-off
rate?
How
often
do
they
start
doing
something
and
fail?
You
know
and
try
and
improve
those
all
the
time
and
then
loop
and
just
constantly
be
unblocking
little
things
and
don't
think.
A
Oh,
no
I
can't
start
doing
DevOps,
because
I
need
to
do
some
massive
deployment
process
and
I
need
to
go
into
kubernetes
and
I
need
to
do
micro
services
and
blah
blah
blah
all
the
buzzwords.
No
just
do
a
little
bit
of
DevOps
like
automate.
Your
builds
automate
a
little
bit
of
your
deployment.
Maybe
it's
just
deployment
into
insert.
You
know
a
dev
environment
that
you
can
easily
test,
throwing
hugely
improve
your
productivity
constantly.
Just
looking
for
little
things,
you
can
do
to
make
it
better,
try
it
get
a
bit
better
and
then
look
again.
A
What's
the
next
pain
point,
let's
go
and
improve
that.
So,
if
we
look
at
the
planning
side,
we've
as
your
board
as
I
mentioned,
that's
got
all
the
functionality
for
doing
dashboards
for
doing
Kanban
boards,
that
sort
of
thing
and
getting
reporting
based
on
you
know
what
work
is
available
in
my
project
and
all
those
sorts
of
things
I
talked
about
as
your
repos.
That's
the
service,
that's
the
source
control
service.
A
A
It
has
an
amazing
excuse.
Me
has
an
amazing
code
search
capability,
that's
understands
the
code.
So
if
you
do
a
search
for
say
foo,
you
know
it'll
find
you
the
class
that
defines
foo
rather
than
finding
you
the
class
that
mentions
foo
the
most.
He
actually
understands
code
and
helps
you
use
code
search
is
really
well.
A
Then
we
have
as
your
pipelines,
which
was
played
we've
quite
a
lot
already
today.
This,
as
I
mentioned,
you
know,
supports
dotnet,
absolutely
awesome,
not
just
c-sharp
and
vb.net
and
things,
but
the
the
F
sharp
team
have
a
lot
of
you
know,
plugins
into
as
your
pipelines
to
be
able
to
do
stuff.
If
you
want
to
hook
into
fake
and
all
those
sorts
of
things
you
can
do,
that,
they've
got
an
amazing,
really
really
good.
A
You
know
integration
in
there
and
that's
we're
saying:
there's
a
huge
marketplace
of
plugins
into
Azure
pipelines
that
allow
you
to
do
things
so
run
node
on
Python
and
they're
all
open
source.
If
you
want
to
contribute
those,
you
can,
and
you
can
do
your
own.
So,
interestingly,
the
AWS
publishing
stuff,
that's
actually
Wien
originally
started
that
and
then
handed
it
over
to
the
Amazon
team,
and
now
the
dotnet
team
Amazon
are
the
people
that
maintain
that
integrations.
So
they
are.
A
They
are
the
people
that
allow
you
to
deploy
for
measure
pipelines
into
AWS,
which
is
pretty
amazing
and
I.
Don't
know
how
do
I
love
open
source,
it's
great,
when
we
can
do
that
sort
of
thing.
It's
completely
extensible,
as
I've
shown
you
and
if
you
know
it
works
first-class
with
containers
with
docker
hub
we've
actually
container
service
with
Azure
capillary
service,
all
that
sort
of
good
stuff.
If
containers
is
your
thing,
warnings
I
want
to
mention
that
we
announced
on
Tuesday
when
Monday
or
Tuesday
I
forget
and
what
don't
know.
A
What
timezone
of
me
is
the
Azure
pipelines
that
service
we
have
available
is
now
available
for
open
source
projects.
You
don't
have
to
be
logged
in
to
as
your
pipelines
to
be
able
to
look
at
a
bill
report.
If
you
said
it's
public
and
open-source
projects
is,
then
this
is
just
crazy,
I'm.
So
proud.
We
were
able
to
do
this.
They
get
a
limited
number
of
build
minutes,
so
you
can
just
build
as
many.
A
Edward
Thompson
is
speaking
tomorrow
morning,
Friday
and
he's
going
to
show,
like
the
integrations
with
open-source
he's,
the
maintainer
of
a
lib
get
to
project
and
a
few
other
projects
on
github,
and
he
actually
show
you
how
to
get
that
hooked
up
and
how
to
really
delve
into
the
integration
we
get
up
there.
I'm
just
going
to
quickly
show
you
some
of
these
early
adopters,
the
dotnet
foundation
led
by
Orrin
Novotny
who's.
A
So
no
more
XML,
no
more
yeah
more,
you
know,
do
do
your
build
within
c-sharp,
it's
an
awesome
project
and
that's
again
got
set
up
to
use
as
your
pipelines
already,
and
we
only
announced
this
on
Monday
or
Tuesday,
depending
on
your
time
zone.
So,
let's
just
have
a
quick
play.
I
want
to
show
you
some
of
these
projects
and
show
you
how
they've
got
set
up
so
I'm
gonna
jump
in
here.
First
of
all,
let's
look
at
cake,
so
I'm
logged
in
here
I'm,
looking
at
a
pull
request.
A
The
Patrick
sent
off,
but
it's
the
latest
pull
request
is
currently
active
and
we
see
all
the
usual
stuff
that
happens
on
your
pull
request
and
github.
You
know
we're
coming
in
and
we're
having
some
discussion
about
it.
All
that
sort
of
thing
we've
got
approvers
projects
ran
very
well.
It's
got
a
very
good
sort
of
structure
for
deciding
what
goes
live
and
things,
and
you
see
here,
they've
got
all
these
checks
that
look.
A
If
the
pull
request
is
gonna
work
or
not-
and
this
is
how
you
stop-
you
know,
built
broken
builds,
let's
run
a
build
validation
on
poor
request
so
before
pre
merge,
so
that
the
points
of
code
review,
let's
run
a
build
validation
and
see
if
it
if
it's
gonna,
pass
or
fail-
and
you
see
this
one
here
has
come
in
and
it
actually
has
passed,
but
it
hasn't
just
passed
on
Windows,
which
is
awesome.
You
know,
but
it's
coming
here
and
it's
also
passing
on
CentOS
and
fedora
and
on
the
Mac
and
everything
else.
A
So
if
I
go
look
at
the
Mac
build,
we
can
go
jump
in
and
it
takes
us
over
inside.
Your
pipelines
and
I
mean
see.
There's
the
build
running
on
the
Mac.
If
I
quickly
look
over
at
logs,
you
get
that
and
if
I
look
over
at
their
releases,
I
can
look
at
all
their
sorry
builds.
Someone
talking
about
I
can
look
at
all
their
build,
so
they're
different
operating
systems.
You
got
the
Mac
one,
the
ability
one
CentOS
Debian
and
see
what's
happening
with
those.
So
awesome,
that's
very,
very
cool.
A
The
next
one
wanted
to
look
at
was
one
of
the
ones
was
one
of
our
ins
projects,
so
reactive
extensions,
that's
an
API.
You
know
for
doing
asynchronous
stuff,
so
coming
here
again
hooked
up
with
Azure
pipeline's
I'm
just
going
to
quickly
click
on
the
build
badge
and
login.
Their
reason.
I'm
logging
in
is
because
I'm
I'm
vice
president
on
the.net
foundation,
so
I
actually
have
access
to
this
account
and
could
do
crazy
stuff.
A
But
if
you
want
to,
if
you
wanted
to
go
to
reactive
extensions
now
and
follow
along
with
me,
you'd
be
able
to
so
we
come
in
here
and
we
can
see.
We've
got
Co
coverage,
we
didn't
see.
Like
you
know,
70%
of
the
codes
you've
got
seven
percent
code
coverage
right
now.
We
can
tell
that
you
know
ninety-nine
point.
Nine
four
tech
unit
tests
have
passed
so
on
every
single,
build
on
every
single
pull
request
before
I
run
even
bothers
to
review
his
source
code.
A
He
can
see
that
seven
half
thousand
unit
tests
have
passed
or
failed.
So
he
knows
if
it's
worth
his
time
to
review
this
source
or
not.
Oh,
this
pull
request.
Not
only
that
the
person
who
submitted
the
pull
request
gets
instant
feedback.
If
it,
if
it's
good
or
bad
and
then
the
final
one
I
want
to
look
at
just
quickly.
Is
it's
not
a
Donette
project?
It's
an
electron
project,
but
it's
one
I
know
a
lot
of
dollar
developers
use
that's
Visual,
Studio
code.
A
As
you
all
know,
Visual
Studio
code
is
completely
open
source
here
on
github
and
we
can
see
right
now.
The
build
is
partially
successful
on
you
happened
here,
so
we
can
come
in
and
we
can
have
a
look
at
that
build
badge
and
it's
going
to
take
us
over
inside
your
pipelines
and
weensy
they've
got
a
Visual
Studio
code
with
being
an
electron
app.
They
build
for
Windows,
Linux
and
Mac,
and
we
can
see
the
Windows
job
and
the
Linux
job
have
succeeded
and
all
good,
but
it's
failed
on
the
Mac.
This
is
quite
common.
A
When
you're
building
cross-platform
applications
cross-platform
is
hard.
You
know
it's
just
random
stuff,
like
the
differences
between
you
know,
file
systems
what's
valid.
What's
not
and
all
any
other
differences
Britain
the
way
sockets
work
and
things,
and
even
sometimes
different
chipsets
is
make
a--make
cross-platform
very
hard
and
then
there's
pretty
good
example.
We
see
that
there
was
the
build
was
successful,
but
there
were
some
issues
and
if
we
had
a
look
at
what
the
issues
were,
we
can
see
that
the
source
is
compiled.
A
A
A
And
I'm
gonna
say
over
test
assemblies
that
was
on
the
dotnet
framework.
One
sorry
wasn't
it
wasn't
the
dotnet
core
one
mm-hmm
test
assemblies
he's
running
and
it's
just
running.
You
know
running
the
test
execution,
so
that's
basically
doing
a
dotnet
test,
but
you
want
to
look
at
Tony.
You
wanna,
look
at.
Let's
show
you
a
different
project.
That'll
have
proper
a
dominant
framework
project.
A
This
is
here's
one
I
prepared
earlier
that's
doing
a
dotnet
framework,
one
and
I'm
gonna
come
into
here.
Look
at
builds,
I,
bring
it
up.
Basically
test
assembly
so
need
runs,
it
searches
for
things
called.
You
set
the
name,
the
pattern
and
it
searches
for
things
called
startup
tests
and
it
executes
them.
He
uses
a
test
runner
to
xq
those
and
that
test
Runner
supports
and
unit.
You
know,
X
unit,
all
that
sort
of
thing.
A
Okay
and
then
there's
another
question
from
the
NESH
around
the
email
notifications
we'll
get
to
that
one
in
a
second
philip
has
a
question:
is
it
safe
to
publish
scripts
containing
confidential
data
over
the
STS,
build
agents
we're
running
in
document
alien
security
purposes,
wow?
What
a
good
question
publish
scripts
so
what
happens
with
your
build
agent
Phillip
to
try
and
help?
You
explain
this.
A
We
have
a
pool
of
build
agents
that
are
basically
VMs
running
in
the
cloud
and
even
with
Linux,
where
it's
running
in
a
docking
container,
it's
a
docker
container
running
in
a
VM.
We
in
our
hosted
build
agents,
we
take
them,
we
allocate
it
to
the
user.
We
run
the
build
on
that
VM
and
then
we
do
all
the
tests.
A
So
it's
safe
in
terms
of
what
was
on
that
build
machine
is
in
an
isolated
virtual
machine,
sandbox
and
so
which
gets
destroyed
at
the
end
of
your
build
hope
answers
the
question:
if
you're
really
really
concerned
about
you
having
data
at
all
in
the
cloud,
then
let's
show
you
what
you
can
do
there.
You
don't
have
to
use
our
hosted,
build
agents,
you
can
use
self,
hosted,
build
agents.
So
let's,
let's
go
cover
that
now.
Actually
what
a
great
segue
Tony!
Thank
you
very
much.
That's
awesome!
A
If
we
come
in
and
we
have
a
look
we
can
have,
you
can
have
in
a
DevOps
hosted
up
in
the
cloud
or
you
can
host.
You
know
team
foundation,
server
on
Prem,
it's
the
same
codebase
you
can
have
a
hosted
pool
which
we've
set
up
for
you
for
free,
Mac,
Linux
and
Windows,
but
maybe
you
want
and
your
own
agent,
but
you
own,
it's
running
in
a
VM,
for
example,
but
is
yours
in
Azure
or
it's
running
in
AWS
or
GCP?
You
know
who
cares?
A
A
So
as
long
as
that,
build
machine
has
outbound,
you
know
as
to
sell
access,
then
you
can
do
that.
What's
worth
noting
is
if
you're
using
one
of
our
hosted,
build
agents
it
you
can't
connect
a
hosted,
build
agent,
you
can't
create
a
hole
for
it
in
your.
Unless
you
make
your
your
boxes
available,
you
know
on
the
internet,
which
probably
isn't
wise
to
be
able
to
deploy
stuff
on
the
internet.
Your
on-premise
hardware,
you
can't
go
from
the
build
agent
over
the
hosted,
build
or
a
deployment
agent
and
actually
deploy
into
your
on-premises
environment.
A
You
probably
need
to
use
a
self
hosted
agent
to
do
that
unless
you
were
to
open
holes
and
firewalls,
which
I
really
don't
recommend.
Well,
it's,
where
mentioned
is
where
you
can
deploy
from
a
DevOps.
You
can
deploy
a
cloud
or
on
Prem
and
you
go
to
any
cloud
or
any
any
on
prayer
area
and
you
can
actually
deploy
to
a
combination
of
both,
and
this
is
quite
common-
that
customers
keep
have
still
got
their
own
prem
hardware
and
they're
keeping
it
now.
A
They've
not
moved
the
the
production
workload
into
asia,
but
what
they're
doing
is
doing
their
dev
and
QA
runs
out
in
the
cloud
out
out
in
asia,
and
you
can
dynamically
provision
an
environment.
You
know
using
an
arm
template
or
using
puppet
and
chef
or
terraform,
or
something
some
configurations
code
to
actually
set
up
your
environments,
and
you
can
have
those
built
out
in
the
cloud
temporarily
stand
them
up
run
your
dev
and
QA.
A
Leave
it
for
a
certain
period
for
awhile
approval,
and
then,
when
somebody
marks
it
is
approved
within
the
azure
pipelines
that
then
can
move
out
into
production
and
then,
as
part
of
that,
tear
down
the
QA
environment
because
it's
no
longer
needed.
So
you
can
do
all
that
sort
of
further.
That's
actually
a
fairly
common
scenario
for
people
to
do.
A
A
You
know
doing
stuff
with
customers
because
they
would
have
their
source
code
and
they
would
complain
about
a
feature
not
working
or
stuff,
and
we
like,
we
fix
this
and
it
turns
out
they're
not
using
the
latest
version
or
to
get
a
new
version
deployed
out
to
everybody
in
you
know
the
business
who
was
using
it
you
just
take
ages.
We
used
to
have
to
wait,
for
you
know,
machines
to
get
shut
down
and
all
sorts
of
things.
A
So
what
you
want
to
look
into,
if
that's,
if
that's
a
problem
you've
got,
is
one
of
these
evergreen
installation
technologies.
So
the
Evergreen
installation
is
basically
always
use
the
latest
version
if
you
use
Google,
Chrome
or
whatever,
or
if
using
an
app
one
of
the
store
applications
or
an
app
on
your
phone,
it's
always
up-to-date.
Whenever
you
go
into
it,
you've
always
got
the
latest
version
and
to
achieve
that
with
desktop
applications.
A
There's
a
number
of
technologies
available
here,
the
one
probably
the
oldest
one
on
the
list
is
click
once,
which
is
enables
you
to
do
web
deployments,
but
as
well
as
doing
you
know,
being
able
to
easily
install
of
net.
It
also
has
an
update
capability
in
it
as
well
to
enable
you
to
get
latest
versions.
A
Squirrel
is
an
open-source
application
that
allows
you
to
do
this
and
squirrels
really
really
straightforward
to
use,
and
the
thing
that's
awesome
about
squirrel
is
it's
actually.
Packages
using
NuGet
packages
is
what
this
you
know,
that's
how
it
distributes
the
updates
between
versions,
but
with
a
squirrel
application.
It
can
check
for
new
versions
on
app
startup
or
on
a
certain
schedule.
A
So
during
the
day
it's
downloaded
got
the
got
the
new
version
ready
to
go
next
day
when
people
come
in,
they
log
in
start
up
the
application
and
boom
they're
on
that
new
version,
and
that
can
shorten
the
amount
of
time
it
takes
to
get
things
into
production.
Enormous
Lee.
The
other
great
thing
about
squirrel
is
that
you
can
get
it
to
subscribe
to
different
channels.
So
using
a
simple
registry
key
or
even
a
UI
setting,
you
can
get
it
to
have.
You
can
have
a
dev
channel
like
a
CI
CD
channel.
A
A
You
can
have
a
certain
set
of
expert
users
that
are
opted
into
the
fast
ring
and
they
can
come
in
and
actually
you
know,
get
the
latest
bits
sudo
rather
than
the
whole,
your
whole
estate,
so
scrolls
an
awesome
technology
and
then
finally,
squirrel
also
works
with
different
versions
of
Windows.
You
know
Windows
10,
but
also
earlier
versions
of
Windows.
If
you're
lucky
enough
to
have
everybody
in
your
estate
running
Windows
10,
then
you
can
use
the
Microsoft
Store
for
business
and
education,
which
is
your
own
private.
A
Sorry
as
your
artifacts,
it
exists
that
hooks
into
as
your
pipelines
and
that
allows
you
to
store
or
privately
your
maven
feeds
your
NuGet
feeds
and
NPMs,
and
things
like
that,
and
that's
a
great
compliment
to
something
like
squirrel,
because
with
that
you
can
promote
easily
NuGet
packages
from
say,
dev
to
production
within
within
a
channel
which
is
awesome
and
then
finally,
we
talked
about
test
plans
and
that's
the
manual
testing
that
we
kind
of
already
covered
in
one
of
the
questions
earlier
on
right.
So
you've
got
all
these
things.
A
You
know
they're
the
main,
agile,
devops
services
and
then
you've
also
got
you
know.
How
do
you
know
if
my
applications
better
or
worse-
and
this
is
where
we
have
Azure
monitoring
as
your
application
insights
and
as
your
Security
Center,
to
actually
look
for
live
things?
You
know
in
your
application
and
allow
you
to
go.
Do
it
says
root
cause
analysis
that
there
is
no
root
cause
typically
with
a
complex
system.
It's
you
know:
do
post-mortems
actually
figure
out
what's
wrong
with
your
application
and
then
another
cool
thing
that'll
wants
to
make.
A
Sure
you
knew
about
was,
as
you
do,
as
your
lab
services.
So
if
you
want
to
come
in
and
create
a
dev
environment,
it
makes
it
super
easy
to
do
that
spin,
those
up
and
actually
have
configurations
so
that
people
don't
leave
these
resources
on
that's
saved
my
bacon
one
day
when
I
am
I
was
going
to
do
a
demo
for
a
friend
and
I
went
home
to
pick
up.
You
know
the
big
bag
of
dongles.
You
need,
as
you
do,
to
do
any
demos.
A
Nowadays
you
need
bagger
dongles
to
project,
went
home
grab
the
bag
of
dongles
arrived
at
my
mates
to
go,
do
a
demo
to
his
work
and
then,
when
they
got
to
the
carpark,
picked
up
a
bag
of
dongles
and
realized
I've
left
my
laptop
at
home.
You
know:
that's
not
much
used
to
me
so,
while
I
was
walking
from
the
carpark
to
his
office,
I
actually
went
in
and
went
into.
Azure
portal
told
it
to
create
me
a
new
visual
studio,
20-17
instance.
A
In
the
cloud
for
me
walked
into
these
office
and
said:
hey
can
I
have
can
I
just
jump
on
a
machine.
That's
on
your
network,
please
and
then
RDP
from
his
machine
over
into
Azure
and
had
a
full
dev
workstation
because
of
my
source
code
was
in
as
a
repose.
I
was
able
to
just
do
a
quick
get
clone
because
I
was
using
onedrive
from
a
deck.
I
was
able
to
go
there
and
just
able
to
do
a
demo
really
quickly.
A
A
We've
got
Azure
DevOps
services,
so
as
your
boards,
as
repos
as
your
pipelines
as
your
test
plans
as
your
artifacts
that
allows
you
to
go
plan
smarter
and
plan
faster
for
your
teams.
We
also
have
this
amazing
offer,
if
you're
doing
an
open
source
project.
If
you
are
maintainer
of
an
open
source
project,
take
a
look
at
as
your
pipelines
completely
for
free
you've
got.
You
know
a
limited
bill
minutes
and
as
I
say,
10
concurrent
jobs
across
Mac,
Windows
and
Linux,
which
is
just
fabulous.
A
A
Let's
go
through
some
questions,
so
vinash
email
notifications
is
it
possible
to
include
build
summary,
so
work
items
and
things
in
the
mail.
Currently
it
just
says:
success
spell
you
know
what
man
I,
don't
think
it
is
actually
there
is.
There
are
ways
of
customizing
those
notifications
and
I
wouldn't
recommend
any
of
them.
What
you
could
do
quite
easily,
though,
is
use
a
service.
We
have
web
hooks
available
in
notifications,
so
you
could
use
a
service
there
to
actually
come
in
and
do
you
execute
your
own
custom
code
whenever
a
build
succeeded
or
failed?
A
And
if
you
look
at
a
service
called
zapier
z,
AP
iie
are
calm.
They
have
a
bunch
of
things
where
you
can
take
outputs
from
Azure
pipelines
and
actually
turn
that
into
an
email
template
and
send
it
out
next
question
from
Ben
how
squirrel
and
Azure
artifacts
interact
in
terms
of
licensing.
That's
a
great
question:
Ben
right
now
it's
a
it's
a
user
license
for
artifacts
and
so
yeah.
We
should.
We
should
see
what
we
can
do
with
licensing
there
in
the
future.
A
If
you've
all
got
MSDN
solutions,
that's
cool,
but
right
now
a
lot
of
people,
don't
so
I'm
hoping
we
can
see
what
we
can
do
around
licensing
and
make
that
more
affordable
for
people.
Ok,
any
other
questions
or
I
think
we're
gonna
wrap
up
and
it
looks
like
Dan's
gonna
be
coming
up
in
a
bit
after
the
adverts,
so
I
think
I'm
going
to
wrap
up
thanks
everybody
for
your
time.