►
From YouTube: 2023 05 22 Docker-based quickstart examples
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
A
A
A
A
A
Bruno
verachten:,
I
was
supposed
to
start
a
discussion
also
with
the
infrared
team.
because,,
as
you
know,.
We
hope
to
have
our
docker
base.
Quick,
start
examples.
part
of
the
jenkins.
Are
your
website
and
tested
on
the
regular
basis.
so
we'll
have
to
discuss
with
the
infra
team
so
that
they
can
help
us
to
automate
that..
So
I
started
that
last
friday.
A
A
A
B
B
A
A
Bruno
verachten:,
but
he
did,
nonetheless,,
and
I
I
wanted
to
review
it
this
morning,
and
then
I
discovered
that
so
you
had
reviewed
it,
that
chris
had
beened
us,
and
that
it
all
already
emerged,,
which
is
fine,
because,
of
course,.
My
review
would
have
been
looks
good
to
me,,
so
no
value
added
on
my
side..
So
just
during
the
weekend,
if
the
other
are
okay
with
that.
A
A
A
A
A
A
A
Bruno
verachten:,
I
wouldn't
say
branches.
but
yes,
we
will
have
to
write
some
documentation
on
jenkins..
I,
of
course
you've
got
your
own
for,
and
you
will
have
to
use
branches
on
your
fork
before
making
a
pr..
I
haven't
checked,,
but
of
course
I
guess
that's
what
you
did
with
your
jenkins
particularly.
okay.,
because
master
to
master,.
That's
a
mess.
A
Bruno
verachten:
make
pull,
request
to
another
repo,,
just
to
keep
things
well
separated,
and
to
have
a
main
branch
that
always
does
work,
and
all
the
that
could
be
called
feature.
Branch,
or
whatever
maybe
be
able
to,
I'll
say
we
have
better
id
than
I
have.,
but
you
know,,
when
you're
working
on
a
part
particular
subset
of
what
we
are
asking
you
to
do.
maybe.,
create
a
branch
and
then
make
a
pr
to
your
own
main
branch.
A
A
Bruno
verachten:
branch
on
your
fork
or
jenkins
I/o
repo.,
so
your
docker
composite
get
integrated
into
the
jenkins,.
I
your
website.,
but
first
timing,
we're
working
with
a
standalone
repository
with
your
own
examples.,
but
please
do
use
branches.
whenever
you
are
starting
with
a
new
docker
compose,
or
a
new
feature
that
you
want
to
implement?.
D
D
A
D
B
B
A
A
A
A
A
A
A
A
Bruno
verachten:,
then
I
know
it's
pretty
early,
but
you
could
start
the
discussion
on
community
jenkins.
I/o,
about
the
mandatory
steps
to
get
automation.
Started,
you
know,.
Whenever
you
have
a
docker
compose
that
does
work
for
you,
we'd
like
to
add
it
someday
in
the
jenkins
I.
o,
and
it
should
be
linked
to
an
existing
documentation,
but
also,,
and
that
the
main
point.
A
A
Bruno
verachten:
and
the
rest
of
the
community
to
know
how
we'll
be
able
to
implement
that.
for
example,.
They
did
something
special
for
another
project,
which
is
jenkins.
plug
in
health?
no,.
They
had
to
add
something
to
test
regularly,
and
so
on..
So
that's
the
same
kind
of
things.,
so
first
thing
would
be
to
create
a
community.
jenkins,,
I/o,
blog
post
and
then
tagging
the
intra
team
in
that
post.
A
A
A
A
A
A
B
A
Bruno
verachten:,
it's
available
on
the
community.
jenkins,
I/o.
by
the
way,.
If
you
make
a
source
about
in
for
a
team,,
you
should
find
the
videos..
There
is
one
post
per
week,
because
it's
on
every
tuesday..
So
if
you
want
to
see
what's
going
on,,
it
should
be
fairly
easy
to
find
that
in
community
jenkins,
I
you.
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
C
C
A
C
A
A
A
A
Bruno
verachten:
newcomers.,
because
when
I
was
a
newcomer
last
year,
some
of
the
trouble
figuring
out
why
I
had
to
create
a
dock.,
a
fine!
why,
there
was
bluish,
and
why
there
were
so
many
cryptic
arguments
and
comments..
I
just
want
people
to
make
something
like
dog
or
compose
up
and
down.
they've
got
to
jenkins
working.
A
A
A
Bruno
verachten:,
but
bruno
verachten:
I.
I
let
you
go
for
the
rest
of
the
project,,
but
for
the
very
first
step
I
really
want
to
make
it
as
simple
as
possible,.
So
don't
expect
me
to
be
as
pushy
as
I
am
now
for
the
rest
of
the
project,,
because
it's
your
project,,
but
for
this
one
I
know
I
can
be
a
pain
in
the
neck,.
But.