[Qa-jenkins-scm] [jenkins.debian.net] 01/02: notes as taken with gobby during https://summit.debconf.org/debconf15/meeting/186/jenkinsdebianorg-session/

[Holger Levsen]

This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch master
in repository jenkins.debian.net.

commit b5a73132770c4ff60b3f7a0f00e8174febe73de0
Author: Holger Levsen <holger at layer-acht.org>
Date:   Wed Aug 26 11:59:51 2015 +0200

    notes as taken with gobby during https://summit.debconf.org/debconf15/meeting/186/jenkinsdebianorg-session/
---
 TODO | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/TODO b/TODO
index b8f6c9a..eb7673e 100644
--- a/TODO
+++ b/TODO
@@ -59,19 +59,20 @@ Most jobs have been converted, a few are left to do:
 === move this setup to jenkins.d.o
 
 The plan is to run a jenkins.d.o host, which is maintained by DSA, but we are maintaining jenkins on it (so we can install any plugins we like etc). then we also setup several jenkins slaves, probably/maybe also maintained by DSA (so we get them into their munin), but on which we can use sudo as we need it. (or maybe not dsa-maintained slaves, so that we can use sudo as we need, for the price of not being in DSAs munin.)
+ - install munin on jenkins, monitor nodes as slaves
 
 ==== next steps for jenkins.d.o migration
 
-* h01ger: sit down with weasel at cccamp or debconf and document current state and discuss next steps
-** probably do (at least) the 2nd step at debconf so others can participate
-* old plan:
+* add more pressure to DSA to get jenkins.d.o set up
+** "having this mid september is doable, just grab some from DSA on irc"
+** the machine is already setup, it just needs the name changed.
 ** weasel/h01ger: install jenkins.deb from jenkins-ci.org
 *** also create jenkins users in jenkins (KISS)
-** h01ger: get slaves: wishlist for starting: 3 slaves, 8 cores, 32gb ram, 150gb hd space if we dont need squid3 on them, 200gb if we do.
-*** install slaves - how (to automate)?
+** install slaves - how (to automate)?
 ** install jenkins-job-builder "somehow", currently "only" a package from fil exists (but needs build-depends not yet even in sid atm)
 ** update DNS to point jenkins.d.o to jerea.d.o
 *** the existing jenkins.d.o host needs to be renamed to something else (thats "just work" to do but not a major obstacle)
+** zigo offers to maintain j-j-b as part of openstack. we need the package (which is not) in sid (atm) in jessie-backports.
 
 ==== unsorted notes for jenkins.d.o migration
 
@@ -106,6 +107,7 @@ The plan is to run a jenkins.d.o host, which is maintained by DSA, but we are ma
 
 * use fil's package: http://ftp.hands.com/hands-deb/pool/main/j/jenkins-job-builder/jenkins-job-builder_1.2.0~git-0~1.gbp1ae299.dsc
 ** needs at least some of the stuff on fil's j.d.n.git/needs-jjb-1.2.0 branch to work with that
+* investigate whether its possible nowadays to let it delete jobs which were removed..
 
 ==== old jenkins-job-builder TODO, mostly (all?) obsolete thanks to fil's work:
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/qa/jenkins.debian.net.git