You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-43
Original file line number
Diff line number
Diff line change
@@ -10,53 +10,14 @@ Your contributions such as reporting a bug and sending pull-request are very wel
10
10
## How to send pull-request
11
11
12
12
1. Fork the repository: https://github.com/multiarch/qemu-user-static . Ex. https://github.com/junaruga/qemu-user-static
13
-
2. This repository is using Travis CI. You can test your modified code on your forked repository before sending a pull-requeste. Go to https://travis-ci.org/your_account_name/qemu-user-static , then enable Travis. Ex. https://travis-ci.org/junaruga/qemu-user-static
13
+
2. This repository is using Github Actions. You can test your modified code on your forked repository before sending a pull-requeste.
14
14
3. If you want to test pushing created container images,
15
15
* You need to have your own container repository such as DockerHub or Quay.io. Ex. https://quay.io/repository/junaruga/qemu-user-static
16
-
* You need to set environment variables `DOCKER_USERNAME` and `DOCKER_PASSWORD` on your repository's Travis CI Settings page. Please remember it is better to set `DOCKER_PASSWORD` without displaying the value for your security.
17
-

18
-
16
+
* You need to set environment variables `DOCKER_USERNAME` and `DOCKER_PASSWORD` on your repository's Settings page. Please remember it is better to set `DOCKER_PASSWORD` without displaying the value for your security.
19
17
4. You also need to have your https://quay.io/repository/junaruga/qemu-user-static
20
-
5. You need to edit `.travis.yml` with your container repository. This step can be improved in the future.
18
+
5. You need to edit `.github/workflows/actions.yml` with your container repository. This step can be improved in the future.
21
19
6. Below is an example of how to test with your container repository.
22
-
23
-
```
24
-
$ git diff
25
-
diff --git a/.travis.yml b/.travis.yml
26
-
index 79ca070..edee35e 100644
27
-
--- a/.travis.yml
28
-
+++ b/.travis.yml
29
-
@@ -15,13 +15,13 @@ env:
30
-
- VERSION=4.0.0-5
31
-
# See qemu-user-static's RPM spec file on Fedora to check the new version.
For 32-bit container image, the result of `uname` can be the 64-bit's one. But it is 32-bit environment. Please see the [example](docs/examples.md) - junaruga/ci-multi-arch-test i386 case on Travis CI.
Copy file name to clipboardExpand all lines: docs/developers_guide.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -80,9 +80,9 @@ binfmt_misc is a feature of kernel. A container uses the host OS's kernel.
80
80
## Programs input & output
81
81
82
82
In this section, we describe a program's input and output.
83
-
This repository is a pipeline system by using Travis CI.
83
+
This repository is a pipeline system by using Github Actions.
84
84
85
-
First, we describe the entire pipelne system's input and output. `.travis.yml` is the top level file.
85
+
First, we describe the entire pipelne system's input and output. `.github/workflows/actions.yml` is the top level file.
86
86
87
87
* Input of the pipeline: `qemu-user-static-X.Y.Z-R.fcNN.$arch.rpm` RPM file under [Fedora Project URL](https://kojipkgs.fedoraproject.org/packages/qemu). Right now `$arch` is only x86_64.
0 commit comments