[buddypress-trac] [BuddyPress Trac] #6726: Run Grunt build tasks in Travis
buddypress-trac
noreply at wordpress.org
Sat May 14 06:40:17 UTC 2016
#6726: Run Grunt build tasks in Travis
-----------------------------------+------------------
Reporter: netweb | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: 2.6
Component: Tools - Build Process | Version:
Severity: normal | Resolution:
Keywords: needs-refresh |
-----------------------------------+------------------
Comment (by netweb):
Replying to [comment:13 boonebgorges]:
> @netweb Sorry to be dense - can you explain what
[attachment:6726.1.diff] does?
Sure
> Is this meant to be a patch for our trunk `.travis.yml`?
Yes
> It looks like it runs a single `grunt build` job to every build. Is that
right?
Incorrect, the [attachment:6726.1.diff] patch adds 1 extra job to the
build matrix to run a PHP 7 job that runs `grunt build` once
It is not part of any of the existing jobs, the existing jobs remain
unchanged and will continue to perform exactly as they currently do.
> Or is this meant to describe the once-daily matrix?
No
> I'm getting a bit bleary-eyed at the double- and triple-negatives in the
matrix definition :)
The patch [attachment:6726.2.diff] is only a refresh of
[attachment:6726.1.diff] but probably still doesn't make a whole lot of
sense, the two key pieces are adding Travis environment variables
`BP_TRAVISCI=travis:grunt` and `BP_TRAVISCI=travis:phpunit` to either the
Grunt or PHPUnit Travis CI jobs, each job is then passed these environment
variables and ran via `script: grunt $BP_TRAVISCI` for each type of job
Currently there are 34 jobs per Travis CI build plus an additional job for
PHP7 Nightly totalling 35 jobs per build
* https://travis-ci.org/ntwb/BuddyPress/builds/130173785
Using [attachment:6726.2.diff] an extra job [https://travis-
ci.org/ntwb/BuddyPress/jobs/130175543 50.36] is added to the build matrix
taking the total to 36 jobs per build.
* https://travis-ci.org/ntwb/BuddyPress/builds/130175507
The primary purpose of adding this job per the original Slack chat was to
provide a way to pickup utilising Travis CI for any potential failures
running the primary Grunt tasks. Previously the existing tasks only ran
`grunt travis:phpunit` which in turn runs each of these grunt tasks:
`grunt jsvalidate:src`, `grunt jshint`, `grunt checktextdomain`, `grunt
test`, the "main" Grunt task `grunt build` was previously never ran within
Travis CI.
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6726#comment:14>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac
More information about the buddypress-trac
mailing list