PR #2500 Followup

[kadel]

• Add devfile parser #2500 (comment) let's use the fake fs package here and write the stuff in memory instead of the disk. That will speed up the testing.
• Add devfile parser #2500 (comment) why not use the Fs Filesystem which is part of the DevfileCtx? What will help us with unit tests using the fake system.
• Add devfile parser #2500 (comment) We can pass the fake filesystem here in DevfileCtx
• Add devfile parser #2500 (comment) since the description says run command not present, should this be build app?
• Add devfile parser #2500 (comment) can we convert these tests to the tabular format we currently use in odo?

/assign @kanchwala-yusuf
/kind devfile
/label state/Ready

[openshift-ci-robot]

@kadel: The label(s) /label state/Ready cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga

In response to this:

• Add devfile parser #2500 (comment) let's use the fake package here and write the stuff in memory instead of the disk. That will speed up the testing.
• Add devfile parser #2500 (comment) why not use the Fs Filesystem which is part of the DevfileCtx? What will help us with unit tests using the fake system.
• Add devfile parser #2500 (comment) We can pass the fake filesystem here in DevfileCtx
• Add devfile parser #2500 (comment) since the description says run command not present, should this be build app?
• Add devfile parser #2500 (comment) can we convert these tests to the tabular format we currently use in odo?

/assign @kanchwala-yusuf
/kind devfile
/label state/Ready

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.

[kadel]

/kind cleanup
/area devfile

[kadel]

/triage ready

[openshift-ci-robot]

@kadel: The label(s) `/label state/Ready

cannot be applied. These labels are supported:platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash`

In response to this:

• Add devfile parser #2500 (comment) let's use the fake fs package here and write the stuff in memory instead of the disk. That will speed up the testing.
• Add devfile parser #2500 (comment) why not use the Fs Filesystem which is part of the DevfileCtx? What will help us with unit tests using the fake system.
• Add devfile parser #2500 (comment) We can pass the fake filesystem here in DevfileCtx
• Add devfile parser #2500 (comment) since the description says run command not present, should this be build app?
• Add devfile parser #2500 (comment) can we convert these tests to the tabular format we currently use in odo?

/assign @kanchwala-yusuf
/kind devfile
/label state/Ready

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.

[openshift-ci-robot]

@kadel: The label(s) `/label state/Ready

cannot be applied. These labels are supported:platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash`

In response to this:

• Add devfile parser #2500 (comment) let's use the fake fs package here and write the stuff in memory instead of the disk. That will speed up the testing.
• Add devfile parser #2500 (comment) why not use the Fs Filesystem which is part of the DevfileCtx? What will help us with unit tests using the fake system.
• Add devfile parser #2500 (comment) We can pass the fake filesystem here in DevfileCtx
• Add devfile parser #2500 (comment) since the description says run command not present, should this be build app?
• Add devfile parser #2500 (comment) can we convert these tests to the tabular format we currently use in odo?

/assign @kanchwala-yusuf
/kind devfile
/label state/Ready

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.

[openshift-ci-robot]

@kadel: The label(s) `/label state/Ready

cannot be applied. These labels are supported:platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash`

In response to this:

• Add devfile parser #2500 (comment) let's use the fake fs package here and write the stuff in memory instead of the disk. That will speed up the testing.
• Add devfile parser #2500 (comment) why not use the Fs Filesystem which is part of the DevfileCtx? What will help us with unit tests using the fake system.
• Add devfile parser #2500 (comment) We can pass the fake filesystem here in DevfileCtx
• Add devfile parser #2500 (comment) since the description says run command not present, should this be build app?
• Add devfile parser #2500 (comment) can we convert these tests to the tabular format we currently use in odo?

/assign @kanchwala-yusuf
/kind devfile
/label state/Ready

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.

[openshift-ci-robot]

@kadel: The label(s) `/label state/Ready

cannot be applied. These labels are supported:platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash`

In response to this:

• Add devfile parser #2500 (comment) let's use the fake fs package here and write the stuff in memory instead of the disk. That will speed up the testing.
• Add devfile parser #2500 (comment) why not use the Fs Filesystem which is part of the DevfileCtx? What will help us with unit tests using the fake system.
• Add devfile parser #2500 (comment) We can pass the fake filesystem here in DevfileCtx
• Add devfile parser #2500 (comment) since the description says run command not present, should this be build app?
• Add devfile parser #2500 (comment) can we convert these tests to the tabular format we currently use in odo?

/assign @kanchwala-yusuf
/kind devfile
/label state/Ready

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.

[openshift-ci-robot]

@kadel: The label(s) `/label state/Ready

cannot be applied. These labels are supported:platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash`

In response to this:

• Add devfile parser #2500 (comment) let's use the fake fs package here and write the stuff in memory instead of the disk. That will speed up the testing.
• Add devfile parser #2500 (comment) why not use the Fs Filesystem which is part of the DevfileCtx? What will help us with unit tests using the fake system.
• Add devfile parser #2500 (comment) We can pass the fake filesystem here in DevfileCtx
• Add devfile parser #2500 (comment) since the description says run command not present, should this be build app?
• Add devfile parser #2500 (comment) can we convert these tests to the tabular format we currently use in odo?

/assign @kanchwala-yusuf
/kind devfile
/label state/Ready

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.