Hello, We are migrating Jenkins jobs to simply invokes [test entry points] (ex: composer test, npm test).
Some repositories have documentation generated by Jenkins and pushed under https://doc.wikimedia.org/ . I would like to make it as trivial as possible for developers to configure Jenkins, hence I am looking to establish a convention to generate doc. We would need: - a single command we agree on (ex: make doc) - a way to pass/override the destination directory so the jobs in Jenkins can enforce the output where it expects it I have filled https://phabricator.wikimedia.org/T88999 for it. Discussions on wikitech-l preferred. If there is no objections by next week. I will define the convention to be 'make docs' and create all the needed Jenkins jobs templates. Thanks! [test entry points] https://www.mediawiki.org/wiki/Continuous_integration/Test_entry_points -- Antoine "hashar" Musso _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
