Hi, I also think a clean cut is a good solution. I've deployed Jenkins on a couple of machines and I used exclusively the upstream packages. I try to keep to a minimium the number of non-oficial packages but sometimes it's not doable. Also, having a mix of officially supported and some not supported might create a bit of confusion. Regards, On 11.01.2016 17:52, Markus Koschany wrote: > Am 11.01.2016 um 16:04 schrieb Emmanuel Bourg: >> Hi all, >> >> I'm pondering what we should do about Jenkins in Debian. > > [...] > >> 2. Package a subset of Jenkins. >> We could keep only the jenkins-cli and jenkins-slave package as they >> provide a real added value over the upstream .deb package. This >> subset should be easier to maintain. >> >> 3. Remove Jenkins completely. >> >> What do you think? > > Hi, > > I am in favor of removing Jenkins completely because of the reasons you > have already mentioned. It just doesn't fit into Debian's release cycle > and it requires way to much effort to keep it in shape unless there > would be someone who wants to work full-time on it. I presume > jenkins-cli and jenkins-slave would be affected by the same short three > month support release cycle. Thus I'm not sure whether it's worth to > keep them, except they are dependencies for other packages or are better > supported upstream. Otherwise I would do a clean cut here. > > Regards, > > Markus >
Attachment:
signature.asc
Description: OpenPGP digital signature