Feature #8636: Deploy our Puppet recipes for Jenkins from scratch

Feature #8636

Deploy our Puppet recipes for Jenkins from scratch

Added by Dr_Whax about 10 years ago. Updated about 10 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Infrastructure

Target version:

Tails_1.5

Start date:

2015-01-09

Due date:

2015-02-28

% Done:

100%

Feature Branch:

Type of work:

Contributors documentation

Blueprint:

Starter:

Affected tool:

Deliverable for:

266

Description

The objective is to have our current Jenkins setup easy to replicate and document on how to do so.

Subtasks

History

#1 Updated by Dr_Whax about 10 years ago

I’ll get an introduction on how to deploy this soon(asap).

#2 Updated by intrigeri about 10 years ago

related to Feature #6922: Document how to replicate parts of our infrastructure for local testing added

#3 Updated by intrigeri about 10 years ago

Subject changed from Deploy our jenkins puppet recipes from scratch to Deploy our Puppet recipes for Jenkins from scratch

#4 Updated by bertagaz about 10 years ago

Target version set to Tails_1.3

#5 Updated by bertagaz about 10 years ago

related to deleted (~~Feature #6922: Document how to replicate parts of our infrastructure for local testing~~)

#6 Updated by bertagaz about 10 years ago

Parent task set to ~~Feature #6196~~

#7 Updated by bertagaz about 10 years ago

blocked by Feature #6922: Document how to replicate parts of our infrastructure for local testing added

#8 Updated by Dr_Whax about 10 years ago

We’re thinking of adding this to the following page: https://tails.boum.org/contribute/working_together/roles/sysadmins/

Or do we want another page for this? /roles/ci-team/ ?

#9 Updated by bertagaz about 10 years ago

Are you talking about the documentation about how to deploy parts of our infra?

In this case, I guess this is ticket Feature #6922 then.

#10 Updated by intrigeri about 10 years ago

I think this was completed. Wasn’t it?

#11 Updated by Dr_Whax about 10 years ago

Yes, we have deployed 2 vm’s!

#12 Updated by intrigeri about 10 years ago

> Yes, we have deployed 2 vm’s!

So… why is this ticket still open?

#13 Updated by Dr_Whax about 10 years ago

% Done changed from 0 to 100

I put done to 100%. I can’t choose the status with resolved, only with fix committed. Is this sufficient for now?

#14 Updated by intrigeri about 10 years ago

> I put done to 100%. I can’t choose the status with resolved, only with fix committed.

… because this ticket is marked as blocked by Feature #6922, which has Confirmed status. Given that you apparently managed to resolve ~~Feature #8636~~ without Feature #6922 being fixed first, that relationship seems to be buggy. So please delete it and close this ticket, otherwise we’ll be twisting Redmine semantics in confusing way.

#15 Updated by bertagaz about 10 years ago

% Done changed from 100 to 80

I believe we haven’t really finished this task, we still have one final last step to have this deployment in a working state (deploying a local Tails git clone and hook it into jenkins to trigger builds on changes).

Regarding Feature #6922, the relationship between the 2 tickets makes sense. It is being worked on, but I’m unsure of when it will be finished, in the coming week if everything goes fine.

This tickets are not really blockers for the 1.3 release anyway, this milestone was mainly there to be an indication and they can be delayed a bit.

#16 Updated by intrigeri about 10 years ago

Thanks for the explanation :)

> […] this milestone was mainly there to be an indication and they can be delayed a bit.

Fair enough.

#17 Updated by Dr_Whax about 10 years ago

This work will be finished at the end of the upcoming week. No mercy!

#18 Updated by Dr_Whax about 10 years ago

Due date changed from 2015-01-30 to 2015-02-28
Target version changed from Tails_1.3 to Tails_1.3.2

Made good progress on this today, minor bug remaining.

#19 Updated by BitingBird about 10 years ago

Status changed from Confirmed to In Progress

#20 Updated by Dr_Whax about 10 years ago

Alright, we have a build working. If the build finishes successfully, I declare this ticket as resolved.

#21 Updated by intrigeri about 10 years ago

> Alright, we have a build working. If the build finishes successfully, I declare this ticket as resolved.

Good, it means that our Puppet stuff is starting to be good enough that one can replicate it given enough hand-holding!

Hence, I don’t see why this ticket could be marked as resolved yet, for the same reasons that we discussed two weeks ago on this very ticket. Did I miss anything?

(Details: my understanding of the relationship between this ticket and Feature #6922 (that I asked to be clarified 2 weeks ago, and then bertagaz confirmed to make sense in ~~Feature #8636#note-15~~) is that the idea was to write doc (Feature #6922), and then use this from scratch deployment (~~Feature #8636~~) to validate both the doc and the Puppet code. So, it seems that we’ve now validated the Puppet bits, but not the doc yet — since it doesn’t exist.)