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

Phase condition does not work like task condition #7963

Closed
StefanKoell opened this issue Aug 8, 2018 · 1 comment

Comments

@StefanKoell
Copy link

commented Aug 8, 2018

Environment

VSTS
https://royalapplications.visualstudio.com/Royal%20Applications/_build/results?buildId=192&_a=summary&view=logs
Build 20180808.17

  • Agent - Private:
    Windows Server 2016
    Microsoft Windows [Version 10.0.14393]
    C:\agent>bin\Agent.Listener.exe --version
    2.136.1

Issue Description

Working with several agent phases in VSTS and trying to use a custom condition on the phase itself to only run when a specific text is in the commit message. For this, I'm using the following condition:
and(succeeded(), contains(variables['build.sourceVersionMessage'], '[win]'))

The phase is always skipped but if I use the same condition on the individual tasks, it's working fine. This seems to be a bug on the phase condition evaluation.

Error logs

no errors can be found in the logs and no information why the phase has been skipped can be found either

@bryanmacfarlane

This comment has been minimized.

Copy link
Contributor

commented Aug 17, 2018

Service issue. Not an issue with with the tasks in this repo.

Note that some variables are realized JIT agent side. Phase conditions are evaluated service side before it goes to the agent.

If that doesn't answer your question, you may want to log an issue in vsts-agent repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.