►
From YouTube: 2023 02 07 Jenkins Infra Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
B
Yeah,
yes,
so
this
this
announcement
topic
is
actually
a
just
an
alert
that
we've
got
conversations
happening
right
now,
so
jira
announced
a
year
or
two
ago
that
their
business
model
was
switching,
that
they
were
no
longer
going
to
support
self-hosted
jira
instances
of
their
standard
product.
They
were
going
100
Cloud
for
their
standard
product
and
we
use
a
donated
license
of
their
standard
product
that
donated
license
of
their
standard
product
is
hosted
for
us
by
Linux,
Foundation
issues.jenkins.io.
B
In
February
of
2024,
they
will
conclude
that
transition
by
switching
off
they
will
no
longer
support,
hosted
instances
of
their
standard
product.
However,
we've
learned
that
they
have
a
product
called
Data,
Center
and
data
center
is
a
hostable
product
and
we've
asked
them.
Will
they
please
donate
a
data
center
license
to
us
so
that
we
can
continue
using
jira
rather
than
making
the
switch
to
GitHub
issues?
B
Our
security
team
would
very
much
prefer
to
stay
with
jira
because
their
processes
are
strongly
coupled
to
there
are
plenty.
There
are
a
number
of
core
maintainers
who
would
prefer
to
stay
with
jira,
because
jira
has
specific
features
that
make
large-scale
management
of
projects
easier
than
GitHub
issues
are
so
so
right.
B
Now
the
the
effort
is
to
try
to
persuade
atlassian
to
donate
us,
a
data
center
license
and
as
a
board
member
I
have
the
action
item
and
I'm
actively
communicating
with
atlassian
right
now
asking
them
if
they
would
please
be
willing
to
donate
I,
don't
know
if
they're
willing
to
donate
or
not
they've
seemed
to
indicate
they
are,
but
it
has
to
have
special
approval
for
them.
This
is
not
a
common
thing
for
them;
they
correctly
want
people
to
transition
to
their
Cloud
solution.
B
We
have
a
problem
doing
using
their
Cloud
solution,
because
their
Cloud
solution
is
limited
to
not
more
than
30
000
users
on
an
instance,
and
we
have
well
over
a
hundred
thousand.
Their
Cloud
solution
requires
that
that
you
must
use
an
atlassian
account
and
if
we
did
that
for
Jenkins,
it
would
mean
instead
of
two
accounts
to
be
a
Jenkins
contributor,
a
GitHub
account
and
a
jenkins.io
account
IO
account
for
repository
upload.
B
We
would
now
have
three
accounts
and
for
me,
that's
that
would
be
sort
of
a
tipping
point
where
I
would
expect
many
contributors
would
say:
no,
let's
just
switch
to
GitHub
issues.
So
thus
the
the
request
is
happening
now
to
atlassian.
Please
grant
us
a
data
center
license
and
if
they
don't
grant
us
a
data
center
license,
we
then
have
to
have
the
discussion
within
the
Jenkins
project.
What
do
we
want
to
do
next,
whether
it's
change
to
jira
cloud
and
reduce
the
number
of
users
and
use
atlassian
accounts
or
change
to
GitHub
issues?
B
A
C
C
B
Linux
Foundation
has
indicated
that
they
are
already
hosting
one
or
more
other
data
center
licenses.
So
this
is
not
something
that's
that's
unfamiliar
to
them.
Now.
I
have
not
received
final
confirmation
from
them
that
they
are
willing
to
continue
that
hosting,
but
I
think
if
we
bring
the
data
I
will
I
will
check
with
them
on
that
as
well.
Okay,.
C
B
A
C
A
A
So
it
wasn't
a
failure
per
se
because
it
finally
released
correctly
without
reaching
any
timeouts.
So
that
might
be
interesting
to
watch
when
the
package
build
will
happen.
So
as
order
of
magnitudes
once
the
build
is,
is
triggered.
You
have
two
hour
to
two
hours
on
half
of
building
tests
and
then
the
package
happened.
So
when
you
see
that
the
reader
started,
then
that
means
two
hours
after
we.
A
We
will
have
to
start
watching
the
package
I'm
taking
care
of
that,
because
I
understand
the
RV
and
Stefan
might
have
personal
appointment
on
the
day.
So
to
avoid
any
pressure
on
you
is
it
okay,
folks,
if
I
take
care
of
following
up
on
this,
one
I
will
try
to
record
and
Report.
What
happened
is
that
okay,
for
you.
C
A
A
B
It's
been
proposed,
I've
I,
don't
think
that
I've
I've
not
seen
any
announcement.
If
the
proposal
was
accepted,
are
they
it.
A
A
A
A
So
the
real,
that's,
not
the
one
that
we
did
not
fixed.
We
had
two
password
recovery.
Of
course,
no
answer
back
from
the
requester
like
every
time
so
closed
one
access
to
a
plugin
that
is
treated
on
the
rpu,
so
we
were
able
to
remove
a
bunch
of
unused
plugins
I,
wasn't
able
to
close
the
last
one
about
Ace
editor,
but
that
has
been
done
everywhere.
A
So
that
should
add.
Another
task
done
thanks
Mark
for
the
for
pointing
out
that
the
index.html
page
on
the
Reddit,
stable
repository
on
PKG
and
kinsayo
should
not
show
the
latest
version
available,
but
tells
since
when
didica
11
was
supported
for
each
which
line
we
never
had
any
feedback
from
the
user
as
well.
So
I've
took
on
me
to
close
the
issue
and
the
gerato
pick
that
you
that
we
discussed
about
the
fact
that
we
had
to
renew
the
the
license
and
everything
you
explain
about
the
product.
B
A
First
of
all
great
job,
folks,
we
were
able
to
enable
artifact
caching
proxy
for
every
plugin.
Last
week
we
haven't
been
aware
of
any
failure,
yet
we
saw
an
increase
in
the
memory
used
on
most
of
the
instances
which
shows
an
increase
of
activity,
but
also
we
haven't
reached
the
memory
limit,
so
it
means
that
the
current
amount
of
cached
data
is
already
loaded
in
memory.
A
So
due
to
that,
it
means
that
we
weren't
able
to
see
any
I
o
activities
or
something
that
change
anything
on
the
read
and
write
on
the
file
system,
because
the
cache
is
able
to
load
everything
for
now,
there's
been
an
additional
change
that
we
pushed
so
I
think
that
survey
took
care
of
that
Friday
and
it's
there
on
digital
Lucian
and
Azure,
but
not
on
AWS.
A
Yet
we
are
caching
for
one
month
instead
of
one
day,
so
that
should
increase
the
the
amount
of
the
decrease,
the
amount
of
requests
going
to
g-frog
and
now,
as
pointed
by
your
way,
the
next
step
is
the
bum,
because
on
the
metrics
that
we
gather
every
week
from
g-frog,
we
saw
the
outbound
IPS
of
our
kubernetes
clusters
and
our
kubernetes
clusters,
mainly
us
to
build
plugins
builds
on
the
pods
and
bomb
builds.
A
A
A
Cluster
is
currently
trading
when
updating
the
latest
configuration,
as
just
mentioned,
about
the
cache
it's
trying
to
rescue
reports,
but
we
have
an
issue
where
in
AWS
you
are
allowed
to
have
multi
red,
it's
not
region,
but
availability
Zone
cluster.
So
we
are
virtual
machines
on
different
areas,
but
the
persistent
volumes
are
only
per
availability
zone.
So
if
you
spin
the
machine
on
another
availability
Zone,
it
cannot
access
that
the
auto
scaler
should
be
aware
of
that
topology.
A
A
A
A
B
A
On
the
other
issues,
I'm
sure
all
GitHub
action
version
are
pinned
and
tracked,
so
an
initial
work
has
been
done
by
Stefan
thanks
for
that,
so
you
were
able
to
enable
dependables
and
updates
the
associated
thanks
survey
for
catching
that
I
enabled
the
panda
Bots
with
a
wrongly
named
file
two
years
ago
almost
and
it
never
updated.
A
So
thanks
for
fixing
the
typo
and
we
discuss
and
agree
on
different
moments
that
before
closing
that
issue,
we
should
check
and
have
that
exhaustive
list
of
every
repositories
having
a
DOT
GitHub
workflow
directory,
but
no
GitHub
dependables,
and
so
we
will
have
to
exhaustively
cover
all
these
elements
deciding
if
all
these
repositories
archived
nothing
to
do.
Are
these
repository
today.
D
None
of
this
I've
removed
the
archives
repository
from
this
piece.
Okay,
all.
A
D
I
have
on
my
computer
repository
and
I've
done
some
find
and
grip
on
it.
Okay,
I'll
find
the
sign
with
GitHub
workflow
folder
and
find
file
and.
A
A
Problem
at
all,
it's
just
knowledge
sharing,
because
something
that
might
looks
easy
for
you
might
not
for,
although
that
will
want
to
help
on
the
infrastructure.
So
that's
why
I'm
asking
for
this
one,
which
leads
me
to
the
fun
there
might
be
case.
I.
Don't
think
that
will
happen
here,
but
I
just
want
to
be
everyone
to
be
aware
that
if
any
of
the
repository
or
nervous
machine
are
not
up
to
date
with
their
remote.
C
A
I'd,
be
someone
already
pushing
a
depend
about
I'm
sure
that
won't
happen.
In
that
case,
it's
not.
A
A
Renew
designer
certificate
for
Jenkins
and
document
it,
so
we
said
we
will
do
that
next,
iteration
after
the
LTS
release
before
any
upcoming
updates
Mark.
Is
that
still?
Okay
for
you?
First?
Yes,
so
we
we
should
start
working
on
that
area.
Thursday
Olivier
pointed
me
this
weekend
that
there
is
already
a
discussion
on
the
Jenkins
infra
slash,
release
Repository,
so
the
only
run,
vocal
points
to
that
area.
B
B
That's
that's
my
understanding
is
this
should
be.
This
should
be
it.
What
this
act
was
transparent
to
Jenkins
users,
the
last
time
we
did
it
there.
There
was
no
disruption
to
them.
They
they
perceived
that
yes,
now
now
I
suspect.
If
you
attempt
to
run
an
MSI
installer
from
seven
years
ago,
it
will
tell
you
now.
B
The
the
signing
is
has
expired
on
that
MSI
and
that
may
be
the
same
condition
that
will
occur
for
msis
done
with
our
current
installer
after
we've,
after
we've
transitioned
and-
and
it
has
expired
so
when
it
expires
in
45
days
or
whatever
the
expiration
is,
but
I'm,
not
even
confident
of
that
I
the
it's
important
that
we
get
this
updated,
but
as
far
as
the
last
time
we
did
it,
it
was
no
disruption
to
any
users,
cool.
A
So
we
open
the
issue
we
weren't
able
to
walk
on
that
a
radio
you
remember
if
we
were
able
to
finally
clean
up
and
do
what
the
initial
issue
was
fixed.
A
Okay,
so
if
we
have
to,
if
we
can
work
on
this,
that
will
be
nice
to
focus
on
okay,
updating
the
initial
requirement
from
Daniel,
removing
whatever
page
he's
mentioning
and
then
we
can
take
care
of
the
rest
later.
Is
that
okay,
for
you,
is
that
okay
for
you
to
take
this
issue
on
the
upcoming
week,
or
do
you
want
me
or
Stefan
to
do
it.
C
B
A
This
space
is
below
one
gigabyte,
so
that
one
is
a
recurring
armless
alert
that
we
all
keep
since
beginning
of
the
month.
We
have
documented
the
content
and
reason.
The
first
step
we
have
to
run
is
to
ensure
that
we
shift
all
of
our
controllers
when
using
virtual
machines,
particularly
Windows
ones,
to
to
immediately
delete
the
machine
wants
to
build
its
past.
We
want
ephemeral
machine
everywhere.
A
So
it's
not
a
fact
or
proof
is
that
we
have
multiple
builds
coming
on
the
same
Windows
Virtual
Machine
used
as
agents,
because
these
machines
are
usually
waiting
30
minutes
before
being
crushed
by
most
of
the
controllers,
and
the
reason
for
that
behavior
are
are
not
up
to
date
anymore.
So
we
should
shift
to
trash
the
machine
immediately
and
we
shouldn't
have
any
builds
that
try
to
generate
80
gigabyte
of
data.
Even
the
docker
builds.
So
that's
why
that
might
be
a
quick
win.
A
Yep,
okay,
realign
repo
Jenkins
CIO
Mission
I
didn't
do
anything
on
that
topic
because
we
were
focused
on
first
name
and
ACP
Mark.
You
had
a
feedback
from
gifrog
on
the
fact
that
they
cannot
get
the
user
agent
As
It
Seems
on.
B
Well
and
that
I
wasn't
sure
so
I'd
ask
that
question
further
clarifying
I'm,
still
working
a
little
bit
on
hope
that
they
have
some
way
to
do
per
file
reader
per
per
artifact.
Redirect
because,
if
they
do,
we
could
stop
the
that
server
in
China
by
redirecting
the
war
files
to
get.jenkins.io
it'd
be
a
lot
of
work,
but
that's
a
doable
amount
of
work
and
jenkins.war
is
a
big
file,
so
makes.
C
B
A
Might
have
to
raise
that
point
to
are
your
teams
in
Chief
hog,
because
that
war
is
literally
in
the
released
repository,
which
is
not
a
mirror
repository
right
and
they
cannot
block
IPS,
they
cannot
block
user
agent
and
they
cannot
give
us
user
agents.
So
we
cannot
diagnose
what
kind
of
usage
is
behind.
As
Brazil
pointed
out.
We
cannot
be
sure
it's
is
it
a
curl?
Get
it
Maven
badly
configured,
we
don't
know,
but
it's
not
a
mirror,
so
even
enabling
authentication
or
you
enabling
ACP
every
work
we
are
doing.
A
B
C
D
B
D
B
Me
too,
I
want
I
want
to
see
if
that
large
gaming
company
has
has
reduced
like
they
think
they
have,
it
won't
be
eliminated
because
it
was
Tuesday
or
Wednesday
before
they
implemented
their
fix,
but
but
I
would
I
would
love
to
see
that
there
was
at
least
a
diminished.
B
A
Any
other
question
on
that
topic:
okay,
next
one
is
terraform
module
for
AWS
eks,
so
we
found
the
reform
word
Behavior
and
the
way
we
are
using
it
and
on
the
eks
module
that
we
fixed
Friday.
So
now
the
problems
have
shifted
to
the
multi
availability.
Zone
thing
I
mentioned
earlier,
so
once
we
will
have
fixed
that
multi-availability
zone.
A
We
should
be
able
to
close
that
issue,
but
at
least
the
core
issue,
the
core
thing
about
the
EK
styrofoam
module
being
burnt,
and
we
weren't
able
to
use
some
of
these
elements
that
parts
will
be
fixed.
We
shouldn't
have
any
more
issue
with
the
labels
and
load
balancer
unless
this
issue
are
reintroduced
by
the
multi-availability
fixes.
That
could
be
a
possibility
shares.
So
I
will
report
on
that
issue.
Every
findings
and
actions
that
one
is
priority
because
it
ensure
that
the
AWS
repository
ACP
is
still
working.
A
So
I'm
keeping
this
issue
working.
That's
my
today's
job,
an
install
deprecated,
jQuery
and
Ace
editoro.
We
have
to
do
an
exhaustive
check,
but
that
should
be
deployed
everywhere,
all
the
controllers.
So
thanks.
Everyone
involved
in
that
because
everyone
did
a
tiny
task
on
that.
So
that's
cool
and
question
about
OS.
D
A
So
assuming
that
person
will
start
using
CI,
Jenkins
IU
on
for
Linux
builds
at
least
we
already
have
python,
free
and
virtual,
only
installed
on
our
virtual
machines
and
container.
The
only
step
is
installing
the
PIP
package
PCT
and
what
I
suggested
to
Airways
to
communicate
to
that
person.
They
could
configure
the
public
smell
to
ook
on
on
one
of
the
prepared
phase
of
Maven
and
to
use
the
maven
exec
plugin
and
hook
it
on
that
part
to
run
the
command
python.
Free,
Dash,
MP,
pin
Style
bzt-upgrade.
A
So
each
time
the
maven
command
will
be
called
on
the
plugin
that
will
automatically
try
to
install
busyt
eventually
that
command
could
be
enabled
if
there
is
a
CI,
equal,
true
environment
variable
which
chain
can
set
as
far
as
I
can
remember
or
any
of
the
viable
Legend
set
up.
So
when
a
developer
of
the
plugin
runs
it
locally,
it
won't
try
this,
but
I
suspect
that
one
should
be
also
portable
to
developer
if
BCT
is
needed.
A
So
that
means
so
we
discussed
that,
and
that's
true
I
forgot
that
you
asked
me
some
help
on
pointing
out
the
correct
Maven
element.
Where
are
we
so
someone
who
is
Maven
nourage
need
to
help
everyone
that
area
to
have
the
correct
communication
to
the
user?
That's
the
status!
B
So
so
this
one
could
not
have
been
solved
by
them.
Switching
to
use
containers,
it
sounds
like
you've
got
a
better
solution
than
that
than
containers,
because
they
can
already
do
Python
and
VNV.
Okay,
okay,.
A
So
is
it
okay
for
you
still
to
acknowledge
the
message
explaining
them
the
issue,
the
the
idea
sorry
saying:
either
they
could
UK
Maven
to
a
Content
running
process,
or
we
already
have
Python,
3
and
virtual
home.
So
if
they
can,
if
they
know
how
to
hook
up
on
the
maven
release
process,
then
they
should
be
able
to
run
the
command
just
give
them
their
general
idea
and
tell
them
we.
We
will
spend
some
time
trying
to
find
the
correct
pointers
for
you.
A
A
B
Oh
yes-
and
this
is
one
where
Alex
brandes
has
been
working-
a
a
a
project
to
reclaim
ownership
so
that
someone
from
the
governance
board
has
ownership
of
every
mailing
list
out
there.
I
believe
this
is
one
that
we
have
not
yet
reclaimed
the
ownership
and
I
don't
know
who
owns
it.
I
sent
a
message
to
a
few
people
that
I
think
might
be
involved.
B
B
A
Team
just
added
a
comment
on
the
issue
about
migrating
updates
to
and
kinsayo
from
AWS
to
another
Cloud,
which
happened
to
be
a
wrecker.
We
we
put
that
issue
on
hold
because
the
other
topics,
but
he
just
mentioned
a
build
that
was
broken
because
with
the
infamous
HTTP
2
Windows
of
frame
error,
which
is
a
consequence
of
the
underlying
hypervisor
which
is
having
network
issues.
So
then
it's
a
domino
effect
until
the
Apache
server.
A
We
should
be
able
to
use
a
more
recent
Apache
server
to
solve
that
issue,
but,
alas,
we
are
stuck
on
the
Linux
distribution.
If
you
try
to
upgrade
the
Linux
distribution
to
22
on
that
machine,
that
will
break
and
never
reboot.
So
please
don't
do
a
desktop
this
full
upgrade,
and
so
that
means
once
we
will
have
finished
the
whole
cluster
migration.
We
will
have
to
go
back
on
that
area,
the
priority
after
the
World
ACP
and
networking,
but
thanks
a
team
I
just
wanted
to
mention.
A
C
I,
remember
correctly,
you
already
started
the
new
for
the
next
week.
D
A
Now,
yes,
but
since
survey
pointed
it
would
out
I,
remember
yeah,
let's
check
you
right,
yeah,
we,
yes,
both
of
you,
pointed
it
really
early
to
me.
So
I
took
care
of
not
moving
everything
and
I'm
sure
some
of
you
already
corrected.
So
the
only
two
issue.
There
are
issues
that
we
explicitly
decided
to
not
work
on
due
to
the
first
time,
so
that
should
be
okay.
I
just
have
to
update
today's
Milestone
to
this
one,
but
good
points
better
to
check
better
safe
than
sorry.
A
So
I
just
have
a
few
nuts.
Let
me
open
them,
because
these
are
my
personal
notes,
so
I
don't
want
to
show
them
on
the
share
screen.
I'm
saying
thing
about
my
colleagues,
so
I
don't
want
them
to
read
it.
No
but
jokes
aside
a
few
elements
that
I
learned
or
discover
or
discuss
during
the
during
the
first
time,
I
will
share
them
in
a
written
manner
where
the
next
excellent
exchange
with
Carlos
Sanchez.
A
So
it's
trying
different
things,
but
the
message
is
good
job.
Everyone
involved
on
the
official,
Jenkins
image
and
infrastructure
because
it
looks
like
the
results
are
impressive.
As
a
data
point,
he
remember
having
to
wait
two
hours
for
being
able
to
build
a
Jenkins
score
image
two
hours,
the
current
time
as
we
reach
the
time
unit
of
one
hour
when
rebuilding
the
30
past
images
30
times
the
number
of
each
definition.
A
So
we
are
more
in
around
10
minutes
today
than
12.,
so
he
said
great
job
to
everyone.
In
environment,
big
belated,
thanks
from
Carl
Haynes
from
the
maven
project,
we'll
see
that
we
are
almost
always
up
to
date
with
the
latest
Maven
version.
He
pointed
me
to
two
new
elements
that
has
been
supported
by
other
Jenkins
Developers.
A
There
is
something
around
the
new
environment
variable
that
will
be
able
to
hold
the
options
that
we
pass
to.
Maven.
That's
variable
will
be
on
the
new
Maven
upcoming
Maven
3.9,
which
is
on
the
oven,
so
we
should
have
to
update
it
across
the
platform.
Let's
wait
for
the
Jenkins
Co
developer
feedback.
Before
doing
that,
though,.
B
Okay
and
and
I'm
already
using
it,
I've
confirmed
the
10
plugins
that
I
maintain
10,
plus
the
I'll
compile
successfully
with
it
and
it's
yeah.
So
it's
I
I
think
it's
looking
very,
very
good
and
I'll
paste
a
link
to
the
to
the
issue
that
Jesse
Glick
created
to
help
us
track
the
use
of
that
new
Maven
feature.
B
So
what
Jesse
was
suggesting
is
that
there's
some
benefit
here
and
I'll
I'll
paste
the
link
into
the
notes,
so
I
think
it's
the
same
same
thing
that
you
were
discussing
Damian
absolutely.
A
So
my
proposal
is
that
we
wait
not
the
upcoming
Milestone
but
two
weeks
before
starting
updating,
Maven
3.9
everywhere,
just
to
avoid
surprise
rollout
if
we
find
anything
around
them,
especially
because
on
the
bucket
we
have
ACP
things.
We
have
an
LTS
tomorrow
we
have
cut
signing
to
change
until
the
upcoming
weekly
and
we
have
to
fix
a
lot
of
alerts
on
the
elements,
so
I
propose
not
being
too
too
greedy
on
this
one
is
that,
okay
for
everyone
that.
B
A
And
also
Carl
was
happy
to
look
on
the
public
infrastructure
code
to
solve
some
of
his
issues,
especially
around
the
pipe
and
Library
I,
pointed
him
to
the
org
scanning
and
showed
him
the
prone
cons.
He
started
to
try
also
the
LM
template
that
we
are
using,
especially
for
defining
job
DSL
with
less
efforts,
because
job
DSL
is
Nightmare
to
write
and
needs
templating.
A
So
really
interesting,
discussion
but
same
car
was
impressed
by
the
world
Community
progress
since
the
past
two
years.
So
congratulations
to
everyone
again.
We
also
met
Tracy,
Miranda
and
Alfonso
from
chain
guard.
So
I
understand
that
her
way
you
might
be
interested
on
the
wall
feed
topic,
so
there
will
be
one
area,
so
we
need
to
all
discuss
by
email
to
get
started,
but
the
idea
will
be
to
check
with
looks
like
it
will
be.
A
James
rolling,
Champs
built
different
images
for
Jenkins
at
least
weekly
with
gdka
17,
so
could
be
interested
to
check
wisdom
opportunity
to
create
a
new
official
image
based
on
Wolfie,
at
least
for
the
controller,
but
also
study
the
area
of
the
agents.
How
is
it
working?
Is
it
easy
to
build?
One
of
our
challenges
will
be
controlling
the
Git
Version
inside
these
images.
A
The
benefit
for
the
infrastructure
will
be
to
think
about.
Could
we
use
Wolfie
based
images
on
some
of
our
container
running
in
production,
Jenkins
controller,
but
also
container,
like
Jenkins
plugins,
the
nginx
ETC?
The
goal
is
having
the
ability
to
enable
esperm
and
track
dependencies
and
security
vulnerability
without
paying
a
complexity
task
due
to
oh,
let's
build
packages
with
that
new
way
of
doing
which
is
absolutely
hard
to
maintain.
So
the
goal
is
to
explore
that
area.
So
you
understand
our
way.
You
are
you
might
be
interested
by
this
topic.
D
A
Finally,
discussion
so
around
the
CDF,
but
it's
a
gerato
picks
already
discussed
that
at
large.
We
have
discovered
that
Toshiba
and
the
CERN
the
particle
accelerator
are
using
a
bunch
of
Jenkins
controller
and
they
are
working
with
Jenkins
and
they
are
really
happy.
How
is
that?
So?
That
was
a
nice
surprise
and
finally,
I
will
communicate
with
you
so
Lori
from
the
CDF,
but
acting
also
has
someone
as
a
G4
employee,
accidentally
added
me
to
nginx
mailing
list
because
of
someone
else
named
Damien.
A
Who
is
the
same
writing
but
that
Demian
working
for
nginx?
They
are
eager
to
learn
about
engineics,
War,
Stories
or
user
stories,
so
I
told
Lori,
especially
if
it
helps
g
frog
internally
in
their
battle
against
accounting
for
decreasing
bandwidth
and
costs
that
we
call
right
how
we
use
engine
X
for
the
ACP
if
they
are
interested
for
me,
that
will
be
differed
to
Earth.
A
If
you
are
okay,
because
you
build
main
or
main
of
the
walk,
but
I
think
you
will
be
at
the
center
and
also
we
could
discuss
so
we
use
nginx
on
other
areas,
even
if
it's
simple
I'm,
not
sure
that
one
might
be
that
interesting,
but
the
ACP
use
case
could
be
could
be
nice
to
presents,
and
that
will
LBG
frog
indirectly
because
they
will
have
marketing
public
messages.
That
Jenkins
is
doing
things
with
nginx
to
decrease
the
bandwidth
so
the
match.