This only impacts the script that prints the differences between current and previous distribution. Here is a fix for the error: https://git.opendaylight.org/gerrit/#/c/79775 BTW I also updated the

AR Oxygen #556 has passed sucessfully. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-oxygen/556/

Great. Thanks Robert & Anil.

Excellent, I've triggered job AR Oxygen #556, and hopefully once this goes through we can merge the CR. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-oxygen/556/

Ah, by the way, the new distribution is 14.8MiB (~4.2%) smaller than SR4. Regards, Robert

Hello, Oxygen branch is stable as of now in that it successfully underwent merge jobs for all projects and resulted in a fresh distribution in nexus. My work here is done :) I would suggest spinning

Hey, watching https://jenkins.opendaylight.org/releng/job/distribution-merge-managed-oxygen/4185/console is saw this bit: Is there a bug we are silently ignoring? Regards, Robert

Just one question: since the odlparent test-distribution does not include the infrautils ready feature or any RESTCONF API to poll, what is is the best way to programmatically determine all features

Hello Anil, It took a bit longer than expected, but odlparent-3.1.6 is out and the patches are out there. yangtools-2.1.6.7 to go with that is also out and I am preparing patches (should be a couple

See below This thread provides some solutions: https://stackoverflow.com/questions/8974170/jenkins-parameterized-job-that-only-queues-one-build Most popular: 1) Use Jenkins groovy script to clear job

This kind of job would be also useful to test self-managed distributions, and required if we take the path of moving common distribution to SM distributions. I will take a look at this. BR/Luis

About the stuff below - to address Robert's point about quiescent period and xtend breaking us - maybe reduce the frequency from daily to weekly (or some other suitable interval like twice a week)?

Hello, the odlparent-4.0.8 problem which is causing so much pain could be avoided if we had the equivalent of distribution-check-managed hooked onto odlparent. We are hosting a project-specific

Proper upgrade to the latest version fixed the issue. Thanks Anil and Ivan! Regards, R P Karthika

Please update you JJB to a more recent version and try if it work. Here is the output from my virt environment. $ pip

Jenkins job version : 2.0.10 To create the env : source sandbox/bin/activate Output of pip freeze : (sandbox) mininet@mininet-vm:~/builder\> pip

Please provide more info about your dev env along with output of `pip freeze`. Thanks, Anil

Note this applies to merge jobs as well, but there we have a rather different requirement: the pre-existing enqueued-but-not-started job should never be canceled. Since we do not have

Did not help much the same error still occurs. Regards, R P Karthika

Hi, try: pip install jenkins-job-builder==2.9.1 Regards Od: R P Karthika . <r.p.karthika@...> Odoslané: piatok, 18. januára 2019 6:33:49 Komu: 'integration-dev@...' (integration-dev@...)