►
From YouTube: Kyma Prow Migration WG meeting 20181123
Description
Meeting notes: https://docs.google.com/document/d/1ljEAoCBJXlxx_ATPyvKZ1KoyFOSIBzEAOkN-2H-HhUY/edit
A
So
hello,
everyone
on
the
next
working
group
pro
meeting
I'm
your
host
today
and
Solomon-
will
take
notes.
Agenda
for
today
is
following
at
the
beginning:
I
will
present
you
the
current
status
and
the
next
priorities
and
later
layman
give
you
some
update
about
accessing
job
due
dates,
and
so
at
the
beginning.
Let's
have
a
look.
What
we
have
done
in
the
recent
week,
as
you
can
see,
2024
poll
will
pull.
The
requests
were
merged
quite
a
lot,
and
now,
let's
go
to
the
dashboard.
A
We
have
a
lot
of
issues
in
to
accept
column.
First
one
is
about
preparing
for
submit
flow
for
component.
It
was,
it
was
done,
I.
Think
for
this.
You
appeal
a
component
and
I
think
that
here
you
have
more
information
that
we
added
not
only
possibly
jobs
for
UAB
layer,
but
also
some
renomii
was
done.
For
example,
previously
we
pipeline
is
aged
script.
Now
we
noticed
that
probably
better
name
will
be
built
as
age
and
some
other
things
were
change.
Also,
migration
guide
was
updated
and
the
next
issue
was
about
kima
integration,
jobs.
A
Next
thing
is
also
very
important:
we
define
the
branch
protections
for
the
test
entry
repository,
so
let's
have
a
look
on
the
tests
intra
and
in
the
CRO
config,
and
on
the
bottom
of
that
file
you
have
branch
protections
defined
and
for
the
it
has
entered
repository,
we
mark
that
required
status.
Checks
are
required,
and
this
is
very
important
to
remember
that
whenever
you
add
new
job
for
the
test,
incredible
story.
A
A
Ok,
then
we
also
have
done
some
refactoring.
For
example,
some
scripts
from
from
for
provisioning
cluster
was
most
two
different
placed.
We
also
had
testing
a
sage
to
be
execute
on
Jiki
integration
pipeline
and
generally
this
the
whole
story
about
Jiki
integration
test
are
already
finished,
but
still
we
will
have
a
lot
of
improvements
in
that
area.
A
We
also
define
sorry
for
screwing
with
the
fine
job
for
validating
tools
project.
So
in
the
tests
infra
repository
in
the
development,
we
have
tools
project
and
we
define
job
for
validating.
If
everything
is
fine
there,
we
also
start
migrating
some
components:
for
example,
remote
environment
broker,
Oh.
A
A
We
already
define
some
jobs
for
the
test
in
therapist
Tori,
so
let's
have
a
look.
What
we
already
have,
it
probably
will
be
in
the
Pro
and
Pro
jobs,
test
infra,
and
so
we
have
a
jobs
for
validating
all
built
backs.
We
have
tests
for
before
checking
job
definitions
and
that
test
just
run
all
tests
which
are
placed
in
tools
jobs.
A
A
And
can
you
see
my
slides
yeah,
thank
you,
and
so
previously,
I
represented
that
our
next
goal
is
to
enable
migration
of
components,
and
we
have
three
prerequisites
and,
as
you
can
see,
all
of
them
are
already
done.
So
we
have
this
one
working
example:
documentation
is
provided,
and
this
incredible
story
has
different.
A
So
now
our
current
goals
are
fall
following
certain.
First
of
all,
we
have
to
help
in
the
migration
we
have
an
epoch
for
that.
That
gather
all
issues
related
to
the
migration
of
components,
and
we
also
have
three
very
important
topics.
First,
is
about
accessing
logs
from
jobs,
so
this
is
in
progress,
and
today
Solomon
give
you
an
update
about
that.
We
have
also
another
story
about
providing
key
metrics
from
pro
to
see
how
our
system
is
behaving.
A
B
B
Actually,
this
is
the
product
component
that
they
would
like
to
migrate
to
from
Governator.
So
for
now
they
only
have
it
to
see
the
job
details
from
deck
and
but
in
the
future
it
will
be
used
to
view
the
jobs
from
directly
from
the
PR
as
well,
and
but
it's
not
there.
Yet
they
have
a
training
issue
and
I'm
also
on
track
to
see
the
progress
here-
and
this
is
one
of
the
one
of
the
tasks
here
saying
that
they
need
to
replace
the
your
banister
links
with
spyglass
links
on
get
appears.
B
So,
unfortunately,
since
it's
not
there
yet,
we
I
had
to
deploy
both
Jabbar
Nader
and
also
spyglass.
So
this
right
now
it's
on
the
PR,
but
I
was
testing
it
on
production
cluster.
Today,
that's
why
I
have
some
things
to
show
you,
for
example,
from
ya
heartache.
Now
we
have
this
funny-looking
ice
this.
These
are
actual
links
to
spyglass.
So
let's
check
how
it
looks
like
when
you
click
on
them.
It
fetches
some
metadata
before
these
are
all
come
from
the
production
bucket.
We
have
that
we
are
using
for
deluxe
what
it.
B
As
it
from
github
UI,
actually
I
can
show
you
one
of
them
that
I
tried
here.
As
you
see,
for
the
other
jobs,
we
don't
have
a
details
link,
whereas
we
have
for
this
test.
Infrared
dates
are
secrets
because
that
was
I
was
trying.
Let
me
click
on
that.
It
will
lead
us
to
the
pure
nature
we've.
Actually
it
doesn't
have
much
here
because
it
was
successful,
but
still
when
we
click
on
the
locks,
we
can
see
the
rocks
here
saying
no
issues
detected
this.