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

Support for "Queue with Diagnostics" #46

Closed
richardgavel opened this issue Jun 14, 2019 · 2 comments · Fixed by #69
Closed

Support for "Queue with Diagnostics" #46

richardgavel opened this issue Jun 14, 2019 · 2 comments · Fixed by #69
Labels
Milestone

Comments

@richardgavel
Copy link

In Azure DevOps, you can queue a build or "Queue with diagnostics", which sets a variable "system.debug" to "true". It would be nice if we could define 2 different verbosity levels, one for default and one for when when "with diagnostics" is used. Right now, with YAML based builds, to do an elevated logging level, I have to check in a YAML change.

@gep13 gep13 added the Feature label Feb 29, 2020
@gep13 gep13 added this to the 0.5.0 milestone Feb 29, 2020
@gep13 gep13 modified the milestones: 0.5.0, 2.1.0 Aug 10, 2020
@gep13
Copy link
Member

gep13 commented Aug 12, 2020

@richardgavel we have recently released a new cross platform version of the Cake Task, and I would like to tackle this task next. Do you happen to know of any documentation around how this works under the hood? Thanks

@gep13 gep13 closed this as completed in #69 Aug 13, 2020
gep13 added a commit that referenced this issue Aug 13, 2020
(GH-46) setting verbosity to "diagnostic", when "system.debug" is set.
gep13 added a commit to gep13/cake-vso that referenced this issue Aug 13, 2020
Just to make it consistent with other log messages
@cake-build-bot
Copy link

🎉 This issue has been resolved in version 2.1.0 🎉

The release is available on:

Your GitReleaseManager bot 📦🚀

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

Successfully merging a pull request may close this issue.

3 participants