Feature #8357

Turn the check_PO Jenkins job into a template

Added by intrigeri 2014-12-02 06:48:56 . Updated 2019-03-08 15:53:01 .

Status:
Rejected
Priority:
Low
Assignee:
Category:
Continuous Integration
Target version:
Start date:
2014-12-02
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

In the past, we failed at doing that when {name} contains e.g. dashes or slashes, using jjb’s job-template. Maybe preprocess some template of our own into as many job definitions we need?

Subtasks

History

#1 Updated by intrigeri 2014-12-02 06:50:03

  • blocks Feature #8358: Automatically check PO files in all our repositories added

#2 Updated by bertagaz 2014-12-09 19:09:12

I agree having some sort of job config generation might be the only way to workaround this limitation in jenkins-jobs.

The decision on this ticket might have consequences on ticket Feature #5898 too, but I’m for doing baby steps and implementing this ticket first quickly using what exists, without waiting for a decision here.

#3 Updated by intrigeri 2017-06-05 14:25:24

  • Assignee deleted (intrigeri)

#4 Updated by Anonymous 2017-06-28 08:10:02

  • Assignee set to bertagaz

Tentatively assigning to bertagaz. Please unassign yourself if you think you can’t work on this.
This might be a ticket for new team mates otherwise.

#5 Updated by intrigeri 2017-06-28 08:49:08

  • Assignee deleted (bertagaz)
  • Priority changed from Normal to Low

I think bertagaz should focus on stuff we have explicitly put on our plate for this year.

#6 Updated by intrigeri 2019-03-08 15:52:38

  • blocked by deleted (Feature #8358: Automatically check PO files in all our repositories)

#7 Updated by intrigeri 2019-03-08 15:53:01

  • Status changed from Confirmed to Rejected