Update README.md

This commit is contained in:
Alexander Stefanov 2019-02-04 17:01:25 +03:00 committed by GitHub
parent 4eccac4371
commit c990e8facf
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions

View File

@ -31,3 +31,8 @@ ABFUI container that's responsible for the web interface and API that workers us
Sidekiq is a ruby library that is a background job executor. It uses redis to store job information. Sidekiq is a ruby library that is a background job executor. It uses redis to store job information.
Some stuff can't just run in the web interface code, stuff like mass build creation for example. You need to create a lot of build lists which takes time, so it's not practical to put it into the web interface itself. Some stuff can't just run in the web interface code, stuff like mass build creation for example. You need to create a lot of build lists which takes time, so it's not practical to put it into the web interface itself.
Our sidekiq executes jobs like creating mass builds, or changing build list statuses. When a builder sends feedback a job gets scheduled and processed by our main sidekiq container changing status of a build list and updating files if there are any. Publisher and ISO builder are both sidekiq workers too that run 1 job: publishing and product building respectivly. Postgresql container is our main database(well that should be obvious :)) Our sidekiq executes jobs like creating mass builds, or changing build list statuses. When a builder sends feedback a job gets scheduled and processed by our main sidekiq container changing status of a build list and updating files if there are any. Publisher and ISO builder are both sidekiq workers too that run 1 job: publishing and product building respectivly. Postgresql container is our main database(well that should be obvious :))
How to kill stucked builds
```BuildList.where(id: [362471, 362473]).destroy_all```