Project

General

Profile

Bug #39638

Change iocage plugin mechanism to use branches

Added by Brandon Schneider over 1 year ago. Updated over 1 year ago.

Status:
Done
Priority:
No priority
Assignee:
Brandon Schneider
Category:
Middleware
Target version:
Severity:
Med High
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

We need this to be able to safely sunset plugins when a release ships, pkgs are unaffected, this is only for listing of plugins and their JSON.


Related issues

Related to FreeNAS - Feature #39258: Allow branch selection for iocage pluginsDone
Related to FreeNAS - Feature #41080: Switch plugin release back to 11.1-RELEASE in 11.1-RELEASE branch of freenas/iocage-ix-pluginsClosed

History

#1 Updated by Brandon Schneider over 1 year ago

  • Related to Feature #39258: Allow branch selection for iocage plugins added

#2 Updated by Brandon Schneider over 1 year ago

  • Status changed from Unscreened to In Progress

#3 Updated by Brandon Schneider over 1 year ago

PR: https://github.com/freenas/iocage/pull/6
DESC: We now use branches for all plugin artifacts and the main repo with the index.
RISK: Low
ACCEPTANCE: Plugins still install.

#5 Updated by Dru Lavigne over 1 year ago

  • Status changed from In Progress to Ready for Testing
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#6 Updated by Dru Lavigne over 1 year ago

  • Related to Feature #41080: Switch plugin release back to 11.1-RELEASE in 11.1-RELEASE branch of freenas/iocage-ix-plugins added

#7 Updated by Dru Lavigne over 1 year ago

  • Status changed from Ready for Testing to Done
  • Needs QA changed from Yes to No

#8 Updated by Dru Lavigne over 1 year ago

  • Subject changed from Change iocage's plugin mechanism to use branches to Change iocage plugin mechanism to use branches

Also available in: Atom PDF