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

Wish: Separate Quote types based on success / failed #10

Open
patdaman opened this issue Dec 6, 2018 · 5 comments
Open

Wish: Separate Quote types based on success / failed #10

patdaman opened this issue Dec 6, 2018 · 5 comments

Comments

@patdaman
Copy link

patdaman commented Dec 6, 2018

It would be great if the quote type related to the success / failure of the build.

I haven't yet seen an environment variable for success / failure while executing, only as a condition for the task to execute or not. Previous tasks to this one would output a non success, not sure if we need to save the output or search for $($env:ErrorMessage) in the running log.

I would love him to talk smack if the build failed!

@MOlausson
Copy link
Member

I like the idea. Just to make sure I get this right, you would like a way to control so that Chuck only is shown when builds fail?

@patdaman
Copy link
Author

patdaman commented Dec 9, 2018

That's another idea, a configuration option to only display for failed, successful, or both. I like that. Failed builds are also more likely to be inspected!

What I meant was to have two separate 'buckets' of quotes; one bucket for successful builds (or no errors to that point), and another bucket with quotes for when the build fails (or has a preceding error).

That way he can say something in the list more specific for a failed build like:
"“It works on my machine” always holds true for Chuck Norris."

All other categories reserved for successful builds.

Kind of having Chuck taunting the developers.

@MOlausson
Copy link
Member

Ok, got it. Sounds like a good idea. Have a look here and would appreciate your help categorizing the jokes (or add more if you're up to it!):

@patdaman
Copy link
Author

patdaman commented Dec 9, 2018

I sure will!

Thanks

@MOlausson
Copy link
Member

@patdaman did you get to look at this?

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

2 participants