Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Edges in WorkflowGraph contain source and destination that are not part of the origin pipeline #3206

Open
VonnyJap opened this issue Sep 24, 2024 · 0 comments

Comments

@VonnyJap
Copy link
Member

What happened:

I noticed this scenario in the workflow graph.

const workflowGraph = {
    nodes: [
        {
            name: '~pr'
        },
        {
            name: '~commit'
        },
        {
            name: '~sd@123:deploy-db',
            id: 573500
        },
        {
            name: 'sd@123:deploy-api',
            id: 573501
        },
        {
            name: 'certify-db',
            id: 573502
        }
    ],
    edges: [
        {
            src: '~pr',
            dest: 'pr'
        },
        {
            src: '~commit',
            dest: 'component'
        },
        {
            src: '~sd@123:deploy-db',
            dest: 'certify-db'
        },
        {
            src: 'certify-db',
            dest: 'sd@123:deploy-api'
        },
        ### entry below comes from two remote pipelines
        ### is this possible?
        {
            src: '~sd@123:deploy-api',
            dest: 'sd@456:mysql'
        }
    ]
};

What you expected to happen:

At least one source or destination of an edge in the workflow graph should originate from a node in the original pipeline. If neither does, it could indicate a bug.

How to reproduce it:

See the thread in the PR below
#3202

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant