Skip to content

Creation of new release definition fails when a release trigger is defined. #91

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

Closed
ntrogh opened this issue Jul 6, 2018 · 2 comments
Closed
Assignees
Labels

Comments

@ntrogh
Copy link

ntrogh commented Jul 6, 2018

When creating a new release definition which contains a release trigger (no matter which type), the process fails with the following error:

vsts.exceptions.VstsServiceError: Invalid data is passed for artifact source trigger object.

Trigger definition:

"triggers": [
        {
            "artifactAlias": "_CI",
            "triggerConditions": [],
            "triggerType": 1
        }
    ]

It seems only the trigger type is being passed to the VSTS REST API and other properties are being stripped out.

When removing the trigger definition from the new release definition, the creation works successfully.

@tedchamb tedchamb added the bug label Jul 6, 2018
@tedchamb tedchamb self-assigned this Jul 6, 2018
@tedchamb
Copy link
Member

tedchamb commented Jul 9, 2018

Fixed in #92

@tedchamb
Copy link
Member

tedchamb commented Jul 9, 2018

The fix is available in 0.1.10

@ntrogh ntrogh closed this as completed Jul 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants