►
A
A
So
this
week
we're
going
to
do
things
a
little
bit
different,
we're
not
going
to
demo
anything
specifically,
but
we're
going
to
take
a
step
back
and
look
at
the
overall
vision
for
this
group
and
kind
of
what
we're
focused
on
over
the
next
coming
months.
And
I've
broken
this
down
into
a
few
different
categories
here.
So
I'll
kind
of
go
through
each
of
these
and
talk
through
kind
of
what
the
thinking
is
for
each
one.
A
So
the
first
section
here
is
about
code
signing,
and
this
is
one
of
the
first
things
we
identified
as
a
really
confusing
and
error
prone
process
as
part
of
the
mobile
devops
experience,
and
so
what
we've
been
working
on-
and
this
is
in
progress
right
now-
is
a
feature.
We're
calling
secured
files-
and
this
is
like
a
generalized
solution
to
the
problem.
A
It
does
solve
the
problem
for
mobile
teams,
but
it
also
is
generalized
so
that
it
can
be
used
for
other
use
cases,
so
I've
linked
to
a
couple
of
the
the
issues
around
this,
and
then
I've
got
a
screenshot
in
here
or
a
couple
screenshots
in
here
to
show
kind
of
like
what
the
ui
is
going
to
look
like
and
at
a
high
level.
The
idea
is
for
gitlab
to
be
able
to
support
uploading
of
binary
files
that
can
then
be
used
in
the
ci
pipelines.
A
So
this
is
important
for
mobile,
because
provisioning
profiles
and
key
stores
are
binary
files
and
can't
be
used
in
a
very
simple
way,
with
our
current
ci
variable
system.
So
building
out
a
new
system
for
this
is,
is
going
to
be
very
helpful
and
make
the
process
very
easy.
So
from
here
you
can
see
the
the
idea
is
generally
to
be
able
to
click
and
click
and
drag
or
upload
a
file,
and
that
gets
added
to
the
project
with
that
file
in
the
project.
A
You
can
then
pull
that
file
into
your
runner
for
the
the
ci
jobs
that
need
it.
So
the
first
iteration
of
this
ui
is
very
straightforward
kind
of
just
lists
the
file
and
a
few
attributes
as
we
expand
this,
though
we
can
really
pull
in
some
more
mobile,
specific
use
cases,
so
here
I'm
showing
that
we
can
look
into,
we
can
inspect
the
certificates
and
determine
which
team
which
bundle
identifier,
which
you
know,
project
they're
for
and
like
what
their
expiration
dates
are
too.
A
These
are
pretty
important
for
for
mobile
teams
to
be
able
to
see
this
stuff.
So,
instead
of
just
having
kind
of
a
a
nondescript
link
to
a
file,
we
can
actually
provide
some
more
visibility
here.
So
this
will.
This
will
be
really
nice
for
teams
and
they
can
be
able
to
see
like
what
they're
working
with
and
which
profiles
and
certificates
are
being
used
in
which
ci
jobs,
so
that
is
kind
of
the
the
high
level
details
of
that.
A
A
So
then
the
next
section
I
have
in
here
is
about
app
store
and
google
play
store
integration.
So
this
is
another
example
of
where
we
need
credentials
and
certificates
and
various
different
configurations
for
the
actual
deploy
process
to
work.
So
this
would
be
taking
up
an
app
that
has
been
built
and
then
pushing
it
to
either
store,
and
this
would
be
in
the
various
scenarios,
so
it
could
be
internal
testing,
like
beta
groups
or
actual
public
releases.
A
Another
thing
that
is
is,
I
think,
important
to
call
out
typically
in
a
ci
pipeline,
your
deploy
step
is
going
to
be
at
the
end,
and
so,
if
you
have
a
configuration
problem,
you
have
to
run
through
the
whole
pipeline
before
you
get
there,
which
is
frustrating,
and
so
what
we
can
do
is
we
can
build
out
some.
You
know,
testing
tools
that
allow
us
to
actually
test
the
the
connection
within
gitlab
before
we
have
to
run
a
whole
pipeline.
A
The
third
thing
I
have
listed
here
is
improved
review
apps
for
mobile,
so
we
started
doing
some
of
this
early
on
a
few
months
ago,
which
was
a
ci
template
that
integrated
appetize
as
a
emulator
that
can
be
hooked
right
into
the
review,
apps
functionality
that
we
have
in
gitlab-
and
this
is
a
nice
feature-
it's.
It
is
a
bit
limited
in
scope,
and
I
think
we
can.
We
can
expand
on
that
and
improve
that.
So,
there's
a
couple
issues
that
I've
linked
in
here.
A
The
first
one
is
about
being
able
to
support
additional
emulators
like
device
farm
or
browser
stack
or
some
of
these
other
tools
and
there's
there's
some
changes
to
review
apps
that
will
need
to
to
come
in
to
make
that
all
work.
So
these
device
emulators,
don't
work
the
way
that
traditional
web
apps
do
they're,
not
always
on
and
just
sitting
there
waiting
for
requests.
So
we
will
want
to
expand
review
apps
so
that
we
can
give
users
the
ability
to
select
the
device
type
that
they
want
boot.
A
So
if
you
were
wanting
to
take
your
flutter
app
and
have
a
pipeline
that
ran
both
android
and
ios
and
build
it
all
in
one
in
one,
go,
there's
no
way
to
really
like
have
both
of
those
review.
Apps
running-
and
I
found
an
issue
where
some
folks
have
been
asking
for
this
already,
so
this
would
be
an
opportunity
to
deliver
on
that
and
solve
that
use
case
for
mobile
as
well.
A
I
think
we
can
limit
the
complexity
in
the
ci
templates,
while
still
being
able
to
provide
some
pretty
cool
functionality,
and
I
think
that's
important,
because
we
don't
want
to
get
into
a
state
where
the
ci
templates
are
brittle
and
hard
to
maintain
and
hard
to
enhance,
and
things
like
that,
so
I
think
leaning
on
fastlane
will
will
be
really
helpful
to
to
provide
that
capability.
So
so
those
are
the
main
things
that
we're
focused
on
right.
Now,
I'm
looking
for
suggestions
and
feedback.