Sergii Kabashniuk
f4cc97acce
Set next version 6.0.0-M1-SNAPSHOT
2017-10-19 13:53:40 +03:00
Roman Iuvshyn
abe3271908
RELEASE: Set next development version ( #6692 )
...
* RELEASE: Set next development version
2017-10-14 20:17:04 +03:00
Roman Iuvshyn
8e03d56bfb
RELEASE: Set next development version ( #6345 )
2017-09-19 14:52:53 +03:00
Roman Iuvshyn
2850a74a11
RELEASE: Set next development version ( #6067 )
2017-08-23 11:11:34 +03:00
Sergii Kabashniuk
5b373e6cf5
Used Google Java Codestyle ( #5851 )
2017-08-18 17:00:58 +03:00
Mykhailo Kuznietsov
69d5148385
Changed copyright owner to "Red Hat, Inc." in license headers ( #5964 )
...
Change license header contributor to Red Hat, Inc.
2017-08-11 10:46:58 +03:00
Roman Iuvshyn
c2eb3188c1
RELEASE: Set next development version ( #5949 )
2017-08-09 11:17:20 +03:00
Roman Iuvshyn
185273f8b9
RELEASE: Set next development version ( #5734 )
...
* RELEASE: Set next development version
2017-07-19 12:45:32 +03:00
Roman Iuvshin
eab04ddd6b
RELEASE: Set next development version
2017-06-29 07:59:05 +00:00
Roman Iuvshin
513aa19ebd
RELEASE: Set next development version
2017-06-21 13:04:16 +00:00
Roman Iuvshin
eb2fa0eeed
RELEASE: Set next development version
2017-06-14 07:13:04 +00:00
Roman Iuvshin
9fbf173eb9
RELEASE: Set next development version
2017-05-24 07:30:41 +00:00
Roman Iuvshin
b3ae33acf5
RELEASE: Set next development version
2017-05-10 10:54:42 +00:00
Roman Iuvshin
6d88cf8c73
[maven-release-plugin] prepare for next development iteration
2017-04-25 18:19:17 +00:00
Roman Iuvshin
d7f023fd89
[maven-release-plugin] prepare release 5.9.0
2017-04-25 18:19:10 +00:00
Roman Iuvshin
7805c146e6
[maven-release-plugin] prepare for next development iteration
2017-04-13 11:07:13 +00:00
Roman Iuvshin
e8107fd96c
[maven-release-plugin] prepare release 5.8.0
2017-04-13 11:07:06 +00:00
Roman Iuvshin
840ae853f8
Revert "RELEASE: set minor change version"
...
This reverts commit e23b9257a3 .
2017-04-11 20:55:24 +03:00
Roman Iuvshin
e23b9257a3
RELEASE: set minor change version
2017-04-11 18:10:45 +03:00
Roman Iuvshin
08d4d0f25c
[maven-release-plugin] prepare for next development iteration
2017-04-06 14:28:39 +00:00
Roman Iuvshin
53a0325213
[maven-release-plugin] prepare release 5.7.0
2017-04-06 14:28:33 +00:00
Roman Iuvshin
342f103654
[maven-release-plugin] prepare for next development iteration
2017-03-30 12:25:35 +00:00
Roman Iuvshin
e6e4a652cc
[maven-release-plugin] prepare release 5.6.0
2017-03-30 12:25:28 +00:00
Roman Iuvshin
e7588aa2b3
[maven-release-plugin] prepare for next development iteration
2017-03-15 14:59:35 +00:00
Roman Iuvshin
69cf9f5528
[maven-release-plugin] prepare release 5.5.0
2017-03-15 14:59:28 +00:00
Roman Iuvshin
ceff3938ff
[maven-release-plugin] prepare for next development iteration
2017-03-02 18:33:12 +00:00
Roman Iuvshin
8ed6e10476
[maven-release-plugin] prepare release 5.4.0
2017-03-02 18:33:06 +00:00
Roman Iuvshin
e71c7b5671
[maven-release-plugin] prepare for next development iteration
2017-02-17 11:04:07 +00:00
Roman Iuvshin
c071c65aa2
[maven-release-plugin] prepare release 5.3.0
2017-02-17 11:03:59 +00:00
Yevhenii Voevodin
f2bcdfb596
Adds system graceful stop tracking events
...
3 new events are added, they are:
* STOPPING_SERVICE - published before service is stopped
* SERVICE_ITEM_STOPPED - published each time service item(like workspace) is stopped
* SERVICE_STOPPED - published after service is stopped
2017-02-07 16:52:20 +02:00
Roman Iuvshin
0dd0dea686
[maven-release-plugin] prepare for next development iteration
2017-02-01 13:31:32 +00:00
Roman Iuvshin
d138c3623f
[maven-release-plugin] prepare release 5.2.0
2017-02-01 13:31:25 +00:00
Yevhenii Voevodin
9effc0716f
Add system service that allows to prepare system to shutdown ( #3917 )
...
Resolves #3892 .
Two API methods are available:
* _POST /api/system/stop_ - stops corresponding system services, for now it's workspace service.
Basically it stops all the RUNNING workspaces snapshotting them before if configured to do so,
also it interrupts start of currently STARTING workspaces.
* _GET /api/system/state_ - returns current system state(only status for now).
By default system status is RUNNING, but after stop is called or che server is
stopped directly system status is changed like the following:
```
RUNNING -> PREPARING_TO_SHUTDOWN -> READY_TO_SHUTDOWN
```
Status changes are followed by status changed events, to recieve these
events client has to subscribe on *system:state* channel.
So client can use different ways to track system status changes.
Doesn't matter whether API method is used or che server is stopped directly,
events will be sent anyway.
2017-01-30 17:58:57 +02:00