Maciej Gol

Have you tried using always eager celery during your tests? wt., 2 sie 2022, 20:46 użytkownik Michael You ***@***.***> napisał: > I get this message from tenant_schemas_celery > > >...

Its because your tests are running in a database transaction. In order for your tasks to see the results of your tests, you need to commit it or enable always...

Its because your tests are running in a database transaction. In order for your tasks to see the results of your tests, you need to commit it or enable always...

Have you guys looked into a shared database as storage? For example, local redis or memcached? Their semantics when it comes to missing values align with Prometheus' (new/expired initializes to...

Why joining on the `gitlab_ci_pipeline_id` is not sufficient? You can lookup how it works in the example dashboards.

I understand your issue, as I'm facing it, too. Having said that I don't believe adding labels will solve it (on its' own). Why? You can already figure out what...

Since I've been working quite a lot with Gitlab here at Codility, I've started to use GCI in place of Gitlab CI, as it gets tiresome writing the full name...

@ErezArbell since your use-case is monitoring general ratio of successes of your jobs (per ref, perhaps), I believe implementing job hooks to simply store success/failures counters would be enough, without...

you mean it is impossible to have periodic tasks stored in the database, on a per-tenant basis?

Do you have the periodic tasks inserted dynamically into the DB, or are they sourced from your source code?