►
From YouTube: CI/CD Catalog overview - September 2023
Description
Frédéric goes through what the CI/CD Catalog looks like in September 2023 and what are the next steps.
A
Hello:
everyone-
my
name-
is
Frederica
plot
and
I'm
here
to
talk
about
the
CI
catalog
latest
overview.
For
the
sake
of
this
demo,
I've
already
created
an
empty
project
with
a
simple
readme
which
says
hi
from
the
pipeline
authoring
team
and
the
project
is
called
JavaScript
stuff
and
it
lives
under
the
root
namespace
of
our
admin
user.
So
we
have
a
brand
new
project
and
it's
empty
and
I
want
this
to
become
a
CI
catalog
repository.
What
I'm
going
to
do
is
I'm
going
to
create
a
new
file
which
I'm
going
to
call
template.yaml.
A
This
is
currently
the
default
name
that
will
be
picked
up
automatically
to
work
as
our
main
entry
for
the
the
component,
then,
for
now,
I'm
just
going
to
write
a
very
okay,
literally
a
simple
job
which
will
do
just
a
heko
hello
from
the
pipeline
honoring
team
perfect.
Now
they
have
this
file
I'm
just
going
to
commit
it
right
here.
A
So
we
have
all
of
the
requisite
requires
all
of
the
requirements
for
a
component
repository
which
is
to
have
a
readme
file
and
a
root
and
have
a
template.yaml
for
the
actual
templates
of
the
component.
Now
that
we
have
this,
we
have
to
go
in
settings,
we
have
to
go
and
set
in
general
and
we're
going
to
go
and
Mark
this
repository
as
a
catalog
resource.
This
is
for
now
still
in
debate
and
very
much
MVC.
A
The
idea
is
that
user
can
convert
an
existing
project
to
become
a
component
repository
if
they
have
all
of
the
requirements.
So
we
have
cicd
resource
Mark
project
as
a
CI
catalog
resource
and
then
with
an
explanation.
If
I
click
on
the
toggle
I
have
a
warning
that
this
is
not
reversible
again,
this
is
very
MVC.
A
This
may
or
may
not
be
reversible.
This
may
not
be
a
toggle.
This
is
there's
still
a
bunch
of
issues
which
we
can
link
after
this
video,
so
I'm
going
to
mark
this
as
a
component
repository
and
what
that
effectively
does
is
that
it
will
look
inside
this
repository
and
make
oh,
oh
here
we
go.
I
forgot
to
have
a
description.
Yes,
project
must
have
a
description.
Thank
you
error
message
and
therefore
we
need
to
add
a
project
description,
and
so
this
this
is
a
project.
A
And
we're
going
to
received
this
here,
we
go
now
if
I
go
back
into
visibility
and
I
do
this
again
and
I
mark
it
has
worked.
So
what
this
effectively
does,
as
I
was
saying
before,
is
that
now
this
repository
is
a
catalog
resource
and
it
will
expose
any
components
that
is
under
the
root
namespace
or
any
namespace
for
that
matter,
any
of
any
components
that
lives
under
root
is
going
to
be
exposed
to
the
same
catalog,
so
JavaScript
stuff
is
exposed
within
any
project
that
has
the
same
namespace.
A
A
A
One
of
the
solution
for
this
is
to
moving
the
catalog
from
a
project
name
space
to
an
organizational
namespace,
but
organizations
are
not
released
yet
so
this
little
Quirk
will
will
stay
for
a
while.
So
if
I
go
on
this
we'll
see
here
we
have
the
description.
This
is
a
component
repository
for
JavaScript
related
stuff.
There
are
no
released.
This
is
also
interesting.
A
So
for
the
MVC,
you
did
not
need
to
release
a
component
for
it
to
be
visible
inside
the
CI
CD
catalog,
but
it
has
been
discussed
and
it
is
the
intention
that
only
release
component
would
appear
here
and
therefore
this
is
being
worked
on
right
now,
but
for
now,
unreleased
components
are
just
fine
and
they
automatically
appear.
I
can
scroll
through.
We
have
multiple
pages
of
components
and
for
this
demo
I
can
go
and
see
what
about
JavaScript
stuff.
What
is
it
that
we
have
here?
So
we
have
a
few
useful
link.
A
We
can
go
to
the
project
itself
which,
if
I
click,
will
take
me
right
to
the
repository
View.
We
are
working
on
adding
a
little
badge
to
the
project
view
here.
That
will
say
this
is
a
component
repository
as
well
to
avoid
confusion.
So
if
I'm
going
back,
we
have
the
kind
of
issue.
Other
kind
of
merge
requests
the
latest
release
and
right
now
there
are
no
release
the
project
description,
and
this
is
this
is
new.
So
if
you
would
go
right
now
on
on
production,
you
would
not
see
exactly
the
structure.
A
This
information
is
all
available,
but
just
not
instead
of
being
right
here
on
the
left.
It's
it's
in
the
sidebar
on
the
right,
but
I'm
currently
on
my
on
my
Branch
right
here,
and
this
is
implementing
the
new
view,
which
is
the
readme
here
over
fetching
right
hi
from
the
pipe
I
think
this
is
the
the
markdown
version
of
our
readme,
and
this
already
exists.
It's
just
not
under
the
readme
tab.
A
But
now,
on
top
of
that,
I
can
go
into
my
rail
console
and
I
can
enable
the
feature
flag,
CI
catalog
components,
tab
which,
what
it
will
do
is
add.
This
new
tab
called
components,
and
this
is
this
documents
all
of
the
inputs
and
a
different
way
of
using
the
component
directly.
So
we
still
have
the
readme
tab,
but
this
is
going
to
be
automatically
generated
by
the
structure
of
your
component.
So
what
are
the
inputs?
A
What
are
the
the
default
value
and
is
it
mandatory-
and
here
here
this
is
a
snippet
of
how
you
would
use
it
and
we're
going
to
add
a
copy
button
right
here
to
copy
to
clipboard,
and
so
this
is
pretty
interesting
right
now.
This
is
mock
data.
It's
it
is
not.
This
is
why
it's
populated,
if
you're
wondering
why
does
it
disappear?
He
hasn't
done
anything
on
his
component
repository.
A
This
is
just
fake
data,
but
the
the
structure
is
exactly
what
we're
going
to
use
on
the
API,
and
this
is
the
actual
visual
representation
of
what
that
would
look
like,
and
so
now
we
can
toggle
in
between
and
we're
here.
We
are.
Another
interesting
thing
to
note:
is
that
the
the
information
that
is
fetched
when
you
are
in
this
list?
A
So
if
I
click
on
I
think
for
the
sake
of
this
showcase
I'm
going
to
turn
this
feature
flag
off
to
have
only
the
readme
tab,
I'm
going
to
refresh
if
I
go
in
the
rails
component
and
I
have
this
big
readme
here
and
I'm
reading?
True,
we
have
all
of
this
information.
If
I
go
back,
see
the
the
list
is
instantly
loaded
because
we've
cached
the
list
of
components
while
the
user
was
there
and
if
I
go
back
on
this
component,
it's
already
prefetched
as
well.
A
So
this
is
just
a
nice
little
bonus
that
I
wanted
to
show
that
I
quite
like
which
make
browsing
quite
quite
fast
if
you're
going
back
and
forth
on
components
that
you've
already
seen,
which
is
interesting.
So
this
is
where
we
are
right
now
with
all
of
the
front-end
stuff
and
how
this
looks
like
and
how
it's
being
used,
the
most
Charming.
A
Next,
steps
are
going
to
be
well
jarring,
I
would
just
say
the
most
oppressing
matter,
and
next
would
be
how
how
the
release
component
looks
right
now,
with
the
release
interface
that
we
have
and
how
do
we?
How
do
we
leverage
that
Insider
or
interface?
So
that's
it.
If
you
have
any
more
questions,
please
let
me
know
thank
you.