Uploaded image for project: 'Moodle Community Sites'
  1. Moodle Community Sites
  2. MDLSITE-3874

Move from shifter to grunt on master CI jobs


    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Low Low
    • Integration
    • None

      Right now we are running the "06. Run shifter for all modules" job in all branches. It basically does:

      1) self-install shifter with a given version.
      2) run it for all yui modules.
      3) compare results with committed contents to verify that everything is on sync.

      Note it ignores jshint lint warnings and friends, that's out from the job achievements.

      With Moodle 2.9 we are replacing shifter by grunt, in order to be able to build both yui modules (will continue using shifter internally) and amd modules (will use uglifyjs).

      So this is about to implement a new job "06. Run grunt for all modules" that will replace current one only processing yui modules. To be applied to 2.9 and upwards. Same behavior that the described above.


            stronk7 Eloy Lafuente (stronk7)
            stronk7 Eloy Lafuente (stronk7)
            0 Vote for this issue
            2 Start watching this issue


                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.