Skip to content
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

Implement post-flight check requirements into the codenvy/che-test image #2127

Closed
6 tasks done
dmytro-ndp opened this issue Aug 15, 2016 · 0 comments
Closed
6 tasks done
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. status/in-progress This issue has been taken by an engineer and is under active development.

Comments

@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Aug 15, 2016

For the Codevny on-prem propose, the che-test should:

  • Perform check in the next separate steps:
  1. Authenticating as admin.
  2. Generating 'your-first-workspace'.
  3. Starting workspace runtime. (downloads 500MB image)
  • Add create project step

4/. Creating Spring project in your-first-workspace.

  • Stop and remove created workspace after the check.
  • Support quiet mode with flag --quiet to avoid to display logs of starting workspace
  • Support log without prefix mode with flag --logger-prefix-off to display results in the next format:

-> stdout
Authenticating as admin.
Generating 'your-first-workspace'.
Starting workspace runtime. (downloads 500MB image)
Creating Spring project in your-first-workspace.
(exit 0)

or, in case of error:

-> stdout
Authenticating as admin.
Generating 'your-first-workspace'.
-> stderr
error message
(exit 1)

  • Input arguments: admin name and password. IP of Codenvy on-prem instance could be obtained by ifconfig command.
    login/password is given with --user= --password=

Here is a pull request.

@dmytro-ndp dmytro-ndp added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Aug 15, 2016
@benoitf benoitf self-assigned this Aug 16, 2016
@benoitf benoitf added the status/in-progress This issue has been taken by an engineer and is under active development. label Aug 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. status/in-progress This issue has been taken by an engineer and is under active development.
Projects
None yet
Development

No branches or pull requests

3 participants