Hi, We are seeing missing dependency warnings on, for `org.opendaylight.integration:features-integration-index` job on `autorelease-release-boron`. Please refer to logs in [1.] for more details. 1. ht

Thanh - Thanks for updating me on this. I have submitted a patch to remove the `circuitsw` since its not participating in Boron. Please review. https://git.opendaylight.org/gerrit/42981 Thanks, Anil

Hello Everyone, The distribution and merge jobs required changes to the Jenkins postbuild step, since `maven-deploy` is not a valid option for freestyle jobs. Therefore as a work around we have includ

Luis, I just wanted to add that these images ("ubuntu-trusty-mininet-ovs-25-2c-2g" and "ubuntu-trusty-mininet-ovs-23-2c-2g") are only available on Jenkins/sandbox. I will shortly add them to Jenkins/r

Hi All, I am presently working on migrating the jjb/autorelease templates. Once these are done, I get me hands on the integration and p2repo templates. Thanks, Anil

Hi all, We have a new {verify,merge}-packer jobs available which validates (templates/scripts) and builds images on the private/public clouds. These jobs are triggered on any changes to `releng/builde

We had to clean up the orphaned nodes on the public cloud earlier today. Please let us know, if you are still hitting the issue along with a link to the job. - Anil

Greetings Ravit, I have attached the list of plugins we are using on Jenkins/releng. I think you may also be able to get this directly from the `https://jenkins.opendaylight.org/releng/script` using g

Hi All, Some of the jobs failed on stack creation (timeout), caused due to orphaned nodes not getting cleaned up on rackspace. We are removing the nodes manually and have Jenkins on shutdown mode temp

We have complete removing the orphaned nodes, and Jenkins CI is back to normal. Thanks, Anil

Hi, I thought it would be good to notify everyone since we are seeing changes with old labels format, using `dynamic_*`. We have removed and/or updated some of the labels (earlier used with `node` key

I am trying to build an ubuntu 16.04 image with ovs-2.5 and set it up on sandbox to confirm if integration jobs using ovs/mininet works as expected with the new images. However, I am seeing some issue

Greetings, I have built Ubuntu 16.04 image [1.] and [2.] with the default versions of mininet 2.2.1 and ovs 2.5 installed and used a workaround in [3.] for installing mtcbench binaries. Could we get s

Hi Jamo, Luis: Just wanted to heads up that we have also got another set of Ubuntu 16.04 images for groupbasedpolicy jobs in [1.] and [2.]. The initial version of the images had a few issues with ssh

+1 for the pom name, since the reactor summary looks a lot cleaner and more readable! Thanks, Anil

Hello JamO, As requested I have built new set of centos7 robot images details below and submitted a patch [1.]. Please let me know if this meets your requirements. Private cloud: CentOS 7 - robot - 20

Hi, From SR3 status page in [1.] shows that we are waiting on updates from projects: bgpcep, centinel, didm, groupbasedpolicy, lacp, mdsal, natapp, netconf, netvirt, sfc, tsdr, unimgr, vtn. We request

Do we have a bugzilla id handy to update the spreadsheet ? Unfortunately, I can't find that on the commit message. Thanks, Anil

Greetings Dhevendran: For the change in question, I am unable see anything tied down specific images. Since both versions of the binaries are required have you explored the possibility of using a diff

Greetings: This is possibly caused due to the change in 8cb455437ca3268b6b1a8ddcf5739c966a4cb2dc. I have reverted the change in question and would appreciate any committers to +2 the change at the ear