From Fedora Project Wiki
No edit summary |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
As we move tests from our internal (downstream) repositories into the upstream packages, | As we move tests from our internal (downstream) repositories into the upstream packages, | ||
we will be utilizing a custom [https://upstreamfirst.fedorainfracloud.org/ | we will be utilizing a custom [https://upstreamfirst.fedorainfracloud.org/ Forge] as a staging area in order to make it | ||
easy for internal folks and upstream maintainers to work. Below are the steps you'll | easy for internal folks and upstream maintainers to work. Below are the steps you'll | ||
need to take to get the tests upstream. | need to take to get the tests upstream. | ||
| Line 8: | Line 8: | ||
* 1 Collect tests into a local git repository | * 1 Collect tests into a local git repository | ||
* 2 Create a project on upstreamfirst.fedorainfracloud.org | * 2 Create a project on the [https://upstreamfirst.fedorainfracloud.org Upstream First Forge] | ||
* 3 Push your local repo to the | * 3 Push your local repo to the Upstream First Forge | ||
* 4 Coordinate with package maintainer | * 4 Coordinate with package maintainer | ||
| Line 19: | Line 19: | ||
* 1 - All tests need to be in a git repository to upload. | * 1 - All tests need to be in a git repository to upload. | ||
* 2 - To create a pagure project, you'll first need to create a [https://admin.fedoraproject.org/accounts/ FAS] account. Once you've created a FAS account, you can log into https://upstreamfirst.fedorainfracloud.org and create a new project. The project name needs to match the package name the tests are for. For instance, if you were uploading tests for `sed`, the project name needs to be `sed'. | * 2 - To create a pagure project, you'll first need to create a [https://admin.fedoraproject.org/accounts/ FAS] account. Once you've created a FAS account, you can log into [https://upstreamfirst.fedorainfracloud.org Upstream First Forge] and create a new project. The project name needs to match the package name the tests are for. For instance, if you were uploading tests for `sed`, the project name needs to be `sed'. | ||
* 3 - Once you've created a project, add it as a remote to your local repo: | * 3 - Once you've created a project, add it as a remote to your local repo: | ||
Latest revision as of 21:06, 24 May 2017
How to Move Tests
As we move tests from our internal (downstream) repositories into the upstream packages, we will be utilizing a custom Forge as a staging area in order to make it easy for internal folks and upstream maintainers to work. Below are the steps you'll need to take to get the tests upstream.
- 1 Collect tests into a local git repository
- 2 Create a project on the Upstream First Forge
- 3 Push your local repo to the Upstream First Forge
- 4 Coordinate with package maintainer
Detailed Description of steps:
- 1 - All tests need to be in a git repository to upload.
- 2 - To create a pagure project, you'll first need to create a FAS account. Once you've created a FAS account, you can log into Upstream First Forge and create a new project. The project name needs to match the package name the tests are for. For instance, if you were uploading tests for
sed, the project name needs to be `sed'. - 3 - Once you've created a project, add it as a remote to your local repo:
git remote add origin ssh://git@upstreamfirst.fedorainfracloud.org/<project-name>.git git push -u origin master
- 4 - Get in contact with the Fedora Packager that maintains the package in question. Use this newly created repo to make any changes, or discuss any issues with the uploaded tests. Once the tests are merged with the upstream package repository in dist-git, we'll delete the project in the staging area.