Bug #22675
closed
Commit campaign definition in the configuration repository
Added by Alexis Mousset about 2 years ago.
Updated 27 days ago.
Description
Currently campaigns are stored in the repo but not committed:
root@server:/var/rudder/configuration-repository# git status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
campaigns/
nothing added to commit but untracked files present (use "git add" to track)
- Project changed from 92 to Rudder
- Category set to Web - Campaigns
- Target version changed from 7.3 to 8.2.6
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/6313
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
commit 246a5caa9330dd9312745b869d49b944bd7abd22
Author: rudder <email not set>
Date: Tue Apr 29 12:05:30 2025 +0200
Initial commit for campaigns
then after an edition:
commit 0f888d52ee6691d5115bdc6b4670762d6a658775 (HEAD -> master)
Author: rudder <email not set>
Date: Tue Apr 29 14:44:53 2025 +0200
Archive campaign '5133b640-2168-4983-be03-28b73f793c40'
commit 246a5caa9330dd9312745b869d49b944bd7abd22
Author: rudder <email not set>
Date: Tue Apr 29 12:05:30 2025 +0200
Initial commit for campaigns
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.6 and 8.3.1 which were released today.
Also available in: Atom
PDF