summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-10-29Merge "Move to golang 1.11"Jessica Wagantall1-0/+1
2018-10-29Move to golang 1.11Kiran Kamineni1-0/+1
Move k8s plugin to build with golang 1.11 This is a prerequisite for go mod support in the plugin Issue-ID: MULTICLOUD-387 Change-Id: I1fe6a1b11fdee56b43af2703e5734a8715cbab63 Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
2018-10-29Fetch CLM updates from global-jjbJessica Wagantall4-0/+12
This reverts commit d0e846cb0025bf9f68ce363cfdd42fa403d95968. Fetch lastest HEAD of global-jjb now that lftools 0.18.0 has been released. Localy used lf-infra-gerrit-scm macros need to be updated to add a "submodule-timeout" value as part of global-jjb: commit 9fdb611f1fce34d54be1af81d7baedb86726302c. Issue-ID: CIMAN-33 Change-Id: Ib29b625bb63e1c03988b23122b3157e62de3fa03 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2018-10-27Merge "Install memcached with sudo"Jessica Wagantall1-0/+1
2018-10-26Set policy/engine CLM to 4c 4gPamela Dragosh1-0/+1
The CLM job keeps failing, we think it is because the memory and cpu requirements are randomly being chosen instead of using 4c 4g that we established before. Issue-ID: POLICY-1224 Change-Id: I050ac8afc992ee450ec5877c2ec4b60430794ee4 Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
2018-10-25Install memcached with sudoJessica Wagantall1-0/+1
Change-Id: I941730dedd6ee8cc67901ee30ddf8afae69183d6 Issue-ID: CIMAN-33 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2018-10-25Merge "Update memcached/redis packer templates"Bengt Thuree2-2/+2
2018-10-25Merge "Remove Centos Docker packer jobs"Bengt Thuree1-2/+0
2018-10-25Update memcached/redis packer templatesJessica Wagantall2-2/+2
Update memcached and redis image information to an available one. Change-Id: Id8bd716894ea722d65650897b1bec92afade350d Issue-ID: CIMAN-33 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2018-10-25Remove Centos Docker packer jobsJessica Wagantall1-2/+0
ONAP does not need these since the only Docker nodes being in production are Ubuntu based. There is no requirement for a Centos Docker node. Change-Id: I9ab4b1e75c2297458a10789d675c6a3b453c529c Issue-ID: CIMAN-33 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2018-10-25Use 90 timeout for Docker packer jobsJessica Wagantall1-1/+1
Add 30 more minutes timeout for Docker packer jobs. ARM builds are reaching the timeout of 60 mins and crashing due to that. Change-Id: I2164b70dbada7501a6cd308667c9c9393b099f78 Issue-ID: CIMAN-33 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2018-10-25Switch sms to use golang 1.11Kiran Kamineni1-0/+1
Switch sms to use golang 1.11 This is a prerequisite to start using go mod for module management in Go. Issue-ID: AAF-404 Change-Id: Ia221b93399232ee9fa1c1c63fd6fa752011c5114 Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
2018-10-24Merge "Add golangver allowing projects to pick go version"Jessica Wagantall1-3/+18
2018-10-24Add golangver allowing projects to pick go versionKiran Kamineni1-3/+18
Adding a new golangver variable that is by default set to golang110. Projects do not need to do anything for this. Any project that wants to move to 1.11 just needs to set this variable to golang111 Issue-ID: CIMAN-216 Change-Id: Ia5a5a7dfbc94549726ed97ebc63e5562c19db513 Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
2018-10-24support VID master and casabalanca branchesSonsino, Ofir (os0695)1-0/+4
Change-Id: I0cacbc797bdc9fc810674f12a55a9f87272ebbd5 Issue-ID: VID-334 Signed-off-by: Sonsino, Ofir (os0695) <os0695@intl.att.com>
2018-10-23Add golang 1.11 wrapperKiran Kamineni2-4/+13
Add support for golang 1.11 renamed old golang to golang110 Issue-ID: CIMAN-216 Change-Id: I771f8291b376d4406fd530bf97bb882171f1c936 Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
2018-10-23AAF-Refactor CLM project blockJessica Wagantall3-8/+20
The clm job portion needs to be on its own project section similar to the Sonar portion. The reason behind this, is because we only want this job to be running for master and no other branches. Also, this is in preparation for the work that is to come from global-jjb on application names in CLM. Change-Id: Ib273ae89f672603306104bb43cbfd422e11bf0f8 Issue-ID: CIMAN-213 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2018-10-23Merge "DCAEGEN2-Refactor CLM project block"Jessica Wagantall23-23/+228
2018-10-23Merge "CCSDK-Refactor CLM project block"Jessica Wagantall10-10/+108
2018-10-23Merge "CLAMP-Refactor CLM project block"Jessica Wagantall1-2/+12
2018-10-23Merge "APPC-Refactor CLM project block"Anil Belur3-6/+32
2018-10-23Merge "HOLMES-Refactor CLM project block"Anil Belur4-4/+36
2018-10-23DCAEGEN2-Refactor CLM project blockJessica Wagantall23-23/+228
The clm job portion needs to be on its own project section similar to the Sonar portion. The reason behind this, is because we only want this job to be running for master and no other branches. Also, this is in preparation for the work that is to come from global-jjb on application names in CLM. Change-Id: I47585bc0e3baebea06c3062fe77e88eeeac8e756 Issue-ID: CIMAN-213 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2018-10-23CLAMP-Refactor CLM project blockJessica Wagantall1-2/+12
The clm job portion needs to be on its own project section similar to the Sonar portion. The reason behind this, is because we only want this job to be running for master and no other branches. Also, this is in preparation for the work that is to come from global-jjb on application names in CLM. Change-Id: I52435cda239d8e79ae11e4fc8e2d2e67b964b4b0 Issue-ID: CIMAN-213 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2018-10-23CCSDK-Refactor CLM project blockJessica Wagantall10-10/+108
The clm job portion needs to be on its own project section similar to the Sonar portion. The reason behind this, is because we only want this job to be running for master and no other branches. Also, this is in preparation for the work that is to come from global-jjb on application names in CLM. Change-Id: Ief5e40b3f01cb545e800bb0899019a2da564b40b Issue-ID: CIMAN-213 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2018-10-23APPC-Refactor CLM project blockJessica Wagantall3-6/+32
The clm job portion needs to be on its own project section similar to the Sonar portion. The reason behind this, is because we only want this job to be running for master and no other branches. Also, this is in preparation for the work that is to come from global-jjb on application names in CLM. Change-Id: I45642f6f3c14acd047141d3b8f74113c0674c54a Issue-ID: CIMAN-213 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2018-10-23Merge "SDC-Refactor CLM project block"Anil Belur11-13/+106
2018-10-23Merge "USECASE-Refactor CLM project block"Anil Belur2-2/+20
2018-10-23HOLMES-Refactor CLM project blockJessica Wagantall4-4/+36
The clm job portion needs to be on its own project section similar to the Sonar portion. The reason behind this, is because we only want this job to be running for master and no other branches. Also, this is in preparation for the work that is to come from global-jjb on application names in CLM. Change-Id: I52ea3a5daf583e1a2c65dec819637ad4657d3a7c Issue-ID: CIMAN-213 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2018-10-23Merge "PORTAL-SDK-Refactor CLM project block"Anil Belur1-2/+10
2018-10-23Merge "SDNC-Refactor CLM project block"Anil Belur3-3/+30
2018-10-23Merge "MUSIC-Refactor CLM project block"Anil Belur4-6/+38
2018-10-23Merge "MSB-Refactor CLM project block"Anil Belur4-4/+36
2018-10-23Merge "INT-Refactor CLM project block"Anil Belur1-2/+10
2018-10-23Merge "OPTF-Refactor CLM project block"Anil Belur3-4/+29
2018-10-23Merge "OPARENT-Refactor CLM project block"Anil Belur1-1/+9
2018-10-23Merge "OOM-Refactor CLM project block"Anil Belur1-1/+9
2018-10-23Merge "TESTSUITE-Refactor CLM project block"Anil Belur1-1/+10
2018-10-23Merge "SO-Refactor CLM project block"Anil Belur2-2/+19
2018-10-23Merge "VNFSDK-Refactor CLM project block"Anil Belur6-7/+61
2018-10-23Merge "CLI-Refactor CLM project block"Anil Belur1-1/+10
2018-10-23Merge "VFC-Refactor CLM project block"Anil Belur15-19/+154
2018-10-23Merge "VID-Refactor CLM project block"Anil Belur1-1/+10
2018-10-23Merge "PORTAL-Refactor CLM project block"Anil Belur1-1/+9
2018-10-23Merge "LOG-Refactor CLM project block"Anil Belur7-7/+63
2018-10-23Merge "DMAAP-Refactor CLM project block"Anil Belur8-8/+72
2018-10-23Merge "MOD-Refactor CLM project block"Anil Belur2-4/+21
2018-10-23Merge "POLICY-Refactor CLM project block"Anil Belur14-16/+128
2018-10-23USECASE-Refactor CLM project blockJessica Wagantall2-2/+20
The clm job portion needs to be on its own project section similar to the Sonar portion. The reason behind this, is because we only want this job to be running for master and no other branches. Also, this is in preparation for the work that is to come from global-jjb on application names in CLM. Change-Id: Ifb6705a0c932581e65346c9c0d201af7daff13ee Issue-ID: CIMAN-213 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2018-10-23SDNC-Refactor CLM project blockJessica Wagantall3-3/+30
The clm job portion needs to be on its own project section similar to the Sonar portion. The reason behind this, is because we only want this job to be running for master and no other branches. Also, this is in preparation for the work that is to come from global-jjb on application names in CLM. Change-Id: If9113ca802b2facfe635e7a11dd3e08bce15c05a Issue-ID: CIMAN-213 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>