Hi, On 09/07/2015 01:20 PM, Antoine Musso wrote: > Jenkins jobs start failing on some repositories release branches because > they are lacking the CI [entry points]. For example if the 'npm' job > has been enabled, the master branch has a 'package.json' but the release > branches do not. That causes CI to reject backports.
Another idea I've been thinking about is making the "npm" and "composer-test" jobs pass if no package.json/composer.json is present. In addition to fixing the release branch issue, it also would allow us to make CI/zuul more self-service. We could enable those jobs for all repos, and people could add npm/composer tests and immediately get feedback and start using them, without having to wait for someone to update the zuul config. > The commands being run would need be tweaked but at the very minimal > each branches should check: > > * the i18n files using grunt-banana-checker (in package.json) > * php lint (jakub-onderka/php-parallel-lint) (in composer.json) phplint should be doable, but not all branches may pass banana-checker. Many repositories still don't pass, and many more have only recently begun to pass (see blockers on [1]). [1] https://phabricator.wikimedia.org/T94547 -- Legoktm _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
