Docker-DocumentServer/.github/workflows
Danil Titarenko 9400eedc06
Add auto rebuild previous releases
* Add the ability to rebuild images

Rebuilding images will be done manually (for now). The choice of the number of rebuilt releases is available (1 by default), the choice of repositories for pushing rebuilt images is available (4testing by default).

Principle of operation:
Through the api of the docker hub, we get the last launched tag that falls under the pattern x.x.x.1, after that the tag with the assembly of which the minor tag x.x will be sent will be calculated. Next, at one of the build steps, the number of the previous release will be received, for example x. x.x.4 which will mean that the current one will be x.x.x.5

* Add login to dockerhub

* Refactoring code

Set some variables for all rebuild-info job. Also set default values for repository and quantity variables

* Refactor: remove push trigger

* Refactoring code

* Refactor: Unlinking a version

* Submitting the latest tag for the latest release only
2023-06-29 14:50:17 +05:00
..
4testing-build.yml Fix deprecated set-output (#632) 2023-05-24 13:51:14 +05:00
cron-rebuild-trigger.yml Add auto rebuild previous releases 2023-06-29 14:50:17 +05:00
rebuild.yml Add auto rebuild previous releases 2023-06-29 14:50:17 +05:00
stable-build.yml Add new stable images versioning principles (#633) 2023-05-25 18:36:33 +05:00