Re: Distribution-merge triggering on non-managed projects?

Robert Varga

On 20/07/18 15:26, Sam Hague wrote:
On Fri, Jul 20, 2018 at 7:38 AM Robert Varga <nite@...
<mailto:nite@...>> wrote:

seems to have triggered by transportpce, which is not a managed project.
seems to indicate we are building distribution for a lot of projects
which do not have bearing on it...

Is this something we want to do, or just a misconfiguration?

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 different paths in
the integration/distribution of which transportpce is not in the managed
group. So I think that part is working as intended.

As for the graph, that I don't fully understand. Luis is the expert
here, but I think what I said above is right in that we have different
configurations for managed an unmanaged. But it's possible something
isn't totally right.
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, hence it in no way affects its contents, hence it
makes zero sense to trigger on transportpce-merge.

Of unmanaged projects only SXP is part of int/dist, as Luis noted.


Join to automatically receive all group messages.