►
From YouTube: GitDock - Pipeline setup retrospective
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
Hey
team:
this
is
the
first
video
where
I'm
going
to
talk
about
some
of
the
challenges
I've
had
to
overcome
with
our
own
product,
while
building
get
doc,
and
I
want
to
focus
on
pipeline
specifically
today.
So
let
me
open
up
our
ci
yaml
file
and
the
first
larger
problem
I
ran
into
was
figuring
out
how
to
keep
my
ci
dot
gamut
file
as
small
and
as
readable
as
possible,
while
also
building
out
an
entire
pipeline.
A
Interestingly,
I
started
off
building
the
same
pipeline
for
my
github
mirror
at
the
same
time
as
I
developed
the
product
or
the
small
site
project
on
gitlab,
and
what
you
can
see
here
in
the
github
workflows
folder
is
they
allow
you
to
just
put
in
a
couple
of
different
files,
specifically
mention
when
each
of
these
would
run,
but
all
of
them
would
be
considered
by
whatever
is
running
in
the
background
to
see.
Does
any
of
do
any
of
these
need
to
run,
whereas
for
us,
the
gitlab
ci
dot
demo
file
is
the
only
entry
point.
A
Git
dock
is
built
in
electron
and
for
testing
an
electron
app.
You
need
chrome
driver
because
our
linux
image,
node
latest
that
I've
been
using
before,
doesn't
have
chrome
driver.
I
had
to
spend
a
lot
of
time
testing
out
different
ways
to
get
chrome
driver
to
install.
I
had
to
install
a
ton
of
dependencies
as
well,
and
you
can
see
here.
I
ended
up
with
more
than
100
commits
because
it
was
so
tough
for
me
to
figure
out
how
to
make
this
work
correctly.
A
But
also
how
to
only
install
as
minimal
dependencies
as
possible
to
not
overload
the
pipeline
so
figuring
out
a
way
for
us
to
have
a
template
or
maybe
find
a
way
to
give
users
better
information
about
what
dependencies
they
need
to
install
to
make
something.
Work
could
be
huge
here
because,
as
you
can
see,
this
took
me
a
couple
of
days
and
quite
a
lot
of
pipelines
had
to
run
just
for
me
to
test
whether
it
would
work
or
not.
A
A
A
In
the
same
way,
I
cannot
add
the
version
number
into
the
file
name,
which
is
something
that
users
specifically
have
been
requesting
and
which
makes
a
ton
of
sense,
but,
as
far
as
I
know,
I'm
currently
still
blocked
by
this
five-year-old
issue
and
final
piece
when
I'm
creating
a
new
release.
I
automatically
add
all
of
the
different
installation
files
to
it,
which
works
wonderfully
and
right
when
you
go
to
the
releases.
You
directly
have
all
of
these
linked
here,
but
I
was
very
surprised
by
having
to
use
packages
and
registries
for
that.