►
Description
https://gitlab.com/gitlab-org/incubation-engineering/devops-for-mobile-apps/readme/-/issues/62
🎉 🎉 New Mailing List!! 🎉 🎉
Sign up here: https://www.getrevue.co/profile/devops-for-mobile-apps
A
and
on
my
screen
here,
you'll
see
the
update
issue
so
in
this
in
this
issue,
I've
got
kind
of
the
notes
for
this
update
and
some
links
to
some
of
the
things
I'm
going
to
talk
about.
I'm
going
to
link
this
issue
in
the
youtube
description
below,
so
you
can
get
to
it
there,
but
other
than
that
I'll
just
jump
right
into
it.
A
So
first
things
first
on
the
notes
here:
I've
created
a
new
mailing
list,
so
I
have
talked
to
some
folks
that
haven't
been
able
to
keep
up
with
the
recorded
updates
or
just
kind
of
want,
a
different
way
to
do
it.
So
I'm
going
to
try
this
out
there's
a
link
right
here
and
you
can
click
in
there
and
just
throw.
A
And
and
then
you'll
you'll
get
some
emails
when
I,
when
I
send
those
out,
I
haven't
decided
what
cadence
will
do
that
yet,
but
that's
just
a
way
to
kind
of
get
updated
there.
So
the
the
next
section
here
is
just
about
the
weekly
sync
update
experiment.
So
this
is
what
we're
doing
today
we're
doing
a
sync
update
and
we'll
you
know,
put
it
on
the
calendar
and
put
it
out
for
folks
to
participate
and
then
we'll
put
the
recording
up
on
youtube
when
it's
done.
A
So
that's
kind
of
all
the
housekeeping
notes.
So
much
of
this
week
has
been
focused
on
the
secure
files,
feature
and
kind
of
getting
that
ready
for
production.
So
the
first
issue
here
is
this
readiness
review,
which
is
this
process
that
I'm
going
through
with
infrastructure
to
kind
of
review
the
feature
review,
the
potential
infrastructure
impact
of
it
and
and
be
able
to
kind
of
make
sure
that
we're
we're
pushing
out
something
that's
going
to
be
stable
when
we
release
it.
A
So,
there's
a
there's
a
lot
of
discussion
in
there,
but
I
kind
of
like
that
there
for
anyone
that
wants
to
kind
of
follow
along
and
then
the
the
next
thing
next
link
here
is
the
secure
files
mvc
issue.
So
this
is
kind
of
something
I've
been
talking
about
each
week.
This
is
kind
of
the
big
set
of
work
that
needs
to
be
done
to
get
the
secure
files
feature
rolled
out,
and
so
things
are
moving
along
nicely.
A
We
had
a
couple
mrs
merged
this
week
and
so
we're
just
continuing
to
work
through
the
issues
in
there
and
then
the
the
last
section
here,
let's
see
actually
the
upload
checksum
feature.
This
is
one
of
the
mrs
that
was
merged
this
week,
and
I
thought
I
would
talk
about
this
for
just
a
second.
Basically,
what
this
is
doing
is
this
is
adding
a
capability
to
the
api.
A
So
essentially,
what
this
will
provide,
then,
is
the
ability
to
check
that
the
file
that
you're
sending
is
the
file
that
gitlab
receives,
and
so
the
the
user
will
upload
the
file
they'll
shot
g56,
create
a
shot,
256
checksum
off
of
that
file
and
they'll
send
those
two
things
along,
and
so,
when
we,
when
we
go.
A
That
file
on
the
back
end,
what
we're
going
to
do
is
we're
going
to
check
that
and
make
sure
that
the
the
file
matches-
and
so
you
can
see
kind
of
in
the
code
here,
where
we're
doing
that.
This
is
this
is
kind
of
a
nice
security
feature
that
helps
us,
ensure
that
we're
getting
what
the
user
is
sending
if
there's
no
nothing,
nothing
nefarious
happening
in
between
there.
A
This
kind
of
aligns
on
the
download
side
too,
then.
So,
when
we
we,
we
also
have
an
optional
feature
on
the
download
that
will
give
you
the
file
and
then
we'll
also
send
the
check
some
of
that
file.
A
So
you
can
verify
that
the
file
that
you're
receiving
in
your
project
is
the
file
that
that
you're
expecting
so
kind
of
closes
the
loop
on
that
so
that
that
was
merged
just
today
actually,
and
then
the
the
last
thing
here-
and
I
talked
about
this
last
week
too-
is
the
integration
with
fast
lane
match,
and
so
there
is
an
issue
here
for
this.
So
this
is
to
use
gitlab
secure
files
as
a
backend
for
fastlane
match,
and
so
this
would.
A
I
have
a
working
demo
of
this
and
then
I've
got
a
branch
in
the
fastlane
project
and
in
my
fork
that
I've
that
I've
been
working
on
here,
so
you
can
kind
of
see
how
this
is
all
put
together.
I
haven't
done
a
pr
yet
for
this,
I'm
going
to
wait
till
the
feature
rolls
out
to
production
before
we
before
we
do
that,
just
so
that
the
maintainers
of
fastlane
know
what
this
is
and
can
understand
what
we're
doing
so.
A
So
that's
the
that's
what
we're
working
on
there
and
so
then
I
guess
coming
up
next,
the
focus
is
going
to
be
on
continuing
the
readiness
review
and
then
out
of
the
readiness
review.
There
is
a
nice
discussion
about
potentially
changing
our
file
encryption
process,
and
so
there's
an
issue
here
and
I'm
going
to
work
through
that
this
week
and
potentially
make
a
change.
There
shouldn't
be
too
too
major,
but
it
was
kind
of
a
nice
nice
discussion
and
a
nice
find
there.
B
This
this
is
a
really
good
overview
and
I'd
love
to
see
that
the
the
secure
files
is
the
direction
we're
going
by
speaking
from
customers,
specifically
kind
of
on
the
mobile
and
working
with
competitors
that
it's
a
certain
certain
gap
we
have
with
those
secure
files.
How
is
that
injected
into
the
pipeline
today?
Is
there
a
variable
exposed
or
how
does
that?
How
does
that
work.
A
Yeah
great
question,
so
in
the
let
me
see
where
do
I
have
this
so
right
now
there
is
just
kind
of
a
a
simple
integration.
I
guess
we
could
get
to
it
this
way
here.
So
there's
just
this
little
ruby
script
that
that
I
kind
of
created
to
to
go
to
the
api
and
fetch
the
files
and
download
them,
and
it's
it's
packaged
up
in
a
way
that
makes
it
actually
really
easy
to
to
add
to
a
ci
job.
A
So
if
you
just
copy
this
one
liner
here,
this
will
go
download
the
files
and
put
them
into
a
folder
in
the
project.
You
can
configure
the
folder
that
they
go
into
if
you
want,
but
that's
sort
of
like
the
quick,
the
quick
mvc
in
the
future,
I'd
like
to
have
a
more
kind
of
robust
integration
with
gitlab
runner
to
to
make
it
easier
to
sort
of
like
choose
which
files
go
where
or
which
jobs
they
might
go
to.
A
That's
kind
of,
I
don't
know
future
thinking
about
what
that
might
look
like,
but
this
is
for
for
the
first
iteration.
It's
just
going
to
be
this.
This
one
liner.
B
Awesome
yeah
that
makes
sense
for
an
mbc
for
from
a
permission,
standpoint
oftentimes,
especially
with
like
those
signatures.
A
So
yeah
good
question
so
the
way
that
it's
set
up
right
now
is
I'm
trying
to
the
maintainer
maintainer
access
can
upload
and
delete,
and
then
you
need
developer
access
to
be
able
to
download
the
files
around
the
pipelines
and
that
sort
of
thing.
So
that's
the
way
it's
set
up
today.
We
could
certainly
like
come
up
with
different
permissions
for
that,
but
you
know,
for
I
guess,
for
the
ci5
lines
to
be
able
to
work,
we
need
developers
to
be
able
to
read
them.
Yeah
yeah,
that's
that's!.
A
A
C
A
B
A
Yeah
so
the
way
it's
set
up,
it
can
either
use
like
the
local
file,
storage
or
object
storage,
and
so
the
way
we
would
we'd
roll
that
out
on
gitlab.com
would
be
to
use
object,
storage
and
then
the
files
there,
as
they're
uploaded
they're
encrypted
for
their
or
like,
when
they're
saved,
to
the
file
storage,
so
they're
encrypted
at.