►
Description
Discussion of the custom Jenkins Distribution build service. We discussed this idea with potential project mentors and Jenkins contributor summit at FOSDEM where this idea was discussed. Project idea page: https://jenkins.io/projects/gsoc/2020/project-ideas/jenkins-distribution-customize-service/ . Mailing list discussion: https://groups.google.com/d/msg/jenkinsci-dev/TzZ5mVqinuU/2RRTwaIUBQAJ
A
I
hope
today
we
have
a
short
discussion
about
the
Jenkins
distribution
packaging
service.
This
is
a
Tesla
project
eggie,
which
has
been
proposed
by
Eric.
Who
is
on
the
call,
so
we
will
just
use
this
opportunity
to
think
up
about
the
project
ID
and
about
our
expectations,
because
in
fact
there
were
two
parallel
discussions,
one
in
the
mail
increase
and
the
injury
subchannels.
Another
track
was
at
the
contributor
summit
in
Brussels
way.
We
discuss
pretty
much
the
same
idea
but
from
different
angle.
A
B
C
A
Since
I've
participated
in
post
office,
so
my
understanding
that
he
we
try
to
build
this
service
with
some
examples
of
what
would
be
included.
The
word
discussion
at
the
contributor
summit
was
about
how
to
define
the
packages
and
what
should
be
inside
there,
so
yeah.
These
stories
are
definitely
complement.
Each
other
and
I
was
wondering
whether
we
could
just
set
some
expectations
here
so
that
students
reading
through
this
project
basically
follow
the
expectations.
Also,
definitely
the
contributor
summit,
so
basically
concept
of
meta
packages
for
different
technologies.
E
E
A
D
A
C
E
E
It
would
be
reasonable
to
shortlist
some
of
the
popular
ones
like
a
lot
of
people
will
want
the
AWS
thing,
because
they're
running
Jenkins
on
AWS
and
a
lot
of
people
want
the
ashy
or
equivalent,
because
the
Jenkins
is
on
Asha,
and
so
you
could
in
indeed
I
think
there
is
already
a
mechanism
when
you
first
start
up
Jenkins
it.
It
suggests
packages
that
you
should
have
I
think
just
send
that
to
us
in
the
email.
A
Yeah
the
result
initially
reserved
this
installation
wizard
is
a
bit
outdated,
recently
started
doing
the
documentation
seek.
So
we
are
the
work
in
the
plugin
side
and
just
a
few
days
ago
we
added
the
technology
labels.
So,
for
example,
now
you
can
search
for
AWS
planes
for
Asia,
plugins
or
Google
Cloud
or
several
other
technologies,
and
we
start
to
the
grouping
these
plugins.
So,
for
example,
here
you
can
see
a
bunch
of
plugins
for
Asia.
A
A
For
me,
one
of
the
difference
of
what
is
documented
here
so
yep
should
Jenkins
bundles
with
chiffon
change
for
common
use
cases.
So
it
includes
changes,
plugins
and
extra
configurations.
So
my
understanding
of
the
meta
package
originally
was
that
it
would
also
include
configurations
so
that
we
could
read
okay,
how
I
call
them
ready
to
fire
jenkins
images.
I.
E
E
C
A
B
E
A
C
D
A
C
C
We
can
imagine
that
we
use
deacons
like
we
go
to
as
Rumaki
that
we
just
pick
out
what
we
want.
Maybe
we
don't
need
to
too
much
about
the
details
of
the
technology
which
has
them.
For
example,
we
want
to
use
deacons
under
Java
level
and
that
we
want
to
the
1/3
tickets
wrong
in
companies,
law,
cluster
and
the
Alice's.
Then
the
user
just
cling
to
the
pattern
under
get
what
you
want.
A
E
There
was
a
line
that
you
highlighted
in
the
email
chain
to
share
your
Jenkins
configuration
and
I
think
it
was
always
central.
Tooling
team
does
place,
so
we
have
like
this
team
that
works
on
producing
the
standard,
Jenkins
subway,
which
just
let
me
talk
because
currently
we
don't
have
a
centralized
Jenkins
thing
as
the
team's,
the
product
teams
run
their
own
and
they
all
from
this
template
a.
A
There
are
dozens
of
different
shade
configurations
in
the
net
which
are
based
on
doctored
packaging
example.
This
is
just
one,
my
old
to
demo,
which
basically
extends
jinkies
docker
image
in
standard
is
inject
slam
all
there
and
you
get
everything
working,
yeah
custom
work
package.
It
was
one
step
forward
because
customers
are
package
are
intended
to
switch
all
these
custom
scripts.
So
you
can
see
that
the
data
shows
there,
but
there
is
docker
file
and
other
things.
A
So
a
retention
of
customer
packages
was
to
provide
a
single
regional
waste
definition
which
would
define
what
you
want
to
get
in
your
jenkins.
So
here
you
can
see
that
you
saw
a
world
formed.
You
can
specify
plugins
configuration
as
code
like
that
or
just
by
including
text,
and
then
you
got
your
instance
training
defined
by
a
single
kinetic
and
since
the
siamo
it
would
be
more
compatible
with
helen
charts
and
there's
other
things
like.
Let's
say,
one
could
create
a
special
operator
and
kubernetes
for
Jenkins
or
special
hound
chart
with
sujin,
kids
and
accommodation.
A
A
There
are
some
examples
in
public
which
demonstrate
isn't
good
for
packaging
Jenkins,
but
in
this
case,
with
various
files
a
little
bit,
but
still
there
is
a
config
which
actually
looks
like
that,
because
I
use
for
maximal
as
an
input
and
using
dependable
to
pump
for
my
plugin
dependencies
and
send
for
other
files.
So
it's
probably
not
already
was
an
example.
A
B
I
was
working
on
a
proof
of
concept
with
the
custom
wall
package
of
could
I
mean
it
could
be
so
basically,
maybe
we
could
take
in
from
the
user
interface
of
the
front-end,
what
sort
of
plugins
and
configurations
that
the
user
needs
and
then
generate
the
the
yml
file
and
then
the
custom
wall
bracket,
so
I
could
just
take
that
vironment
file
and
generate
the
instance.
I'd
be
a
good
proof
of
concept.
I
mean
for
this
project.
Yes,
you're,
positive,
okay,
oh.
A
A
So
this
plug-in
and
generates
support
the
bundles
example.
We
used
them
for
support
purposes,
but
it's
generally
handy
for
different
kinds
of
analysis,
and
it
also
generates
a
docker
file
which
allows
to
partially
create
the
instance
result
full
configuration,
but
a
dump.
So
doctor
files
plug-in
with
some
other
things,
so
you
can
partially
decreed
they
user
systems
yeah.
If
you
want
to
create
something
more
sophisticated
which
expose
the
Jenkins
definition,
it's
totally
possible.
A
A
A
A
A
A
Yeah
I
can
just
show
it
but
yeah.
The
main
problem
is
for
the
current
stop
user
that
it
provides
you
suggestions.
But
after
you
see
these
suggestions,
it's
still
not.
There
is
no
method
packages
which
Christopher
also
the
program
tool.
So
if
somebody
wanted
to
implement
that
it's
still
needed
on
the
installation
result.
So
it
might
be
an
interesting
feature.
A
E
A
These
build
materials
mostly
focuses
quite
an
ecosystem
because
test
the
dependency
for
pipelines
is
the
night
my
to
manage
so
jesse
was
most
address
into
this
use
keys,
but
yet
technically,
something
like
that
could
apply
it
on
the
user
side.
So
there
is
a
repository,
a
Jenkins
mom,
so
somebody
could
implement
the
same
pipelines
for
testing,
can
automatic
dependency
updates.
Let's
say
for
AWS
plugins
well-taken,
if
you
have
which
hi
for
that
then
yeah,
it
could
be
mostly
known
to
medic.
We
I.
A
E
A
D
A
But
it's
yet
to
be
implemented,
your
starting
point.
Yes,
there
is
installation
wizard,
but
yeah
I
would
argue
that
doesn't
get
you
where
you
would
like
to
get
so
you
can
see
that
it's
basically
just
a
set
of
recommended
plugins
and
since
we
didn't
really
spend
much
time
on
keeping
it
up
to
date,
so
let's
say
one
wants
to
use
Jenkins
with
docker.
We
don't
have
a
way
to
do
it
here.
A
B
A
If
it
could
solve
the
issue,
so
one
thing
you
would
need
to
keep
in
mind
it's
for
your
information
to
wreak
that
custom
or
texture,
even
if
it
provides
tocut
file.
So
technically
in
your
service,
you
can
spin
a
container
which
builds
an
image
for
user.
The
problem
is
total
packages
because,
right
now
it
doesn't
support
doc.
Engine
doctor
and
customer
packages
just
generates
the
docket
father.
A
B
Okay,
so
so
could
could
it
good
custom
instead
of
just
I
mean
when
you
run
scripts
foreign
yell
I
it
does
download
a
file.
So
could
could
this?
Could
this
service
just
run?
Oh
no
I
mean
separately
where
it
does
allow
you
to
download
a
sort
of
file
or
something
I.
Don't
know
if
I
make
a
change
but
I'm
not
for
them
right
now,
I
mean
how
to
put
it.
B
A
Two
parts,
one
part
see
that
you
can
so
here
you
don't
generate
a
project
for
yourself.
It
doesn't
profit,
you
jars,
it
just
provides
you
project
definition
same
mr.
The
service
could
generate
it.
For
example,
what
I
have
here.
It
was
just
the
configuration
which
includes
a
bunch
of
stuff,
but
basically
this
is
configuration
which
you
can
take
and
build
on
your
own,
but
it's
ready
to
go
so
it's
click
a
button.
You
can
run
a
make
file
and
get
b
image.
A
If
you
want
to
provide
a
good
service,
Machir
actually
builds
the
packages,
then
you
would
need
to
run
customer
acquisition
site
you
service.
Yes,
exactly
that's
what
I
was
saying:
yeah
it's
doable,
but
it
opens
a
lot
of
questions
like
spinning
additional
containers
in
the
service,
all
kinds
of
security
questions.
If
you
wish
you
could
deploy
this
artifact
somewhere,
but
it
is
artifacts.
First
customer
packages
takes
a
while
to
complete
yeah
so
we'd.
A
Well,
not
that
one,
but
it
may
take
10
or
20
minutes,
sometimes,
depending
on
your
configuration
complexity,
so
yep
it
would
be
much
hidden
short.
So
if
somebody's
was
working
on
this
project,
I
would
recommend
to
split
it.
Two
phases,
one
phase
just
generates
confabulation,
and
only
after
that
you
could
work
on
the
bit
service.
Okay,
thank
you.
So
much
that
helps
a
lot.
A
C
C
A
You're
right,
it
may
be
difficult,
but
we
can
have
an
algo
food
packaging
service.
That's
for
sure,
it's
just
quite
difficult
implemented
as
a
first
phase,
because
there
is
a
lot
of
hidden
stones
and
the
second
phase,
for
example,
billet
acquired
quite
different
skills
because
first
you
just
build
this
generator.
It
can
be
written
your
JavaScript
and
if
you
go
whatever
you
like,
but
when
it
comes
to
the
service
itself,
yeah,
you
don't
need
to
likely
recreate
home
chart
for
that.
A
You
will
need
to
resolve
security
questions
if
you
want
to
host
it
two
billion
Jenks.
Are
your
infrastructure
than
I
need
to
talk
to
infrastructure
team
about
that
and
yeah.
You
know
right.
You
will
resolve
and
a
lot
of
budgeting
issues
recently
so
important
new
services,
while
it's
across
the
world
which
will
require
significant
discussion.
So
if
you
put
the
dual
service
as
a
first
step,
it
may
just
require
a
lot
of
extra
effort.
A
E
We
have
some
requirements
around
like
the
actual
build
step,
because
we've
got
stuff
like
they
forget
spray,
and
all
of
that
coming
in
so
like
our
enterprise
wants
to
track.
You
know,
but
you
code,
where
I
can
see
it
please,
rather
than
kind
of
getting
a
remote
service
to
compile
the
war
and
then
handing
to
handing
it
to
us
and
it's
kind
of
a
black
box.
E
E
For
the
brownie
points
and
possibly
increase
it
work
again,
the
time
is
spent
guessing
what
plugin
configuration
is
meant
to
go
in,
and
so
no
not
the
configuration
of
the
call
itself,
because
you
can
go
and
read
one
set
of
dogs
pretty
much
and
work
that
out.
It's
stayed
like
if
I
want
use
both
the
even
my
own
plug-in
they
AWS
credentials
provider
thing
well.
What
configuration
do
I
have
to
put
in
junk
in
general,
okay,
I've
got
to
go
off
and
read
the
plug-in
readme,
and
hopefully
the
plug-in
also
remembered
to
document
that.
E
A
So
in
this
project
you
start
a
project
idea
and
with
this
project
idea,
may
involve
various
directions,
various
goals
and
basically,
we
expect
students
to
come
up
with
their
proposal
based
on
this
list
of
ideas.
So,
even
if
you
think
that
that
prods,
the
project
is
bigger
than
what
can
be
done
in
JSOC,
it's
not
a
blocker.
It
just
needs
to
be
explicit
in
the
project
definition.
A
C
B
B
B
A
You
can
publish
record
link
of
this
meeting
so
that
it
can
provide
additional
information
to
potential
students
yeah
so
yeah
just
to
be
clear
slogan.
It's
not
your
responsibility
to
update
project
idea.
It
would
be
much
appreciated
because
it's
all
second
tribution
to
the
project,
but
your
main
goal
is
to
create
your
proposal.
Yeah
keeping
all
the
information
public
is
important.
Yeah
definitely.
A
E
Like
you
could
imagine,
a
kubernetes
meta
package
in
in
the
registry
aggregating
stay
the
kubernetes
credentials
provider
and
that
is
like
build
agents
and
all
that
and
but
it
wouldn't
be
enough
to
get
going
with,
and
that's
why
we
have
a
pool,
that's
distribution
for
communities,
I'm
wondering
if,
like
for
the
AWS
equivalent
okay,
we
can
have
an
AWS
meta
package,
but
it's
not
quite
enough
to
get.
You
started
because
you
still
have
to
have
all
like
the
surrounding
terraform
and
whatnot
scaffold
cutter
into
existence.
Yeah.
A
E
A
Obsolete
and
it's
archived
because
he
is
a
shutdown
in
such
a
late
january,
but
it
was
exactly
an
attempt
to
provide
a
solution
for
aw
years
with
some
optimist.
Do
some
goals
like
having
energy
is
deliberately
to
these
instances?
But
if
you
deep
dive,
if
you
can
find
that
docker
files
which
package
she
jenkins
use
a
set
of
plugins
and
then
there
are
some
verification
flows
which
prepare
this
list
of
plugins,
so
they
don't
use
custom
work
package
or
internally,
instead
of
that
they
use.
So
they
are
own
scripting.
A
What
customers
packages
was
created
in
evergreen,
but
final
result
is
basically
they
see.
They
have
some
dependency
management,
some
CI.
They
create
a
package
specific
to
AWS.
They
also
the
country
by
things
like
dependence
on
as
three
buckets
other
things.
So
out
of
the
books,
you
get
some
kind
of
web
environment
and
you
can
run
it
so
the
repository
is
still
around
so
some
it
could
be
reused.
E
It
definitely
does
sound
a
lot
of
it
would
be
useful
to
us.
Probably
the
thing
that
would
have
knocked
it
on
the
head
is
the
you
know,
continuous
always
up
to
date
on
the
bleeding
edge
of
plugins,
which
is
I
mean
that
would
have
made
it
unusable
for
us.
We,
although
the
idea
at
the
heat
to
kind
of
I,
suppose
it's
like
the
arch
linux
of
jenkins
always
up
to
date,
and
the
downside
is
always
up
to
date.
A
D
A
One
of
the
choke
points
is
about
production
readiness,
because
what
you
need
is
definitely
a
production
of
AD
template
production,
ready
definition
and
your
team's
already
got
a
load
towards
for
this
way.
So
I
wouldn't
expect
our
first
box
to
be
really
ready,
but
maybe
what
we
could
do
is
example.
If
your
team
is
interested
to
open
source,
some
bits
of
your
shed
configurations
maybe
see
whether
we
could
convert
them
to
templates.