►
From YouTube: Node.js Build WG Meeting 2016-10-11
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
So
I
created
a
job
to
test
the
no
track
record
that
reuses
our
build
and
test
jobs
in
Jenkins,
so
I
just
change
the
normal
test
windows
fan
to
pump
out
for
track
record
and
test
check
require
I
also
dropped
support
for
visuals
to
do
2013
in
v6
and
onwards.
So
now
it's
live
on
the
desk,
see
I
and
the
release.
Jenkins
should
also
use
it.
A
I've
spent
some
time
fixing
issues
with
the
freebsd
hosts.
The
reason
this
they
started
to
fail
was
twofold.
First
of
all,
we
started
running
into
issues
when
upgrading
to
be
854,
I
think
that's
still
to
be
determined
how
wide
reaching
those
issues
are.
But
the
other
problem
was
that
some
of
the
variables
that
was
passed
on
from
the
init
scripts
wasn't
properly
I
committed
to
the
repo.
A
So
when
I
updated
the
slaves
or
the
workers,
as
we
call
them,
we
ran
into
overriding
the
working
in
it
scripts
gold
once
so,
you
know
never
added
live
on
top
of
that.
I've
added
freebsd
11,
which
was
released
a
few
days
ago.
It's
still
in
a
experimental
stage,
I
guess
from
a
testing
point
of
view,
but
when
I
test
locally
and
one
or
two
runs
I've
done
through
the
CI,
it's
been
working
as
in
a
green
run.
So
that's
cool
I've
done
some
reshuffling
of
freebsd
host.
A
You
usually
run
everything
on
a
digital
ocean,
but
I
felt
like
it
would
be
important,
knowing
that
if
we
had
issues
that
were
like
so
we
now
run
a
few
between
Rackspace
digital
ocean
and
giant
I've
also
migrated
all
so.
The
ssh
keys
were
using
to
connect
to
all
the
machines
or
replaced
between
this
and
last
meeting.
I
also
wrote
an
ansible
script
to
do
this,
so
it's
available
in
the
refactor
I'm
working
on
I'm,
also
working
with
rod
to
migrate
our
triple
w
host
we're
kind
of
running
out
of
space.
A
So
it's
actually
a
bit
pressing,
so
we're
hopefully
done
this
week
and
we
can
just
point
the
dns
to
make
that
final
change.
I've
spent
a
lot
of
actually
more
than
I
expected,
but
it's
it's
so
close.
So
it's
just
a
lot
of
fun,
seeing
it
come
to
fruition
when
it
comes
within
you,
refactor
I
have
a
I
have
scripts
to
set
up
new
hosts
which
works
I've
done
it
with
six
operating
system.
So
far
we
have
scripts
to
set
up
the
linters.
We
have
scripts
to
start
setting
up
a
host.
A
We
have
scripts
to
do
the
keys
to
to
write
SSH
configs,
for
you
know,
quality
of
life.
So
it's
really
coming
to
to
a
workable
state.
The
I
will
post
it
as
a
PR
at
when
when
ansible
2.2
is
released,
because
I'm
relying
on
a
few
functions
from
that
version,
so
it's
countering
in
RC
I,
think
RC
one
was
just
released,
so
once
go
ahead.
A
2.2
I
will
also
make
the
PR,
but
I
think
you
really
should
check
it
out
today
and
if
you
want
to
do
changes
to
you,
know,
inventories
or
if
you
want
to
do
changes
to
to
ansible
playbooks.
You
should
really
look
at
the
refactor
because
it's
almost
feature
complete
for
most
kinds
of
os
or
Hardware
combinations.
D
B
D
F
So
I've
been
looking
at
a
couple
of
ax
issues.
There
was
a
problem
with
the
Python
on
ax,
not
finding
the
right
as
a
sales
certificate,
which
was
just
a
question
of
finding
the
right
environment
variable
to
set
that
I
should
hopefully
be
done
so
I'll,
be
working
with
Michael
to
get
that
put
into
the
Jenkins
configuration
scripts.
I
think
that's
it.
E
A
C
A
Yeah,
so
I
think
what
I'm
at
least
waiting
for
is
just
more
feedback
from
other
people.
It's
I
think
it's
seriously
so
far.
That
said
yes,
so
preferably
we
would
get
someone
else
chipping
in
and
saying
this
looks
good
to
me
and
after
that
we
need
to
coordinate
with
the
evangelist
and
timeous.
I
guess
we
could,
you
know,
has
anyone
else
in
and
in
the
build
group
had
a
look
at
it
and
you
know
and
have
any
opinions.
C
A
I
would
like
rods
feedback
as
well,
seeing
how
he's
kind
of
being
driving
this
before
I
picked
it
up,
and
then
you
get
hooked
up
with
the
island
stuff.
So
I
guess
you
know
if
you
can
take
a
minute
of
your
two
minutes
of
your
time.
Just
have
a
quick
look
at
the
issue
and-
and
you
know,
if
you
have
any
comments
on
either
how
we
communicate
this
or
how
we
we
are
to
execute
this,
because
it's
expanding
what
this
means.
A
I
guess
I
mean
it's
related
to
the
rsync
issue,
which
will
be
talked
about
with
layer,
but
at
the
end
of
day
what
we
want
to
do
is
enable
strict
HSE
s,
which
means
that
some
older
clients
will
run
into
problems
talking
over
so
which
also
means
that
they
will
need
to
have
an
option.
So
have
a
look
at
that
and
please
give
us
some
feedback.
A
C
D
I
just
read
the
age,
so
I
do
have
a
question.
Yoha
mentioned
that
older
browsers
would
have
trouble,
I
mean
they
just
disregard
HST
s
right
or
does
it
actually
cause
problems?
Well,.
C
I
think
the
thing
is:
is
that
once
once
it's
enabled
unless
the
browser
says
yeah,
okay,
I
understand
your
your
request
and
switches
to
https.
You
just
can't
connect
right
because,
basically
it
you
know,
you
connect.
If
you
don't
connect
with
HTTPS
and
basically
sends
you
a
message
back
saying:
no,
you
have
to
use
HTTPS
unless
you
switch
over
to
that.
You
can't
access
the
pages
at
all.
D
C
C
Think
it's
that
people
have
the
older
browsers,
they
may
connect
and
say
we'll
wait
a
sec
I,
don't
know.
What's
going
on
I
certainly
I
certainly
had
a
problem
and
I
can't
remember
the
exact
circumstances,
but
you
know
HD.
It
was
turned
on
and
a
site
that
I
went
to
and
it
took
me
a
little
while
to
figure
out.
Why
wasn't
connecting
from.
F
C
E
C
E
D
It's
the
main
repo
is
TJ.
C
Basically,
the
original
issue
was
asking
to
get
Gibson
access
just
to
the
like
the
power,
ARX
and
390
machines
in
in
the
meantime,
he
was
named
as
a
collaborator,
so
I
think
under
our
existing
policy
we
can
just
give
him
access
to
the
test
keys
and
all
the
machines
is
opposed
to
individually
putting
on
the
Keats,
so
I
just
thought
I'd
throw
that
out.
You
know
here
to
say,
if
you
agree
with
that,
if
you
could
add
your
LD
TMS
to
that
issue,
we'll
just
go
that
way
as
opposed
to
specific
access.
E
On
just
message
us
edits:
internet
just
dry
died,
he's
trying
to
get
back
through
3g
and
asked
Michael.
If
you
could
host
sure.
Okay.
C
So
let's
will
continue,
of
course
any
so
so,
basically
you
know
if
you
have
any
objections
or
or
even
better,
if
you
can
add
your
LG
TL
GTM,
so
we
can
move
forward
on
470
I
call
the
go.
Take
a
look
at
that
and
do
that,
so
we
can
get
rip
some
access
as
a
backup
to
me
on
on
those
machines
moving
then
on
to
tap
plug-in
issues
on
Jenkins,
so
453,
let's
open
that
up.
E
Johan
and
I
were
talking
about
it
earlier
today,
so
basically
we're
still
just
like
a
matter
of
finding
time
to
work
on
it.