stronk7

Untitled

Jan 3rd, 2023
77
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.16 KB | None | 0 0
  1. Andrew Lyons
  2. Unrelated, can we please discuss MDL-74833 and MDL-74835?
  3.  
  4. I think that we should just drop support for Travis. We do not test with it any more, so it's just going to be a pain to maintain.
  5.  
  6. Kevin Bot
  7. MDL-74833 - Update travis integration from bionic (18.04) to focal (20.04)
  8. Status: Waiting for peer review
  9. Reporter: Daniel Ziegenberg
  10. Assignee: Daniel Ziegenberg
  11. MDL-74835 - Update nodejs version in travis integration to lts/gallium
  12. Status: Waiting for integration review
  13. Reporter: Daniel Ziegenberg
  14. Assignee: Daniel Ziegenberg
  15.  
  16. ...
  17. ...
  18.  
  19. Jun Pataleta
  20. I think that we should just drop support for Travis. We do not test with it any more, so it's just going to be a pain to maintain.
  21.  
  22. If we're dropping travis support, are we gonna drop it for all security and stable branches?
  23. If so, then it doesn't make sense to spend time updating .travis.yml
  24. But if dropping Travis support will only be for master then maybe we can entertain the patch for 74835
  25. I'm okay too with dropping Travis. I think Eloy still uses it though but not sure
  26. Kevin Bot
  27.  
  28. ...
  29. ...
  30.  
  31. Eloy Lafuente (stronk7)
  32. About Travis we (HQ, also me, personal) have paid accounts. Not all products have moved away from it yet.
  33.  
  34. And, more precisely for core, I only use the integration to:
  35.  
  36. Verify it continues working (when I submit a patch).
  37. Run weekly windows runs (39_STABLE and up). But already have moved those to GHA.
  38. So, with my/our only use being 1) we certainly don't need it in core (again, we need it in some suproducts).
  39.  
  40. What I'm not sure is if people out there will be using it or no, because certainly it just works.
  41.  
  42. Andrew Lyons
  43. Well does it just work..?
  44.  
  45.  
  46. Eloy Lafuente (stronk7)
  47. I think so. One time every few months we have to update it with this or that detail, but I'd not say it's a nightmare to maintain.
  48.  
  49. I mean, the runs I get from my branches work ok:
  50.  
  51. https://app.travis-ci.com/github/stronk7/moodle/branches
  52.  
  53. The point, as commented, is if there are people out there using it with complex plugin aggregations or things like that. But, if that happens, surely they will be using custom .travis file already, heh.
  54.  
  55. So I don't oppose to remove it from 4.1 and up.
Advertisement
Add Comment
Please, Sign In to add comment