Hi Everyone, I created a script [0] that builds a Maven project in an infinite while loop and collects logs to /tmp/buildlogs. It grabs 2 log types: 1. mvn output via | tee file

Dibya, sorry for the delay. The reason for separating this is because I start to see different workflow for pushing test data (every time a test job runs) and pushing a dashboard change (every time

Right, current merge job template triggers distribution build by the end of it as that was the way before we split projects. Going forward we will have to remove this step in the merge job template

Well, after digging a bit ... it is definitely not right to rebuild int/dist if a project is not added to it. I.e. it does not matter what transportpce does at this point, it is not part of int/dist,

I think this is what we want. We want the unmanaged projects to be able to build against managed so they can know what they need to fix to be able to join the release. managed and unmanaged are

Hello, https://jenkins.opendaylight.org/releng/job/distribution-merge-fluorine/1944/ seems to have triggered by transportpce, which is not a managed

Hi Anil, I have updated tag changes in the below link : https://git.opendaylight.org/gerrit/#/c/63519 Regarding the source RPM/Deb packages which are exist in third party ODL nexus repo. You

Hello Mahesh: Thanks for testing it out and providing the detailed steps. Would you be able to update these steps in the change [1.] so that we can get this merged?

Hi Anil, Now installation of zrpcd will work fine. Please check out the tag with 20180720 For example : mkdir -p /tmp/build_quagga cd /tmp/build_quagga git clone

https://meetings.opendaylight.org/opendaylight-integration/2018/integration/opendaylight-integration-integration.2018-07-19-17.06.html

Hi Luis, I went through your suggestions. I also felt the same way about grouping the config files in central templates and project specific dashboard config. It helps in less redundancy and more

Hi Vishal, You will still need to pass any commandline options as you normally would. The only change is using "tox -e jenkins-jobs" instead of "jenkins-jobs". So if you normally pass the --conf file

Hi Thanh, Sorry if the question is too obvious, but am setting up a new jjb environment so this is very timely for me. As per the docs, this is how we currently push the test: jenkins-jobs --conf

Hi Everyone, I proposed this patch yesterday https://git.opendaylight.org/gerrit/74168 which I'm hoping will make everyone's lives easier. The idea is to use "tox" to run jenkins-jobs instead of

Cool. I’ve put this down in my cal and plan to attend. —Tom

Thanks for the update Thanh!

Hi Everyone, If you use the Jenkins Sandbox this email affects you. We're looking into consolidating some of our init scripts (the scripts that run when Jenkins boots a new minion) and one of the

Thanks for the update :)

thanks for all this work Sam.

Hi Luis, My traveling is done and I'll be resuming my work. I'll will test your suggestions and get back to you by tomorrow. Thanks, Dibya