9400eedc06
* 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
22 lines
497 B
YAML
22 lines
497 B
YAML
---
|
|
name: Trigger 4testing rebuild
|
|
|
|
run-name: "Weekly 4testing rebuild trigger"
|
|
|
|
on:
|
|
schedule:
|
|
# Run every Saturday at 10 p.m.
|
|
- cron: '00 22 * * 6'
|
|
|
|
jobs:
|
|
trigger-rebuild:
|
|
name: "trigget-rebuild"
|
|
runs-on: "ubuntu-latest"
|
|
steps:
|
|
- name: Rebuild 4testing manualy
|
|
env:
|
|
GITHUB_TOKEN: ${{ secrets.TOKEN }}
|
|
run: |
|
|
gh workflow run rebuild.yml \
|
|
--repo ONLYOFFICE/Docker-DocumentServer \
|
|
-f repo=4test
|