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

TeamCity block messages #18

Merged
merged 1 commit into from Jan 15, 2016
Merged

Conversation

jozefizso
Copy link
Contributor

Added support to write TeamCity service messages message, blockOpened and blockClosed.

@gep13
Copy link
Member

gep13 commented Jan 2, 2016

@jozefizso do you know what version of Pester is being used by default on AppVeyor? And is there a known issue as to why it is hanging? Thanks!

@jozefizso
Copy link
Contributor Author

According to this tweet we can use the older Pester 3.3.12 https://twitter.com/appveyor/status/683381915550789632

It fixed my branch build: https://ci.appveyor.com/project/jozefizso/psake-contrib/build/1.0.0-build-21

@dlwyatt
Copy link
Member

dlwyatt commented Jan 2, 2016

I don't think it's a Pester problem. Something up with Chocolatey. Explicitly specifying version seems to work, even if it's latest (3.3.16)

@gep13
Copy link
Member

gep13 commented Jan 2, 2016

@dlwyatt what issue are you seeing with Chocolatey? Doesn't look like 3.3.16 has been pushed to Chocolatey.org yet. If you are running into issues with Chocolatey, feel free to reach out to either myself or Rob, and we can help if we can.

@dlwyatt
Copy link
Member

dlwyatt commented Jan 2, 2016

Sorry, meant 3.3.14. I was able to reproduce the hang of "cinst Pester" from my computer when someone tweeted about it, but "cinst Pester --version 3.3.14" worked fine for me.

@dlwyatt
Copy link
Member

dlwyatt commented Jan 2, 2016

Just for giggles, you could try something like this in AppVeyor to download the latest version of Pester until this other problem goes away:

$version = @(clist pester) -match '^pester\s*([\d\.]+)$' -replace '[^\d\.]' | Select-Object -First 1
cinst pester --version $version

@gep13
Copy link
Member

gep13 commented Jan 2, 2016

Hmm, this is very strange! I have just been able to reproduce the issue locally on my machine as well 😢

@gep13
Copy link
Member

gep13 commented Jan 4, 2016

@jozefizso this Chocolatey Issue has been resolved: https://twitter.com/MSH_Dave/status/683677951536312321

Can you update this PR to remove the specific Pester version number, and I can get this pulled in and released?

Thanks!

@jozefizso
Copy link
Contributor Author

I think I will create new pull request with squashed changes. That cinst bug fix should not be part of this changeset.

@gep13
Copy link
Member

gep13 commented Jan 4, 2016

@jozefizso there is no need to create a new PR, just squash/rebase on your existing branch, adn this PR will be updated automagically 😄

@gep13 gep13 modified the milestone: 1.1.0 Jan 15, 2016
@gep13
Copy link
Member

gep13 commented Jan 15, 2016

@jozefizso thanks again for your contributions! 👍

gep13 added a commit that referenced this pull request Jan 15, 2016
@gep13 gep13 merged commit 7f3a398 into psake:develop Jan 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants