This issue is to discuss the way forward for Rules testing. Previously development and testing were primarily done on Github using Fago's repository https://github.com/fago/rules with testing on Travis https://travis-ci.org/fago/rules/branches

However, fago can no longer maintain the Github repository and it is now very out of date. The question is: Do we want a new Github repository where primary development and testing takes place, and continue as before? Or do we abandon Github and do all testing on Drupal.org? Do the benefits of Github/Travis outweigh the disadvantages?

This is a spin-off from #3079297: .travis.yml build needs mysql service which has prompted this bigger question.

Comments

jonathan1055 created an issue. See original summary.

tr’s picture

tr commented

No, I do not want to use a GitHub workflow. That hasn't been used at all for this project for 1.5 to 2 years, and is not practical to use since the github project owner is not participating.

Additionally, this puts additional barriers to contribution, and we already have enough of a problem with getting anyone to help. Moving projects to GitHub weakens the Drupal community.

I've mentioned this in more detail many times since I became a maintainer of this project.

So I don't see that it has any advantages, and it definitely has disadvantages. Plus, since I'm the one doing all the work and I don't want to use a GitHub workflow with Travis testing, it's sort of a moot point ...

jonathan1055’s picture

jonathan1055 commented
Status: Active » Closed (works as designed)

OK, that's fine. I wasn't trying to say we should use it, I just wanted to have the discussion. I did search for github on the issue queue and it was not mentioned in any subject titles. Maybe I should have delved deeper into some of the issue detail. I'm happy that it is concentrated on drupal.org.

However, I do like having the ability to do my own testing of Rules changes on Travis, so I will discard my fork of Fago/Rules and make a new one with the primary source repository being that on d.o. I find the flexiblity of the test matrix (php version x core version) very useful. Also you get early warnings of deprecated code using the Travis environment which I have not seen replicated on d.o. (even with suppress-deprecations: false in drupalci.yml

Thanks for your maintainership of Rules. Sorry if I twanged a nerve, I did not mean to!

Jonathan