►
From YouTube: SheCodeAfrica 2021 04 23 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
B
C
B
D
B
C
Yeah,
like
you,
you
suggested
on
the
slack
channel.
We
could
start
by
going
through
our
task
for
some
of
us
that
are
having
some
challenges
submitting
peers.
So
we
could
start
by
knowing
what
the
challenges
and
how
we
can
be
unblocked.
B
I
like
that
idea
very
much
so
sharon
sharon-
and
I
had
worked
earlier
this
week
on
a
on
an
issue
that
was
blocking
or
is
getting
in
her
way.
Sharon
are
there
things
that
that
you've
learned
since
then,
where
we
need
to
where
we
should
discuss
them,
things
where
we
might
be
able
to
do
a
review
that
others
could
use
and
gain
from
your
experiences.
B
D
B
Okay,
so
you're
going
to
very
good
okay.
E
B
Actually,
it's
perfect
if
we
can
just
watch
you
if
you
don't
mind
us
watching
you
you're
welcome
to
you're
welcome
to
just
go
ahead
unless
there's
something
sensitive,
you
could
because
you're
in
the
plug-in
directory.
So
you
could
do
a
oh,
oh,
wait!
A
sec
you're
in
tild,
slash
jenkins,
underscore
home.
So
is
this
directory
a
development
directory
for
the
plugin?
Or
is
this
a
something
that's
different.
B
Okay
good
well
so,
let's
see,
let's,
let's
watch
the
error,
so
forgive
the
the
terrible
pain
of
typing
in
front
of
other
people.
It's
it's
an
awful
terrible
experience
and
I
agree
it
is
okay,
so
that
message
that
we're
seeing
there
tells
me
that
you're,
probably
running
java
11
and
that
message
is
just
fine.
It
should
be
harmless,
but
we'll
probably
want
to
check
that
you're
running
java
11
and
not
java,
15
or
16
or
or
some
other
version.
B
B
B
B
B
So
sharon
could
you
oh
whoops
now
what
happened
failed
to?
Oh,
oh
good,
okay,
address
already
in
use
all
right
this.
I
know
what
we
can
do
about
it.
Okay,
so
on
your
computer,
there
is
already
a
program.
That's
listening
on
port
8080
and
do
you
is
that
a
program
you
could
readily
stop?
B
A
Sorry
can
I
say
something
just
something
I
think
my
help.
Yes,
I
think
jenkins
is
already
running
on
that
board.
B
B
B
B
Equals,
let's
type,
nine
zero,
nine.
B
B
B
B
B
B
B
B
B
C
D
B
B
B
B
B
B
Do
others
of
you
have
questions
that
you'd,
like
that?
We
should
that
are,
are
getting
in
your
way
of
getting
your
poll
requests
merged
or
submitted
and
merged
esther.
If
I
remember
correctly,
there
were
some
surprises
that
you
had
encountered.
How
is
how
is
it
going
for
you.
A
It's
it's
going,
it's
very
fine
for
me.
I
was
able
to
I
think
my
full
request
got
merged
this
week
sometime
this
week
and
then
I
had
some
suggestions
this
morning
for
multi
multi-line
multi-line
view,
step
steps
and
yeah.
B
A
No,
what
I'm
doing
now
is
I'm
trying
to
work
on
the
the
documentation
for
the
nodes
and
processes,
because
there
is
like
it's
basically
empty,
so
I'm
just
I'm
just
trying
to
I'm.
I'm
I've
been
surfing
on
mine
for
information.
B
F
F
F
Then
I
have
this
question
by
the
way
it's
on.
Let
me
check.
There's
some
things
which
are
some
parameters
are
nested.
Then
I
was
wondering
how
I'm
supposed
to
do
it,
because
most
of
the
parameters
were
already
done.
People
already
added
the
online
help,
but
then
majority
are
nested,
so
I
was
wondering
how
I'm
supposed
to
go
about
it,
but
then
I
after
I
did
the
one
that
were
not
nested.
B
Okay,
all
right!
So,
let's
let
me
let
me
I'm
gonna
run
my
jenkins
instance
and
share
my
screen
and
and
then
let's,
let's
look
at
it
together,
because
there
may
be
something
that
that
I'm
not
yet
understanding
hang
on
just
a
minute.
So
I'm
going
to
share
my
screen
now
and
let's
take
a
look
at
it,
share
screen
here.
B
Input
input,
okay,
good,
all
right
input,
so
input,
and
so
good
there's
already
help
here
and
already
help
for
message.
So
those
two
are
good
and
then,
when
I
click
advanced,
the
okay,
so
custom
id
has
it
but
ok
button
caption
is
the
one
that
does
not
and
the
others.
Oh
all
right.
Okay
and
now,
then
your
question
is:
what
do
I
do
about
these
right?
B
I'm
going
to
add
a
parameter,
that's
a
boolean
parameter
is
am
I
am
I
getting
to
your
question
yeah
and,
and
you
may
or
you
may
find
one
where
you
say:
oh
this
thing
doesn't
have
any
help
on.
It's
got
help
for
parameters
in
general,
but
what
about
get
parameter,
for
instance,
or
some
other
parameter
that
may
not
have
help
for
it
like?
Okay,
here's
a
good
one
label
all
right,
so
here's
a
label
parameter
and
it
has
no
help
for
name
no
help
for
default
value
and
no
help
for
description
am.
B
B
Okay,
so
so,
in
order
to
find
a
place,
where
would
I
add
help
for
a
git
parameter?
I
have
to
go
find
the
plugin
that
is
control
or
label.
I
have
to
go,
find
the
plugin
that
is
contributing
that
and
then
make
changes
in
that
plug-in,
not
even
in
the
input
plug-in.
So
for
me,
that's
a
complicated
one.
This
is
the
same
class
of
problem.
B
So
I
think
what
that
means
is
we
we
assign
you
to
take.
You
can
switch
to
a
new
plugin
and
let
me
see
if
I
can
find
we've
got
one
assigned
for
you.
I
think
when
you
were
done
with
the
first,
so
oh
nope,
I
didn't
have
it
there
yet
so
just
a
minute.
While
we
look
up
the
pivot
table.
F
B
Extension
and
say
all
right
for
the
last
week
of
the
project
work
on
email
extension
and,
let's
take
a
look
at
it,
it
seems
to
have
quite
a
number
of
things
that
have
no
help
like
subject
and
body
and
attach
log.
So
I
think
this
is
a
good
place
for
you
to
be
able
to
do
to
add
some
help
for
those
things.
B
I
think
well,
I
don't
know
that
the
other
tasks
are,
let's
see
so
the
the
task
here
was
insert
missing
pipeline
help,
and
that,
for
me,
is
the
most
valuable
of
the
task.
That's
the
one.
We
really
wanted
to
get
you
through
this
one
is
also
helpful
and
if.
B
B
B
F
B
B
B
B
B
D
I
mean
the
link
in
line
12.
B
B
B
And
it
looks
like
the
change
log
that
I'm
not
sure
on
the
change
log
link
either
that
one
also
needs
a
fix.
Doesn't
it
no?
No.
The
change
like
link
is
correct.
B
B
And
it
looks
like
sharon
is
back
sharon.
Did
you
want
to
continue
the
screen
sharing
or
do
you
have
further
questions.
E
B
B
E
E
B
Okay,
I
don't
know
what
that
could
be,
then
so
we
we
could
certainly
look
at
it
on
your
screen
to
see
if
we
can.
So
it
was
a
jenkins
user
interface,
but
the
jenkins
user
interface
was
not
was
prompting
you
for
a
username
and
password.
B
B
B
C
B
C
The
challenge
I
am
I'm
having
is
the
fact
that
the
appeals
I
submitted
the
maintainers
are
not,
should
I
say
and
always
available
to
review.
So
I
wouldn't
know
if
I
should
continue
submitting
prs,
I'm
supposed
to
wait
for
it
to
get
reviewed
before
I
proceed.
So
it's
it's
a
challenge
to
me
because
I'm
not
getting
reviews
from
them.
B
Let
me
do
a
quick
look
at
its
help
to
see
if
there's
material,
it's
got
two
things
that
don't
have
any
help
for
them,
so
that
would
be
one
that
you
could.
You
could
certainly
do.
We
could
also
have
you
look
at
the
sonar
plug-in,
I
suspect,
is
so
ssh
agent.
I
would
expect
to
have
reasonably
quick
review
time.
B
We
could.
I
don't
think
that
there's
much
chance
that
sharon's
going
to
get
to
another
plug-in,
so
we
could
put
you
on
config
file
provider
or
on
see.
Have
you
looked
at
pipeline
utility
steps
that
one
I
thought
had
many
that
oh
no,
this
one
has
most
of
the
things
that
are
quite
well
documented.
Okay,
so
that's
not
a
not
a,
not
a
good
choice.
To
put
you
on.
B
B
So
had
you
had
you
started
any
work
on
a
different
plug-in
than
your
initial
plug-in.
You
were
working
on.
A
B
B
B
D
D
So
I
took
release
to
fix
tables
to
gifts
in
this
plugin
right.
I
use
permission
from
somebody
but
yeah.
It's
not
like
commenting
from
this
plugin.
So
probably
I
should
put
it
for
adoption.
B
D
That
is
something
else
submitted,
but
yeah.
So
if
there
is
something
which
justifies
the
release,
I
can
just
cut
that
here.
Please
request
my
review
because
if
you
just
pin
me
on
github,
it
may
be
really
lost
with
this.
Well.
B
Well-
and
I
don't
think
I
don't
even
think
we
need
to
require
you
do
the
review
like
I
am.
I
am
happy
to
do
the
review
or
to
enlist
angelique
or
or
meg
or
kristen,
to
help
with
review
it's
just
knowing
that
we've
got
someone
who
has
merge
permission
is
is
already
a
big
plus.
Then
after
we've
done
the
reviews,
we
can
let
you
know,
hey
reviewed
this
and
we
think
it's
ready.
B
E
G
I
have
a
question
so
when
I'm
trying
to
add
examples
called
examples.
So
when
I,
when
I
look
at
the
git
plugin,
so
like
the
examples
look
quite
bold,
I
don't
know
how
they
they
added
they
just
to
make
them
like
black.
G
B
B
And
and
so
let's,
let's
take
a
look
at
that,
so
what
you're?
Maybe
we
could
first
look
at
at
the
plug-in
document,
so
the
example
that
the
example
that's
surprising
you
is
inside
jenkins.
Is
that
right?
So
it's
it's
here
and
when
we
look
at
an
example
here,
whoops
just
a
moment.
So
if
I
look
at
under
this
question,
mark
the
things
that
you're
seeing
bold
are
these
exam,
these
texts
tell
me
more,
which
which
thing
are
you
seeing.
G
So
if
you
okay,
maybe
I
think
it
would
be
different
for
the
documentation,
but
maybe
so
if
I
go
to
the
documentation,
there's
an
example
like
git
step
with
https
and
change
log.
Disabled.
B
G
G
Yeah,
yes,
like
those
the
pipelines,
snippet
generator,
like
the
examples,
look.
G
B
D
B
B
G
Sorry
mark
I'm
not
I'm
not
saying
the
title
like
the
example
did
stab
me.
So
I'm
saying
that
if
I
try
to
look
at
how
it
looks
in
the
online
how
and
how
it
looks
in
the
documentation
like
this
example,
the
pipeline
snippet
generator,
generates
this
example.
It
looks
different.
G
So
yeah
the
one
you
just
selected
first
looks
different
when
it's
in
the
online
hub.
B
B
G
G
B
A
Yes,
hi
mark
for
the
the
the
definition
on
the
website
of
not
the
website.
A
On
the
on
the
page
on
the
documentation
page,
I
was
wondering
if
you
could
say
give
a
little.
G
Yeah,
so
this
is
how
the
examples
look
for
me,
but
then,
when
I
do
the
the
git.
G
G
G
B
Not
as
not
as
well
certainly,
there
is
css
that's
being
used
in
in
each
of
the
contexts
to
to
control
things,
but
I
don't
think
that's
within
your
control.
Let
me
do
a
quick
check
on
that
on
the
the
markup
used
for
those
those
examples.
I
thought
it
was
just
the
code
style
or
but
but
let
me
look,
let's.
B
Yeah,
it's
just
using
pre
interesting.
All
it's
using
is
the
pre
tag,
and-
and
that
may
be
the
wrong
thing
oleg
do
you
remember-
am
I
supposed
to
use
a
different
markup
for
source
code?
D
B
Okay,
so
then,
then,
what
that's
saying
is
I
made
a
mistake
in
the
git
plugin
and
we've
got
different
formatting
because
of
my
mistake.
It
should
be
listed
as
code
instead
of
or
so
it's
I
don't
need
to
worry
about
it.
Wrapping
or
well
do
I
I
want
it.
I
want
it
to
be
I'll,
have
to
look
at
it
and
see.
That's
a
good.
It's
a
good
question,
excellent
question.
G
I
don't
think
it's.
The
problem
of
the
prequels
actually
also
had
to
use
pre
so
that
I
can
maintain
the
structure
of
the
chord
examples
and
also
I
tried
using
the
chord
block,
but
it
didn't
work.
G
So
I
don't
think
the
problem
is
the
pre-tag,
because
the
pre-tag
is
actually
needed
to
keep
the
structure
then
how
it
looks.
B
Interesting,
okay!
Well,
so
then,
maybe
have
you
been?
Have
you
committed
your
changes
to
your
repository
and
pushed
them
to
github?
If
so,
if
you
could
send
me,
either
by
slack
or
by
email,
a
link
to
the
branch
where
you're
working,
I
could
take
a
look
at
it
and
see
if
I
could,
if
I
could
understand
it
better.
B
Because
I'm
I'm
not
I'm
not
100
certain
the
the
advice
from
the.
I
think
we
received
advice
from
daniel
beck
or
someone
else
that
that
pre
was
was
a
poorer
choice
than
code
because
code,
this
is
code.
That's
noting
the
semantics
of
it
is
code.
So,
let's
let
me
take
a
look
at
your
example
and
see
if
I
can
understand
it.
G
A
Yes,
I'm
here,
yes,
I
was
basically
saying
okay,
so
I'm
trying
to
open
up
the
page,
okay,
so
for
the
nodes
and
processes
documentation
page,
it
says,
pipeline
steps,
locking
agents
and
workspaces
and
running
external
processes
that
may
survive
a
jenkins
restart
of
agent
reconnection.
A
Yeah,
I
was
wondering
if
you
could
just
maybe
do
a
little
explanation.
B
A
It's
plugins.jenkins.io,
slash,
lockdown,
variable
test
works.
E
A
A
A
D
B
This
plugin
has
very
limited
documentation
in
this
particular
file.
It's
showing
us
I'm
going
to
go
through
the
sentence
and
let's
talk
about
each
piece
of
the
sentence
as
we
go
so
pipeline
steps,
locking
agents
and
workspace.
So
these
are
the
this
plugin
provides
pipeline
steps
that
can
acquire
locks
on
agents
that
can
use
agents
and
workspaces,
so
so
directories
or
folders
inside
the
agents.
B
B
So
you
know
okay,
great
all
right
so
that
now
now
the
next
part
is,
is
that
jenkins
origin,
as
it
originally
was
originally
was
created,
had
a
job
type
that
if
I
restarted
jenkins,
all
the
work
that
was
being
done
inside
that
job
type
would
be
lost,
it
would
lost.
Is
the
wrong
way
to
say
it.
The
processes
running
inside
it
would
die.
It
would
be
stopped
and
unable
to
unable
to
continue.
B
B
B
But
that's
what
you
described,
looks
fine,
great
and-
and
so
so
so
that
far
says
these
things,
that
this
plug-in
provides
do
things
with
agents
in
workspaces
using
external
processes,
and
they
will
continue
running
on
the
agent.
Even
if
I
restart
the
controller.
D
Yeah,
so
actually,
the
artifact
idea
of
this
plugin
is
this
more
descriptive
than
the
text,
because
we
have
a
durable
task
plugin,
which
basically
provides
this
framework
which
allows
to
create
processes
and
tasks
on
agents
which
would
survive
a
loss
of
connection
with
the
junkies
controller
and
by
planning.
Durable
tasks
table
basically
api
on
the
top
of
that
for
specifically
for
pipeline,
so
that
you
can
run
asynchronous
pipeline
steps
which
again
use
the
cpi
and
become
robust
against
restarts.
B
D
B
So
so,
then,
then
esther
the
next
piece,
this
agent
reconnection,
is
for
me
my
mental
model,
another
variant
of
jenkins,
restart
right.
If,
for
some
reason,
the
network
connection
between
the
agent
and
the
controller
were
broken,
but
the
agent
process
kept
running
and
the
controller
was
eventually
able
to
reestablish
that
connection,
the
the
results
would
be
retained
and
usable
still
by
that.
B
B
What
we
will
see
is
that
either
the
test
may
already
be
failing
on
the
master
branch
or
the
tests
may
be
fail,
maybe
intermittent
on
the
master
branch.
So
let's
go
look
at
it
and
see
so
nope.
The
master
branch
tests
are
all
passing.
B
B
I
I
don't
know
why
that
would
fail,
but
it's
certainly
not
related
to
anything.
You
changed
as
far
as
I
know,
let's
look
and
see
anything
that
it
hints.
No,
so
my
usual
pattern.
There
is,
let's
run
it
again,
and
I
have
permission
to
do
this.
Unfortunately,
and
the
maintainers
have
permission
to
do
this,
but
pull
request
submitters
do
not
so
the
only
answer
I've
got
right
now
is
that
looked
like
a
transient
error,
because
you
had
had
tests
that
passed
in
build
number
four
and
build
number
three
and
the
code
you're
changing.
B
B
B
The
ci.jenkins.io
test
are
flaky,
could
you
run
it
again
right
and
and
that
that,
for
this,
for
the
moment
is
probably
the
simplest
approach
there,
just
mention
me
or
yeah
me,
or
there
are
several
others,
but
I
promise
I'm
one
of
them
so.
B
G
B
All
right,
you've
been
most
patient,
meg
and
potentially
angelique
will
meet
with
you
on
monday.
If
you've
got
questions
over
the
weekend,
I'll
probably
available
be
available.
In
slack,
so
don't
be
shy
about
asking
your
questions
I'll
post,
a
recording
of
this
session
it'll
likely
be
one
or
two
hours
from
now
before
the
recording
is
posted
in
case
you
need
to
refer
back
to
it.
B
B
Excellent,
so
on
ne
there
may
be
even
more
things
arriving
in
on
the
http
request:
plugin
that
will
need
even
more
more
have
even
more
items
to
document.