►
From YouTube: SheCodeAfrica 2021 04 16 PM
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
B
B
A
That's
completely
strange,
I
don't
know
what
I
did
with
our
notes
document.
Have
I
not
been
taking
notes
while
we've
met
together.
A
Okay,
well
I
like
to
start
on
time,
so,
let's
I'm
going
to
turn
oh
and
it's
already
recording
that's
even
better
great,
so
we're
recording
and
thank
you
for
being
with
us.
We
intentionally
don't
enable
video,
because
that
way
you
can
join
from
low
band,
lower
bandwidth
connections.
If
that
helps.
A
C
C
I
have
something
so
my
question
is
what's
different
in
the
jenkins
and
other
plugins,
because
I
did
when
I
was
trying
to
work
on
it
on
the
I
couldn't
see
like
a
hpi
and
they
they
they
failed
to
use.
So
I
can
upload
it
in
like
they.
I
can
upload
it
locally.
C
A
Okay,
so
so
let
me
I'm
going
to
try
to
say
back
to
you
what
I
think
your
question
is.
You
can
then
correct
me
if
I'm
wrong
on
what
the
question
is.
So
your
question
is:
what's
the
distinction
between
a
jenkins
plug-in
where,
in
order
to
see
changes
to
the
plug-in,
you
upload
the
hpi
file
into
jenkins
and
look
at
it
or
your
work
in
jenkins
core
and
by
the
way
you
just
submitted
a
pull
request
to
jenkins
core
well
done.
A
A
A
C
A
When
you
need
to
make
changes
to
jenkins
core
it's
right
inside
the
jenkins
core,
and
then
it
has
to
be
recompiled
or
or
reloaded.
There
are
actually
ways
to
do
the
same
same
style
of
interaction
with
jenkins
core,
as
you
do
with
plugins.
It
actually
could
be
a
little
easier.
It's
just
uncommon
that
you
need
to
make
a
change
in
jenkins
core,
so
the
maven-
and
I
believe
in
that
case
it's
called
jetty.
A
A
A
Was
there
did
you
have
additional
questions
related
to
that
or
or
things
that
you
found
perplexing
I'm
I
was
really
pleased.
I
wasn't
expecting
any
of
any
of
you
to
submit
changes
to
jenkins
core
and
I'm
delighted
that
you
did
and
you
found
found
a
way
to
do
it
yourself.
Well
done,
did
you
did
you
before
you
submitted
your
pull
request
to
jenkins
core?
Did
you
actually
build
jenkins
core
and
see
that
the
text
was
visible.
C
Yeah,
so
that's
the
issue
I
missed,
but
angelique
sent
me
some
of
the
code.
I
can
use
to
run
it
locally,
so
I
need
to
do
that.
A
A
Are
there
other
questions
that
you
have?
If
not
what
I
was
going
to
do
was
I
was
going
to
go
through
the
the
various
documents
that
you've
been
using
and
I
was
going
to
share
those
on
screen
and
see.
If
I
could
ask
each
of
you
in
turn,
if
there
were
things
you
you
experienced,
that
you
wanted
to
help
with
or
other
areas
based
on
the
documents
that
we've
been
collecting.
A
A
A
D
A
Okay,
so
so
you
added
the
help
but
you're
not
sure
how
it's
going
to
look
when
when
seen
online.
So
we
could
show
today
how
to
view
that
online
from
from
the
computer,
where
you're
doing
the
checking
that
it
actually
works.
D
A
It
actually
ends
up
in
both
places.
So
when
you
add
the
help,
that's
a
very
good
question
when
you
add
help
to
a
jenkins
pipeline
implementation
inside
of
jenkins
plug-in.
So
so,
for
instance,
in
your
case,
I
think
you're
working
on
the
pipeline
nodes
and
processes
plug-in.
So
if
you
add
help
or
improve
the
help
for
the
bat
step
or
for
the
node
step
or
for
the
power
shell
step
any
one
of
those
steps.
A
When
you
do
that,
it
will
be
included
into
the
next
and
once
the
pull
request
is
merged,
it
will
be
included
in
the
next
release
of
that
plugin
and,
after
that,
next
release
of
that
plugin.
It
will
also
be
visible
on
the
www.jenkins.io
site
after
that
plugin
has
released.
So
it
would
both
be
available
online
in
every
users,
jenkins
installation
that
has
installed
the
plugin
and
on
the
master
documentation
page
at
www.jenkins.io,
and
you
can
actually
thank
kristen
for
that,
because
she
wrote
the
original
tool
that
reads
the
contents
of
the
released
plugin
and
publishes.
D
A
Different
sorry
go
ahead
and
say
that
again
windows
or
linux
or
mac
windows-
okay.
So
if
it's
all
right,
it'll
take
a
little
bit
more
time
to
show
the
demo
on
windows,
but
I'm
on
windows.
So
maybe
it's
if
it's
okay
with
you
and
with
others
I'll
show
it
on
windows,
and
that
way
the
recording
may
be
more
helpful.
If
you
need
to
look
at
it
later,.
A
All
right,
so
I'm
going
to
just
start
sharing
my
screen
and
we're
going
to
go
through
a.
How
do
you?
How
do
you
do
jenkins
on
a
windows
computer
and
then
how
do
we
work
with
a
plug-in
and
ester?
If
it's,
okay
with
you,
I'm
going
to
use
the
nodes
and
processes
plug-in
or
would
people
prefer
that
I
use
something
different,
that
none
of
you
have
done
yet?
Nodes
and
processes
is
easy
enough
and
it's
a
good
excuse
to
make
something
that
might
be
helpful.
A
A
The
files
that
are
on
that
directory
and
in
it
there's
this
contributing.md
file
and
it
contains
inside
of
it
the
instructions
on
how
to
do
a
build.
So
this
is
the
command
I
want
to
use.
It
says
if
you
want
to
just
build
it
as
fast
as
possible,
without
test
just
do
this,
so
I'm
just
going
to
copy
that
and
go
ahead
and
run
here.
A
Now
we've
I've
found
at
least
for
my
observation.
That
windows
tends
to
run
a
little
bit
slower
than
my
linux
experiences.
Do
I
assume
that's
because
of
virus
scanning
that's
happening
and
other
conveniences,
so
this
may
take
a
little
bit
and
we'll
talk
while
it's
while
it's
building
so
right
now.
What
it's
doing
is
it's
downloading
dependencies
making
sure
it
has
the
most
current
dependencies
and
now
it's
going
to
start
the
compilation
process.
A
A
A
A
A
A
Install
kristin,
I
think,
that's
a
reasonable
way
to
do
it.
If
I
remember
correctly,
for
for
others,
are
there
better
suggestions
you
have
to
offer
than
clean,
install
or
is
that
a
workable
way
to
do
a
build
to
get
started
on
a
plug-in.
B
Install
works
just
as
long
as
it
ends
up
creating
the
package
or
like
it
ends
up
going
through
the
package
step
at
the
end
of
maven,
and
the
install
will
do
it
as
long
as
you.
A
A
So
the
idea,
then,
is
that
what
I'll
do
is.
I
will
run
jenkins
from
here
and
initially
I'm
going
to
choose
to
install
the
plugin
as
released
after
installing
the
plugin.
That's
released
I'll
just
use
the
jenkins
ui.
To
do
that,
then
I
want
to
be
able
to
make
small
changes
to
this
plugin
that
I
just
created
locally,
compile
it
and
prove
that
my
changes
are
visible.
A
A
A
A
B
A
It's
it's
acting
like
this
is
an
xml
file,
even
though
the
suffix
is
html.
If
I
remember
correctly
right
something
like
that,
where
okay
so
and
then-
and
if
I
want
to
do
a
break,
I
have
to
say
something
like
that:
oh
actually,
maybe
it's
even
better.
Let's
just
use
paragraph
markup
like
it's
supposed
to
be.
A
A
A
A
A
A
A
A
Is
so
that
local
host
colon80-
and
this
is
a
brand
new
empty
jenkins?
Now
we
see
the
the
nice
little
warnings
over
here.
It
says
jenkins,
is
currently
unsecured
and
allows
anyone
on
the
network
to
launch
processes
on
your
behalf,
secure
it
well
in
this
particular
case,
that
message
is
misleading,
because
the
only
ones
that
can
connect
to
this
process
right
now
is
me
on
my
local
computer.
A
It's
intentionally
started
that
it
only
listens
to
things
from
my
local
computer
so
for
as
a
developer,
it's
safe
for
you
to
do
this
inside
your
environment,
other
other
developers
or
attackers,
for
instance,
can't
reach
this,
because
it's
not
listening
to
them.
It's
only
listening
to
connections
on
localhost.
A
A
A
A
A
It
did
not
okay,
so
I
need
to
install
another
plug-in.
I
made
a
mistake:
it's
this
thing
pipeline
colon
declarative
that
I
also
want,
because
I'm
going
to
be
doing
some
work
with
declarative
pipeline
here
and
notice,
it
listed
a
whole
number
of
other
dependencies
is
bringing
those
in.
So
I
had
not
installed
pipeline
basic
steps
or
pipeline
multi
branch.
B
A
All
right
now,
let's
check
it
and
see
if
pipeline
dash
syntax,
yes,
okay,
good!
Here
we
go
all
right
so
now
I've
got
bat,
and
here
is:
let's
see
the
one
I
used
was
the
one
I
modified
was
ws,
allocate
workspace,
and
if
we
look
here
we'll
see,
there's
online
help
on
the
help
over
there.
This
is
the
original
in
the
released
version
of
the
plugin,
and
this
one
gives
okay
more
about
the
the
custom
location
and,
let's
say
a
custom
der
name.
A
A
A
A
A
And
I
am
going
to
go
to
the
advanced
tab,
click
and
I
want
to
upload
a
file
by
clicking
choose
file,
and
now
I
need
to
go,
find
my
home
directory
and
it
was
my
git
directory
jenkins,
workflow
durable
task
step
target
and
there
is
that
hpi
file.
If
I
open
that
and
then
click
upload
now
notice,
what
it
says
here,
it
says:
workflow,
durable
task,
step
plugin
is
already
installed.
A
Jenkins
needs
to
be
restarted
for
the
update
to
take
effect.
So
I
need
to
restart
jenkins
and
the
easy
way
to
do
that
is
I
go
here
and
if
it
works
the
way
it
usually
does
what
I'll
do
is
I'll
hit
enter
and
that
stops
and
restarts
jenkins.
So
all
I
did
was
press
the
enter
key
or
the
return
key
for
it
to
stop
and
restart
jenkins.
And
if
we
now
look
at
this
page,
it's
going
to
tell
us
that
jenkins
is
restarting.
A
So
what
did
I
do?
I
used
my
web
browser
to
upload
jank
upload,
the
new
plugin.
Then
I
hit
enter
in
the
terminal
window
where
I
was
running
jenkins
from
the
maven
jetty.
Colon
run
command
line,
and
now
here
I
am
now.
If
I
look
at
manage
jenkins-
and
I
go
to
manage,
plugins
plugin
is
missing.
Did
I
make
a
mistake?
A
A
A
Okay,
so
so
please
forgive
my
mistake.
Let
me
describe
my
mistake
in
case.
Somebody
else
makes
my
mistake,
so
I
think
anyway,
let
me
so
I
think
what
happened
here
is.
I
have
cloned
a
copy
of
workflow
durable
task
step
and
I
cloned
it
from
my
repository,
which
is
exactly
the
right
thing
to
do,
except
my
repository
is
probably
out
of
date
with
the
upstream
repository.
A
A
B
A
A
A
So
I
have
to
do
this
a
little
bit
harder
way,
and
this
is
what
I've
got
to
do
instead
of
oh
and
look
here,
it
is
the
message
in
in
the
console
window.
If
I
just
come
here
to
look,
I
could
have
seen
the
exact
same
message
as
saying
guess
what
something
went
wrong.
It
cannot
access
the
file
because
it's
in
use
by
another
process
and
what
that
is,
is
the
windows
file
system
saying
I
can't
remove
a
busy
file,
so
I'm
gonna
stop
it.
A
A
A
A
A
There
we
go
so
now,
I'm
going
to
run
jenkins
again,
so
it
looks
like
for
the
the
the
press
return
to
restart
jenkins,
workflow
isn't
as
tidy
on
windows
as
I
would
have
liked
it
to
be
because
of
the
busy
file
the
busy
file
problem
that
the
windows
file
system
has
on
linux
or
on
mac.
Os
you'd
see
that
pressing
enter
just
lets.
You
switch
and
it
will
restart
jenkins.
A
A
B
A
B
A
B
A
A
Well-
and
I
want
to
see
if
it
actually
does
something
with
it,
because
there
are
cases
where
it's
it's,
where
I've
seen:
oh
whoops,
not
archive
artifact.
We
need
ws,
okay.
So
now,
if
I
click
this
nope,
so
it
did
not,
it
did
not
re-read
it
from
the
file
system
right!
Oh,
no!
No
right!
Of
course
it
didn't.
What
am
I
saying?
That's
that's
silly
right!
I
was
just
I
okay.
Remember
it's
a
two-step
process
right.
A
I
can't
make
changes
inside
the
plug-in
and
have
those
changes
be
immediately
visible
when
I
loaded
the
plug-in
into
jenkins,
because
it's
not
watching
this
piece
of
the
plugin
file
system
to
to
find
me.
So
that's
not
going
to
work
now.
I
thought,
though,
kristen
isn't
it
possible
that
this
can
work.
If,
then,
I
run
maven
hpi
colon
run
from
the
plug-in
directory.
D
D
A
A
A
If
I
do
maven
hpi
colon
run
what
it
does.
If
I
remember
correctly,
is
it
will
start
a
jenkins,
oh
and
I'm
going
to.
I
never
remember
which
ver
jenkins
version
people
are
using
inside
their
plugins.
I
like
reasonably
new
versions,
so
I'm
going
to
say
minus
oops,
minus
d
jenkins.version
equals
2.277.2,
because
that's
a
current
current
version
of
jenkins.
B
A
A
That's
a
very
good
question:
okay,
so
esther's
question
was
there's
a
step
return
standard
out
on
the
google
sheets
and
I
think
actually,
rather
than
a
step,
it's
probably
an
argument
and
it's
not
available
in
the
syntax
generator
or
on
the
online
doc.
Okay,
let's
see
if
we
can
find
that.
That's
a
that's
a
good
question!
A
A
A
A
Now,
if
this
is
this
is
a
different
directory
than
the
earlier
ones.
So
if
I
look
at
the
plugins
that
are
installed
here,
you'll
see
it's
got.
Oh,
there
are
some
plugins
that
are
out
of
date.
There
are
plugins
that
need
to
be
upgraded,
but
ignore
all
that
the
nicety
is.
There
is
in
nodes
and
processes
that
2.14
39
snapshot
is
still
there.
A
This
does
not
have
anything
about
return
standard
out
and
it
doesn't
unless
over
here
on
the
right,
I
click
the
advanced
button
and
some
plugins
have
that
advanced
button.
Just
like
that
now,
what
we
see
is
here
is
return
standard
out,
and
here
is
the
help
for
return
standard
output,
so
sometimes
the
the
thing
that
we're
looking
for
is
behind
an
advanced
button.
Now,
let's
try
this.
A
A
A
B
I
think
too,
just
kind
of
looking
at
some
of
the
comments
in
the
sheet,
because
I
would
decide
is
like
hey
what
are
people
I.
I
wasn't
entirely
clear
about
where
you
found
the
return
standard
out.
So
I
was
like
I
just
did
a
search
on
the
page
on
the
user
documentation
sheet
and
it
sounds
like
maybe
another
thing
that
we
should
make
sure
when
we're
going
through
and
doing
these
steps
is
that
there
are
some
defaults
that
are
selected
for
some
of
the
pieces
like
return
standard
out
which
could
be
a
boolean.
B
B
It
might
end
up
being
that
yeah
see
like
a
blue
answer
like
maybe
we
just
need
to
make
sure
that
when
we
find
booleans
we
should
make
sure
we
say
oh
default,
true,
because
you
it
becomes
optional.
So
yeah
I
was
like.
Maybe
that's
why
people
were
not
entirely
sure
because
they
didn't
know
from
this
page
alone
that
either
the
default
is
true
or
false.
But
when
you
do
the
snippet
generator,
you
can
easily
see
right,
because
you
can
either
check
the
button.
B
When
you
open
the
the
snippet
generator,
it
will
either
be
a
check
box
or
an
unchecked
box,
but
it's
not
clear
from
our
documentation
here
what
it
is.
So
maybe
we
should
put
some
stuff
like
like
the
last
sentence
would
be
default
true
or
like
default
false.
That
might
be
something
that
we
should
do
for
a
lot
of
our
booleans.
I'm
not
confident
that
it's
we've
actually
done
that
for
a
lot
of
them,
but
maybe
maybe
that
would
help
people
as
well.
So
that's.
A
A
really
good
find
that's
excellent,
especially
for
anything
that's
optional
right,
because
for
certainly
an
optional
thing,
people
want
to
know
what
is
the
default
value
and
we
ought
to
say
exactly
default
is
is
in
this
case.
Default
is
false
right.
Isn't
that
what
it
says?
So,
let's
go
back
to
see
what
is
the
right.
B
B
A
A
Right
as
well,
very
good,
well
and
okay,
there's
another
one
hiding
here.
This
one
has
two
check:
boxes,
return,
standard
output,
return
exit
status
and
I
truly
have
no
idea
what
happens
when
I
check
both?
Oh
that's.
A
A
B
A
For
bat,
bat
should
get
that,
and
I
am
confident
that
the
same
thing
applies
to
to
powershell
yeah
and
the
same
thing
applies
to
pwsh,
and
the
same
thing
applies
to
sh
right
that
each
of
them
says
should
say:
oh
you
can't.
You
can't
do
this
or
this
because
the
reader
may
not
realize-
and
this
is
another
reason
why
we
want
to
keep
reminding
people
use
the
snippet
generator.
A
A
A
That
may
be
a
help
for
you
as
you're,
trying
to
add
pipeline
examples
into
the
plugins
that
you're
working
on.
So
what
she'll
do
is
show
you
some
different
repositories
and
google
search
techniques.
You
can
use
to
find
other
people's
pipeline
examples
that
we
can
borrow
that
we
can
put
into
the
documentation
so
that
you
don't
have
to
spend.
A
A
A
A
A
A
A
A
A
A
A
A
A
And
no,
that's
not
it!
Oh
there,
it
is
okay
allocates
a
workspace.
Now
I
am
curious
kristin.
Why?
Oh?
Oh
I
see
why
the
two
question
marks
there
and
I
think
the
answer
is
because
one
is
for
the
custom
location
and
the
other
is
for
the
the
workspace
step
itself,
and
there
is
my
example
with
the
awkward
and
embarrassing
thing
that
I
didn't
get
the
indentation
correct.
A
All
right
so
cynthia
I'll
do
I.
I
look
forward
to
reviewing
your
pull
request
to
jenkins
core.
If
others
of
you
are
and
when
others
of
you
submit
pull
requests,
it
would
help
us
a
bunch
if
you
could
paste
a
link
to
your
pull
requests
into
the
slack
channels
into
the
slack
channel
so
that
we
know
to
go
review
it
or
you
could
copy
us
by.
A
Let's
see,
let's
see
if
I
can
show
how
you
do
that
if
you
just
put
a
specific
annotation
on
on
your
pull
request.
So
let's
go
look
at
cynthia's
pull
request
here,
added
some
examples
of
how
to
archive
multiple
artifacts
she
put
at
mark
e
weight,
and
that
was
that
one
sent
me
a
reminder:
email.
Oh,
I
should
review
this.
A
C
A
A
A
A
But
now
what
you
will
see,
cynthia
on
your
user
interface
is
you'll
see
this
here
I
made
a
comment
and
here's.
My
comment
and
you'll
be
able
to
click
this
button
and
actually
say:
oh
yeah.
I
like
that
I'll.
Take
that
change.
You
can
just
do
it
right
from
your
web
web
browser
without
having
to
even
go
into
your
command
line
and
interacting
with
git.
A
A
Oh
yes,
on
your
and
your
pr
was
your
p.
Your
pr,
I
think,
was
to
the
artifactory
repository
right
yeah
and
that
one
that
one
is
going
to
be
very
interesting
because
it
actually
operates
with
slightly
different
rules
and
and
we're
going.
So,
let's
see,
if
I
remember
right
this,
this
will
then
tell
us
where
is
it
stored
in
two
repositories
and
submit
pull
requests
to
this
one?
A
And
now
this
one
may
be
more
difficult.
The
I
believe
the
maintainers
of
this
plug-in
are
actually
based
in
israel,
and
I
don't
know
that
we
can
get
their
attention
as
easily
as
we
get
the
attention
of
of
co-workers
in
the
company
where
kristen
and
I
work.
But
we
will
do
our
best.
D
A
C
I
think
she's
asking
if
we
should
and
clone
anytime
we
want
to
make
any
changes.
A
Yes,
okay!
Well,
if
so,
if
that's
the
question,
should
I
fork
and
clone
almost
always,
you
will
have
to
fork
and
clone
well,
you'll
at
least
have
to
fork
in
order
to
propose
a
change.
Now
you
could,
in
some
of
these
cases,
propose
changes
to
existing
files
just
by
doing
a
fork
and
then
modifying
it
inside
github,
but
in
order
to
add
new
files,
it's
much
more
difficult
using
the
github
web
interface.
A
A
Oh,
oh
yes,
okay,
maybe
I'm
so
I
see
it.
Thank
you
esther
all
right.
So
do
we
really
have
to
fork
and
clone
every
time?
Maybe
maybe
I
should
be
more
precise,
because
every
time
no
once
you've
done
the
once
you've
done
the
first
first
fork.
You
won't
have
to
do
a
fork
ever
again
on
that
repository
and
once
you've
cloned
it
locally,
you
won't
have
to
do
the
clone
again
locally.
You
you,
a
clone
is,
is
a
good
copy
and
you
can
use
that
copy.
A
If
you
were
to
erase
that
copy
on
your
local
disk,
then
you
would
need
to
clone
again,
but
for
for
later
pull
requests
to
the
same
repository
fork
and
clone
you
do
just
once
now
there
there
is
a.
I
guess,
there's
a
subtlety
there
that,
if
you're
working
on
something
that
moves
faster,
like
cynthia's
changes
to
jenkins
core.
A
If
two
weeks
from
now
she
needs
to
submit
another
change
to
jenkins
core
there's,
an
additional
step.
She'll
need
to
take
to
make
her
personal
copy
come
up
to
date
with
the
jenkins
copy.
That
is
upstream
of
her
most
of
the
plugins
that
you're
interacting
with.
I
think
are
relatively
low
volume
change,
so
you
probably
won't
encounter
that.