#8989 add queued and running as additional supported outcomes to resultsdb
Opened 4 months ago by bgoncalv. Modified 7 days ago

CI pipelines can send queued and running topics, it would be nice if resultsdb could store them so they are show in bodhi.

This is related to https://pagure.io/fedora-ci/general/issue/103

To add this support, it looks like https://infrastructure.fedoraproject.org/infra/ansible/roles/taskotron/resultsdb-backend/templates/settings.py.j2 needs to be updated.


Metadata Update from @mohanboddu:
- Issue tagged with: groomed, high-trouble, medium-gain

4 months ago

Metadata Update from @smooge:
- Issue priority set to: Waiting on External (was: Needs Review)

4 months ago

Note that we are waiting for an upstream to be set up and working before we change things so that we do not fork/break their work.

@smooge hi, this is a major user annoyance, could we make this work pls?

The change here should be just a change in configuration, we use it in downstream for years.

Metadata Update from @smooge:
- Issue untagged with: groomed
- Issue priority set to: Needs Review (was: Waiting on External)

7 days ago

Metadata Update from @pingou:
- Issue priority set to: Waiting on External (was: Needs Review)

7 days ago

Login to comment on this ticket.

Metadata
Related Pull Requests
  • #116 Last updated 2 months ago