-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
dotnet fornax build unable to find config.fsx on CI servers #52
Comments
I ran into this same problem trying to build with GitHub actions, and after doing some research, I can see with |
I confirmed this all works fine on CI servers if you commit the _lib directory and it's contents. Is there a better way to be able to restore those during CI rather than include these binaries in source control? |
Came up with this trick to get the current version of the tool to create the
Confusing error message, but after realizing it was the missing |
Describe the bug
Installing fornax as a local tool on a CI server and trying to build a site throws an error "Couldn't find or load config".
To Reproduce
fornax new
)dotnet-tools.json
with instructions to install fornax locallydotnet tool restore
anddotnet fornax build
Couldn't find or load config
.Expected behaviour
The site should build.
Build Output
Below is the output from TravisCI. The same problem occurs on Azure Pipelines as well as Netlify.
Notice that the working directory contains a
config.fsx
.Additional Thoughts
Fornax works as expected locally with the globally installed dotnet tool, as well as with the locally installed dotnet tool. It seems that on these CI servers, the directory which
dotnet fornax build
is being run from is not the same as the directory which is being passed into the build process (i.e. this path fromDirectory.GetCurrentDirectory()
).The text was updated successfully, but these errors were encountered: