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 not building PDF #308

Closed
olgabot opened this issue Feb 13, 2020 · 6 comments
Closed

AppVeyor not building PDF #308

olgabot opened this issue Feb 13, 2020 · 6 comments

Comments

@olgabot
Copy link
Contributor

olgabot commented Feb 13, 2020

Hello,
I'm not able to build the intermediate PDF of the manuscript which hinders my ability to solicit feedback on intermediate work. In this PR: https://github.com/czbiohub/orthology-free-comparative-transcriptomics-paper/pull/47 the AppVeyor build works at first, but then for some reason stops accepting events:

image

I don't understand why skip_branch_with_pr: true is set in the appveyor.yml file, since don't we want to build the pdfs for PRs?

Let me know if there is anything else I can provide!
Warmest,
Olga

@dhimmel
Copy link
Member

dhimmel commented Feb 13, 2020 via email

@agitter
Copy link
Member

agitter commented Feb 13, 2020

@dhimmel
Copy link
Member

dhimmel commented Feb 14, 2020

As @agitter diagnosed in https://github.com/czbiohub/orthology-free-comparative-transcriptomics-paper/pull/47#issuecomment-585748162, the issue is due to the pull request having a merge conflict:

Screenshot from 2020-02-14 10-47-19

AppVeyor (and other CI services) evaluate a merge commit for pull requests rather than the actual commit on the PR branch. Therefore when there is a conflict, they cannot proceed with CI.

Changing to skip_branch_with_pr: false would probably not have an effect because we are specifying only master branch builds anyways:

# See https://www.appveyor.com/docs/getting-started-with-appveyor-for-linux/
skip_branch_with_pr: true
# Enable 'Do not build on "Push" events' in the AppVeyor project settings
# to only build commits from pull requests
branches:
only:
- master

But if you remove everything quoted above, then you would be able to build the push event for your branch. Once the merge conflict was resolved, you'd then get two CI jobs for each PR commit (one for the branch push event and another of the pull request event).

@olgabot
Copy link
Contributor Author

olgabot commented Feb 14, 2020

Ohh I see! Now I understand. Would it be possible to add an error message from AppVeyor that he PDF wasn't built because of the merge conflict? I wouldn't have thought to fix that without your help. Thank you so much!

@olgabot
Copy link
Contributor Author

olgabot commented Feb 14, 2020

YAYY IT BUILT!!!! THANK YOU SO MUCH!!! https://github.com/czbiohub/orthology-free-comparative-transcriptomics-paper/pull/47/#issuecomment-586493091

🎉🎉🎉🎉🎉🎉🎉🎉🎉

@agitter
Copy link
Member

agitter commented Feb 14, 2020

The merge conflict prevents AppVeyor from running at all, so I don't think we have control over the AppVeyor notifications to point out the merge conflict caused the problem. I first noticed this in https://github.com/czbiohub/de-novo-orthology-paper/pull/47 because in the commit showed a failed build
image

Perhaps this points to a place where we could improve documenation.

dhimmel pushed a commit that referenced this issue Feb 14, 2020
ploegieku added a commit to ploegieku/2023-functional-homology-paper that referenced this issue Aug 6, 2024
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

3 participants