@hashar, rake sounds good to me. @dduvall, what do you think?

From a 1/1 with Zeljko, Dan and Zeljko will look at it during the Wikimania hackathon.

We will also need the ruby entry point to be documented at https://www.mediawiki.org/wiki/Continuous_integration/Entry_points#Ruby and add related JJB job templates :)

What is the status of this task, now that Wikimania 2015 is over? Did this hacking project take place and was successfully finished? If yes: Please provide an update and potentially summarize findings / provide a link to anything relevant (and if the task is not completely finished yet, please move the project to the "Work continues after Mexico City" column on the Wikimania-Hackathon-2015 workboard). If no: Please edit this task by removing the Wikimania-Hackathon-2015 project from this task. Thanks for your help and keeping this task updated!

From a discussion between @dduvall and @zeljkofilipin during the Mexico hackathon, introducing rake as an entry point would cause developers to learn yet another tool.

Instead Dan suggested to move to make which is pretty standard and let developers reuse whatever they want as the actual ruby runner.

That also leverage the possibilities to migrate all the other entry points such as npm/tox/composer to be unified as simply make test.

A potential issue is we still need to pass some specific settings for caching packages. Something to investigate later on.

Another possibility would be to reuse the npm entry point to run the ruby commands. So in npm package.json we could add a grunt task to run bundle exec rubocop.

That is similar to a proposal I made back in February to generate documentations and having a single entry point make docs. We will probably want to write a short RFC to have agreement from all devs.

A message to all open tasks related to the Wikimania-Hackathon-2015. What do you need to complete this task? Do you need support from the Wikimedia Foundation to push it forward? Help promoting this project? Finding an intern to work on it? Organizing a developer sprint? Pitching it to WMF teams? Applying for a grant? If you need support, share your request at T107423: Evaluate which projects showcased at the Wikimania Hackathon 2015 should be supported further or contact me personally. Thank you!

@dduvall and @zeljkofilipin any clues?

From our weekly triages, we can use rake. Dan proposed to namespace the entry point with a ci:: prefix to let us split local / CI tests.

So we would end up with something like:

rake test
rake ci::test

Note, it is possible to detect whether rake test is running in Jenkins by looking at a Jenkins environment variable. tox looks for JENKINS_URL.

tox doc: https://testrun.org/tox/latest/config.html#tox-global-settings

Change 246194 had a related patch set uploaded (by Hashar):
Run various commands via rake in the bundler env

https://gerrit.wikimedia.org/r/246194

We gave it a try on mediawiki/vagrant and that seems to play well.

I proposed a similar change to mediawiki/selenium https://gerrit.wikimedia.org/r/246253 . The Rakefile has:

# pre-flight
require 'rubygems'
require 'bundler/setup'

require 'rspec/core/rake_task'
require 'rubocop/rake_task'
require 'yard'

RSpec::Core::RakeTask.new(:spec)
RuboCop::RakeTask.new(:rubocop)
YARD::Rake::YardocTask.new(:yard)

task default: [:test]

desc 'Run all build/tests commands (CI entry point)'
task test: [:rubocop, :spec, :yard]

desc 'Generate all documentations'
task doc: [:yard]

Doc:

$ rake -T
rake doc                   # Generate all documentations
rake rubocop               # Run RuboCop
rake rubocop:auto_correct  # Auto-correct RuboCop offenses
rake spec                  # Run RSpec code examples
rake test                  # Run all build/tests commands (CI entry point)
rake yard                  # Generate YARD Documentation

Change 246194 merged by jenkins-bot:
Run various commands via rake in the bundler env

https://gerrit.wikimedia.org/r/246194