Bug #8913

Jobs removed in the jenkins-jobs repository are not (always?) deleted from Jenkins

Added by intrigeri 2015-02-17 19:37:04 . Updated 2015-02-25 12:56:33 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Tails_1.4
Start date:
2015-02-17
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

I’ve just deleted a Jenkins job via the jenkins-jobs repo, and then it was still active in Jenkins. I had to manually jenkins-jobs delete build_Tails_ISO_feature-linux-3.18 to remove it for real. Of course this cannot possibly scale once we add/remove dozens of jobs each month.

A similar problem we were suffering from was fixed in Jessie with jenkins-job-builder (0.9.0-0.2), which we are running, but it doesn’t fix this issue.

Subtasks

Related issues

Blocks Tails - Feature #6196: Build all active branches Resolved 2013-08-07 2015-07-15

History

#1 Updated by intrigeri 2015-02-17 19:37:29

  • Assignee set to bertagaz

Assigning to bertagaz to start with, I’ll let you decide with DrWhax who does what exactly.

#2 Updated by intrigeri 2015-02-17 19:48:07

  • Description updated

#3 Updated by intrigeri 2015-02-17 19:53:29

  • Description updated

#4 Updated by intrigeri 2015-02-19 22:22:04

#5 Updated by intrigeri 2015-02-19 22:22:20

#6 Updated by bertagaz 2015-02-25 09:49:10

Pushed a small change to our automatic job deployment script in the puppet Tails module that might fix this. It uses the —delete-old option of the jenkins-jobs update command.

We’ll see if it works next time someone push a change that remove some job.

#7 Updated by intrigeri 2015-02-25 10:42:37

> We’ll see if it works next time someone push a change that remove some job.

Good news: the RM asked you yesterday to disable the testing branch build job, so here’s one test case :)

#8 Updated by bertagaz 2015-02-25 12:47:26

  • Status changed from Confirmed to In Progress
  • Assignee changed from bertagaz to intrigeri
  • % Done changed from 0 to 90
  • QA Check set to Ready for QA

Just removed the testing job then, and it disappeared from the jenkins interface, so it seems to work. Please have a look and close this ticket if you’re happy.

#9 Updated by intrigeri 2015-02-25 12:56:33

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 90 to 100
  • QA Check changed from Ready for QA to Pass

Looks good, nice catch!