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 configuration prompting for overwrite some file(s) #21

Closed
lpranam opened this issue Jul 9, 2019 · 5 comments
Closed

AppVeyor configuration prompting for overwrite some file(s) #21

lpranam opened this issue Jul 9, 2019 · 5 comments

Comments

@lpranam
Copy link
Member

lpranam commented Jul 9, 2019

I just configured my project to use AppVeyor:
https://github.com/lpranam/astronomy/blob/CI/appveyor.yml

I encountered this bug:
https://ci.appveyor.com/project/lpranam/astronomy/builds/25792430/job/1r5xckyfoe6090g7

It prompts the message in the console and then it has to wait for infinite time as no input cannot be given and ultimately job fails due to the time limit.

I am not sure if I am doing anything wrong or it is indeed a bug. I am not much familiar CIs.

@jeking3
Copy link
Collaborator

jeking3 commented Jul 10, 2019

boost-ci assumes there is no ci directory in your project. Do you have one?

@mloskot
Copy link
Member

mloskot commented Jul 10, 2019

@lpranam In GIL, we have .ci directory, not ci, in case that is the case.

@lpranam
Copy link
Member Author

lpranam commented Jul 10, 2019

boost-ci assumes there is no ci directory in your project. Do you have one?

@jeking3 yes I have ci directory here:
https://github.com/lpranam/astronomy/tree/CI/ci

@lpranam In GIL, we have .ci directory, not ci, in case that is the case.

@mloskot, as you told me earlier that you are also changing gil config according to boost-ci, I also used the configuration from boost-ci.

@jeking3
Copy link
Collaborator

jeking3 commented Jul 11, 2019

The ci directory gets copied into place by the .travis.yml and appveyor.yml files. This allows us to update the ci-specific scripts independently from the repo using them. The only files we can't update dynamically are the .travis.yml and appveyor.yml scripts. So if you just delete the ci directory from your repo, it should work. IF the instructions in the boost-ci readme indicate you need to copy the ci directory into your repo, that's a mistake we need to fix.

@lpranam
Copy link
Member Author

lpranam commented Jul 11, 2019

@jeking3 Thank you very much removing ci directory worked. I went through the documentation again and there was no mention of copying ci directory, it was my mistake.

@lpranam lpranam closed this as completed Jul 11, 2019
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