run heroku tests on detection from title OR schedule

[madhur-tandon]

No description provided.

[codecov]

Codecov Report

Base: 87.81% // Head: 84.81% // Decreases project coverage by -2.99% ⚠️

Coverage data is based on head (03e92cf) compared to base (663862f).
Patch has no changes to coverable lines.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #433      +/-   ##
==========================================
- Coverage   87.81%   84.81%   -3.00%     
==========================================
  Files          96       96              
  Lines        7909     7804     -105     
==========================================
- Hits         6945     6619     -326     
- Misses        964     1185     +221     

Impacted Files	Coverage Δ
mlem/contrib/rabbitmq.py	48.05% <0.00%> (-50.67%)	⬇️
mlem/contrib/kubernetes/utils.py	21.05% <0.00%> (-42.11%)	⬇️
mlem/contrib/kubernetes/base.py	44.08% <0.00%> (-39.79%)	⬇️
mlem/contrib/docker/base.py	57.50% <0.00%> (-30.13%)	⬇️
mlem/contrib/kubernetes/build.py	70.00% <0.00%> (-30.00%)	⬇️
mlem/contrib/docker/utils.py	58.82% <0.00%> (-24.68%)	⬇️
mlem/contrib/kubernetes/service.py	41.37% <0.00%> (-10.35%)	⬇️
mlem/utils/fslock.py	88.05% <0.00%> (-3.49%)	⬇️
mlem/contrib/venv.py	86.13% <0.00%> (-2.98%)	⬇️
mlem/cli/dev.py	47.36% <0.00%> (-2.64%)	⬇️
... and 34 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[aguschin]

Good work! Trying to understand how this should work. Will it require commit hash when one tries to run the tests manually? Also, can I test it out in this branch before merging to main?

UPD: I just did a commit assuming it will ask me for input (commit hash), but looks like this works differently.

[aguschin]

@madhur-tandon could use your help here to understand this ^ :)

[madhur-tandon]

@madhur-tandon could use your help here to understand this ^ :)

Earlier, I was using something known as a workflow dispatch -- i.e. you need to trigger an action manually.
But now, I have switched to detection of the keyword heroku in title of the PR

[madhur-tandon]

The PRs #457 and #458 confirm that this works 😄

[aguschin]

Looking good! Thanks @madhur-tandon!

I remember we had a discussion about doing the same for k8s/sagemaker. Don't remember the resolution. Should we do this for them also?

[madhur-tandon]

I remember we had a discussion about doing the same for k8s/sagemaker. Don't remember the resolution. Should we do this for them also?

K8s test are self contained, won't be necessary.
@mike0sv can comment on Sagemaker maybe.

[aguschin]

K8s test are self contained, won't be necessary.

how much time do they take? Speeding up CI would be a good thing also.

[madhur-tandon]

how much time do they take? Speeding up CI would be a good thing also.

The point of this PR was not to speed up CI, it was to control flaky behaviour of heroku so we don't get unnecessary failures.