In the interest of streamlining releases (e.g. the release process) and maintenance generally, I question the value of CI jobs for releases. There is toil in making those jobs and removing/copying them. A release branch is generally pretty darned close to the dev branch it came from (e.g. branch_9x). Furthermore, IMO, the release process itself should sufficiently validate the release. Contributors do as well on their OSs & JVMs.
I only see one gap so far -- docker tests. It'd be easy to add that as a step for the smoke tester, maybe conditionally if the docker daemon is running. The alternative of depending on CI means adding to docker-nightly.yml on each release, and forgetting or eventually remembering to remove. Not to mention, those nightly runs are costing somebody money for dubious value. ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
