Hello,
I try to do something that seems not doable.
I have a simple Projet with a docker file
And I also have a Test Project that use TestContainer to build Docker Image.
var image = new ImageFromDockerfileBuilder()
.WithLogger(logger)
.WithDockerfileDirectory(CommonDirectoryPath.GetSolutionDirectory(), "")
.WithDockerfile("samples/Sample.Function.InProcess/Dockerfile")
.WithName(_image.FullName)
.WithDeleteIfExists(true)
.WithCleanUp(true)
.Build();
Is there any way to make it work with ncrunch ?
Regards
Build/Test Issues
TestContainers generated by tested from docker file of another project
Started by bhugot on 1,183 views
Remco NCrunch Developer
#17583
05 Sep 2024 01:37 UTC
Hi, thanks for posting.
I am unfamiliar with this particular framework, which makes it hard for me to give specific advice on its limitations in regards to NCrunch. However, it looks to me like the framework is designed to treat the solution as a single cohesive unit (based on the need to inject the solution directory). This sort of structure isn't something that is supported under NCrunch, because we separate projects from the solution and into background workspaces where they can be crunched in isolation.
I recommend having a look at NCrunch's project atomicity constraints, and make sure you are aware of how absolute file references work in NCrunch. It may be that you can rig something up with copied files or references to the foreground solution that might give some degree of a workaround.
I am unfamiliar with this particular framework, which makes it hard for me to give specific advice on its limitations in regards to NCrunch. However, it looks to me like the framework is designed to treat the solution as a single cohesive unit (based on the need to inject the solution directory). This sort of structure isn't something that is supported under NCrunch, because we separate projects from the solution and into background workspaces where they can be crunched in isolation.
I recommend having a look at NCrunch's project atomicity constraints, and make sure you are aware of how absolute file references work in NCrunch. It may be that you can rig something up with copied files or references to the foreground solution that might give some degree of a workaround.
Post a reply
Log in to reply.