►
From YouTube: Package stage end-to-end testing overview
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
Hi
everyone
we
are
having
a
fair
programming
session
for
the
package
group
where
we
are
going
to
hopefully
develop
an
end-to-end
test
to
to
the
ruby
to
the
ruby
gems
package
manager,
we're
briefly
going
to
go
through
some
setup
details.
A
I
actually
prepared
a
bit
of
a
checklist
here
to
so
we
make
sure
that
we
are
set
up
for
success
I'll
I'll
start
by
just
sharing
my
own
screen.
If
you
don't
mind
steve
yep
yeah,
so
I
I
I've
sent
this
link
the
package
end-to-end
testing
guide.
A
A
There
we
go
okay,
so
I
think
that
the
best
way
to
start
this
usually
is
to
just
make
sure
that
your
jdk
is
able
to
run
this
end
to
end
tests.
B
A
And,
and
to
do
so,
I
would
like
to
make
sure
that
we
have
a
few
things,
such
as
your
jdk
is
able
to
to
have
a
host
name
map
to
the
loopback
interface.
A
No
because
the
magic
here
is
that
the
test
will
set
up
the
runner
for
you,
but
it
needs
to
have
this.
This
loopback
interface
and
the
hostname
of
your
jdk
has
to
be
not
localhost
3000.
A
So
we
also
have
to
have
some
environment
variables
in
order
to
set
up
in
order
to
run
this
test
command,
and
this
is
basically
the
test
command
right
here,
the
most
important
one,
just
to
make
sure
that
we
can
run
one
of
the
tests
and
that
everything
is
correctly
set
up.
A
So
I
will
I'll
just
do
it
I'll
just
show
it
in
mine
how
it
looks
like
and
then
maybe
you
could
try
in
yours
and
sure
yeah
we'll
take
it
from
there.
So
let
me
share
my
vs
code.
B
A
A
There
is
another
keyway
folder
here
and
under
that
it's
I
just
have
many
things
open
here
under
that
there
is
inspects,
features
it's
a
browser,
ui
test
running,
so
it's
also
within
the
package
folder.
Basically,
this
is
in
the
documentation,
but
it's
just
to
to
also
guide
you.
There
conan
repository
respect,
so
this
is
one
of
the
tests
we
have
for
the
package
managers.
We
will
go
briefly
over
this
one,
just
for
the
just
for
an
example
and
also
feel
free
to
stop
me.
A
Okay,
where
here
we
would
add
the
path
to
this
particular
test,
so
canon
repository
spec,
the
jdk
test,
is
basically
my
host
name
for
my
jdk.
I'm
not
sure
if
you
named
yours
exactly
jdk
task,
but
this
should
be
it.
A
One
more
note
that
I
would
like
to
add
is
that
I
have,
I
have
actually
environment
variables
set
up
and
and
this
this
is
actually
important,
because
because
they
allow
you
to
actually
see
the
test
running,
sometimes
that's
useful,
so,
for
example,
chrome
headless
is
set
to
false.
So
this
means
that
you
can
see
the
test
running.
A
Keyway
debug
means
that
you
can
see
the
logs,
so
each
action
and
interaction
in
the
browser
is
as
being
it's
being
logged
and
it's
easier
for.
You
know
for
finding
issues.
This
is
an
an
enterprise
license,
I'm
not
sure
if
you
have
it
already
for
your
jdk
setup,.
B
A
I
have
one
I
think
I
think,
for
the
tests
we're
going
to
run.
We
don't
necessarily
need
this
license
because
we're
not
running
any
premium
pressures,
so
it
should
be
fine,
this
this
tunnel
ssh.
This
is
for
another
another
stuff,
not
not
needed
for
hours,
and
you
can
save
some
time
by
having
also
gitlab
admin
username
set
to
root
and
the
admin
password
set
to
the
usual
jdk
route,
seated
password.
A
A
This
is
this:
is
I'm
pretty
I'm
using
the
z
shell,
so
just
it's
in
a
z,
z,
s,
h,
m
file
just
to
as
a
an
environment
variable.
A
A
A
B
So
I
missed
you,
just
opened
your
browser
and
or
did
you
did
it
automatically
it.
A
So
I
think
one
of
the
approaches
I
usually
take
for
adding
package
manager
tests
is,
I
started
with
the
documentation
right.
It
is
also
a
test
to
to
the
documentation
itself
and
see
if
there's
something
missing
or
not
clear.
A
So,
basically
for
this
for
the
conan
test,
I
went
to
the
conan
conan
documentation
in
docs
and
I
particularly
used
the
zicd
method
to
publish
the
conan
package
and
to
install
so
it
is.
It
was
really
about
following
the
documentation
that
was
there.
B
A
So
we
could
just
based
on
that
so
yeah
right
now
there
is
a
ci
job
which
is
taking
care
of
the
the
the
publishing
and
the
installation
of
this
package.
It's
going
to
verify
if
it's
existing.
It
has
a
right
version
and
it
deletes
the
package
in
the
end.
So
we
don't
get
these
packages
accumulated
in
our
either
jdk
or
in
some
staging
environments,
some
some
environment
which
is
not
destructible,
so
I
was
able
to
run
it
on
my
machine.
Were
you
successful
in
your
side?
I
am
getting.
It
started.
A
B
B
Will
I
need
the
username
and
password
environment
variables
to
run
that
conan
test?
I
think
you
don't.
B
And
then
I
need
the
whole
gdk
running
right
in
order
to
run
the
test.
B
B
A
All
right,
r
spec,
that
was
just
an
assumption,
yeah
jdk,
needs
to
be
to
be
running
because
the
tests
basically
go
and
target
the
the
instance.
I've
I've
shared
here
some
diagrams,
which
can
help
also.
A
How
are
we
doing
this
end-to-end
testing,
which,
basically
so
we
have?
We
have
a
gitlab
keyway
gem.
Are
you
able
to
see
that
the
drawing
we
have
the
gitlab
qa
gem,
and
this
is
basically
a
project
that
we,
this
is
our
tool
to
use
for
end-to-end
testing
and
basically,
what
this
gem
does?
Is
it
spins
up
the
containers
that
are
needed
to
run
the
tests,
meaning
the
container,
which
has
the
gitlab
instance,
the
container,
which
has
a
runner
the
container,
which
has
I
don't
know
a
server
depends
on?
A
What's
what's
the
what's
the
test
about,
so
it's
just
an
orchestration
of
of
the
tests
and
the
components
of
the
tests
and-
and
this
is
mainly
or
particularly
used
in
the
ci,
where
we
we
need
to
build
this
kit
lab
instance
and
set
it
up
and
then
we
have
it
tested.
So,
basically,
when
we
have
the
when
we
are
running
it
with
the
gdk,
we
have
the
gitlab
qa.
A
Having
the
building
the
gitlab
qa
image,
which
then
is
going
to
target
your
gitlab
instance
and
run
the
tests
against
this
instance,
but
in
the
ci
what's
happening,
it's
more
like
the
gitlab
qa
is
going
to
spin
up
the
the
qa
image
which
is
going
to
be
target
another
container,
which
is
the
gitlab
instance
and
the
complexity
of
the
scenarios
you
know
they
there
are
several
depends
on
the
depends
on
what
we
want
to
build
right.
A
I
I
would
like
to.
I
think
this
is
in
documentation
linked
in
the
issue,
but
it's
also.
I
would
like
to
link
this
particular
architecture
because
it
can
get
handy
once
things
get
more
complex
and
we
need
more
different
components
for
our
tests,
but
since
we're
gonna
just
be
using
we're
just
gonna
be
using
the
package
registry
and
and
rubygems
it's
in
gitlab,
we
don't
need
like
a
specific
external
service
to
be
spin
up.
A
There's
no
need
for
for
that.
We
just
need
our
this
scenario
here.
B
B
A
A
I'm
going
to
to
open
the
rubygems
documentation
just
to
so,
we
could
briefly
go
for
it
just
understand
in
the
meantime,.
B
A
To
probably
also
have
to
update
the
network
from
driver
for
this.
What's
that,
we
probably
also
have
to
update
this
in
in
the
in
the
in
our
in
the
keyway
project.
You
know
just
to
keep
up
the
the
driver
with
the
correct
browser
update
as
well.
Oh
sure,
I
think
that
we
yeah
something
that
we
have
two
different
times
time.
A
Okay,
in
the
meantime,
I'm
checking
here
the
documentation
for
the
rubygems
registry.
It's
behind
the
feature
flag.
A
B
Oh
yeah,
that
is
incomplete.
B
Yeah,
I
don't
know
if
I
I
I
don't
think
I
ever
actually
created
a
package
with
ci
cd.
A
A
A
B
A
B
B
If
you
go
to
your
chrome-
and
you
like,
you,
do
like
about
chrome,
what
version
are
you
on
there?
Oh
you're
on
90
as
well.
B
I
wonder
if
there's
something
else
I
need
to
update
in
the
qa
folder
like
I've
run,
bundle
install.
Would
there
be
anything
else
I
would
need
to.
A
Do
not
really
can
I
can
I
see,
would
you
be.
B
B
Me
switch
over
to
mine
here.
A
Okay,
have
you
have
you
checked?
What
is
the
current
from
version
you
have
so
for
me,
I'm
running
okay.
You
have
19
such
as
just
like
me
and
then,
if
you
go
in
the
terminal
and
you
do
chrome
driver
version,
is
it
I
think
it's.
B
A
A
Yeah
I
I
do
have
a
question,
though,
when
I,
when
I'm
just
checking
them
this,
is
we
basically
are
we
do
we
have
the
ap
the
delete
via
the
ui
implemented,
because
I
think,
as
you
mentioned
here,
the
installation
is
done
via
you
can
download
the
gem
files
from
the
ui
or
using
the
api.
Is
it
also
possible
to
delete
this
package
with
the
ui.
B
B
Yeah,
the
the
part
that's
not
currently
supported
is,
like
you
can't
say,
gem
install
or
bundle
install
and
have
it
install,
but
we.
A
It's
project
endpoint
and
for
well,
I
think,
usually
the
very
basic
of
tests.
It's
even
it's
just
doing
the
publishing
and
then
delete
it.
So
if
I
mean
we
could
do
the
the
installation-
but
maybe
maybe
we
could
actually
split
this
down
to
just
a
very
basic
as
of
publishing
and
entering
if
it
works-
oh
yeah,
this
one,
I
think
you
have
to
go
to
you-
have
to
go
to
the
privacy
settings
and
in
your
mac,
oh,
and
allow
it
to
allow
the
yeah.
B
A
B
B
B
A
B
A
Okay,
okay,
yeah,
so
it's
I
think
we're
just
gonna,
let
it
run
and
then
just
probably
briefly
go
through
through
the
tests
logic.
A
A
We're
having
this
issue,
have
you
have
you
updated
jdk
recently
or.
A
It
has
yeah
because
basically
was
trying
to
remove
something
that
has
failed
to
create.
I
would
I
would
suggest
this
is
just
basically
sometimes
what
I
do
is.
I
would
suggest
to
run
one
more
time
and
just
to
make
sure
it's
not
something
flaky
and
and
leave
it
running,
and
sometimes,
if
there
are
these
issues,
it
can
be
also
that
there
was
a
known
issue
in
the
test,
and
so
it's
also
worth
to
just
do
jdk
update
and
try
to
run
the
latest
version
because
there
might
be
some
fix
in
the
meanwhile.
B
B
Cool,
while
that's
going,
should
we
jump
in
looking
at
some
of
this
or.
A
So
we
are
using,
we
are
basically
using
our
spec
and
capybara,
so
some
of
these
things
might
be
familiar
to
you
already.
They
are
just
wrapped
around
various
page
objects.
A
Are
you
familiar
with
the
page
object
model
or
I'm
not
okay,
so
here
in
the
in
this
test,
when
when
we
are
when
we
are
starting
to
prepare
the
test,
we
create
certain
things
that
are
necessary,
such
as
the
project
where
the
package
is
going
to
be
stored.
As
you
see
there,
the
first,
let
just
creates
this
project
resource
I
will.
I
will
we
will
later
go
and
see.
What's
the
reason
what
does
resource
mean,
but
in
just
just
for
the
sake
of
simplicity?
A
It
creates
a
package
as
a
resource
as
well,
so
it
doesn't,
it
doesn't,
publish
it
or
pushes
it's
just
to
create
the
package
and
give
it
a
name
and
associate
it
to
which
project
is
it
going
to
go
and
it
creates
a
runner.
We
need
a
runner
as
well,
so
we
get,
we
give
it
a
name.
We
give
it.
We
give
it
some
tags
to
run
just
on
that
project
and
it's
a
docker
runner
and
it's
associated
to
this
project.
B
A
B
A
Yeah,
okay,
exactly
this
is
just
an
abstraction
so
to
speak
and
and
then
afterwards
we
have
some
things
that
we
need
such
such
the
gitlab
address
with
the
port,
because
we
basically
need
this
to
when
we
are
setting
up
when
we
are
setting
up
the
uris
that
are
needed
for
the
for
the
gitlab
cimo
file
to
work,
we
will,
we
will
see
it's
a
little
bit
below
how
it
works,
and
then
we
have
the
after
block,
which
is
basically
what
to
do
after
the
test
is
run,
and
basically
this
is
where
we
are
doing
the
removal
of
the
resources
such
as
the
runner
and
the
package.
A
Basically,
we
have
this
package
dot,
remove
via
api
for
the
cases
where
imagine
that
the
test
actually
fails
to
delete
the
package
via
the
ui
and
what
this
does
is
just
basically
going
to
through
the
ui
and
say
hey
if
this
is
still
there
just
go
ahead
and
send
a
delete
to
this
to
this
endpoint
for
this
package.
A
A
A
So
basically
we
just
we
just
have
the
the
yaml
fixture
here
right
in
the
code,
so
we
can
see
okay.
What
are
we
adding
and
and
within
this
gitlab
ciamo
is
basically
the
instructions
that
that
are
in
the
documentation
for
uploading
for
publishing
the
package
right.
B
A
A
Yeah,
so
if
we
were
so,
this
adds
this
gitlab
ci
file
to
the
repository
and,
as
you
can
see
here,
basically
those
gitlab
address
with
port
variables,
a
package
dot
name.
This
is
just
two.
These
are
just
variables
to
you
know,
follow
the
the
procedures
that
are
in
the
documentation
for
for
setting
the
remote
for.
B
A
With
and
last
we
have
attack,
so
we
associate
this
job
to
the
runner
that
we
have
created,
and
the
reason
is
that
some
some
developers
were
actually
not
creating
the
runner
because
they
were
having
the
runner
already
associated
in
their
jdk.
But
the
thing
is
that
this
has
to
this:
test
has
to
run
in
the
ci
and
the
ci
doesn't
have
the
runners
associated.
It
just
starts
from
completely
scratch,
so
it
needs
to
create
the
gitlab
instance
and
the
runner
and
then
associate
one
with
the
other.
So
this
is
why
we
are.
A
We
are
creating
the
runner
from
scratch:
poor,
okay
and
then
yeah.
Basically,
what
we're
going
to
do
is
just
going
to
visit
the
latest
pipeline,
so
we're
going
to
try
to
go
to
this
job
that
is
running
this
script
and
click
on
it.
A
And
then
it's
going
to
be
waiting
for
this
job
to
be
successful
and
for
the
package
to
actually
be
upload
it
cool.
Then
it's
gonna
go
also
via
the
ui
to
the
package
package
link.
This
is
basically
the
site
menu
where
we
have
package
registry
and
it's
going
to
try
to
verify
that
this
package
exists.
It's
indexed
as
you
see
page
project
packages
index
and
it's
going
to
try
to
find
that
package
dot,
name
and.
B
A
B
A
We
don't
have
this
in
the
listed
this
package
name.
A
A
Yeah,
okay
yeah
this
could
this
could
also
be
another
right.
I
would
just
if
you
let
me
just
for
for
brevity.
I
will
share
my
screen
as
well
as
well.
No
because
we
either
it's
mine
or
yours,
yeah.
B
A
A
A
A
Even
zoom
out
very
well
lately,
okay,
so
so
yeah
as
I
was
telling
you
there
is
this
these
resources,
and
basically,
I
think
from
the
beginning,
while
maybe
not
less,
not
so
familiar
with
it.
It's
better
to
just
you
know,
take
an
example
and
and
try
to
tweak
it
and
see
and
start
to
understand,
instead
of
perhaps
creating
those
new
resources,
but
but
with
the
you
know,
with
with
new
ui
interactions,
it's
necessary
to
add
those
page
objects.
A
A
And
this
is
how
a
resource
looks
like
so
this
takes
the
project,
for
example
the
project
api
and
and
models
the
this,
this
project
class,
such
as
the
necessary
things
like
id
name,
the
runner
token,
for
this
project,
the
template
that
this
project
is
going
to
have,
which
group
it
belongs
to
what
is
their
what's,
their
name,
space
and
and
so
on,
and
this
is
where
it
is
so
when
project
is
created,
goes
through.
A
This
method
called
fabricate
and
fabricate
is
basically
the
recipe
on,
while
using
the
ui
or
the
apti,
to
create
this
resource.
Okay,.
B
So
it's
specifically
fabricate
should
be
like
create
this.
Create
this
actual
project
using
ui
or
fabricate
via
api
is
create
a
project
using
the
api.
B
A
B
B
A
No,
we
are
really
trying
to
make
it
through
either
the
ui
or
the
browser,
because
for
project.new
we
already
have
the
other
level
of
the
tests
calling
for
it.
So
this
this
has
a
bit
of
a
you
know.
It
takes
longer
to
create
these
entities,
so
these
tests
do
run
for
longer,
but
we
we
are
trying
to
yeah
either
use
just
this
two
methods,
cool
and
back
to
our
tests
in
here.
A
It's
just
gonna
go
in
the
background
and
create
this
project
with
this
name
here
the
resource
package.
I
need
to
show
it
to
you.
A
The
resource
package,
also
well,
it
was
just
created
to
this-
is
not
like,
probably
the
best
resource
to
show,
because
it
was
just
created
to
be
removed
in
the
sense
of
just
basically
to
to
have
a
mechanism
of
removal
of
the
package
in
case
the
ui
fails.
A
Cool
right,
the
runner
as
well,
I
think
it
of
course
gets
can
get
more
complicated
than
that,
but
I
know
I
think
now
for
the
for
the
first
pass,
I
think
you're
understanding
that
this
also
goes
and
creates
runner,
and
if
yeah,
you
just
need
to
pass
the
name
attack
for
your
project,
then
the
rest
after
I
think
it's
very
familiar
to
what
you
might
have
seen
in
in
some
other
tests
and
using
it
and
using
describe
as
well.
This
is
something
that
you're
we've
been
using
already
in
other.
A
Just
our
spec,
so
the
thing
is
that
this
test,
basically
just
does
a
sequence
of
of
steps.
It's
not
so
so
encapsulated
it's
just
a
flow
of
tests
like
a
user,
would
do
so
to
speak,
so
yeah,
the
user
goes
and
logs
in
and.
A
B
Yeah
right
yeah,
it's
it's!
It's
like
the
resource
in
terms
of
how
a
user
would
interact
with
this
thing
through
the
ui
or
through
the
api.
It's
not
actually
like
necessarily
thinking
of
the
object
in
terms
of
you
know
how
it's
stored
in
the
code
or
database,
it's
more
of.
B
If
you
want
to
interact
with
pipelines,
then
you
use
the
resource
great.
I
was
curious
with
the
tests
like
I
know
not
all
of
them
run
automatically
when
you
push
a
normal.
Mr
will
these
run
automatically
like.
If
we
create
a
new
test
for
the
ruby
gems,
will
it
run
automatically
when
we
push
it
or
will
we
have
to
still
go
and
manually
kick
it
off
in
the
pipeline.
A
No,
it
would
actually
run
automatically
cool
it's
within
the
package
and
qa
job.
I
I
I
could
also
show
you
because
it's
a
bit
it's
a
long.
You
know
it.
It
just
takes,
of
course
long
because
we
are
building.
B
A
Instance-
and
we
run
a
full
set
of
tests,
not
only
that
test,
it's
a
full
set
of
keyway
end-to-end
tests,
but
I
could,
I
could
show
you
where
they,
where
they
would
be
running
if
you,
if
you
would
like.
B
A
A
Yeah,
the
page
is
also
here
so
within
page
pages
are
basically
the
building
blocks
of
the
ui
right
like
they
are
modeling.
How
a
page
looks
like
which
elements
are
in
this
page,
and
how
can
we
interact
with
this
page
and
just
encapsulates
the
elements
in
in
such
way
just
to
show
you
the
this
particular
one?
So
it's
in
within
page
page
project.
A
A
Are
you
familiar
with
the
concept
of
selectors?
Yes
right?
So
if
I'm
actually
I'm
going
to
just
try
to
find
the
selector,
my
blind
heather.
A
What
am
I
doing
right-
and
this
is
the
view
component
for
the
other
cm
and
within
this
component
you
will
see
the
pipeline
yeah
there
you
go
so
it.
This
is
something
that
we
are
adding
in.
This
case
was
miguel,
which
is
in
the
front-end
team
in
ci,
so
he
added
the
selector
and
basically
it's
just
adding
an
id
to
to
be
able
to
interact
with
the
ui
and-
and
we
are
gluing
the
view
with
the
selector
when
we
are
doing
this
block
here.
B
A
A
A
If
it
would
be
a
button,
would
be
blue
underscore
button
or
if
it
would
be,
there
is
a
style
guide
for
that.
I
would
you
know,
I
would
worry
only
when
the
code
review,
of
course,
this
this
just
comes
with.
You
know,
adding
and
experience
and
just
checking
the
style
guide
as
well.
A
B
A
Yeah
exactly,
but
I
would
just
like,
I
was
just
showing
you
the
the
way
that
this
is
that
we
are
gluing
it.
It's
just
this
view
block
you
create
a
new
block.
You
associate
the
the
view
file
with
the
elements
some
of
them
have
more
than
one
data
qa
selector
there
and
yeah.
This
is
just
where
they
get
listed
and
then
later
in
this
file,
you
you
define.
How
are
we
going
to
interact
with
them
so,
for
example,
as
job
it's
just
it's
just
basically
using
pure.
B
A
A
A
B
A
B
A
Exactly
just
your.
A
A
So
where
is
the
yeah?
It's
it's
basically,
something
like
this
right
she's
going
to
try
to
check
if
the
badge
the
ci
badge
is
going
to
say,
success
or
pass
or
complete
cool
yeah.
So
this
is.
This
is
just
the
underworks
of
the
of
the
tests,
but
script
wise.
A
A
The
point
the
the
same
logic
yeah
same
logic
here.
This
is
another
page
that
has
it
has
a
matcher
trying
to
see.
If
there's
this
package
name
and
it's
going
to
click
on
it,
do
you
have
any
questions
so
far,
I've
been
a
little
bit
faster,
but
it's
just
trying
to
make
most
of
our
time.
B
Oh
yeah,
this
is,
this
is
great.
I
don't
think
you
have
any
questions.
A
Because
because
I
think
it
it
may
need
very
similar,
it
may
have
a
very
similar
structure
and,
and
most
most
importantly,
actually
where
we
are
doing
the
real
testing
is,
is
just
writing.
B
Okay,
it
looks
like
I'll
probably
have
to
do
some
debugging
with
my
local
setup,
I'm
still
getting
the
failures,
so
I
can,
I
can
do
the
code,
but
I
probably
won't
be
able
to
run
it
or
if
we
want
to
do
it
on
your
side.
That's
fine
too.
A
You
know
I
I
think
just
for
us
to
be
within
time.
What
we
could
do
is.
I
would
just
I
would
structure
the
outline
of
this,
the
test,
the
ruby
test
and
I
would
push
the
branch
and
then
we
could
collaborate
like
that.
So
you
know
we
have
the
the
the
jdk
instance
running
and
that
test
passing
just
just
to
make
sure
that
it's
okay
and
then
we
go
back
and
forth
like
don't
you,
we
don't
have
to
send
a
final
version
to
it.
A
We
just
you
know
assigned
to
me
and
I
will
give
feedback
as
it
goes.
That
sounds
good.
That
sounds
good,
okay,
so
yeah,
let's
go
and
create
the
test.
A
A
A
A
B
A
B
I
think
I
thought
you
might
have
pinged
me
in
one
here
I'll
link
it
in
the
chat.
A
Cool
well,
this
is
going
to
be
maintaining
the
same.
You
need
to
project
anyways
to
to
be
creative
right,
so
just
gonna
give
it
a
different
name.
If
we
have
to
debug,
we
are
able
to
delete
the
this
package
via
the
api.
Is
it.
A
I'll,
just
these
are
just
you
know,
components
that
have
to
be
necessary.
I'm
not
sure
if
we
need.
B
B
Yeah,
I
think
we'll
need
that
with.
If
you
look
at
the
ruby
gems
docs
when
we
authenticate
via
ci
or
whatever
we'll
need
that
address.
A
A
Right,
oh.
B
Yeah,
I
think
you
might
just
looking
at
the
top.
The
top
was
indented
differently.
A
Okay,
I'll
I'll
turn
in
this
in
a
bit
just
just
for
before
I
push
the
branch,
don't
worry,
yeah
we,
after
afterwards
we're
gonna,
be
yeah,
run
removing
the
runner
removing
the
package.
We
could
also
remove
the
project
by
the
way,
oh
sure,
we'll
remove
it
via
the
api,
and
this
part
I'll
be
yeah.
It
will
be
very
similar
to
the
other
to
the
other
test,
meaning
that
login
makes
sense-
and
you
will
add
this
to
your
project
and
and
push
the
package.
But
ideally
the
project
itself
should
be
realistic.
A
I'm
just
I'm
just
gonna
go
and
quickly
check
this.
Just
let
me
share
with
you
as.
A
A
So
what
what
I
tend
to
do,
I'm
just
gonna,
show
you,
can
you
see
it
or
was
it
sharing.
B
A
B
It
looks
like
this
one
isn't
set
up
to
be
published
as
a
gem.
No,
this
is
a
yes.
A
But
but
so
the
logic
would
be
that
not
only
would
be
adding
the
gitlab
file,
you
at
least
need
to
have
that
file
for
it.
For
the
gem.
B
A
B
A
A
B
I
think
I
definitely
have
enough
to
start
here
and
I'll
be
able
to
to
write
up
a
test,
at
least
and
then
hopefully
be
able
to
run
it
soon.
B
I
mean
I
I
can
easily
enable
it.
We
need
to
do
that.
I
mean
because
if
it's
not
enabled
when
the
test
runs,
you
know
once
we
push
it.
Do
we
have
to
add
that
somewhere
in
the
test
or
anything.
A
Yeah
we
do
and
programmatically
I'll
I'll
show
you
the
documentation
I'll,
send
you
the
documentation.
It's
just
like
a
line,
saying
feature
you
know
you
can
have.
You
can
have
a
block
here
and
just
you
know
before
the
after
you
can
have
a
before
app
where
you
could
enter.
I'm
not
sure
exactly.
What's
the
syntax
feature
enable
and
then
have
the
name
of
the
flag
and
then
in
the
after
block,
you
would
do
something
like
feature
disabled
okay.
A
A
B
B
A
Okay,
I
think
we
are
also
at
time,
and
now
we
have
to
be
a
little
bit
brief.
I'm
sorry
if
I
were
just
running
to
it
any
questions,
just
just
yeah
comment
in
in
dmr
would
be
super
glad
to
help.
B
Okay,
yeah,
I
will
create
an
mr
and
ping
you
in
it
and
yeah.
Hopefully
we
can
go
from
there
and
see
how
how
it
goes.
A
A
B
I
know
my
gdk
is
probably
a
little
bit
all
over
the
place
right
now,
so
it
might
just
be
how
I'm
configured
but
we'll
see
I'll
ping
you
if,
if
I
keep
seeing
a
specific
error
yeah,
this
is
awesome.
I
really
appreciate
you
taking
the
time
to
go
through
this
with
me.
A
Thanks
a
lot
steve,
likewise,
really
yeah
I'll
stop
this
year,
and
I
think
we
can
stop
reporting
as
well.
Yep
stop
by
recording.