Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
S
sysadmin
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 82
    • Issues 82
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards
  • tails
  • sysadmin
  • Issues
  • #10068

Closed
Open
Opened Aug 20, 2015 by bertagaz@bertagaz1 of 1 task completed1/1 task

Upgrade to Jenkins 2.x, using upstream packages

Originally created by @bertagaz on #10068 (Redmine)

The current state of the Jenkins Debian package is quite scary: it’s lagging a lot behind Jenkins’ LTS version, and it has quite a bunch of known security bugs (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781223)

The Debian package state will probably not be fixed, given the Jenkins LTS release fast pace. In this situation, we’re quite stuck using outdated Jenkins plugins too, given they often depends on precise Jenkins versions. This doesn’t help our Jenkins plugins upgrade sysadmin task.

jenkins.debian.net is using upstream’s LTS package. We probably should discuss the situation with them, as they’ll probably stumble upon the same problem as they want DSA to take care of the sysadmin maintenance of their instance.

Some discussions are planned at the 2015 Debconf about jenkins.d.n. Could be good to follow what happen on this front.

We could use the upstream APT repo and their Debian package, but it would need some review from our side, to see how the packaging is done and what it really install. Sadly, the Debian package sources don’t seem to be available.

Subtasks

  • #15155 (closed)

Related issues

  • Related to tails#10117 (closed)
  • Related to #11739 (closed)
  • Related to #17088 (closed)
  • Blocks tails#10328
  • Blocks #11295 (closed)
  • Blocks #10601 (closed)
  • Blocks #16954 (closed)
  • Blocks #16955 (closed)
  • Blocks #6270 (closed)
  • Blocks #17080 (closed)
Edited May 15, 2020 by bertagaz
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tails_4.0
Milestone
Tails_4.0 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: tails/sysadmin#10068