►
From YouTube: Incubation Engineering Mobile DevOps -- Update 2022-11-4
A
Hi
folks,
this
is
the
Mobile
devops
update
for
November
4th
2022..
This
week,
I've
been
focused
on
adding
support
for
project
level,
secure
files
to
the
gitlab
runner,
so
I
thought
I'd.
Take
this
opportunity
to
demo
the
changes
and
talk
about
why
they're
needed
for
some
context.
Project
level,
secure
files
is
a
feature
that
allows
files
to
be
securely
uploaded
to
a
gitlab
project
outside
of
Version
Control,
so
that
they
can
be
used
in
CI
jobs
similar
to
CI
variables,
but
with
support
for
binary
file
types
and
a
different
UI.
A
This
feature
is
useful
for
any
projects
that
need
to
utilize
certificates
or
Keys
during
their
build
process
and
in
the
case
of
mobile,
we
use
it
to
manage
provisioning
profiles
and
signing
certificates
needed
in
the
code
signing
process
to
upload
these
files.
We
can
simply
use
the
secure
files
section
in
the
CI
CD
settings
page
once
the
files
are
uploaded.
We
need
a
way
to
load
those
files
into
CI
jobs
in
the
gitlab
runner.
The
first
iteration
of
this
leverage,
the
Ruby
script
that
used
the
API
to
load,
secure
files
into
a
CI
job.
A
The
script
works
fine
and
is
actively
in
use
by
over
300
projects
today,
but
some
users
have
run
into
issues
and
we
need
a
native
integration
before
we
roll
out
the
feature
to
self-manage
customers.
The
proposal
for
secure
files,
Runner
support
MVC,
describes
an
implementation
similar
to
the
original
Ruby
script
without
the
extra
dependencies.
A
This
implementation
looks
for
a
CI
variable
called
secure
files,
download
path.
If
that
variable
is
defined,
the
secure
files
loader
is
invoked
in
the
runner
and
all
the
secure
files
for
the
project
are
downloaded
to
the
location
specified
in
the
variable
to
make
this
work.
I've
drafted
two
Mrs
one
for
gitlab
and
one
for
the
runner
The
Gate
lab
Mr
extends
the
payload
of
the
jobs
request,
API
to
include
attributes
for
the
projects
to
secure
files,
specifically
the
name,
download,
URL
and
checksum.
A
A
Both
of
these
Mrs
are
in
the
early
stages,
so
I'm
looking
to
get
feedback
on
the
overall
approach,
as
well
as
the
implementation
specifics
in
each
change
feel
free
to
leave
any
comments
or
suggestions
in
these
Mrs
or
ping
me
on
Slack.
That's
all
for
today.
The
issue
for
this
update
is
linked
in
the
video
description
below
and
has
links
to
everything
I've
covered
in
this
demo.
Thanks
for
watching.