I prefer the freedom, why restrict as long as it benefits the project and does not create any hindrance?
The reason for configuration-as-code to have both GitHub actions, Travis and ci.jenkins.io because we have experienced issues with both ci.jenkins.io and travis, so useful to being able to rely on more than one system. On Friday, October 4, 2019 at 4:53:24 PM UTC+2, Victor Martinez wrote: > > I've seen some repos already using GitHub actions, Travis and some others > tools, which from a collaborator point of view doesn't look easy to follow > up what GitHub checks are valuable. > > I'd prefer to avoid using GitHub actions as much as possible for the > benefit of a more stable ci.jenkins.io and encourage people to use it as > much as possible though. > > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4a6e471f-c3dd-43d6-abd9-22c381a0fce2%40googlegroups.com.
