Issue hardware and build Jenkins 2 instance for OBO

Question

Issue hardware and build Jenkins 2 instance for OBO

Closed this issue 5 years ago · 4 comments

build.obolibrary.org jenkins 2 instance for obo
starting with build-mp-edit
talked to @cmungall , use one of our machines, at least 16GB
let's see what we got

Answer 1 · 2019-04-24T22:19:25.000Z

In order of preference:

dicer (down, was spotty in the past, can maybe make amends)
grater (down, unused, why?)
slicer (old vm host; wipe/upgrade)
satin (move from current tasks)

Answer 2 · 2019-04-25T00:45:43.000Z

thx. Btw you can use the OBO tracker for this

…

On Wed, Apr 24, 2019 at 5:09 PM kltm ***@***.***> wrote: build.obolibrary.org jenkins 2 instance for obo starting with build-mp-edit talked to @cmungall <https://github.com/cmungall> , use one of our machines, at least 16GB let's see what we got — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAMMOMRF4MF5SJ6TTZPDILPSDJPZANCNFSM4HIIGSIQ> .

Answer 3 · 2019-04-30T01:06:27.000Z

Fair enough, but technically BBOP-only software and hardware (although the running Jenkins and such will be completely OBO).

Answer 4 · 2019-04-30T01:09:41.000Z

Remember that we need the firewall down for the machine before attempting let's encrypt. A note to LBL should be enough for them to bring it down until we can get the cert.