infra

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
infra [2014/12/09 10:00]
rogerio [Adding a new repository to monitor, build and deploy] 		infra [2014/12/09 10:06]
rogerio
Line 174: Line 174:
       cap lacinfratest integration -s keys integration_local_to_remote=true force_ref=master       cap lacinfratest integration -s keys integration_local_to_remote=true force_ref=master
       cap lacinfratest teardown       cap lacinfratest teardown
- 
-{{::ci-config1.png?200|}} 
  
 ==== Adding a new repository to monitor, build and deploy ==== ==== Adding a new repository to monitor, build and deploy ====
- 
-{{:ci-config3.png?direct&700|}} 
  
 When you need to add a new component to the build process, you need to modify as follows: When you need to add a new component to the build process, you need to modify as follows:
Line 218: Line 214:
  
     * Add the new repository to the contextnet-master-trigger job in Jenkins.     * Add the new repository to the contextnet-master-trigger job in Jenkins.
 +
 +    1. First open the configuration of the main job trigger.
 +
 +{{:ci-config1.png?direct&300|}}
 +
 +    2. Then go to the last repository in the list.
 +
 +{{:ci-config2.png?direct&300|}}
 +
 +    3. And click "add repository".
 +
 +{{:ci-config3.png?direct&300|}}
 +
 +    4. After you insert your new Git repository to be monitored, just save the configuration.
 +
 +{{:ci-config4.png?direct&300|}}
 +
 +You may also want to sync the new configuration to the INFRA-Provision repository:
 +
 +    ci/download-config.sh
 +    git add provision/rootfs-ci/home/lac/.jenkins
 +    git commit -am 'Jenkins config save'
 +    git push
  
 ===== Important links ===== ===== Important links =====
  • infra.txt
  • Last modified: 2017/07/21 03:08
  • (external edit)