Open liangchenye opened 7 years ago
On Wed, Nov 29, 2017 at 11:56:53AM +0000, 梁辰晔 (Liang Chenye) wrote:
- In the travis, I upload them to a server -- 'ocihub.org' which I applied.
How will this be secured? Will the admin will hand out per-project credentials to project admins who put those credentials in Travis repository settings 1 and use those settings for their POST?
Yes, the admin will send the 'token' to the user, the user can put it in the travis environment.
Taking codecov
for example, a user could login by his/her github account. codecov
will generate the token and send it to the user automatically. I don't know how many man-power it will cost to develop such a system.
The certification progress is more official. In that case, we may not need to develop a 'token-generate' system. The certification team could just generate it by hand and hand out pre-project credentials to project admins.
I've run the validation tests on runc with CircleCI: https://github.com/opencontainers/runc/pull/1757
Once https://github.com/opencontainers/runtime-tools/pull/439 been merged, we will have a very flexible way to verify/certify a runtime. I wrote a demo to explain how we can integrate it with
travis.ci
. The approach is similar with code coverage which does these:prove validate/*.t
> output.txt to get a testing reportI wrote a demo project to show how to achieve this:
In the future, 'runc', 'rkt', runv' and other runtime projects could apply this approach. So both the maintainer/user could be easily know a runtime is conformed with oci spec.
The server code is very simple, I reuse isula/ihub framework.