toggle quoted messageShow quoted text
The check conditions have changed after we introduced MRI projects, so now it is possible to have projects in distribution but not in AR. Because of this, we can either rework the script to check something different (not sure what) or just remove as I did.
On Jun 12, 2020, at 10:06 AM, Thanh Ha <zxiiro@...
This just turns off the comparison entirely so not really fixing but I think it's the right approach until someone can fix the script. Did a quick look at the script and it looks like it parses pom.xml files dynamically to figure out what to compare which means we definitely need to adjust the script to allow exceptions for MRI projects.
On Fri, Jun 12, 2020 at 12:22 PM Luis Gomez <ecelgp@...
This should fix: https://git.opendaylight.org/gerrit/c/releng/builder/+/90432
On Jun 12, 2020, at 9:13 AM, Robert Varga <nite@...
Well, we fixed feature packaging in distribution (i.e. we now include
features-controller-testing and others).
Also, validate-autorelease triggers only when pom.xmls are modified I
think, hence it is not typically seen.
On 12/06/2020 18:11, Luis Gomez wrote:
I think you are right, but why this starts to fail now?
On Jun 11, 2020, at 11:41 PM, Robert Varga <nite@...> wrote:
[infrautils-validate-autorelease-aluminium] $ /bin/bash -l /tmp/jenkins5280574077411919720.sh
ERROR: List of projects in integration/distribution but NOT in releng/autorelease: mdsal yangtools controller
Build step 'Execute shell' marked build as failure
I think this is wrong, since MRI projects need to be in the distribution
and not be present in autorelease.
Perhaps compare-autorelease-projects.sh needs to be updated with list of