►
From YouTube: 2022 04 19 Inclusive Naming
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
Welcome
this
is
the
inclusive
naming
project
in
the
jenkins
project
as
part
of
she
code,
africa,
contributon
2022,
it's
the
19th
of
april,
thanks
for
being
here
so
topics
I
had
on
the
agenda.
How
are
we
doing
on
startup
tasks?
How's
the
progress
on
the
google
sheet?
That's
collecting
the
data
and
a
timeline
reminder
and
timeline.
Reminder
is
mostly
for
me
and
for
nafisa,
but
I
think
it's
good
for
us
to
remind
ourselves
of
the
timeline
reminder
of
the
project
phases
and
be
sure
that
we
we
know
when
we
start
things
when
they
end
etc.
A
A
A
And,
and
thank
you
for
going
through
those
difficulties,
I
hope
I
hope
you
found
them
instructive
and
I
hope,
as
you
as
you
go
on
in
your
career,
I
suspect
you'll
be
have
an
opportunity
to
learn,
learn
jenkins
more
elsewhere.
So
I
thanks
for
going
through
that
anything.
You
want
to
recommend
where
hey
it
would
be
better
if
we
did
this
documentation,
improvement
or
that
documentation.
B
Well,
I
have
a
nose
pad.
I
am
jotting
down
all
my
difficulties,
so
maybe,
when
I'm
maybe
one
of
these
the
meetings,
I
will
read
them
out,
because
there
are
some
things
that
I
had
to
work
on
by
myself
and
it's
not
in
the
documentation
that
was
indicated
so
in
case.
Someone
else
faces
that
kind
of
issue,
so
they'll
be
able
to
carry
out
the
tax
without
having
any
problem.
A
Good,
thank
you.
Thanks
for
keeping
a
notebook
and
if,
in
a
future
session,
you'd
be
willing
to
share
or
or
walk
us
through,
your
notebook.
That
would
be.
That
would
be
absolutely
great,
because
then
we
can
use
what
you
learned
to
find
ways
to
do
better
documentation
on
the
jenkins
at
ios
site
and
better
plans
for
these
kinds
of
projects.
Thanks
for
taking
a
notebook,
that's
really
great.
B
Thank
you
mark
bo.
I
want
to
ask
the
question:
yes,
okay,
while
I
was
why
I
was
trying
to
okay,
that
was
number
nine.
A
B
It
took
me
several
hours,
yes,
creating
a
pipeline
using
blue
ocean
that
it
gave
me
a
very,
very
big
problem,
because
when
I
did
the
first
one
I
just
did
it.
I
went
through
blue
ocean
and
then
I,
when
I
clicked
on
it,
I
went
to
create
a
pipeline
and
then
I
inserted
the
url
from
the
github
pipeline
plugin,
and
then
it
was
giving
me
an
error.
B
Yeah
so
I
had
to
I
had
to
go
through
our
chat
on
slack
and
then
I
realized
you
already
explained
for
catering,
so
I
had
to
use
the
method
you
explained
for
sketching
while
using
the
metal
us
thing
for
catering.
I
realized
that
my
gets
wasn't.
The
right
is
not
the
right.
They
get
installed.
The
git
dot
exp
installed
on
my
system.
Isn't
the
right
kit
I'm
supposed
to
use
for
the
for
the
for
running
the
pipeline
plugin,
so
I
had
to
delete.
B
A
A
It's
completely
missing
and-
and
here
here
it's
assumed
later
in
this
in
step,
seven
that
git
is
installed
and
configured
now
on
linux,
computers,
it
it
commonly
is,
but
on
windows
and
mac
os,
it's
not
so
good
good
catch.
Thank
you
very
much,
and-
and
that
certainly
makes
things
much
worse,
for
your
experience,
keep
going.
B
Yes,
so
I
had
to
go
to
my
system,
environment
variable
and
I
had
to
copy
my
gits
from
my
pc,
my
git
name,
like
the
domain
variable
for
my
pc,
and
then
I
had
to
paste
it
on
my
environment
variable
before
I
was
able
to
run
it
through
cmd
and
then
yeah.
That
was
when
I
was
able
to
undo
the
issue,
but
because
git
was
not
mentioned
in
the
in
the
document,
it
was
it
made
it
very
difficult
because
we
didn't
know
that
we
were
supposed
to
install
git
on
our
system.
First.
A
Right
right
absolutely-
and
that
is
that
is
an
example
of
me
being
contextually.
Blind,
contextual
blindness
is
where
I
do
something
so
often
that
I
simply
forget
to
describe
the
step.
For
me.
No
computer
exists
that
doesn't
have
git
installed,
but
that's
not
the
reality.
That's
just
my
every
time.
I
start
with
a
computer.
I
immediately
install
git,
but
other
people
don't
do
that
thanks
very
much
for
catching.
It.
B
Oh
thank
you
mark.
Well.
For
the
rest,
I
think,
okay,
I
also
had
issues
when
I
was
installing
java,
because
okay
yeah,
because
okay,
not
not
java
when
I
was
trying
to
run
jenkin
when
I
was
trying
to
install
jenkin
on
my
pc,
because
after
installing
jenkin,
I
tried
to
use
cmd
to
check
if
jenkin
is
loaded
on
my
pc.
It
was
not
so
I
didn't
know
that
I
was
supposed
to
after
installing
jenkin
jenkins.
B
You
know.
After
installing
java
I
will
have
to
copy
the
java
link
and
then
paste
it
on
my
environment
variable
before
I
can
run
it,
because
I
realize
that
there
are
some
pc
that
don't
even
need
you
to
paste
on
the
environment
variable.
While
there
are
some
pc
that
when
you
use
it,
you
have
to
run
some
manual
stuff
by
yourself.
B
So
maybe
my
pc
is
one
of
them.
Actually
everything
I
do
I'll
have
to
copy
and
paste
on
the
environment.
Variable
like
my
system,
environment
variable
before
I
can
use
it,
so
that
made
it
very
difficult,
because
I
was
trying
I
I
used
different
method.
I
couldn't
get
it
I
had
to.
Then
I
had
to
use
that
method.
That
was
when
my
cmd
was
able
to
read
my
java,
my
apache
and
the
jenkins
before
I
blow
jenkins
on
my
pc.
Another
mistake
I
did
again
was:
I
went
to
install
jenkins
17
version.
B
B
Why
didn't
notice
until
you
corrected
me
on
the
slack
that
the
version
I
was
using
is
not
the
right
version,
so
I
had
to
no
it's
not
the
jenkins
version,
the
java
version,
the
javascript
version
I
was
using
was
wrong,
so
I
had
to
delete
the
java
version
and
then
installed
version
11,
because
I
installed
version
17
also
for
my
phone's
java,
so
I
had
to
delete
and
then
install
version
11
before
I
could
run
it.
So
it
was
a
little
tough,
but
I
thank
god
I
was
able
to
cross
pass
those
parts.
A
Very
good,
thank
you
and
thanks
for
sharing,
so
so
I
think
we
should
plan
to
dedicate
a
a
session,
a
future
session
where
we
give
at
least
20
or
30
minutes
for
question
and
answer
based
on
your
notebook
notes
about
hey,
I
bumped
into
this,
I
bumped
into
this,
and
then
we
can
discuss
all
right.
What's
the
best
way
to
approach
that
because
some
of
them
it
may
be,
we
update
the
jenkins
documentation
and
say:
hey
the
documentation
on
the
jenkins
site
should
say
this
because
it'll
be
used
by
more
people,
others.
A
B
For
now
I
would
say
no,
but
I
for
the
I
had
to
the
other
plugin
this
the
I
was
giving
some
plugin
I
when
I
checked
the
google
sheets
I
saw
some
plugins
I
was
given
to
a
name.
Then
I
the
miller
plugin,
but
I
it
not
because
there
was
there
were
any
mistaking
the
name
or
any
name
correction.
I
focus
because
when,
while
I
was
trying
to
work
with
the
with
the
pipeline
plugin,
I
was
having
lots
of
issue,
so
I
asked
I
was
thinking
it's
the
plugin.
B
B
There
was
no
error
in
the
names
and
I
remember
last
meeting
you
indicated
that
when
there
is
no
need
to
a
plugin
and
when
there
is
no
correction
or
any
changes
to
make,
we
should
not
any
plugin.
So,
as
I
had
to
tell
you
now
so
that
I
didn't
it
not
because
there
were,
there
was
any
error
I
was
just.
I
was
just
trying
to
see
if
the
plugin,
my
mistake,
was
from
the
plug
now,
so
I
had
to
the
miller
plugin.
A
A
My
only
reason
for
noting
that
you
don't
have
to
do
it
is
you
may
not
want
to
clutter
your
your
own
github
environment
with
forked,
copies
of
repositories
that
you
don't
need,
so
so
there's
no
harm
that
you
did
a
fork,
it's
good
practice
and
you
can
actually
so,
for
instance,
when
I
do,
I
can
delete
forks
all
the
time
and
and
so
there's
no
no
reason
that
you
can't
just
go
ahead
and
delete
it
later.
If
you
don't
need
it,
but
no
harm
that
you
forked
it
good
for
you.
A
A
So
the
fact
that
you
found
no
no
changes
is
is
a
good
thing,
and
it's
even
expected
we
may
in
the
first
40
or
50.
Plug-Ins,
may
only
find
two
or
three
that
need
any
change,
and
that's
okay.
That,
because
that
that's
a
actually
a
big
win,
because
that
means
you'll
be
able
to
work
on
things
that
are
lower
on
the
list
and
help
with
them.
B
C
C
A
A
Yes,
yes,
thank
you
very
much
that
that
hints
that
there
may
be
a
challenge
here,
because
this
link
this
this
shortcut
in
the
google
drive
is
not
a
guarantee
that
permission
has
been
granted,
whereas
the
permissions
on
the
folder
generally
grant
permissions,
but
not
for
shortcuts.
So
so
that's
a
reminder
that
we've
got
to
be
sure
that
everyone
gets
access
to
those
files
so
that
they
can
see
them
thanks
for
catching
it.
That's
great.
A
D
Yeah
yeah
to
nothing
that
are
we
supposed
to
update
the
documents
or
update
on
slack.
D
A
And
and
the
reason
the
reason
I've
preferred
the
document
it
gives
us
a
place
to
focus
100
on
you
and
your
experience
and
you
can
take
notes
right
there.
But
but
if
you
have
a
question
or
a
problem,
then
slack
is
a:
is
the
best
place
to
do
it?
Because
then
other
people
see
your
question
and
they
benefit
from
the
answer.
A
So
for
me,
I
I,
like
I,
like
the
the
the
document
as
a
notepad
or
a
place
where
you
s
you
scribble,
quick
notes
or
or
make
a
comment.
Oh
this
was
broken
or
oh,
this
didn't
work
the
way
I
expected
or
well.
That
was
a
surprise
and
then,
when
you
hit
a
problem
that
needs
someone
else's
help,
then
we
do
it
in
slack,
because
that
way
we
can
share
the
share
the
solution
with
others.
A
A
A
A
Okay,
all
right,
so
then
we
had.
We
had
listed
a
let's
see
where
oh
here
it
is
in
this
one
identify
terminology
errors
in
searching
the
jenkins
repositories.
A
C
A
Great
okay,
well,
and-
and
we
could
take
time
today
to
work
on
that
pipeline
issue
that
you
had
in
slack
if,
if
you're,
okay
with
that,
I
think
that's
a
good,
a
good
use
of
our
time
here.
If
you're
willing
go
ahead.
A
D
Yeah
I'm
on
my
laptop
just
okay.
A
A
Good
right,
okay,
so
this
is
this:
is
the
pipeline
build
okay?
So
so
this
one
highlights
all
sorts
of
interesting
challenges,
so
the
pipeline
build
step
plug-in
if
you'll
click
click
on
the
master
thing
here
or
on
any
one
of
the
others,
any
one
of
those
rows.
Let's
say:
branch
indexing
click
that.
A
So
it
says
start
of
end
of
pi
start
of
pipeline
line
four
end
of
pipeline
line
five,
and
then
it
says
no
such
method
error.
That
line
six.
Is
this
big
long
line
of
wow?
There
are
a
bunch
of
possibles
that
no
such
such
method
area
so
scroll
back
up
to
it,
says:
hey.
It
was
looking
for
a
method
named
build
plugin
and
your
jenkins
right
now
doesn't
have
a
method,
a
domain,
specific
language.
A
But
it's
it's
not
ready
for
someone
who's,
not
really
ready
to
run
a
full
ci
system
like
ci
jenkins
that
I
o
it
assumes
things
like.
You
must
have
a
windows
agent
available
and
you
must
have
a
linux
agent
available
and
you
may
need
to
have
docker
available
and
you
may
need
to
have
cloud
resources
available.
A
A
Of
of
this,
so
let's
see
if,
if
you
click
in
the
top
right
hand,
corner
the
let's
see
the
x,
that's
in
the
top
right.
A
A
So
now
what
this
is
doing
is
it's
checking.
Oh,
is
there
a
jenkins
file
already,
and
it
says:
oh
there
isn't,
since
there
isn't
a
jenkins
file,
it's
putting
you
into
an
editor
that
will
let
you
create
one
and
now
you're
sort
of
this
is
sort
of
advanced
stuff
here,
but
click
the
plus
sign
and
name
this
stage.
Let's
call
this
stage
checkout.
A
Fake
checkout,
this
is
this
is
just
for
experiments
purposes,
so
fake
checkout
and
now
click
on
the
plus
sign
over
on
the
center
again
on
after
checkout
we're
going
to
actually,
let's
just
save
it,
let's
save
it
for
now
and
watch
this,
so
save
click
save
in
the
top
right
hand
corner
and
we
wanna
and
a
good
description
might
be
something
like
add.
A
skeleton
jenkins
file.
A
And
we
want
to
commit
to
the
master
branch,
so
click
save
and
run,
and
what
this
is
going
to
do
is
now
it's
going
to
say:
hey,
let's
actually
store
this
to
github.
It's
going
to
now
check
out
your
master
branch,
and
it's
going
to
execute
that
pipeline.
Now
that
pipeline
that
we
executed
is
really
kind
of
dumb
right.
It
just
does
nothing,
it
says,
I'm
doing
it.
It
gives
one
message
and
then
it'll
be
finished.
A
Good,
okay,
so
notice
that
it
says
check
out
from
version
control.
So
if
you
click
on
that
row
it
will
expand
it
and
you
can
see
what
it's
doing.
And
here
it
is.
It's
saying,
I'm
cloning,
your
repository,
github.com
katherinekiro,
ecommerce
site
api
and
now
that
it
finished
that
checkout,
I
put
a
message
in
there
that
says
fake
checkout
and
if
you
open
expand
that
one
you'll
see
the
message
says:
fake
checkout,.
D
A
A
A
A
So
now,
if
you
click
the
master
row
there,
it
should
take
us
to
okay,
there's
one.
Let's
go,
it
should
show
us
another
one
running
okay,
so
let's
go
go
back
in
the
top
left
hand,
corner
click,
e-commerce
site
there.
It
is,
it's
already
run
it.
It's
already
finished
the
run.
Let's
go
look
at
it
and
see.
A
A
A
A
A
I
made
a
mistake
when
I
had
you
define
this
initially
that
stage
that's
called
checkout
is
actually
not
needed,
because
it's
implicit
it's
by
the
mere
act
of
attempting
to
do
a
pipeline.
It
by
default,
does
a
checkout,
so
click
on
the
checkout
node
over
there
on
the
checkout
step
right
and
now,
on
the
right
hand,
side.
There
are
three
dots
immediately
to
the
right
of
the
word:
checkout
click
that
and
click
the
delete,
because
we
don't
actually
need
to
do
a
checkout.
It's
automatic
now
save.
A
A
D
D
All
right
that
helps
it
this
okay,
okay,
yeah
this
this
this
helps.
So
one
thing
wondering
is
this:
that
the
point
of
this
is
to
help
to
help
developers
in
the
pipeline
of
of
committing
their
work,
to
get
help.
A
They
don't
want
to
break
things
by
making
a
change
that,
and
so
what
we
do
typically
is
on
every
change
made
by
anyone.
We
rebuild
the
software
and
we
rerun
all
of
its
automated
tests
and
that's
what
this
is
doing.
So
the
every
time
you
commit
a
change
to
e-commerce
site
and
jenkins
is
running
jenkins
can
see
it
and
it
will
say.
Oh,
I
should
run
this
this
job
to
be
sure
that
it's
still
okay
now,
admittedly,
what
we
created
here
is
is
completely
empty
right.
It
doesn't
build
anything.
It
doesn't
actually
test
anything.
A
A
A
A
We
use
jenkins
to
compile
the
product
to
deliver
the
built,
the
build
results
to
various
distribution
places
like
the
windows
msi
file
like
the
debian,
the
debian
deb
file
or
the
red
hat
rpm
file.
So
each
of
those
delivery
activities
happen
in
jenkins
because
jira
is
not
really
focused
on
delivery.
Jira
is
focused
on
tracking
bug,
reports,
tracking
enhancement,
requests
and
helping
us
know
when
we're
done
with
those
kind
of
activities.
A
They're
two
different
they're,
two
very
different
tools
and
they
handle
different
different
parts
of
the
software
development
life
cycle.
Different
parts
of
of
software
development
activities,
jira
does
does
issue
tracking
and
it
does
work
tracking
very,
very
well.
What
jenkins
does
is
automation
of
activities
that
are
part
of
the
software
development
process,
like
compilation
and
test
and
deploy.
A
C
A
Okay,
good
all
right,
so
we've
got
about
15.
A
In
our
meeting
today
we
had
we
had
identified
this
getting
you
started.
It
feels
like
you're,
both
getting
started
very
well.
Maybe
we
could
take
a
few
moments
and
take
a
quick
look
at
the
timeline
to
be
sure
that
nafisa-
and
I
know
where
we're
at
in
terms
of
the
timeline
and
and
I
apologize
in
advance-
I
had
I
should
have
checked
this
before
we
started
our
meeting.
I
didn't
so
we're
going
to
look
at
it
now
together.
A
So
this
is
the
timeline.
It
was
right.
Okay,
so
here
we
are.
We
are
in
boot,
camp
phase,
working
on
assigned
project
ideas,
mentoring
and
weekly
calls
between
mentors
and
mentees.
Okay,
good,
so
we're
we're
we're
started,
and
so
I
think
we're
ready
for
the
two
of
you
to
get
started
on
working
through
that
sheet
and
trying
to
identify
places
where
a
change
is
needed
and
then
have
you
submit
your
first
changes,
proposing
fixes
to
those
things.
A
B
A
Okay,
great
yeah:
let's
do
that
so
that
way
we've
got
it
recorded
and-
and
you
can
refer
to
the
recording
so
so
we
need
to
find
an
example
of
something
that
has
a
that
has
a
a
a
naming
reference.
That's
not
inclusive
right,
that's
uses
either
the
word
master
or
the
word
slave
or
the
word
blacklist
or
whitelist.
Those
are
all
all
non-inclusive
terms
that
we
would
like
to
eliminate.
A
So,
let's,
let's
try
one
like,
and
this
is
me
making
making
guesses
I'm
going
to
try
jdk
tool
because
it's
a
relatively
older
plug-in,
not
very
frequently
maintained.
So
you
notice
what
I
did
is
I
clicked
this
link
on
jdk
tool.
It
took
me
to
the
plug-in
the
plugin's
own
page
and
on
this
page
over
here
in
the
links
section,
is
a
link
to
the
github
repository
for
that
that
plugin.
So
I'm
going
to
go
to
that
repository
and
now
here,
I'm
just
going
to
look
for
master
in
this
repository.
A
Okay,
that's
that's
the
and
remembering
the
rules
say
if
it's
in
java
source
code-
and
it
is
a
a
java
identifier
in
this
case
it
is
master-
is
a
master
to
slave
callable
is
in
fact
a
java
identifier.
We
can't
change
it,
so
that's
not
something
we
could
change.
Let's
try
slave
nope,
that's
not
a
problem
either.
Whitelist
nope
blacklist.
A
Okay,
so
my
first
attempt
failed.
I
thought
that
would
work.
Sorry,
catherine,
that
one's
no
change
is
needed.
Let's
try
a
different
one:
how
about?
Let's
try,
let's
try
something
I'm
going
to
jump
further
down,
because
there
are.
There
are
probably
things
later
on
that
I
could
use.
Let's
try
docker
commons,
this
one
right
here.
A
A
Okay,
this
one
is
in
a
test,
a
test,
a
test,
more
tests
found
one-
maybe
okay,
so
at
least
here
it's.
This
is
a
javadoc
comment
and
javadoc
comments
are
safe
to
change.
So
I'm
going
to
go
ahead
and
propose
a
change
to
this
one.
A
A
As
part
of
changes,
so
slave
whoops
use
agent
in
the
javadoc
rather
than
slave,
oh
excuse,
my
fat
fingers.
A
A
A
A
Okay,
I
don't
have
any
relevant
issues
to
link
to
so
I
can
check
it
because
there
isn't
a
relevant
issue.
Likewise,
there
isn't
a
relevant
pull
request,
ensure
you
have
provided
tests.
I
don't
have
a
way
to
test
this,
so
I'm
going
to
use
this
two
tildas
the
curly
character,
because
what
that
doesn't
get
marked
github
markup
is
it
makes
the
text
be
strikeout
struck
through
so
now
notice
that
there's
this
preview
thing
here
that
will
show
how
it
looks
to
people
who
read
it.
A
B
I
want
to
ask
the
question:
please:
does
it
mean
we
don't
need
to
repository
before
creating
a
full
request.
A
Well,
it
good
question
very
good
question
because
notice
what
this
says.
It
says
that
it's
already
forked
the
repository
for
me
and
it
did
that
for
me
as
part
of
creating
the
pull
request
with
this
technique,
so
by
my
using
github
to
do
the
to
do
the
editing,
the
change
it
forked,
the
repository
for
me
now,
let's,
let's
see
that
that's
the
case,
let's
go
look!
So
if
we
look
at
my
github
repository
just
to
be
sure
git
github
and
the
repositories
docker
commons
plugin.
A
A
C
Okay,
my
question
is
on
when
you
try
to
search
for
the
names
you're
trying
to
change
the
master
or
the
slave
and
keywords
there
are
times
it
came
up
in
method,
names
or
package
names.
Does
it
mean
you
don't
have
to
change
search
or
is
there
a
particular
step
they
have
to
take
to
change
that.
A
Yeah,
so
so
that
part
of
this
is
is
why
we
need
your
software
skills
so
that
you
understand
oh,
I
should
not
propose
a
change
that
would
break
compilation,
because
if
I'm
going
to
break
compilation,
that's
not
going
to
help
the
people
who
maintain
the
plug-in
they're
going
to
see.
Oh,
you
submitted
something
and
it
didn't
even
compile
you
clearly
didn't
didn't.
Do
the
the
usual
checks
that
are
needed
before
you
submit
a
pull
request.
A
A
Now,
let's
go
back
because
there's
another
piece
of
this
we're
almost
out
of
time,
but
I
wanted
to
show
you
one
more
piece
so
so
after
I
submitted
my
my
pull
request
and
we
see
the
pull
request
on
screen,
this
commits
tab
shows
me
here's
the
thing
that
I
did.
The
next
tab
over
checks
shows
me
the
checks
that
are
running
to
see
if
my
change
is
a
good
change
and
what
this
does
is
it.
A
This
is
jenkinsci.jenkins.io
running
checks
on
linux
and
on
windows
to
see.
If
my,
if
the
change
I
made
is
a
good
change
and
if
I
want
to
see
more
details
about
what's
happening
there,
I
click
this
link
and
it
takes
me
right
to
write
to
ci.jenkins.io.
Now
I
can
even
open
blue
ocean
here
and
see
how
it's
doing
so
you'll
see
here.
Blue
ocean
has
done
the
checkout
on
linux.
It's
done
the
checkout
on
windows,
it's
now
building
on
linux,
and
if
I
open
this,
I
can
see
the
progress
it's
making.
A
D
I
have
a
question
so
that
process
of
checking
on
jenkins
is
that
what
it
means
to
build
a
plugin
and
test
and
test
it.
A
It
it
is,
that's
that's
one
of
the
ways,
so
this
is
definitely
building
the
plug-in
and
it's
running
automated
tests.
Now
many
of
us
like
to
also
do
interactive
tests
when
we
do
significant
changes,
but
but
these
small
changes
of
just
changing
text-
it's
okay.
If
we
just
rely
on
the
automated
tests.
D
Okay,
so
that
means
because
in
the
in
the
task
outline
under
the
under
the
task
under
the
task
session,
it
says
we
are
changing
the
terminology
and
building
the
plug-in
and
also
testing
it.
So
does
this
process
cater
to
it
or
is
there
another.
A
Oh,
oh,
okay,
right,
okay,
so
this
one
in
this
task
list
this
is,
would
be
used
for
the
cases
where
you
had
to
make
a
local
change,
because
it
was
so
large
that
you
want
to
be
sure
that
you
can
do
all
the
tests
locally.
So
this
very
good
question
this
one
is
talking
about
how
do
we,
if,
if
I
have
to
make
so
many
changes
that
I
need
to
that,
I
need
to
do
that
locally
on
my
computer,
then
these
are
the
steps
I
do
locally
on
my
computer.
D
A
You
should
my
preference
is
that
you
would
rely
on
the
automated
tests
from
jenkins
so
that
you
don't
have
to
do
these
steps
at
all
now,
particularly
for
your
first
several
it's
best,
if
they're
relatively
small,
so
that
so
that
I
can
work
quickly
with
you
and
you
can
work
quickly.
So
in
that
case
you
would
just
do
it
from
github.
A
Now
you
may
find
some
plug-in
in
your
review
here
where
you,
you
discover
a
plug-in.
Let's
say:
let's
pick
an
a
potential
one
like
you
might
find
that
good
choice,
pipeline
maven
is
a
relatively
older
plug-in
and
you
may
find
it's
got
many
many
problems
in
it
and
it's
got
so
many
problems
in
it
that
you'll
be
faster,
doing
the
changes
locally
and
if
that's
the
case,
then
you'll
need
to
do
the
build
and
test
yourself
locally.
A
I
don't
see.
Oh,
oh
yes,
okay,
there's
a
that's
very
good
this!
Yes!
So
so
this
one
has
a
number
of
places
where
it's
got
interesting
things,
and
this
one
may
be
one
where
you
have
to
say.
I'm
going
to
do
this
one
locally,
because
I
have
to
evaluate
the
specific
specific
things
so
preference
first,
first
preference
is
use
the
github
editing
ui
first,
wherever
you
can.
D
B
A
Okay,
yeah
so
next
session
next
session,
let's
go
through
this
sequence
and
be
sure
that
you're
comfortable
with
this
sequence
and
absolutely
I
like
that
now,
would
you
like
to
try
for
a
next
session
later
this
week,
rather
than
waiting
all
the
way
until
next
week?
Or
do
you
want
the
time
this
week
to
work
through
some
of
these,
so
that
you've
got
you've
got
time
to
make
progress
on
them
and
then
we'll
just
meet
next
next
tuesday?
What's
your
preference.
B
A
A
Great
all
right,
thank
you.
Thank
you.
Recording
should
be
available
within
the
next
24
to
48
hours
so
that
you
can
refer
to
it
thanks
very
much.