-
Notifications
You must be signed in to change notification settings - Fork 243
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
Tests for devfiles in odo devfile registry #3378
Comments
@kadel: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-priority medium |
@amitkrout please observe that the tests are to be added in the odo-devfiles/registry |
@kadel @girishramnani i started few scripting steps, then thought let me check how you see the requirement and the solution.
OR
NOTE: If we are following the type 1 then we can not guaranty that https://github.com/odo-devfiles/registry master is not broken. In type two we can atleast make sure that odo-devfiles/registry master is not broken. Can you please confirm ? |
This should be another CI setup independent from The tests should use latest released odo binary. |
@kadel For CI job configuration i need admin access to this repo https://github.com/odo-devfiles/registry. Can you please provide me the required access |
done |
Hit the issue #3476 while i was applying the test flow through the script. |
Hit another issue while accessing the route - #3477 |
Focus on Travis for now and get tests working on it. Focus on Prow later. |
After discussion with @amitkrout Here is what I propose: Every devfile directory will contain a file
In travis script, we will
Note: to list the directories in a directory shell script, you can either
or
cc @kadel |
@mohammedzee1000 Actually i was doing over engineering. This looks cool to me 👍 |
As per the last discussion with @kadel, steps to be followed
|
Validation steps remaining
Ping @anandrkskd |
|
We should have tests for each devfile in https://github.com/odo-devfiles/registry that will verify that they are valid and usable.
There should a common test flow that will be executed using each devfile in the registry.
odo create <devfile>
odo url create
odo push
odo push --debug
odo debug port-forward
odo delete
The tests should be executed on https://github.com/odo-devfiles/registry repository for every PR
We can start by running this on Travis
/area registry
/kind test
/priority medium
The text was updated successfully, but these errors were encountered: