Feature #9618

Check if we still need to patch the Jenkins puppet service definition

Added by bertagaz 2015-06-19 01:35:37 . Updated 2015-07-07 05:40:51 .

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Start date:
2015-06-19
Due date:
% Done:

0%

Feature Branch:
puppet-jenkins:features/9618-stronger_plugin_verification
Type of work:
Sysadmin
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

We patched the upstream puppet-jenkins module to have a better service definition working with Debian’s Jenkins daemon.

That’s feature/better_service_definition branch of the Tails puppet-jenkins module clone.

But our puppet-module is lagging a lot behind the upstream.

We need to first upgrade this module and check if this change is still relevant. If it is, then we’ll have to upstream it.

Subtasks

Related issues

Is duplicate of Tails - Feature #9683: Check if we still need to patch the Jenkins puppet service definition Resolved 2015-07-04

History

#1 Updated by bertagaz 2015-06-19 01:36:30

  • blocks #8668 added

#2 Updated by bertagaz 2015-06-19 01:43:44

  • Parent task set to #6956
  • Type of work changed from Code to Sysadmin

#3 Updated by bertagaz 2015-06-19 01:44:26

  • blocked by Feature #9619: Upstream our changes to the puppet-archive module. added

#4 Updated by bertagaz 2015-06-19 01:45:55

  • blocks deleted (Feature #9619: Upstream our changes to the puppet-archive module.)

#5 Updated by bertagaz 2015-06-19 01:46:42

  • blocked by Feature #9619: Upstream our changes to the puppet-archive module. added

#6 Updated by intrigeri 2015-06-22 09:01:27

  • Target version set to Tails_1.4.1

(same as the parent ticket; if not realistic, please reschedule)

#7 Updated by intrigeri 2015-06-22 09:03:35

I don’t understand why this is blocked by Feature #9619, but that’s no big deal.

#8 Updated by bertagaz 2015-06-25 09:10:07

  • Assignee changed from bertagaz to intrigeri
  • QA Check set to Info Needed
  • Feature Branch set to puppet-jenkins:features/9618-stronger_plugin_verification

So the puppet-archive has been updated with the patch we want, this branch rebase our puppet-jenkins module to the last upstream and apply the old features/stronger_plugin_verification on top of it.

That’s the one supposed to be sent to the upstream and used in our infra. Shall I deploy it? I don’t think we need to change our Tails manifests appart from this.

Once done, I’ll start on this service definition branch.

#9 Updated by intrigeri 2015-06-28 02:08:35

  • Status changed from Confirmed to In Progress

#10 Updated by intrigeri 2015-06-29 00:28:57

  • Target version changed from Tails_1.4.1 to Tails_1.5

bertagaz wrote:
> So the puppet-archive has been updated with the patch we want, this branch rebase our puppet-jenkins module to the last upstream and apply the old features/stronger_plugin_verification on top of it.

Excellent! I stopped reviewing the diff in the middle, since the upstream changes are huge. I’ll trust you to have done that.

> That’s the one supposed to be sent to the upstream and used in our infra. Shall I deploy it?

Yes, please, once 1.4.1 is out :) (hence postponing to 1.5)

#11 Updated by bertagaz 2015-07-04 11:13:09

  • blocks Bug #9682: Upstream our changes in puppet-jenkins added

#12 Updated by intrigeri 2015-07-07 05:34:54

  • blocks deleted (Feature #9619: Upstream our changes to the puppet-archive module.)

#13 Updated by intrigeri 2015-07-07 05:34:58

  • blocked by deleted (#8668)

#14 Updated by intrigeri 2015-07-07 05:35:15

  • blocked by deleted (Bug #9682: Upstream our changes in puppet-jenkins)

#15 Updated by intrigeri 2015-07-07 05:40:51

  • Status changed from In Progress to Duplicate
  • Assignee deleted (intrigeri)
  • Target version deleted (Tails_1.5)

#16 Updated by intrigeri 2015-07-07 06:21:23

  • is duplicate of Feature #9683: Check if we still need to patch the Jenkins puppet service definition added