From 82d5c5ea421b50066dce1d80f570486473a59add Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Est=C3=A8ve?= Date: Mon, 13 Nov 2017 09:42:24 +0100 Subject: [PATCH 1/3] DOC add documentation about Travis cron job --- doc/developers/maintainer.rst | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/doc/developers/maintainer.rst b/doc/developers/maintainer.rst index ff639d55009ba..2e2874b0fb60d 100644 --- a/doc/developers/maintainer.rst +++ b/doc/developers/maintainer.rst @@ -55,3 +55,27 @@ Making a release 7. FOR FINAL RELEASE: Update the release date in What's New + +Travis Cron jobs +---------------- + +From ``_: Travis CI cron jobs work +similarly to the cron utility, they run builds at regular scheduled intervals +independently of whether any commits were pushed to the repository. Cron jobs +always fetch the most recent commit on a particular branch and build the project +at that state. Cron jobs can run daily, weekly or monthly, which in practice +means up to an hour after the selected time span, and you cannot set them to run +at a specific time. + +For scikit-learn, Cron jobs are used for builds that we do not want to run in +each PR. As an example the build with the dev versions of numpy and scipy is +run as a Cron job. Most of the time when this numpy-dev build fail, it is +related to a numpy change and not a scikit-learn one, so it would not make sense +to blame the PR author for the Travis failure. + +The definition of what's get run in the Cron job is done in the .travis.yml, +exactly the same way as the other Travis job. We use a ``if: type = cron`` +filter in order for the build to be run only in Cron jobs. + +The branch targetted by the Cron job and the frequency of the Cron job is set +via the web UI at https://www.travis-ci.org/scikit-learn/scikit-learn/settings. From c7adae8d202bb0ec1c61fc84512e0cf61f6a95d3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Est=C3=A8ve?= Date: Mon, 13 Nov 2017 10:54:42 +0100 Subject: [PATCH 2/3] Fix typos --- doc/developers/maintainer.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/developers/maintainer.rst b/doc/developers/maintainer.rst index 2e2874b0fb60d..d2eafe4a660bb 100644 --- a/doc/developers/maintainer.rst +++ b/doc/developers/maintainer.rst @@ -73,9 +73,9 @@ run as a Cron job. Most of the time when this numpy-dev build fail, it is related to a numpy change and not a scikit-learn one, so it would not make sense to blame the PR author for the Travis failure. -The definition of what's get run in the Cron job is done in the .travis.yml, -exactly the same way as the other Travis job. We use a ``if: type = cron`` -filter in order for the build to be run only in Cron jobs. +The definition of what gets run in the Cron job is done in the .travis.yml +config file, exactly the same way as the other Travis jobs. We use a ``if: type += cron`` filter in order for the build to be run only in Cron jobs. The branch targetted by the Cron job and the frequency of the Cron job is set via the web UI at https://www.travis-ci.org/scikit-learn/scikit-learn/settings. From 7248153fc56cb9cdfa57b281d8e464a72749a08b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Est=C3=A8ve?= Date: Mon, 13 Nov 2017 15:56:19 +0100 Subject: [PATCH 3/3] Move wiki release link to the proper section --- doc/developers/maintainer.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/developers/maintainer.rst b/doc/developers/maintainer.rst index d2eafe4a660bb..c645a5c71dbec 100644 --- a/doc/developers/maintainer.rst +++ b/doc/developers/maintainer.rst @@ -1,10 +1,10 @@ Maintainer / core-developer information ======================================== -For more information see https://github.com/scikit-learn/scikit-learn/wiki/How-to-make-a-release - Making a release ------------------ +For more information see https://github.com/scikit-learn/scikit-learn/wiki/How-to-make-a-release + 1. Update docs: