Skip to content

Add scheduled runs of MQTT workflows #408

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

embhorn
Copy link
Member

@embhorn embhorn commented Nov 11, 2024

No description provided.

@bandi13
Copy link
Contributor

bandi13 commented Nov 12, 2024

The only trouble I have with this, is that it's not going to be seen by anyone. It would be better to have a single job that triggers the tests so that at least the information is consolidated in one place. Then ultimately that one job could send e-mails in case there is a failure.

@gojimmypi gojimmypi assigned embhorn and unassigned bandi13 Apr 6, 2025
@gojimmypi gojimmypi requested review from philljj and removed request for bandi13 April 6, 2025 15:35
@gojimmypi
Copy link
Contributor

Hi @embhorn - what's the objective here?

Recently in wolfSSL/wolfssl-examples#499 I added a new arduino.yml workflow. The thing is: being in wolfssl-examples , I actually want to run it when examples change locally, or, even more importantly, changes are made in the wolfssl repo. I too had considered scheduled task.

Instead, I'm considering workflow_dispatch. Do you think that might work here for MQTT as well?

@gojimmypi gojimmypi self-assigned this Apr 6, 2025
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

Successfully merging this pull request may close these issues.

3 participants