Project

General

Profile

Actions
Copy link

Bug #2804

closed

In rudder upgrade, the Rudder Technique Reference Library attribute in rudder-wbe.properties should be checked with a more flexbile way

Added by Nicolas PERRON over 12 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
5 (lowest)
Assignee:
Nicolas PERRON
Category:
Packaging
Target version:
2.4.0~rc2
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Since #2802 , the Rudder Technique Reference Library attribute is checked and truncated in order to be on a right branch. Nevertheless, we only take into account of "nameOfBranch", "/refs/heads/nameOfBranch", "refs/tags/nameOfBranch" and "refs/remote/origin/nameOfBranch". We should be able to handle other conditions

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #2802: Rudder can't start after a migration if the Rudder Technique Reference Library branch is not the same than the /var/rudder/configuration-repository branchReleasedNicolas PERRON2012-08-13Actions
Related to Rudder - Bug #2805: After a migration from 2.3 to 2.4.0~beta3, if a migration has been made with a wrong git branch on /var/rudder/configuration-repository it is impossible to return in a normal stateRejectedNicolas PERRON2012-08-14Actions
Actions
Copy link

Also available in: Atom PDF