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

Jobs may need to run just once #120

Open
gemblerz opened this issue Feb 26, 2024 · 0 comments
Open

Jobs may need to run just once #120

gemblerz opened this issue Feb 26, 2024 · 0 comments
Assignees

Comments

@gemblerz
Copy link
Collaborator

The science rules are designed to support recurring executions of application. In some cases, applications in a job need to run just once and "completes," I think most of them would be for testing purposes.

We can think of 2 cases: do this at either plugin level or job level. For example,

scienceRules:
- schedule("myprogram", once=True): True

The once=True can let the scheduler not to schedule "myprogram" once it ran and completes. However, the scheduler may "forget" the fact that it ran the program because it may have limited memory.

In the second case,

successCriteria:
- Once("myprogram")

The Once in the success criteria will let the scheduler know that it can drop the job after a completion of myprogram. However, it is unsure how we can apply this for multiple plugins in a job. If plugins run at different times, the scheduler still has the problem of memorizing.

@gemblerz gemblerz self-assigned this Feb 26, 2024
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

1 participant