Search results

Create the page "Continuous Integration" on this wiki! See also the search results found.

Page title matches

Page text matches

• CI Best practices
  #REDIRECT [[Continuous Integration: Best practices]]
  52 B (5 words) - 04:20, 13 May 2019
• Continuous Integration: Best practices
  #REDIRECT [[Continuous Integration: Best Practices]]
  52 B (5 words) - 04:20, 13 May 2019
• Gitea/Jenkins: Setting up Webhooks
  ...o a Gitea repository. This can be a very useful improvement to continuous integration setup with Jenkins because this method is only telling Jenkins to attempt a
  4 KB (554 words) - 18:51, 30 November 2019
• How many builds?
  ...er too many builds and transform the pipeline into something we can call ''Continuous Building''. Parallel builds of the same project that interfere with each ot
  2 KB (262 words) - 21:35, 11 May 2019
• Jenkins Analysis
  ...n done in 2016 to evaluate the option of using Jenkins instead of ETICS as integration tool. ...ain tools adopted in the Java’s world for the Continuous Integration and Continuous Delivery. It’s supported from wide community Open-source and it’s possi
  10 KB (1,512 words) - 16:03, 15 December 2016
• CI Minimalistic Gitea's Guide
  ''To have a complete overview of the Continuous Integration Procedure to [[Continuous_Integration_procedure_(2019)#Complete_Guide | CI
  1 KB (148 words) - 22:58, 18 January 2020
• Continuous Integration: Releases
  ...obs]] are triggered at each commit in the master branch for the Continuous Integration. Their outcomes are deployed on the Maven Snapshot Repository.
  1 KB (171 words) - 18:05, 3 October 2019
• Continuous Integration: Releases Maven
  The build configurations must guarantee the integrity of the Continuous Integration pipeline. Jenkins builds must use only the outcomes of other Jenkins builds ...ne and deployed to Maven snapshot repository is a potential threat for the integration process. There are several cases in which such an artifact could be not in
  5 KB (767 words) - 06:01, 12 September 2019
• Continuous Integration: Releases Jeknkins
  #REDIRECT [[Continuous Integration: Releases Jenkins Pipeline]]
  63 B (6 words) - 15:43, 29 May 2019
• Continuous Integration: Developer
  ...t activity (even if it's suggested to always keep these formats to avoid a continuous switching) but must then comply to the formats on the master branch at rele = Release integration steps=
  1 KB (217 words) - 18:38, 24 November 2020
• CI Minimalistic Developer's Guide
  ''To have a complete overview of the Continuous Integration Procedure to [[Continuous_Integration_procedure_(2019)#Complete_Guide | CI
  1 KB (152 words) - 16:56, 23 September 2019
• Continuous Integration procedure (2019
  If you are looking for the Continuous Integration Guide, it's here: https://wiki.gcube-system.org/gcube/Continuous_Integratio
  143 B (19 words) - 15:31, 31 May 2019
• Continuous Delivery: Definition and Principles
  ''Continuous Delivery is a software development discipline where you build software in s You’re doing continuous delivery when:
  3 KB (387 words) - 12:44, 3 July 2019
• Continuous Integration: Releases Jenkins Pipelines
  ...combination of plugins that support the integration and implementation of continuous delivery pipelines using Jenkins. A pipeline has an extensible automation s = Continuous Delivery and Jenkins =
  4 KB (682 words) - 00:29, 29 December 2019
• CI Minimalistic GitHub's Guide
  ''To have a complete overview of the Continuous Integration Procedure see [[Continuous_Integration_procedure_(2019)#Complete_Guide | CI
  910 B (125 words) - 01:24, 1 December 2019
• GitHub/Jenkins: Setting up Webhooks
  ...o a GitHub repository. This can be a very useful improvement to continuous integration setup with Jenkins because this method is only telling Jenkins to attempt a
  4 KB (556 words) - 05:17, 1 December 2019