|Re: [cbi-dev] CI and Jenkins pipeline best practices|
Hi Frederic SCM polling is good, but periodical is good too.For my projects I do SCM polling Monday to Saturday and a forced build on Sunday.
The latter ensures timely detection of EF/dependency API breakages so that there is a better chance that the problem is reported while still in the developer's minds and with a chance of fixing before a milestone.
The latter also avoids the confusion whereby your build breaks just after you've done a code change so you of course assume you broke it, but actually another project broke it first.
Regards Ed Willink On 10/05/2021 11:25, Frederic Gurr wrote:
Hi, To get the most out of your CI jobs, here is a refresher/reminder about general CI and Jenkins pipeline specific best practices: General CI best practices: -------------------------- * *Keep builds and tests FAST!* * Create robust tests, do not rely on best-case-scenario timeouts * Always use job timeouts * Disable concurrent builds * Always use "poll scm" option, don't do plain periodical builds * Keep your build history at a reasonable length * Do not keep more than 5 builds with artifacts * Clean out your old/deprecated build jobs regularly See also https://wiki.eclipse.org/CI_best_practices Jenkins pipeline best practices: -------------------------------- * Use Jenkinsfiles (commit pipeline definitions to SCM) * Use declarative pipelines, use scripted syntax only as last resort * For complex pipelines, consider shared libraries See also https://www.cloudbees.com/blog/top-10-best-practices-jenkins-pipeline-plugin You can find even more info about CI and Jenkins on our wiki page: https://wiki.eclipse.org/Jenkins If you have any questions, concerns or other best practices that should be shared, please let us know. Regards, Fred
-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Back to the top