-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
way to integrate runtime validation with travis.ci #527
Comments
On Wed, Nov 29, 2017 at 11:56:53AM +0000, 梁辰晔 (Liang Chenye) wrote:
2. In the
[travis](https://github.com/liangchenye/oci-cert-demo/blob/master/.travis.yml#L16),
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?
[1]: https://docs.travis-ci.com/user/environment-variables/#Defining-Variables-in-Repository-Settings
|
Yes, the admin will send the 'token' to the user, the user can put it in the travis environment. 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: opencontainers/runc#1757 |
Once #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.
The text was updated successfully, but these errors were encountered: