没有合适的资源?快使用搜索试试~ 我知道了~
使用 GitHub Enterprise 进行开放开发的影响.docx
1.该资源内容由用户上传,如若侵权请联系客服进行举报
2.虚拟产品一经售出概不退款(资源遇到问题,请及时私信上传者)
2.虚拟产品一经售出概不退款(资源遇到问题,请及时私信上传者)
版权申诉
0 下载量 39 浏览量
2024-04-17
12:47:24
上传
评论
收藏 539KB DOCX 举报
温馨提示
试读
53页
使用 GitHub Enterprise 进行开放开发的影响.docx
资源推荐
资源详情
资源评论
Memo No 914
Impact of using GitHub
Enterprise for Open
Development
Tiago Quintino, Iain Russell,
Daniel Tipping, Dusan Figala
October 2023
Series: ECMWF Technical Memoranda
A full list of ECMWF Publications can be found on our web site under:
http://www.ecmwf.int/publications/
Contact: library@ecmwf.int
© Copyright 2023
European Centre for Medium Range Weather Forecasts
Shinfield Park, Reading, Berkshire RG2 9AX, England
Literary and scientific copyrights belong to ECMWF and are reserved in all countries. The content of this
document is available for use under a Creative Commons Attribution 4.0 International Public License. See
the terms at https://creativecommons.org/licenses/by/4.0/.
The information within this publication is given in good faith and considered to be true, but ECMWF accepts
no liability for error, omission and for loss or damage arising from its use.
Impact of using GitHub Enterprise for Open Development
Technical Memorandum No. 914
1
Contents
1. Introduction 7
1.1. Scope 7
1.2. Introduction to Open Development 7
1.3. Overview of GitHub
8
1.3.1. GitHub Enterprise 8
1.3.2. GitHub Actions 9
1.4. Overview of the Atlassian stack 9
1.4.1. Bitbucket 9
1.4.2. Bamboo 9
1.4.3. Jira 10
1.5. Findings from Interviews with the ECMWF Development Section 10
1.5.1. ECMWF needs 10
1.5.2. Problems with the current Bitbucket/Bamboo and legacy GitHub setup 12
1.5.3. Additional concerns 12
1.6. Project Goals
12
1.7. Overview of report 13
2. Investigation of Self-hosted GitHub Actions Runners 13
2.1. Overview of self-hosted GitHub Actions runners at ECMWF 14
2.2. Provisioning and configuring self-hosted runners 14
2.3. Platform Builders 14
2.4. MacOS Builders
15
2.5. HPC Builders 15
2.6. Web Builders 16
2.7. Limitations of self-hosted runners 16
2.8. Security implications of self-hosted runners 16
2.8.1. Background 16
2.8.2. Public PR Approval
Process
17
2.8.3. Access controls for GitHub
Labels
17
2.9. Conclusion 18
3. Continuous Integration with GitHub Actions 18
3.1. 3.1. Downstream CI 18
Impact of using Github Enterprise for Open Development
2
Technical Memorandum No. 914
3.1.1. Downstream CI Environments
19
3.1.2. Extensibility of Downstream CI by ECMWF developers
21
3.2. Nightly CI
21
3.3. Build Matrix
21
3.4. CI for Quality Control
21
3.5. CI for mars-hpss
22
3.6. Conclusion
22
4.
Continuous Delivery with GitHub Actions
23
4.1. Nexus CD with GitHub Actions
23
4.2. Homebrew CD with GitHub Actions
23
4.3. PyPI CD with GitHub Actions
23
4.4. Conclusion
24
5.
Continuous Deployment of Web Apps with GitHub Actions
24
5.1. Desired web app deployment process
24
5.1.1. Requirements for an ideal web app CD system
25
5.2. Web app CD prototypes: IFSHub and Polytope
25
5.2.1. IFSHub CD prototype
25
5.2.2. Polytope CD prototype
27
5.3. Limitations of the current design
27
5.3.1. Lack of visibility on the full deployment pipeline
27
5.3.2. Manual approval for prod deployment is not straightforward
28
5.4. Conclusion
29
6.
Reusability of GitHub Actions workflows
29
6.1. Reusable Workflows
30
6.1.1. Advantages of Reusable Workflows
30
6.1.2. Limitations of Reusable Workflows
30
6.2. Composite Actions
30
6.2.1. Advantages of Composite Actions
30
6.2.2. Limitations of Composite Actions
30
6.3. TypeScript Actions
31
6.3.1. Advantages of TypeScript Actions
31
6.3.2. Limitations of TypeScript Actions
31
Impact of using GitHub Enterprise for Open Development
Technical Memorandum No. 914
3
6.4. How to choose between a Reusable Workflow, a Composite Action, and a TypeScript
Action 31
6.5. Using GitHub Actions for reusable automations beyond software testing 32
6.6. Conclusion 32
7. Integration of GitHub Enterprise with ECMWF Single Sign-On (SSO) 33
7.1. Options available for GitHub Enterprise access management 33
7.2. Integration of GitHub Enterprise and ECMWF SSO 33
7.2.1. Using SSH keys with SSO 34
7.2.2. Provisioning a user account 34
7.2.3. Deprovisioning a user account 34
7.3. Conclusion 35
8. Integration of GitHub Enterprise with Jira 35
8.1. Linking GitHub Enterprise with Jira 35
8.1.1. GitHub Autolinks 35
8.1.2. GitHub for Jira App 36
8.2. Jira and Open Development
36
8.3. Possible Processes to Integrate GitHub Issues and Jira for Open Development 37
8.3.1. Option 1: Automatic Link between GitHub Issues and Jira Tickets 37
8.3.2. Option 2: Move Software Development tickets from Jira to GitHub Issues 37
8.4. Conclusion 38
9. Disaster Recovery and Backups 38
9.1. Analysis of recent GitHub uptime 39
9.2. Option 1: Self-host GitHub Enterprise at ECMWF 39
9.3. Option 2: Use GitHub Enterprise Cloud and Bitbucket as redundant read-only service 40
9.4. Option 3: Use GitHub Enterprise Cloud and continuous backups 40
9.5. Option 4: Trust GitHub Enterprise Cloud 41
9.6. Conclusion 41
10. Expected Costs 41
10.1. Cost of GitHub Enterprise seats 42
10.2. Cost of CI runners 42
10.2.1. GitHub-hosted cloud runners 42
10.2.2. MacStadium-hosted runners 42
剩余52页未读,继续阅读
资源评论
百态老人
- 粉丝: 1707
- 资源: 2万+
下载权益
C知道特权
VIP文章
课程特权
开通VIP
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功