►
From YouTube: GitLab 13.3 Kickoff - Configure:Configure
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
The
second
is
to
ship
a
future
proof.
Multiple
traffic
report
support
in
the
merged
requests,
widget
that
we
shipped
two
months
ago.
Our
current
design
is
nothing
not
aligned
with
gitlab
merge,
request
widgets.
So
we
have
to
change
that
and
we
want
to
improve
it
at
the
same
time,
by
adding
support
for
multiple
platform
reports,
we
have
a
strategic
goal
as
well
for
this
milestone,
which
is
to
provide
admin
interfaces
for
the
gitlab
manager
from
state.
A
Let's
get
into
more
details,
we
have
some
ongoing
work
unrelated
to
these
goals,
with
respect
to
support
of
cloud
native
buildbacks
cognitive,
build
packs
are
the
future
and
next
generation
of
buildbacks
after
hirokush
and
herokuchi
is
expected
to
be
end
of
life.
Any
time
damien
reached
out
to
us
time
months
ago
and
told
us
that
they
will
probably
archive
the
project
in
q1,
so
we
want
to
be
safe.
We
already
missed
q1.
As
a
result,
we
would
like
to
provide
the
best
cloud
native
support
available
on
the
market
as
soon
as
possible.
A
A
A
We
we
want
to
improve
the
git
laptop
from
provider
as
we
became
the
maintainers
of
that,
and
there
are
a
few
outstanding
pull
requests
once
the
api
parts
at
git
website
is
settled.
We
can
accept
the
merge
request
in
the
upstream
github
repo
and
we
would
like
to
provide
environment
variable
support
inside
the
transformation
backend.
This
will
make
the
gitlab
terraform
manage
state
experience
much
more
pleasant
because
we
don't
have
to
specify
all
kinds
of
variables
on
the
command
line.
We
can
just
use
the
environment
for
ibus.
A
And
then
getting
back
to
the
outer
devs
issues
here,
ham
2
is
expected
to
be
deprecated
in
november,
so
we
want
to
provide
hand
free
support
by
that
time,
actually
the
earliest
possible,
and
for
that
we
did
all
the
necessary
back
and
work
and
exploratory
work
in
13.2,
and
we
can
start
rolling
out
a
handful
support
in
13.3.
A
We
want
to
support.
We
want
to
provide
support
for
cutting-edge
users
who
really
want
to
try
out
or
need
hand-free
support.
We
are
not
providing
an
upgrade
path
yet
and,
as
you
can
see,
but
people
who
actually
want
to
use
humphrey,
they
will
have
the
possibility
to
do
so
instead
of
autodevops
and
at
the
same
time
as
you
see,
these
are
stretch
goals
so
consider
it
as
such.
A
We
want
to
focus
a
lot
on
the
workflow
around
the
gitlab
kubernetes
agent
from
the
developer's
point
of
view.
So
this
is
not
about
installing
the
agent
we
have
that
workflow
figured
out,
but
how
does
a
git
commit
in
a
business
logic,
application
repository
results
in
code
being
deployed
to
a
cluster
using
the
gitlab
kubernetes
agent?
This
is
the
question
you
would
like
to
answer
and,
as
you
might
see
on
this
nice
diagram,
this
is
not
a
trivial
question
or
because
we
have
to
figure
out
all
the
workflows
or
the
triggers
around
it.
A
First
of
all,
we've
created
a
jobs
to
be
done
list
in
the
past
month
and
we
would
like
to
validate
it
in
order
to
have
a
better
maturity
for
our
institute's
code
feature
set
and
category
and
the
other
issues
here
are
about
moving
forward
with
our
terraform
support
we
are
looking
into.
We
are
actually
looking
into
how
to
add
more
information
around
our
form
into
merge
requests.
The
current
widget
is
great.