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

[cli] graceful stop should work with any system state #4063

Merged
merged 1 commit into from
Feb 9, 2017
Merged

Conversation

benoitf
Copy link
Contributor

@benoitf benoitf commented Feb 8, 2017

What does this PR do?

cli graceful stop should work with any system state
until now it was expecting remote state was RUNNING.

Now if state is:

  • RUNNING -> call stop and wait for system to be in READY_TO_SHUTDOWN state
  • READY_TO_SHUTDOWN -> do nothing(maybe print something useful)
  • ANY_OTHER_STATE -> wait for system to be in READY_TO_SHUTDOWN state

What issues does this PR fix or reference?

#3988

Changelog

[cli] graceful stop work with any remote system state

Release Notes

N/A

Docs PR

N/A

Change-Id: I55a8b5ecb2b016d31dbbd95b8793af4952d8116b
Signed-off-by: Florent BENOIT fbenoit@codenvy.com

  - RUNNING -> call stop and wait for system to be in READY_TO_SHUTDOWN state
  - READY_TO_SHUTDOWN -> do nothing(maybe print something useful)
  - ANY_OTHER_STATE -> wait for system to be in READY_TO_SHUTDOWN state

Change-Id: I55a8b5ecb2b016d31dbbd95b8793af4952d8116b
Signed-off-by: Florent BENOIT <fbenoit@codenvy.com>
@benoitf benoitf added kind/bug Outline of a bug - must adhere to the bug report template. status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. labels Feb 8, 2017
@benoitf benoitf self-assigned this Feb 8, 2017
Copy link
Contributor

@JamesDrummond JamesDrummond left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approval of changelog and release notes.

@TylerJewell
Copy link

@JamesDrummond - on anything related to CLI, you can skip over. I'll be responsible for changelog and release notes.

@benoitf - do you have some various sample outputs that you can share? I think we need to update the release notes to be more explanatory. They need full paragraphs and maybe an example or two.

@codenvy-ci
Copy link

Build # 1912 - FAILED

Please check console output at https://ci.codenvycorp.com/job/che-pullrequests-build/1912/ to view the results.

@benoitf
Copy link
Contributor Author

benoitf commented Feb 8, 2017

@TylerJewell well the output is the same in all cases. It's just that now we handle cases where remote system is not in running state. But for 99% of ppl there is also no change as it's the default case. Other cases only happen if rest API is called by something else than cli

@benoitf benoitf merged commit 5c7e9a9 into master Feb 9, 2017
@benoitf benoitf deleted the che#3988 branch February 9, 2017 07:03
@benoitf benoitf added this to the 5.3.0 milestone Feb 9, 2017
@benoitf benoitf removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Feb 9, 2017
@JamesDrummond JamesDrummond mentioned this pull request Feb 17, 2017
9 tasks
JPinkney pushed a commit to JPinkney/che that referenced this pull request Aug 17, 2017
eclipse-che#4063)

- RUNNING -> call stop and wait for system to be in READY_TO_SHUTDOWN state
  - READY_TO_SHUTDOWN -> do nothing(maybe print something useful)
  - ANY_OTHER_STATE -> wait for system to be in READY_TO_SHUTDOWN state

Change-Id: I55a8b5ecb2b016d31dbbd95b8793af4952d8116b
Signed-off-by: Florent BENOIT <fbenoit@codenvy.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants