Add a CI job that is explicitly for "run with latest version of dependencies" #4021

Open
opened 2023-04-28 17:46:51 +00:00 by exarkun · 0 comments
exarkun commented 2023-04-28 17:46:51 +00:00
Owner
  • It should run on a schedule, not as part of normal PR workflow.
  • It should be clearly marked as the "latest version" job so failures from it are more easily interpreted.
  • Its results should go somewhere so they're not overlooked (as surely will be the default outcome if they're not part of the normal PR workflow).
  • It should obey constraints in our metadata (so if we rule out a new version intentionally, we don't get it).
  • It should have a lot of retries so it doesn't fail because of a network error downloading new packages or a pypi API hiccup.
* It should run on a schedule, not as part of normal PR workflow. * It should be clearly marked as the "latest version" job so failures from it are more easily interpreted. * Its results should go *somewhere* so they're not overlooked (as surely will be the default outcome if they're not part of the normal PR workflow). * It should obey constraints in our metadata (so if we rule _out_ a new version intentionally, we don't get it). * It should have a lot of retries so it doesn't fail because of a network error downloading new packages or a pypi API hiccup.
tahoe-lafs added the
unknown
normal
defect
n/a
labels 2023-04-28 17:46:51 +00:00
tahoe-lafs added this to the undecided milestone 2023-04-28 17:46:51 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#4021
No description provided.