►
From YouTube: GitLab 12.10 Kickoff - Verify:Continuous Integration
Description
12.10 Verify:CI - Highlights:
Dynamic child pipeline creation via artifact includes
https://gitlab.com/gitlab-org/gitlab/-/issues/35632
Wrapper for Jenkins execution inside of GitLab MVC
https://gitlab.com/groups/gitlab-org/-/epics/2779
CLI tool for building Jenkins execution container from existing server
https://gitlab.com/gitlab-org/gitlab/-/issues/208848
A
A
So
we
previously
introduced
support
for
a
parent-child
pipeline
which
allowed
you
to
configure
a
pipeline
that
can
trigger
another
pipeline
where
the
triggering
pipeline
is
the
parent
and
the
triggered
pipeline
is
the
child.
As
a
follow-up
to
that
feature,
we
began
work
on
a
couple
a
couple
milestones
ago
to
release
in
the
upcoming
12:10.
This
dynamic
child
pipeline
creation
via
artifact
includes
feature.
A
This
is
the
ability
to
dynamically
generate
a
get
lab,
see
IMO
file
and
what
it
allows
you
to
do
is
generate
child
pipelines
that
reflect
runtime
analysis
of
what's
changed
or
a
multitude
of
other
criteria,
which
can
be
defined
in
a
build
matrix
of
input
variables.
So
this
feature
should
open
up
a
lot
of
interesting
use
cases
and
we're
looking
forward
to
delivering
that
to
you
in
12
at
10.
A
Next,
during
12.9,
we
started
our
work
to
improve
the
experience
migrating
from
Jenkins
to
get
lab.
We,
as
part
of
that
work,
is
this
issue
for
a
wrapper
for
Jenkins
execution
inside
of
gate.
Lab
MVC
is
our
initial
step
in
the
larger
effort
for
migrating
from
Jenkins
to
get
lamb,
and
what
we
want
to
do
is
make
it
easy
to
get
started
with
an
option
to
run
Jenkins
files
in
a
container
inside
gitlab.
A
The
existing
implementations
that
we
know
of
this
approach
is
entirely
a
manual
process,
so
our
first
steps
are
twofold:
to
automate
as
much
as
possible
the
process
that
is
now
purely
manual
and
to
document
all
the
how
to's
for
the
remaining
manual
processes,
such
as
how
to
set
up
your
pipeline
to
correctly
run
your
jenkins
file
in
a
container,
how
to
create
a
runner
capable
of
running
the
jenkins
file
container
or
even
how
to
use,
get
lab
features
with
the
outputs
from
the
jenkins
file.
John.
A
A
Well,
this
is
just
an
initial
step
and
a
minimal
viable
change
in
the
journey
to
convert
Jenkins
installations
to
get
lab
CI.
We
hope
that,
along
with
the
detailed
documentation
and
this
tool
that
it'll
assists
assist
users
needing
to
convert
from
Jenkins
to
get
lab,
that's
it
for
what
we
plan
for
1210
release
for
the
verified,
continuous
integration
group,
thanks
for
listening,
and
if
you
have
any
questions,
please
feel
free
to
ping
me
in
the
issues
that
will
be
listed
at
the
bottom
of
this
video
description.
Thank
you.