Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
|
|
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
|
|
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>
|
|
Change-Id: I0cacbc797bdc9fc810674f12a55a9f87272ebbd5
Issue-ID: VID-334
Signed-off-by: Sonsino, Ofir (os0695) <os0695@intl.att.com>
|
|
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>
|
|
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>
|
|
|
|
|
|
|
|
|
|
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
|
|
|
|
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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>
|
|
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>
|
|
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: Ib22c4e5bfc5f8b74cf37c339ead26baf52518eaf
Issue-ID: CIMAN-213
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
|
|
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: I25bbd84c898464c2b1955e4892b5b9a43c037efe
Issue-ID: CIMAN-213
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
|
|
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: I6bd7db60496fcbfdd52993959c9b080cabe1b8a9
Issue-ID: CIMAN-213
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
|
|
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: I11cbbda546570c1451421ee353c338c7e2f09a4f
Issue-ID: CIMAN-213
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
|
|
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: If5fcceb09b82baf5cff7189c631c4c406454eb50
Issue-ID: CIMAN-213
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
|