Bug #42653
Add support to iocage for git@github.com syntax
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No
Description
Brandon, as we discussed, iocage doesn't play nice when using artifact repos and the git@github.com:ixsystems/<foo> notation. This is required for private repos in many cases. (IT also doesn't work with https://<name>@github.com/iXsystems/foo as well)
History
#1
Updated by Kris Moore about 2 years ago
- Category changed from OS to Middleware
#2
Updated by Brandon Schneider about 2 years ago
Updated by Brandon Schneider - Status changed from Unscreened to In Progress
#3
Updated by Brandon Schneider about 2 years ago
PR: https://github.com/freenas/iocage/pull/24
DESC: Allow usage of git@ syntax
RISK: Low
ACCEPTANCE: Use a custom plugin json using the git@ syntax instead of HTTPS
Helpful Hint: Go to github and click clone and you’ll see a ssh option
#4
Updated by Jurgen Segaert about 2 years ago
Updated by Jurgen Segaert This change seems to have some undesired side-effects: https://github.com/iocage/iocage/issues/605
#5
Updated by Brandon Schneider about 2 years ago
iocage PR merged, however needs an additional cherry pick from jurgen's branch.
#6
Updated by Brandon Schneider about 2 years ago
- Status changed from In Progress to Ready for Testing
- Needs Merging changed from Yes to No
#7
Updated by Dru Lavigne about 2 years ago
Updated by Dru Lavigne - Subject changed from Iocage unhappy with git@github.com: syntax to Add support to iocage for git@github.com syntax
- Needs Doc changed from Yes to No
#8
Updated by William Grzybowski almost 2 years ago
Updated by William Grzybowski - Status changed from Ready for Testing to Passed Testing
There is nothing useful for QA to test here.
#9
Updated by Dru Lavigne almost 2 years ago
- Status changed from Passed Testing to Done
- Needs QA changed from Yes to No