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

AppVeyor builds are not shown as PRs checks. #139

Closed
gdziadkiewicz opened this issue Oct 10, 2019 · 5 comments
Closed

AppVeyor builds are not shown as PRs checks. #139

gdziadkiewicz opened this issue Oct 10, 2019 · 5 comments

Comments

@gdziadkiewicz
Copy link
Collaborator

gdziadkiewicz commented Oct 10, 2019

Description

AppVeyor builds are not triggered for Pull Requests. The builds take place, but the status is not reported on the PR or commits. This may be similar to https://help.appveyor.com/discussions/problems/17150-github-doesnt-report-build-status-on-prs

Repro steps

Please provide the steps required to reproduce the problem

  1. Create PR

Expected behavior

Checks from both Travis and AppVeyor visible.

Actual behavior

Check only from Travis visible.

Known workarounds

Setup your own AppVeyor account, execute the merge on your fork, trigger AppVeyor build and check the results. Check the build status on AppVeyor page manually.

Related information

  • Operating system N/A
  • Branch N/A
  • .NET Runtime, CoreCLR or Mono Version N/A
  • Performance information, links to performance testing scripts N/A
@gdziadkiewicz gdziadkiewicz changed the title AppVeyor builds are not triggered for PRs. AppVeyor builds are not shown as PRs checks. Oct 10, 2019
@gdziadkiewicz
Copy link
Collaborator Author

Can the someone with permissions to modify https://ci.appveyor.com/project/fsgit/fsharpx-collections settings try to help or advise? @fsgit @fsprojectsgit ?

@gdziadkiewicz
Copy link
Collaborator Author

Commit checks:
image

PR checks:
image

@sergey-tihon
Copy link
Member

sergey-tihon commented Oct 15, 2019

please check #92

Master branch badge:
Build status

@gdziadkiewicz
Copy link
Collaborator Author

@sergey-tihon Thanks for help. It seems to work now! What was the solution?

@sergey-tihon
Copy link
Member

I am not sure... I created new AppVeyor project and it probably reregistered webhooks in the repo.

I personally prefer Azure Pipelines these days (one service, one config file - runs on win, linux and macOS in the same time)

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