►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 24th of October. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI, Reusable SPFx controls and PnP SPFx Yeoman extension.
Detailed covered content from SharePoint Dev Blog at http://aka.ms/spdev-blog.
- Demo | Site header toggler SPFx extension | Ram Prasad Meenavalli (Infineon Technologies) | @ram_meenavalli
- Demo | Azure DevOps pipelines | Andrew Connell (Voitanos) | @andrewconnell
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
You can find more details around the open-source and community work from http://aka.ms/sppnp
A
Whoa
and
welcome
to
the
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly
sync,
it
is
October
24th
2019.
Thank
you
all
for
joining
us
here
today
got
a
great
agenda
as
usual
for
everybody
latest
updates
on
SharePoint
framework,
as
well
as
updates
across
the
patterns
and
practices,
program,
offerings
and
then
demos.
We
are
first
demo
from
ROM
Prasad
min
ivali
who's
got
a
site,
header,
toggler,
SP,
FX
extension,
and
then
we've
got
another
demo
from
Andrew
Connell,
which
is
Azure
DevOps
pipelines.
A
You
could
have
had
a
PM
pjs
demo,
but
everybody
voted
to
have
Andrews
demo.
So
it's
going
to
be
really
spectacular,
so
opportunity
to
participate
in
P
and
P
Hauser
practices
all
up,
and
this
cig
in
particular.
We
always
always
always
encourage
everybody
to
to
reach
out
with
demos.
I
think
the
demos
continue
to
be
one
of
the
best
parts
of
these
calls
just
to
see
all
the
great
stuff
everybody
out
there
in
the
community
is
working
on,
so
that
could
be
something
around
SharePoint
framework.
A
Whether
you've
got
a
web
part
application,
customizer
you're
doing
something
around
provisioning,
really
anything
in
that
space
and,
of
course,
if
it
includes
something
from
the
at
P
and
P
set
of
offerings.
That
makes
it
even
a
little
bit
better
on
this
call
and
then
just
a
reminder.
We
of
course
encourage
everyone
to
contribute
on
github
to
all
of
our
projects,
so
that
includes
reporting
issues,
submitting
pull
requests
and
then
as
well.
A
If
you
see
a
question
that
you
might
know
the
answer
to
take
a
few
minutes
or
if
you
can't
take
a
few
minutes
and
respond
to
that
question,
that's
always
a
big
help
and
gets
folks
an
answer,
perhaps
a
little
bit
faster
than
waiting
for
somebody
on
the
core
team
to
get
to
that
and
all
the
projects
absolutely
welcome,
folks
contributing
code
and
issues
and
ideas
to
those
projects.
So
please
do
reach
out
there
and
then
finally
providing
feedback.
How
are
these
calls
going?
How
are
generally
all
our
work
going?
A
What
kind
of
documentation
needs
are
there,
and
where
can
we
help
out
a
little
bit
more
and,
of
course,
positive
feedback
is
okay
too.
A
lot
of
this
work
is
done
kind
of
in
a
vacuum.
So
it's
good
to
hear
what
is
working
well,
so
that
we
can
do
more
of
that
or
kind
of
bring
that
a
little
bit
more
to
for
and
before
we
get
to
the
SharePoint
framework
updates.
One
last
thing:
we've
got
our
links
there,
so
a
kms,
SP,
dev
Doc's,
will
take
you
to
the
all
up.
A
Sharepoint
developer,
documentation,
SP
dev
videos
will
take
you
to
our
YouTube
channel,
where
you
can
find
the
recordings
for
this
special
interest
group,
as
well
as
the
other
special
interest
group
and
lots
of
other
neat
stuff,
so
tutorials,
both
long
and
short
in
there
on
various
topics,
there's
a
different
series
of
tutorials
that
go
together,
for
example,
on
provisioning.
So
you
can
find
a
lot
of
great
resources
there
for
learning.
A
You
know
all
about
SharePoint
development,
different
techniques,
different
strategies
and
as
well
as
catching
up
on
our
various
calls,
because
well
the
monthly
calls
are
on
there
as
well
and
then
based
on
waldek
have
their
weekly
series.
That's
on
there
as
well,
so
definitely
check
all
that
out.
If
you
need
a
little
bit
more
SharePoint
content
in
your
life
and
then
finally,
SP
dev
issues
is
issues
list
to
report
anything
with
SharePoint
product.
So
you
can
check
that
out
and
torture
issues
see
if
issues
you
might
be.
B
Excellent,
just
the
main
point
that
one
what
to
set
around
the
dev
issues.
It
is
for
dev
issues,
dev
dev,
dev
issues.
We
can't
unfortunately
process
any
and
non-deaf
issues
using
the
issue
list
to
stay,
updated
statistics,
I,
didn't
wanna,
add
nothing
too
dramatic
here.
We
did
see
this
massive
leap
forward
on
during
this
autumn,
so
on
the
on
the
September
October
time
frame,
and
now
it's
slightly
slowing
down,
but
again
it
is
too
early
to
say
what
will
happen
next
week
and
what
is
the
curve
on
that?
B
B
Why
we're
not
actually
giving
you
again
to
exact
detailed
numbers,
and
this
is
we
have
a
pretty
interesting
way
of
calculating
actual
usage
of
third-party
extensive
and
sharepoint
online,
so
giving
you
the
number
if
it's
like
five
million
people
in
a
day
or
doing
something,
it
doesn't
actually
give
you
the
usage,
because
there's
a
big
difference.
Is
the
user
using
a
one
application
once
a
day
or
is
it
using
the
one
application
ten
times
of
a
day
or
ten
T
from
the
application
20
times
in
the
day?
B
So
it's
not
just
about
the
number
of
users,
it's
also
about
the
actual
usage
of
those
applications
and
that's
what
we're
trading
with
in
this
charge,
just
an
update
on
the
on
the
roadmap
things.
So
the
next
things
what's
are
coming
out.
So
we
have
been
quite
silent
on
releasing
things
and
that's
mainly
because
we
now
prioritize
what's
coming
and
announced
in
ignite.
So
within
two
weeks
and
ignites,
we
do
have
an
ignite
special
scheduled
for
the
two
weeks
ago.
B
Two
weeks
from
now,
there
will
be
an
ignite
special
related
on
updates
on
the
SharePoint
dev
site
and
what
we'll
kind
of
actually
release
there
is,
let's
say,
an
SPF
X,
the
two
or
updates
and
so
on.
What
we
can
announce
that
so
there
will
be
logical,
let's
say
next
steps
on
this
journey
of
extending
SharePoint
framework
not
to
be
anymore
just
ship
on
framework.
B
365
extensibility
is
using
then
SharePoint
framework
or
similar
kind
of
a
pattern,
and
then
there
will
be
other
announcements.
We'd
be
pretty
open
on
talking
about
the
fact
that
there
will
be
a
fluid
framework
capability
coming
out.
We
demoed
that
in
build
that
is
coming
up
to
preview
at
soon
or
later,
and
that's
kind
of
relates
on
on
the
bigger
picture
as
well,
but
that's
pretty
much
what's
happening
here
for
the
existing
SharePoint
framework.
B
Obviously
the
day-to-day
shape
on
frame
request
build
stuff
and
we
use
on
a
day-to-day
basis,
there's
no
traumatic
days
on
that
one,
and
we
will
make
this
transition
a
pretty
seamless
and
there
will
be
one
point
ten
sooner
or
later
coming
out.
It
is
a
slightly
resource-constrained
right
now,
because
we're
prioritizing
the
date
night
announcements
and
all
that
stuff
on
these
things,
which
is
a
pity,
but
it's
always
the
challenge.
With
these
things,
garland
did
really
the
new
capabilities
which
we
are
well.
B
At
least
one
of
these
is
coming
out
still
in
October,
in
its
24th
of
October,
there
will
be
the
pre
allocation
of
extension
sizes
on
page
rendering
this
is
actually
already
visible
in
the
in
the
tenants.
We
talked
about
this
one
few
times
already
in
the
community
code.
This
is
actually
already
visible
in
the
tenant
wide
extensions
list
in
the
I
think
99%
of
the
tenants.
We
will
talk
on
document
this
capability
pretty
soon
and
we
can
actually
start
using
that
as
part
of
the
extension.
B
The
main
objective
of
this
one
is
to
avoid
the
the
screen
flickering
so
that
the
screen
escapes
from
moving
as
part
of
the
loading
events
which
you
probably
have
seen
with
the
application
customizers
in
your
implementation,
but
that's
basically
already
working
and
it's
now
a
matter
of
getting
it
documented
I
really
wanted
to
actually
demoed
that
today,
but
I
was
unable
to
find
time
because
of
my
technical
computer
issues
so
spending
time
on
support
actually
ate
up
time
from
the
demo.
Unfortunately,
but
let's
move
forward
on
the
following
slide.
A
So
updates
on
PMP
jsv,
so
big
push
aiming
for
the
release
candidate
or
the
beta
one
in
October.
So
did
a
lot
of
stuff
late
into
last
night
on
that
did
a
lot
of
code.
Cleanup
and
I
got
to
say
thanks
again
to
everybody,
who's
helped
out.
Writing
all
the
new
tests.
I
was
able
to
do
a
lot
of
pretty
big
changes
and
caught
some
bug's
die
myself
introduced
through
all
those
new
tests,
so
very
great
to
see
that
work
paying
off.
So
thanks
everybody
again
for
that
what
is
left.
We
have
five
sub
modules.
A
We
gotta
get
docs
and
tests
for
I've
got
some
articles
left
to
write
on
some
of
the
new
features
to
help
explain
those
and
how
to
use
them.
We've
gotta
fix
up
the
make
Doc's
index
file
and
then
I've
got
some
other
stuff.
I,
probably
haven't
even
thought
of
yet
but
I'm
going
to
create
a
issue
in
the
issues
list.
That'll
be
the
beta
release
punch
list.
So
that
way
everybody
can
see
that
and
see
that
list
of
stuff
and
then,
of
course,
if
I've
forgotten
something,
you
can
always
remind
me
in
that
issue.
A
A
So
we'll
have
some
small
updates
then,
and
we'll
get
that
out.
Moving
forward
office,
365
CLI
beta
2
to
0,
is
out
with
support
for
retrieving
offices.
V
group
group
activities,
removing
flows,
adding
power,
apps
enabling
web
and
site
features,
retrieving
Yammer
networks
and
true
and
retrieving
teams,
message
replies.
So
as
always,
you
can
install
the
latest
beta
from
at
PNP
office,
5
CLI
at
next,
and
for
those
of
you
that
might
not
be
familiar
with
the
CLI,
definitely
check
out
the
documentation
at
a
kms,
365
CLI.
A
That
will
get
you
all
the
details
on
what
is
a
great
cross-platform
tool
for
managing
your
office,
365,
SharePoint
and
other
work
stream.
You
know
tasks,
so
you
could
do
some
administrative
stuff,
you
just
maintenance
stuff,
it's
really
great!
If
you
need
to
use
it,
you
know
as
part
of
your
development
setup.
So
if
you
need
to
set
up
new
sites
or
new
resources,
things
like
that,
the
CLI
is
a
great
way
to
do
that.
A
Cross-Platform
and
incorporating
lots
of
great
work,
as
always
from
the
community
on
all
that
stuff,
so
really
excited
to
see
that
continued
to
grow
next
up,
reusable
SPF
x,
components
for
folks
that
might
not
be
familiar.
We
have
two
sets
of
components:
there
is
the
property
controls
that
are
designed
to
work
in
the
Edit
pane
of
your
webparts,
and
then
we
have
the
controls
or
the
controls
react
as
they're
named
that
are
designed
to
work
in
the
body
of
your
webparts
or
just
as
well
could
be
in
an
application,
customizer
or
other.
A
You
know
more
presentation
focused
places,
so
the
latest
version
of
the
controls
is
115,
and
that
includes
a
file
picker,
a
grid
layout
and
a
carousel,
as
well
as
numerous
enhancements
and
fixes
to
various
bugs
that
have
been
reported,
and
we've
got
a
ton
of
great
contributors
on
this
project
again
as
well.
Some
of
them
listed
there.
You
can
find
more
information
SharePoint
at
github
I
owe
at
/s
P
dev,
FX
property
controls
and
SP
dev
FX
controls
react
for
all
the
documentation
and
information
on
there.
A
So
again,
thanks
to
all
the
folks
that
have
contributed
on
the
controls,
it's
another
great
tool
to
have
in
your
tool
kit
for
SP
FX
development
can
save
you
a
lot
of
time
and
they
come
styled
with
the
office
UI
fabric.
So
they're
gonna
give
you
that
great
out-of-the-box
look
and
blend
right
into
SharePoint
so
that
you
don't
have
to
focus
as
much
on
that
as
you
can
on
composing.
These
controls
together
to
create
your
solutions,
and
they
can
also,
of
course
be
extended.
A
So
if
you
want
to
take
them
and
extend
them,
make
them
a
little
more
customized
for
your
needs.
That's
of
course
possible
as
well-
and
you
know
if
you
have
good
ideas
for
new
controls
or
fixes
to
existing
controls,
of
course
welcome
those
contributions
as
well
and
finally,
before
we
get
to
the
demos,
we've
got
the
P
and
PS
VFX
generator.
So
this
is
an
open
source,
yeoman
generator
built
on
top
of
the
out-of-the-box
standard,
Microsoft
SPF
X
generator.
A
So
under
the
hood
you're
going
to
get
a
quote,
unquote
real
SPF
X
project
that
has
all
the
same
dependencies
and
you
know
core
Microsoft
libraries
inside
it,
but
you
can
include
very
easily
a
lot
of
additional
capabilities
that
you
can't
in
the
out-of-the-box
human
generator.
So
you
can
choose
to
include
things
like
p.m.
PJs
or
jQuery
or
office
365
CLI.
You
could
choose
different
templating
packages.
Instead
of
just
react,
you
could
do
things
like
handlebars
in
View
and
then
as
well.
A
Angular
so
really
check
that
out
again
another
great
tool
to
have
in
your
tool
kit.
So
all
of
these
together
really
can
help
speed
up
your
development
and
help
get
you
started
very
quickly.
The
latest
version
of
the
generator
is
110
or
110,
and
you
can
always
read
about
that
at
a
kms,
P&P
generator
we'll
get
you
all
the
documentation
for
the
generator,
and
there
is
installation
instructions
there
and
as
well.
A
A
C
C
So
when
I
collapse
it,
the
header,
gets
hidden
and
I
have
more
space
for
the
content
area
where
I
can
read
so
basically
the
motivation
behind
developing
this
is,
if
we
look
at
the
classic
sites,
we
always
had
this
option
to
focus
on
content
which
hides
most
of
the
static
ones
and
we
got
more
reading
area.
So
that
was
one
of
the
idea
to
think
of
this
solution,
and
there
was
another
scenario
where
we
I
wanted
to
use
this.
C
So
for
a
developer
like
most
of
the
time
when
we
develop
the
SPF
X
webparts,
we
use
the
developer
tools,
a
lot
like
if
you
see-
and
we
just
go
through
if
we
want
to
check
the
HTML
structure
or
we
want
to
see
the
react,
components
and
check
the
properties
and
States.
This
is
the
most
of
this
time.
We
use
this
developer
tools
and
when
I
want
to
inspect
certain
element
like
the
content
area
is
very
small.
It's
it's
almost
not
even
20%
of
the
screen
and
in
such
scenarios.
Also.
C
This
is
helpful,
where
I
can
just
hide
the
header
and
I
have
more
space
to
check
out
or
debug
on
the
content
and
the
SPF
X
structure
here.
So
basically,
this
is
the.
This
is
one
of
the
problem,
which
is
because,
like
many
people
use,
multiple
monitors,
I
don't
have
a
multiple
monitors
system
so
and
it's
only
on
one
monitor
which
I
work.
This
could
be
helpful
in
such
scenarios
as
well
and
there's
no
other
complication.
It's
a
very
simple
extension,
so
I
will
jump
to
the
code.
C
The
placeholder
for
the
the
top
placeholder
and
within
this
I
have
written
some
basic
HTML
to
show
two
anchor
tags
using
the
fabric,
icons
for
the
expand
and
collapse,
icons
and
then
I've
registered
the
event
handlers
or
the
click
handlers
for
these
two
buttons
and
we
add
CSS
class
to
the
body
of
the
page,
and
there
is
the
corresponding
CSS
which
hides
the
header
this
part.
So
basically,
we
find
a
div
where
we
have
this
data
automation,
idea
of
site
header
and
we
display
it
display:none
for
that
site
header.
C
So
that
way
we
can
hide
the
header
as
well
as
we
can
also
try
hiding
the
soap
bar.
So
that's
all
I
want
to
share,
but
before
I
close,
what,
as
you
can
see,
this
is
about
playing
with
the
Dom
structure,
which
is
definitely
not
recommended.
So
I
wouldn't
suggest
this
using
in
a
production
scenario,
but
in
my
case
it's
mostly
useful
as
a
developer,
to
hide
the
header
and
have
a
more
more
content
area
on
the
canvas
for
troubleshooting
and
such
things,
yeah,
yeah
Patrick.
That's
all
I
want
to
share.
B
So
Patrick,
if
you
don't
mind,
I'll
just
jump
here
on
the
ramp,
so
that
the
keep
reason
is
actually
what
Ram
said
at
last
is
to
have
this
demo
as
well.
So
technically,
you
can
absolutely
do
this
kind
of
atom
injection
implementations
using
application
customizer.
It
is
definitely
not
also
recommended,
because
there's
a
high
risk
that
whenever
we
change
the
page
structure,
they
stay
in
a
structure
of
debates
which
is
the
Dom
structure.
B
Your
extension
will
not
work,
so
the
debates
HTML
on
the
page
should
not
be
considered
as
an
API
now
to
be
fair
again.
So
this
is
not
a
black
and
white
discussion,
though
you
might
have
a
customer
who
says:
okay,
fine
I
will
then
move
away
from
the
modern
and
then
we're
in
an
interesting
discussion
that
well,
you
probably
still
wanna
use
modern.
So
if
we
need
to
do
a
small
hack
here
is
that
birth
while
but
that's
something
which
we
obviously
from
a
Microsoft
side.
B
We
can't
say
that
it's
recommended
pattern,
but
we
definitely
want
people
to
use
modern
options
as
well
and
using
this
kind
of
a
dumb
medical,
you
can
change
the
page
structure.
Quite
heavily
definitely,
but
there
are
implications
you
need
to
be
then
taking
responsibility
of
the
page,
but
that's
it
just
to
reiterate
on
the
under
discussion.
So
thank
you
Ram
on
that
one
yeah.
Thank
you
will
then
jump
directly
on
ACS
house
AC.
Are
you
done
ready
for
your
demo
setup.
D
Here,
so
you
should
be
able
to
see
the
SharePoint
Docs.
What
I
want
to
talk
about
in
this
in
this
demo
is
doing
continuous
integration
and
continuous
deployment
with
the
SharePoint
framework
and
I.
Don't
have
any
slides
because
I'm
a
developer
and
we
don't
use
those
things
so
I
want
to
show
I'm
going
to
show
you
a
little
bit
more
about
how
you
can
automate
the
entire
story
of
rolling
out
your
SharePoint
framework
project
and
I'm.
Starting
from
you
know,
we
want
to
go
from
build.
D
If
you
have
tests,
you
want
to
be
able
to
leverage
tests
as
well,
and
then
I
want
to
be
able
to
deploy
this
to
multiple
to
one
or
more
different
environments.
Now
everything
that
I'm
gonna
focus
on
here
is,
let
me
just
throw
some
things
out
there.
First,
some
of
the
stuff
I'm
going
to
show
you
is
using
some
preview
features
from
Azure
DevOps.
They
are
all
available
today.
You
do
have
to
opt-in
to
them.
D
I'm
using
them
in
production,
I've
been
using
them
in
production
for
a
couple
months
now,
they're
very
stable
I.
Don't
it's
one
of
those
things
like
how
Gmail
was
sitting
in
beta
for
five
years.
It
didn't
really
need
to
be
there
I
kind
of
feel
the
same
way
about
this.
This
one
feature
with
Azure
pipelines
that
will
I'll
talk
about,
and
then
another
thing
I
want
to
mention
is
that
everything
that
I'm
going
to
show
you
is
really
targeted
for
sharepoint
online.
So,
and
the
reason
for
this
is
that
there
is
a
significant
part.
D
The
deployment
piece
to
this
requires
you
to
use
the
alm
api's
that
are
in
that
are
that
shipped
and
are
part
of
sharepoint
online.
They
do
not
exist
in
sharepoint
on-prem,
so
they're,
not
of
only
like
2/3
of
what
I'm
going
to
show
you
today
is
only
available
on
Prem
and
that's
just
the
build
and
the
testing
piece
of
this.
The
deployment
piece
is
something
else
you're
going
to
have
to
do.
D
D
So
let
me
first
kind
of
give
you
a
where
are
we
today
and
where
are
we
tomorrow,
so
we're
gonna
spend
most
of
our
time
tomorrow,
for
where
we
are
today
is
that
we
have,
we
can
do
continuous
integration
and
continuous
deployment
with
Azure,
DevOps
and
I
have
an
article
from
the
SharePoint
framework
documentation
about
continuous
integration
and
continuous
deployment
that
we
already
have
up
on
the
SharePoint
Docs.
So
it's
the
CI
NCD
now
this
is
focusing
on
the
present-day.
D
What's
called
the
general
availability
stuff
and
I'll
show
you
where
you
gonna,
be
able
to
tell
the
difference
here,
but-
and
this
is
just
walks
you
through
how
to
set
everything
up
using
the
GUI
to
create
the
different
tasks
or
the
steps
that
you
want
to
run,
to
set
everything
up,
how
to
go
through
and
set
your
tests
up
how
to
set
up
the
deployment.
All
of
that
stuff.
Now
I'm,
not
gonna,
focus
on
this.
D
This
is
available
today
and
we
are
gonna
have
another
article
that
is
gonna
ship,
but
we
want
to
wait
until
like
the
GA
stuff
is
when,
when
the
pipeline's
goes
GA,
what
Microsoft
did
back
in
at
Build
of
2019
this
year?
Is
they
introduced
a
new
thing,
a
new
kind
of
refactoring
to
this
stuff
called
Adger
or
sorry
yeah,
as
your
yeah,
more
pipelines
and
it's
part
of
DevOps
now.
D
The
difference
here
is
that,
unlike
before,
where
you
could
define
some
of
your
your
workflow,
like
your
continuous
integration
piece,
you
could
define
it
with
y
Amal
or
through
the
browser
to
the
the
browser
based
GUI
interface,
but
your
release
phase.
So
once
you've
built
your
SharePoint
package,
your
SP
pkg,
to
be
able
to
take
that
package
and
and
deploy
that
to
your
SharePoint
environment.
That
was
all
done
through
a
browser-based
GUI
and
you
could
export
that
or
import
it.
D
But
the
language
that
you
would
be
using
is
all
JSON
and
there
was
no
real
super
automated
way
to
do
all
that
stuff.
It
was
all
still
kind
of
manual
and
I
find
it
to
be
a
little
a
little
like
a
little
flaky
for
me,
I,
like
to
think
of
when
I
do
as
your
DevOps
or
when
I
do
any
kind
of
DevOps
I
like
to
have
everything
expressed
in
code,
because
it
allows
me
to
version
any
of
the
changes
that
we
have
in
our
rollout.
D
You
don't
go
to
a
browser-based
GUI,
where
you
can
end
up
making
your
changes
and
each
change
when
you're
gonna
make
a
save,
it
adds
another
commit.
Never
it's
just
I
think
it's
very,
very
messy.
Instead
I
like
to
do
everything
all
through
to
find
it
all
in
yeah
Milland
all
in
code.
So
the
new
thing
they've
done
is
that
we
do
everything
we
can
do
everything
with
these
things
called
yamo
pipelines,
and
what
a
yellow
pipeline
is
is
that
this
is
gonna.
D
I
gave
him
a
preview
of
the
links
that
I'm
doing
today,
so
he's
dropping
some
links
as
I
go
in
here
and
going
through
some
stuff
on
the
and
the
demo.
There
we
go,
there's
a
gist
right
there.
So
let
me
kind
of
explain
what's
going
on
in
this,
this
pipeline
is
doing
four
things.
It
is
going
to
build
my
project
at
the
exact
same
time.
D
It
is
also
going
to
run
all
of
my
tests
and
if
either,
if
both
of
those
stages
pass
successfully
and
there's
no
errors,
then
it
will
then
deploy
my
project
to
my
developer
environment
and
will
also
deploy
it
to
my
production
environment.
Now
you
may
wonder
like
why
do
you
want
to
do
it
to
both
I
will
talk
about
that
stuff
in
a
little
bit
so
here?
What
is
this
doing?
D
Let
me
I'm
gonna
walk
through
each
one
of
these
pieces
here
and
you
may
be
a
little
against
a
little
intimidating,
but
it's
actually
really
slick,
so
here
this
first
part
lines
one
through
four,
this
trigger
part.
What
this
says
is
I
always
want
this
pipeline
to
run
all
the
time,
every
branch
that
gets
pushed
in
this
case.
D
You
may
want
this
to
only
run
at
specific
times,
so
like,
for
example,
like
I,
have
a
job
I
have
a
separate
Azure
pipeline
that
I
run
for
one
of
my
sites
and
it
runs
whenever
I
do
a
push
to
master,
but
then
it
also
has
a
cron
job
that
says:
go
run
at
four
or
five
specific
times
throughout
the
day
and
because
they
just
want
these
bill.
I
need
these
bills
to
happen
in
specific
times.
D
D
You
can
create
this
thing
called
a
library
or
a
variable
group,
and
what
that
is
gonna
do
is
it
allows
you
to
have
name
value
pairs
where
you
can
go
put
the
dynamic
stuff
in
there,
so
this
would
be
a
great
place
to
put
things
like
usernames
and
passwords,
and
all
of
that
stuff
inside
of
this
Gary
I'm,
not
sure
what
you
mean
by
the
type
of
host
I.
Don't
know
if
your,
if
you
mean
that
the
agent
just
clarify
your
question
and
I,
can
I'm
happy
to
answer
that?
Oh
yes,
okay,
yeah!
D
So
in
this
case
here
you
so
Gary's
asking
in
there
about
the
I'm
gonna
I'm
gonna,
try
it
I'm
gonna
change
his
question.
I'm
gonna
be
a
politician
changes
question
because
I
can
do
the
answer
a
little
bit
better
that
way.
So
what
Gary
is
asking
is,
when
you
run
the
stuff
in
Azure
pipe
lines,
you
have
the
option
to
run
your
your
jobs,
either
on
Windows,
on
Linux
or
on
Mac
OS
or
on
your
own
environment
like
a
container
or
something
like
that,
you
can
define
what
you
want
to
use.
I've
simplified
this
one.
D
A
little
bit,
I've
pulled
out
the
part
where
you
can
say
what
agent
you
want
to
use.
I
do
all
my
builds
on
Linux,
it's
much
faster
than
doing
it
on
on
Windows,
but
that
doesn't
mean
that
Windows
is
bad
or
Linux
is
good
or
anything
like
that.
You
can
totally
set
that
there's
a
whole
option,
there's
a
setting
in
there
within
the
pipeline,
where
you
can
set
that
and
you'll
see
that
in
a
few
minutes.
But
yes,
you
can't
you
have
full
control
over
that
anyway.
D
D
You
can
know
that
so
Lou,
the
question
there
about
the
cron,
the
cron
configuration
that's
the
same
for
Windows
and
Linux
cron
is
just
the
standard.
That's
just
the
turn
industry
term
that
you're
configuring
as
your
DevOps
to
run
these
jobs
specific
times,
so
that
has
nothing
to
do
with
the
difference
here.
D
I
have
those
inside
of
those
credentials
and
you
can
encrypt
the
the
password
so
that
they're
not
going
to
show
up
all
right,
so
they
won't
be
readable
and
you
can
also
map
those
things
to
an
azure
key
Balt
as
well.
If
you
wanted
to
all
right,
so,
let's
get
into
the
work
here.
So
the
way
that
this
all
is
done
is
we
have
these
concepts
of
stages
all
right,
so
a
stage
is
just
a
grouping
of
a
bunch
of
jobs
and
all
of
the
jobs
have
to
succeed
for
that
stage
to
be
successful.
D
Now,
in
this
case
here,
it's
kind
of
simple
I
only
have
one
job
really
for
each
one
of
these
for
each
one
of
my
stages.
But
here
what
this
is
doing
is
it
says
this
stage
is
called
build
and
let's
just
ignore
what
depends
on
for
right
now.
That
just
means
it
doesn't
depend
on
anything
which
means
it's
going
to
run
every
time.
I
give
the
bill
the
job,
a
name.
D
Think
of
this
as
like
it's
internal
ID,
it's
got
to
be
alphanumeric,
actually
I,
don't
even
know
if
it
could
be
numeric,
it's
got
to
be
alpha
and
it's
got
no
spaces
and
then
display
name.
Well,
that's
kind
of
obvious
now
what
happens
when
it's
when
a
project
is
built?
You
guys
are
gonna
recognize
this
as
being
SharePoint
framework
developers.
The
first
thing
we
have
to
do
well,
what's
gonna
happen
by
default
without
us
doing
anything,
is
it's
going
to
do
a
git
clone
and
pull
down
our
entire
project?
D
Now
we
can
have
these
pipelines
set
up
for
projects
hosted
and
get
we
get
hub.
We
can
have
them
posted
inside
of
Azure
DevOps
doesn't
matter,
it
can
be
anywhere.
In
fact,
I'll
show
you
one
in
a
minute:
that's
hosted
in
github,
but
it
the
pipeline
runs
inside
of
Azure
DevOps,
but
you
can
just
think
of
when
you
do
one
of
these,
these
one
of
these
jobs.
When
you
see
job
like
this
right
here,
it's
going
to
do
a
checkout
and
you
can
control
that.
D
D
D
So
some
of
you
may
look
at
that
and
say
that
looks
a
little
weird,
that
is
the
beta
version
or
the
preview
version
of
the
gulp
task,
the
the
ga
version,
which
apparently
wasn't
really
GA
gulp
at
one,
had
a
bug
in
it
and
I
found
that
it's
kind
of
cool
when
you
find
a
bug
in
something
production
and
you
convinced
Microsoft,
but
it
is
a
bug
and
they
fixed
it.
The
fix
is
still
rolling
out
and
so
I've
cut
a
few
things
out
here.
D
You're
gonna
see
where
those
things
where
are
those
things
were
in
a
few
minutes
but
effectively
well
I'll
explain
why
in
a
little
bit,
you'll
understand
why
but
yeah
I
had
to
explicitly
specify
where
the
in
gulp
file
that
j/s
file
was
and
when
you
did
it
with
the
the
at
the
at
one.
You
may
be
wondering
like
why
I
didn't
have
to
do
that.
Well
again,
just
hold
your
horses.
I'll,
come
back
to
that
second
step.
We
want
to
run
gulp
bundle
ship.
How
do
you
do
that?
You
say
run
the
gulp
task.
D
The
task
is
a
bundle
and
the
goldfish
ship,
so
you
notice
here
you
get
these
different
tasks
of
these
things
ahead
of
time.
Yes,
horses,
there
goes
Chris
wakes
up.
Ga
stands
for
general
availability,
in
other
words
its
production,
it's
released
when
you
see
these
tasks.
These
are
things
that
have
been
defined
ahead
of
time
by
the
azure
DevOps
guys
what
why
they
are
DevOps
team.
You
can
also
create
your
own
custom
things
as
I'll
do
in
just
a
minute,
so
the
last
one
we
had
to
do.
D
Now
this
piece
here,
no
Ralph,
you
don't
have
to
I.
Just
do
it
to
be
explicit
now
this
next
piece
right
here
is
I
want
to.
You,
want
to
publish
I,
want
to
save
this
SP
pkg
file.
Ok,
so
I
just
skip
this
step
right
here
and
let
me
explain:
let
me
let
me
come
back
to
this
in
just
a
minute.
I'm
explain
what's
going
on
here,
so
this
piece
right
here
about
publishing
the
the
artifact.
D
What
I
need
to
do
now
that
I've
generated
I
built
this
SP
pkg
file,
it's
on
the
virtual
machine
or
on
the
agent,
where
my
build
is
happening.
I
need
to
take
that
file
and
put
it
somewhere
shared,
so
other
stages
in
my
pipeline
will
have
access
to
it
and
that's
that's
called
publishing
an
artifact,
so
I'm,
effectively
upload
this
file
to
a
shared
folder.
Think
about
it
like
that,
okay,
so
I'm
saying,
go,
publish
an
artifact!
D
What
artifact
I'm
using
these
variables
that
we
get
inside
of
Azure,
DevOps
I'm,
saying:
go:
look
inside
the
current
local
path!
Look
in
the
slash,
SharePoint,
slash
solution!
You
guys
are
familiar
with
that
and
grab
this
file
right
and
I
want
you
to
publish
that
as
an
artifact
name,
SPF
X
package
now
you're
like
well
wait
a
minute.
Where
is
this
coming
from?
D
This
is
coming
from
this
step
right
here
you
have
to
know
you
when
you,
when
you
publish
a
file
or
when
you
you
you
even
when
you
upload
it
to
SharePoint
Online
to
a
catalog
or
when
you
go
to
install
it.
You
have
to
know
the
exact
file
name
and
that
can
be
a
that
can
be
a
pain
because
every
project
is
gonna,
have
a
different
file
name,
and
so
what
I
did
here
is
I
created
this
little
bash
script,
and
what
this
does
is
it's
running
a
bash
commander.
D
This
works
on
Linux,
if
you're
doing
it
on
Windows,
you're
gonna
have
to
write
a
separate
command
for
this,
but
in
this
one
here,
what
it's
doing
is
is
I'm.
Creating
this.
This
method
here
think
of
it
like
a
little
function.
That's
gonna
run
to
find
something
I'm
looking
for
a
file
named
this
and
then
I
want
to
get
just
the
base
name
out
of
it,
so
it
would
be.
D
If
my
file
was
hello
world
that
SP
pkg,
then
the
result
of
this
entire
run
is
hello
world,
then
down
here
on
this
echo
statement,
what
I'm
doing
is
doing
you
use
a
syntax
that
looks
like
this.
What
it's
doing
is,
is
it's
telling
it's.
It's
gonna
run
something
on
the
command
line
on
the
agent,
but
it's
gonna
get
sucked
out
of
the
command
line
into
a
variable,
so
I'm
saying
create
a
variable
for
this
task
named
SP
pkg
file,
name
and
I.
D
Want
it
to
be
an
output
variable,
go
run
this
command
and
stuff
the
value
of
this
command
or
the
result
of
it
inside
that
variable,
so
that
I
have
this
thing
called
get
SharePoint
package
with
this
variable
name:
tada,
that's
where
I'm
getting
the
name
right
there
make
sense,
so
makes
things
a
little
kind
of
cool,
okay.
Well,
that's
builds
running
off
on
the
side.
I
want
to
test
my
stuff,
so
same
deal.
I've
got
a
bunch
of
unit
tests
that
have
been
set
up
here.
So
how
am
I
gonna
do
this?
D
Well
again,
this
is
a
totally
separate
thing.
That's
running
on
a
totally
different
virtual
machine
or
on
a
totally
separate
instance,
so
I
need
to
do
everything.
I
need
to
go
to
an
install,
I
need
to
do
a
build
and
then
I
need
to
run
all
my
tests
in
this
case
here.
This
was
an
update
that
was
provided
here
from
some
Indian
community.
We,
if
you
have
any
failures
in
your
tests,
it's
a
good
idea
to
say
continue
on
air
is
true
so
that
you
can
still
publish
your
code
coverage
results
and
your
test
results.
D
But
if
there
was
a
failure
in
the
test,
I'll
fail
it
when
I
actually
go
after
I
published
the
test
results.
So
this
is
a
cool
little
trick
so
that
you
still
get
all
the
reporting
stuff
that
you
want
code
coverage
is
just
gonna.
Show
you
like
how
what
lines
of
code
have
been
covered.
You
know.
That's
all
unit
testing,
stuff,
I'm
gonna
dive
into
that
kind
of
detail
right
now,
all
right!
So
now
we've
got
our
build,
has
run
and
our
test
has
run
and
we
have
an
artifact
couple.
Artifacts
that
have
been
generated.
D
We've
got
our
SP.
Pkg
file
has
been
generated,
we've
got
our
test
results
that
have
been
generated
and
we
got
our
code
coverage
report.
That's
been
generating
they've
all
been
published
to
our
pipeline
now.
The
next
step
is
gonna,
be
deployment
and
I'm
doing
two
deployments
here.
The
first
one's
going
to
play
to
a
dev
environment.
Second
was
gonna
play
to
a
production
environment.
So
the
exact
same
thing:
I'm,
just
gonna,
look
at
the
production
environment
right
now,
so
here
this
is
a
little
bit
different.
D
This
is
a
little
bit
different,
so
see
this
depends
on
this
says
only
run
this
somebody
is
not
on
mute.
If
you
wouldn't
mind,
please
mutant
yourself,
so
this
depends
on
what
this
is
saying
is
there
are
two
other
stages,
main
build
and
test.
Remember
we
have
one
up
here
called
test
and
we
have
one
up
here
called
build.
This
says
down
here
only
proceed
with
my
deployment
here.
D
It
is,
this
says,
only
proceed
with
this
stage
if
those
two
things
past
so
my
build
and
tests
are
gonna
run
in
parallel
and
if
either
one
of
them
fail,
no
deployment
happens.
You
got
a
red
build
and
that's
where
we
go
find
somebody
find
the
developer
gather
on
his
desk
and
start
yelling
out.
Shame.
Shame.
Shame
now
this
job,
if
you
notice
from
the
builds,
is
a
little
bit
different
because
he's
no
longer
a
job
he's
a
deployment.
This
is
a
special
kind
of
a
job.
D
This
is
different
and
yeah
more
pipelines
than
what
we
had
in
the
traditional
pipelines,
because
this
is
indicating
that
something
is
going
to
be
is
going
to
be
shipped.
This
is
kind
of
the
replacement
for
the
release
stuff
that
we
used
to
do
so
deployment
there
you
go
displayname
going
to
give
a
friendly
name
in
the
environment
is
something
that
can
go
back
and
look
and
see
hey
this
environment.
D
Let
me
see
all
the
times
I've
deployed
to
this
and
I
can
roll
back
to
the
thing
was
that
it
was
deployed
to
it
all
this
strategy
run
once
the
ploy
steps
don't
worry
about
what
the
other
options
are
there?
That's
all
you
got
right
now
is
the
run
once
strategy.
They
are
adding
additional
ones
like
if
you
guys
are
familiar
with
green
blue
there'll,
be
stuff
like
that.
All
right
next
up,
I
want
to
do
my
deployment.
Well,
how
do
I
do
my
deployment?
D
Well,
yours
truly
isn't
a
fan
of
PowerShell,
so
we're
gonna
go
with
the
office
365
CLI,
and
so
what
I
have
to
do
is
that
it's
most
is
probably
likely
that
my
agent
or
that
the
office
365
CLI,
doesn't
exist
on
the
hosted
agent.
We
only
need
a
sharepoint
online
space,
so
I'm
going
to
first
install
the
office
365
CLI,
see
Ralph's
got
a
question
here.
D
To
make
things
run
in
parallel
means
having
their
own
agent
parlance
of
no
agents
having
multiple
eight
so
that
we're
having
things
run
in
parallel
is
when
you
have
two
stages:
you'll
see
that
so
right
now,
I
have
four
stages:
total
I
would
have
to
have
I
would
have
to
we'll
talk.
I
can
talk
about
licensing
at
the
end
of
there's
time.
I
really
don't
want
to
be
someone
developer
and
I
like
that
stuff,
but
you're
you
get
one
everybody.
If
you
have
as
your
DevOps,
you
get
one
agent.
D
You
can
buy
more
agents
that
can
run
in
parallel,
but
in
this
case
here
my
build
would
run
and
my
test
would
run,
but
they
won't
run
in
parallel,
because
I
only
have
one
agent.
Those
are
two
separate
stages.
My
deployments
each
one
of
those
is
gonna
run
separately
as
well.
If
I
had
two
agents,
two
hosted
agents
or
if
I
had
like
say
multiple
containers
that
I'd
set
up
and
did
where
called
self
hosted
agents
and
there's
a
cost
associated
with
that,
then
I
could
have
multiple
things
and
run
them
in
parallel.
D
These
are
variables.
Coming
from
that
variable
group
that
I
defined
at
the
top
okay,
so
I've
logged
in
then
I
need
to
go
download.
The
pipeline
artifact
I
need
to
go
download
that
SP
pkg
file
I
got
to
download
that
guy
into
this
deployment
stage
now
I
have
a
local
copy
of
what
am
I
downloading
the
thing
that
was
named
SPF
SPF
X
package?
Well,
that's
not
really
the
name!
D
Remember
it's
like
hello,
world
SP,
SP,
SP
pkg,
so
I
got
to
get
the
name
of
it
again,
so
I
grab
the
name
of
it
and
then
it's
just
standard
deployment,
hello,
365,
SharePoint,
Online
at
an
app
where's
the
file.
It's
right
here.
Where
is
it
going?
There's
the
URL?
This
is
a
site
collection,
scope,
app,
catalog,
I'm,
gonna,
overwrite,
anything,
that's
currently
there
and
then
say:
I'll
skip
deployment
next
step,
I'm
gonna,
do
the
deployment
phase,
tada,
ok
and
in
production
the
exact
same
thing
just
going
to
a
separate,
URL
and
you're
like.
D
Why
are
you
doing
it
twice
again,
we'll
talk
about
it
later?
What
does
it
look
like?
Here's?
What
it
looks
like
check
this
out,
so
this
is
one
that
has
been
run.
We've
got
our
three
different
agents
that
run
so
this
is
an
entire
pipeline.
So
if
I
go
to
my
agile
devops
for
pipelines,
so
here's
I
have
one
pipeline
that
set
up
now
for
you
to
be
able
to
get
these
pipelines
that
are
shown
up
here.
You're
gonna
have
to
come
over
here
into
your
azure
dev
ops.
D
Might
not
look
this
good
I'm,
not
I'm,
a
joke.
That's
a
joke!
You're
gonna
come
over
here
to
preview
features
and
you
have
to
make
sure
that
this
guy
is
enabled
multistage
pipeline.
This
is
what
gives
you
your
opting
into
the
preview
features
of
Azure,
DevOps
and
Duhamel
pipelines
once
you
do
that,
then
you
see
pipeline
show
up
here
on
the
left,
so
I
added
a
new
pipeline
and
then
it'll
ask
you:
where
do
you
want
the
pipeline
to
be
so
I?
D
Have
it
inside
of
in
this
case
it's
a
github,
repo,
sorry
I'd,
say
github
repo
and
then
it's
gonna
ask
me
what
what
repo
you
want
to
have
access
to
and
all
that
so
which
is
a
different
project.
You
have
access
to.
Do
you
want
to
use,
and
then
you
end
up
picking
the
file
as
your
pipelines
that
yamo
all
right?
Let's
go
back
to
this,
though,
do
two
pipelines
alright.
Here
we
go
so
here's
one
that's
run
so
this
is
one
instance.
That's
run
for
this
guy.
D
Okay,
ignore
the
fact
that
it
broke
a
couple
times.
So,
if
I
click
into
this
guy,
what
do
we
see?
Well,
here
our
stages,
there's
my
build
stage
and
there's
my
test
stage
and
notice
that
both
of
these
guys
passed
and
then
they
went
into
the
deployments.
Can
you
change
variable
groups
per
environment,
yes
and
actually
Nick
I'm,
going
to
show
you
how
I
do
that
in
just
a
minute,
because
this
is
gonna
get
a
lot
easier
in
just
a
minute.
So
here
we
can
see
all
the
details
of
it.
D
You
can
see
what
artifacts
were
published.
Well.
I
can
see.
There's
my
SP
pkg
file
that
was
published
and
there
it
is
my
all
of
your
react.
I
can
does
the
email
files
be
created
manually,
yes,
but
I'm
going
to
show
you
how
that's
easy
here
in
just
a
second
here's.
My
test
number
I
published
my
test
results:
sweet
no
test
failures
right,
so
I
got
all
my
tests
got
published
up
here
because
I
published
the
test
results.
D
What
about
my
code
coverage
results
same
deal,
I
published
the
report,
so
I
can
even
dig
in
and
see
all
the
results.
My
code
coverage
my
testing.
What
about
my
environments?
I,
can
see
what
got
deployed
to
the
development
environment.
I.
Can
see
when
things
got
deploy?
What
the
last
thing
was
that
was
deployed
here
now
back
up
a
bit
check
out
one
of
these
jobs,
so
you
can
see
some
of
the
details
with
this.
So
here
here's
what
this
guy
looked
like.
D
So
this
one
took
about
a
minute
and
50
seconds
you
can
see
here.
It
first
went
through
it,
checked
everything
out
and
then
installed
everything.
So
you
can
see
the
details
of
what
ran
so.
It
ran
NPM.
Install
next
step.
Ignore
these
guys
they
didn't
run.
You
can
see
how
they're
not
they're
not
filled
in
SharePoint
framework
build.
So
there
we
go
recognized.
All
that
stuff
looks
like
a
SharePoint
framework
build
to
me.
You
guys
have
seen
this
before
now.
D
Here's
where
it
gets
kind
of
cool
load,
so
remember:
I,
said
that
we've
got
to
deploy,
deploy
to
development
and
I,
have
a
deploy
to
production,
so
check
this
out
mer
virus,
so
I
had
my
production
environment.
Here's
why
I
have
two
separate
environments
I'm
deploying
to
both
on
because
I
always
want
dev
to
be
having
the
latest
and
greatest
stuff,
but
with
production
I
don't
ever
want
it
to
manually.
Go
out.
I
want
to
have
a
check
here.
I
want
to
put
a
manual
approval
check.
D
That's
going
to
force
myself
to
say
you
need
to
manually
ok
this,
and
what
will
happen
is
this
job.
This
deployment
to
production
will
get
to
this
point
and
it
will
stop,
and
it
will
send
me
an
email
and
say
you
need
to
come
in
here
and
approve
this,
and
so
when
I
go
into
it,
I
go
I.
Click
on
the
link
and
I
come
to
Azure,
DevOps
or
I
hook
up
the
whole
team
integration
to
it.
I
click
approve
and
then
it
will
flow.
So
you
have
that
you
can
have
eyes-on,
ok,
pretty
cool!
D
All
this
stuff
works
right
and
you
can
see
here
I'm
able
to
see.
Let's
see
all
these
pipelines
I'm
able
to
see
like
all
the
stages
that
succeeded
and
when
things
were
actually
running
I
could
see.
I
would
see
things
running
as
well.
Ok!
Now
it's
all
really
cool
here,
but
this
can
be
a
little
challenging
to
write
one
of
these
really
big
files,
so
I
did
something
to
make
light
your
life
a
little
bit
easier.
D
So
I
created
this
project
called
agar
pipelines,
SPF
X
templates
I
created
these
templates
and
what
these
templates
are
are
they're
separate
templates
for
each
one
of
the
different
stages
like
the
build
stage
or
the
deploy
stage.
So
I
think
so
we
had
a
question
earlier,
which
was
well.
Can
I
have
different,
like
environment
variables,
set
for
these
different
things,
all
that
stuff
that
I
showed
you
a
second
ago.
It
looks
pretty
much
the
same,
except
would
it
be
nice
if
I
could
swap
out
the
URL
or
swap
out
the
user
names?
D
You
totally
can
do
that.
The
way
you
do
that
as
up
here
is
I've
created
this
template
and
I've
specified
all
these
parameters
that
have
to
be
passed
in
notice.
Here.
I
even
have
a
default
where
we're
using
Ubuntu,
but
you
can
change
and
use
a
different
agent
if
you
want
it
to
like.
If
you
want
to
use
Windows
so
I've
got
these
parameters
set
up
for
these
jobs,
so
you're
wondering
ok
cool.
D
How
does
it
look
to
actually
use
this
well
in
this
project
if
you
come
over
here
to
the
sample
first
of
all,
but
the
help
tells
you
everything
on
how
to
do
this
in
the
sample
project.
There
is
a
SharePoint
framework
project
here
that,
if
you
click
on
Azure
pipelines,
this
yellow
file
you'll
see
one
new
thing
listed
right
here,
right
after
the
trigger
before
you
get
the
variables
I'm
pointing
to
a
github
repository
I'm,
giving
a
specific
name.
D
It's
a
github
name
and
I
had
to
create
an
endpoint
for
this
at
the
endpoint
is,
what's
called
a
service
connection.
So
in
my
project
and
as
your
DevOps,
if
you
come
over
here
to
your
project,
settings
you'll
have
this
thing
called
service
connections
where
you
have
to
define
a
service
connection
that
effectively
says
this
is
how
I'm
connecting
to
github
and
here
my
credentials
and
how
you're
gonna
connect
to
it.
D
So
I
set
the
credentials
up
and
everything
it's
separate
from
the
pipeline
itself,
so
once
I've
set
that
up
and
it
gave
it
a
name
of
boitano's
github
I'm,
saying
you're,
gonna
use
for
autonomous,
github
and
you're
gonna
connect
to
this
github
repo
to
get
up
repo,
and
this
is
the
the
repository
that
you
want
to
get.
What
that
does
is
that's
gonna
suck
in
the
it's
gonna
clone
the
repo,
so
that
now,
when
I
get
into
my
build
stage,
it's
then
going
I
convince
a
instead
of
specifying
out
the
whole
job.
D
I
can
just
say,
use
the
template,
jobs
and
then
I
want
to
change
the
parameters
or
like
in
my
deployment,
job
I'm
gonna
change
the
parameters
to
use
this
name,
this
username
and
password
this
URL,
my
dev
environment,
site
collection.
Anything
else
I
want
to
do
on
the
top
end
and
then
same
thing.
I'll
do
the
same
thing
for
production
and
list
that
out
all
right
here
so
now.
This
is
that
entire
file
that
I
showed
you
a
minute
ago.
D
D
That
allows
you
to
say
if
I
only
want
like
the
version,
one
of
these
templates-
and
you
don't
want
to
be
like
if
we
make
an
update
to
it
and
we
add
some
new
features
and
change
functionality,
you
may
not
want
your
build
pipeline
to
change
without
notice,
so
you
may
want
to
pin
your
stuff
to
these
specific
things,
and
so,
where
do
we
tag
stuff?
You
can
you
can
pend
to
a
specific
branch
you
can
spit.
You
can
pend
to
a
specific
tag.
D
It's
all
listed
there,
okay
and
it
documents
everything
you
need
to
do
on
how
you
set
this
up
and
all
the
explanation
of
the
stuff,
and
if
you
need
any
more
explanation
of
this
stuff,
I'll
wrap
up
with
this
I
have
a
blog
post.
That
explains
this
whole
thing
on
how
to
automate
everything
this
whole
all
the
stuff
and
using
those
templates.
If
you
want
okay,
and
so
with
that,
I
think
there
might
have
been
a
question
or
two
that
came
up
that
I
might
have
missed.
D
So
if
you
that's
everything
that
I
wanted
to
that's
everything
that
I
wanted
to
show
besa
and
I'ma
be
answering
any
questions.
If
anybody
had
any
questions
to
this
I
believe
that
should
technically
work
on
Prem
as
well.
Jag
I
said
this
earlier.
Some
of
it
does,
it
will
work
on
the
build
and
the
test
stuff
should
work.
Well,
I
kind
of
your
your
mileage
may
vary.
D
The
deployment
stuff
absolutely
won't
work,
because
deployment
requires
the
ale
and
rest
api's
to
be
able
to
deploy
stuff
so
and
that's
not
on
Prem,
that's
only
in
SharePoint
Online.
Second
of
all,
this
whole
thing
with
gamma
pipelines
is
a
preview
feature
for
Azure
DevOps
in
the
cloud
version,
not
for
the
on-prem
version.
So
what
I
showed
for
some
of
the
stuff
that
I
showed?
Yes,
you
could
do
it
on
Prem,
but
I
have
no
idea
what
the
state
of
the
whatever
they
call
it
DevOps
on
Prem
or
VST
s
on
Prem
or
whatever.
D
That
is
I,
don't
know,
I,
don't
know
what
the
story
is
there
for
this.
You
can
employ
220
musing
PNP
PowerShell,
the
api's
are
in
2019.
Oh
I
didn't
know
that
okay,
so
as
your
dev
appserver,
thanks
Vincent,
so
I
mean
if
there
it
then
yeah.
You
could
change
this
setup
here
and
if
you
could
do,
if
there's,
if
there's
a
way
to
be
able
to
deploy
programmatically
yeah,
you
can
do
anything
you
can.
D
D
So
the
way
it
works
is
that
if
you
have
now,
let's
just
talk
about
the
hosted
version
about
I'm,
not
gonna,
even
try
to
broach
the
topic
on
on
Prem
for
the
hosted
version
you
get
one
agent
for
free,
let's
see
if
I
can
pop
this
up.
In
my
account
so
where's
my
agents
agent
pools.
Ok,
so
you
get
one
agent
for
free,
ok
and
that
one
agent
can
be
a
Windows
VM
or
Linux
VM
or
whatever
they
have
a
template
of
the
different
VMs
that
are
available.
D
I
forget
so,
if
you
have,
if
you
have
a
MSDN
subscription,
you
do
have
Azure
devops
with
your
account
and
you
get
one
hosted
agent.
So
that's
like
a
virtual
machine
if
you
needed
and
it
comes
with
I
believe
the
30
hours
of
runtime
per
month.
If
you
want
to
go,
if
you
want
to
add
additional
minutes
like
if
you
run
out
or
if
you
want
to
add
additional
agents
so
that
you
can
run
parallel
jobs,
then
that
is
$40
per
agent
per
month
for
hosted
agent
per
month.
D
Another
option
like
I
use
this
company
here,
where
is
it
voltar,
so
I
use
this
company
to
set
up
to
create
a
virtual
machine?
It's
super
cheap,
they're,
dirt,
cheap
VMs
and
then
I
created
I.
Guess
you
can
I'll
show
you
this
too.
If
you
want
to.
If
you
want
to
explore
this
is
very
much
use
at
your
own
risk.
D
There
I
created
an
agar
pipeline
Linux
agent,
and
this
is
a
docker
container
and
I.
So
I
created
a
virtual
machine
that
was
like
20
bucks
a
month
and
I
put
two
two
of
these
containers.
Instances
on
that
agent
and
what
they
do
is
they
connect
as
your
dev
ops
and
as
an
MSDN
subscriber
you
get
two
of
your
own
user
hosted
agents
that
you
can
use
so
I
was
using
those
I
found,
I
use
those
for
some
stuff,
I,
don't
use
it
for
other
things,
because
they
just
run
into
some
performance
things.
D
But
you
can
do
that
if
you
want
to
do
that
with
containers,
you
can
definitely
do
that
as
well,
and
so
I
was
doing
that
to
not
have
to
spend
another
40
bucks.
Instead,
I
was
effectively
spending
$20
a
month
and
getting
two
agents
to
get
the
parallelism
out
of
it.
Instead
of
spend
40,
if
you
can
add
additional
user
hosted
agents
at
a
tune
of
15
dollars
per
month,
you
have
to
pay
for
the
actual
that
the
whatever's
gonna
host
the
agent
itself.
D
So
if
you
create,
like
a
sure
vm's
each
one
of
those
vm's
is
gonna
cost
you
whatever
the
consumption
is
for
those
and
then
you
have
to
pay
the
15
dollar
tax
to
you
to
hook
it
up
to
as
your
dev
ops.
That's
what
you
saw
when
I
went
over
to
these
pools
here,
and
you
saw
a
list
of
all
of
these
agents
that
were
dead.
These
were
old
containers
that
I
wasn't
using
anymore
and
I
just
recently
killed
these
guys
as
well.
But
these
are
different.
D
A
I
think
this
is
a
good
place
to
jump
back
to
the
slides.
So
we'll
do
that
and
folks
will.
Let
me
know
when
they
could
see
those,
of
course,
but
want
to
thank
everybody
for
joining
the
call
today
once
you
of
course
thank
Rahm
and
Andrew
for
the
awesome
demos
great
stuff,
for
both
of
you
so
really
appreciate
that
and
if
I
can
go
to
the
next
slide.
The
next
sharepoint
development
special
interest
group,
which
would
be
next
Thursday,
is
canceled,
and
this
is
because
ignite
we
got
all
the
folks
are
in
ignite.
A
Imagine
many
of
you
will
be
at
ignite
and
it's
just
easier
for
everybody
to
just
kind
of
cancel
for
next
week.
So
sorry
about
that
you'll
miss
one
week
of
us,
but
we'll
be
back
on
November
7th
with
another
SharePoint
framework,
a
Java
Script
special
interest
group
on
November
7th
and
the
general
dev
cig
will
pick
back
up
as
you
might
expect
on
November
14th.
A
So
if
those
of
you
who
are
travelling
to
ignite
have
safe
travels
and
have
a
lot
of
fun
there
and
look
forward
to
well,
I
won't
be
there,
but
so,
though,
I
don't
look
forward
to
seeing
you
but
I
look
forward
to
hearing
all
about
it
and
I
hope.
Everybody
has
a
great
time.
I
know,
there's
a
lot
of
really
awesome
announcements
and
some
great
sessions
there.
So
do.
Please
have
some
fun
and
safe
travels,
and
thank
you
all
for
joining
the
call
this
week
and
we'll
talk
soon.
Buh-Bye.