Project

General

Profile

Actions
Copy link

User story #2132

closed

Improve process for upgrading techniques

Added by Nicolas PERRON over 12 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
4
Assignee:
-
Category:
Packaging
Target version:
Ideas (not version specific)
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Actually, after each Rudder upgrade, the new techniques are located in /opt/rudder/share/policy-templates .
In order to bring these new PT to the webapp, we have to copy them in /var/rudder/configuration-repository/policy-templates/ , commit the good ones and in the webapp to reload PT Library.

We can improve this process by automation when we are sure that:
- Any update of a PT is made in a new version
- No local PT is modified from original, otherwise local PT don't have to be changed
- Trigger a load in the webapp of these new PT

Actions
Copy link
 #1

Updated by François ARMAND almost 12 years ago

  • Assignee set to François ARMAND
  • Target version changed from 24 to 47

We have to at least handle a better process for techniques update.

First step: what can be achieved in the 2.5 timeline ?

Actions
Copy link
 #2

Updated by François ARMAND almost 12 years ago

The first first step is to cleanup the property file to be able to know what are the relevant properties for the git repository configuration.

See issue #2602

Actions
Copy link
 #3

Updated by François ARMAND almost 12 years ago

  • Status changed from New to In progress
Actions
Copy link
 #4

Updated by Jonathan CLARKE almost 12 years ago

  • Target version changed from 47 to 50
Actions
Copy link
 #5

Updated by Jonathan CLARKE almost 12 years ago

  • Target version changed from 50 to 2.4.0~beta3
Actions
Copy link
 #6

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.4.0~beta3 to 2.4.0~beta4

We still working on it but i'm not sure that this issue should be in 2.4.

At least, I change it to the next run.

Actions
Copy link
 #7

Updated by Jonathan CLARKE over 11 years ago

  • Target version changed from 2.4.0~beta4 to 2.4.0~rc1
Actions
Copy link
 #8

Updated by Jonathan CLARKE over 11 years ago

  • Status changed from In progress to 2
  • Assignee deleted (François ARMAND)
  • Target version changed from 2.4.0~rc1 to 24
Actions
Copy link
 #9

Updated by Jonathan CLARKE over 11 years ago

  • Status changed from 2 to New
Actions
Copy link
 #10

Updated by Nicolas CHARLES over 11 years ago

  • Target version changed from 24 to Ideas (not version specific)
Actions
Copy link
 #11

Updated by Jonathan CLARKE about 11 years ago

  • Project changed from Rudder to 34
  • Category deleted (11)
Actions
Copy link
 #12

Updated by Benoît PECCATTE about 9 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions
Copy link
 #13

Updated by Benoît PECCATTE about 7 years ago

  • Subject changed from Improve process for upgrading policy templates to Improve process for upgrading techniques
  • Description updated (diff)
  • Status changed from New to Rejected

This is a development process suggestion, it should not go into a ticket.

Actions
Copy link

Also available in: Atom PDF