Guys thank you for your tips, One important things the we are missing is the setting.xml that is assigned to each job. I cannot find any trace of how they are built. Any tips ?
Alon From: [email protected] [mailto:[email protected]] On Behalf Of Barak Dabush Sent: Thursday, May 4, 2017 7:48 AM To: Alexis de Talhouët <[email protected]> Cc: [email protected] Subject: Re: [onap-discuss] CI integration Thanks you Alexis & Gino. Barak From: Alexis de Talhouët [mailto:[email protected]] Sent: Thursday, May 4, 2017 1:21 AM To: Barak Dabush <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] CI integration Barak, On May 3, 2017, at 11:56 AM, Barak Dabush <[email protected]<mailto:[email protected]>> wrote: Hi, We are trying to set an internal CI with local Jenkins. Apparently, there are some variables which we could not find their values on the git repo or Jenkins (using normal using access). For example how can I determine the content of the project specific SETTINGS_FILE? You need to install the Config File Provider Plugin: https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin Once install, you can create your settings.xml file that will point to your Nexus repository. I think the question to ask the LF is, can you provide the list of installed plugin in your jenkins instance? Because there is way more than one plugin to install, for sure! Is GLOBAL_SETTINGS_FILE taken from global-defaults.yaml? Additional variables defined globally, e.g. where is GIT_BASE and what is the expected value. I couldn’t figure out about GIT_BASE as well, but this should reflect your internal git instance, the base URL to which the project name will be appended. Is there a documentation which explains how to import the jobs from the ci-management to Jenkins? As mentioned already, you have to use JJB. To use JJB, you need to setup the jenkins.ini with the appropriate information. The ci-management repo provide an example of such file. Once done, here are some example commands that could help you get started: # create job for folder aai jenkins-jobs --conf jenkins.ini update jjb/ \*aai\* # delete job for folder aai jenkins-jobs --conf jenkins.ini delete --path jjb/ \*aai\* # create job for a job jenkins-jobs --conf jenkins.ini update jjb/ aai-model-loader-master-verify-java # delete job jenkins-jobs --conf jenkins.ini delete --path jjb/ aai-model-loader-master-verify-java for more info, please read https://docs.openstack.org/infra/jenkins-job-builder/execution.html#command-reference HTH, Alexis Regards, Barak This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer _______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-discuss This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
