[FOLIO-2329] make `jenkins-pipeline-libs` public and move `folio-infrastructure` private repo to separate GitHub org Created: 28/Oct/19 Updated: 03/Jun/20 Resolved: 10/Feb/20 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Peter Murray | Assignee: | mark.stacy |
| Resolution: | Done | Votes: | 0 |
| Labels: | platform-backlog, platform-core | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | CP: sprint 78, CP: sprint 79, DevOps: sprint 82 | ||||||||
| Story Points: | 3 | ||||||||
| Development Team: | FOLIO DevOps | ||||||||
| Description |
|
The FOLIO project is spending about $1,400/month for the GitHub users in the `folio-org` GitHub organization. The project cannot use GitHub's gratis open source program because we have eight private repositories, of which only `folio-infrastructure` and `jenkins-pipeline-ilbs` seem to be active. GitHub has been unresponsive to giving us an exception to us having two private infrastructure repositories in the open source program. Is is possible to move these two repos to a separate GitHub organization with a private repo subscription? It would only need the six people listed as watchers on this issue, so that would cost considerably less than what is being paid for GitHub services now. |
| Comments |
| Comment by John Malconian [ 28/Oct/19 ] |
|
We can make jenkins-pipeline-libs 'public' and possibly move folio-infrastructure to index data's repo? Would that make sense? If we do the latter, then we need update a bunch of code first. |
| Comment by Wayne Schneider [ 28/Oct/19 ] |
|
If we move folio-infrastructure to the Index Data organization, we will need to make plans to move it again when infrastructure management is assumed by some other organization. Is there another existing Github organization managed by the OLF that would be appropriate? |
| Comment by Wayne Schneider [ 28/Oct/19 ] |
|
Reading a little more carefully – Peter Murray, are you suggesting creating a new Github org managed by OLF that will allow private repos with a smaller number of org members? |
| Comment by Peter Murray [ 28/Oct/19 ] |
|
Yes, exactly Wayne Schneider...a new GitHub org managed by OLF. There is sensitivity to having the project's tools owned/managed by the Foundation, so I don't think they would look kindly to having the `folio-infrastructure` repo in the IndexData organization. But if we can move from $1,400/month to $25/month, that would make a big difference. |
| Comment by Peter Murray [ 30/Oct/19 ] |
|
Could we estimate how much effort it would take to move `folio-infrastructure` to another GitHub organization (say, `https://github.org/folio-ci` for the sake of argument)? (This assumes that `jenkins-pipeline-libs` could be made public so its URLs would not change.) And given that time estimate, when would it be realistic to expect the work could be done? |
| Comment by Peter Murray [ 12/Nov/19 ] |
|
Checking in to see if there is concensus in the Core Platform team on how much effort this would be and how it is prioritized against other tasks. |
| Comment by Oleksii Popov [ 20/Nov/19 ] |
|
COre:Platform plans to take this ticket into the next sprint. |
| Comment by John Malconian [ 20/Nov/19 ] |
|
Peter Murray Could you help facilitate this by creating the GitHub repo and setting up the billing that we will use to migrate folio-infrastructure to? We also intend to keep jenkins-pipeline-libs in folio-org but make it a public repo. |
| Comment by Peter Murray [ 20/Nov/19 ] |
|
Yes, I'll get that new GitHub org set up with Scott Anderson (OLF Treasurer) and assign owner privileges to you. |
| Comment by Peter Murray [ 22/Nov/19 ] |
|
https://github.com/folio-org-priv is set up with billing information and ready for use in the next sprint. |
| Comment by mark.stacy [ 07/Feb/20 ] |
|
Tested Github repo redirects and moved `folio-infrastructure` to new Github organization `folio-org-priv`. `jenkins-pipeline-ilbs` will not be moved. Repo will become public and left in `folio-org` |
| Comment by Peter Murray [ 08/Feb/20 ] |
|
Thanks for the update, Mark! Is there an estimate for when `jenkins-pipeline-libs` will be made public? |
| Comment by mark.stacy [ 10/Feb/20 ] |
|
Peter Murray Jakub Skoczen `jenkins-pipeline-libs` is now public! |