Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tower.yml entry to better control job statuses #69

Open
3 tasks
gwright99 opened this issue Jun 10, 2024 · 2 comments
Open
3 tasks

Add tower.yml entry to better control job statuses #69

gwright99 opened this issue Jun 10, 2024 · 2 comments

Comments

@gwright99
Copy link
Collaborator

gwright99 commented Jun 10, 2024

As per https://support.seqera.io/helpdesk/tickets/5093, the Seqera Platform (Enterprise) exposes configuration values to control how job statuses are displayed in the Runs screen.

Config Snippet

# Sources (Seqera Platform ): 
#  - WorkflowWatchdogJob.groovy
#  - ReconcileProgressJob.groovy

# tower.yml
tower:
  cron:
    watchdog:
      delay: 5s
      interval: 1m
      expire: 190s
      zombie: 1d
    progress-stats:
      delay: 10s
      interval: 1m
      enabled: true

To Do:

  1. Clarify behaviour based on information @swampie shared with client June 10/24 prior to addition into project.
  2. Once clarification occurs:
    1. Add snippet in tower.yml.tpl
@gwright99 gwright99 changed the title Add tower.yml entry to better control Add tower.yml entry to better control job statuses Jun 10, 2024
@pditommaso
Copy link

Much better to keep aligned with default values

@gwright99
Copy link
Collaborator Author

gwright99 commented Jun 10, 2024

Much better to keep aligned with default values

Hit 'save' too early (fixed). My intention was to make these explicit in the tower.yml but not directly configurable from the terraform.tfvars file. This way, sites can choose to tweak if necessary (e.g. they may decide that a zombie should be declared after x hours rather than 24h, or that they want to wait a bit longer before a run is considered expired) but they'll have the defaults OOTB.

I won't add anything into the template file until I have really solid documentation and guidance to precede it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants