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

[discussion] Duplicate job name question #168

Closed
owen95t opened this issue Mar 22, 2022 · 4 comments
Closed

[discussion] Duplicate job name question #168

owen95t opened this issue Mar 22, 2022 · 4 comments
Labels
question Further information is requested

Comments

@owen95t
Copy link

owen95t commented Mar 22, 2022

What would you like to discuss?

After a certain job is ran and successfully exits, when I try to create a new job with the same name, it is telling me that a job with that name already exists. How can that be? I may be missing something?

Checklist

  • [ √] I have read the documentation.
@owen95t owen95t added the question Further information is requested label Mar 22, 2022
@shadowgate15
Copy link
Member

After a job is run the job is not deleted, only the worker. You could use bree.remove followed by bree.add or just modify bree.configs.jobs and then call bree.start. I would suggest using the first option as bree.add will validate the job.

@shadowgate15
Copy link
Member

#169

When I have time I'll add this function which would make this process easier.

@owen95t
Copy link
Author

owen95t commented Mar 23, 2022

After a job is run the job is not deleted, only the worker. You could use bree.remove followed by bree.add or just modify bree.configs.jobs and then call bree.start. I would suggest using the first option as bree.add will validate the job.

I see. Thanks I'll use bree.remove for now. But it seems that Bree caches these names as well as it seems to persist. I have no idea what names exists in the cache so is there a location to clear such cache? Or can I just reinstall bree.

@shadowgate15
Copy link
Member

shadowgate15 commented Mar 23, 2022

Bree doesn't do any caching. It is just scanning the bree.configs.jobs[].name. You should be able to call bree.config.jobs.map((j) => j.name) to get the list.

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

No branches or pull requests

2 participants