I have tried to run Bullseye with Electric Make, but running into problems.
The first time the whole build was completely serialized, because every compilation and every unit test run, modifies the same file (Bullseye coverage one).
Then I tried to put the coverage file on NFS share, which all agent hosts can see, but it seems that different hosts are seeing different versions of the file.
I asked Bullseye support and they suggest that from their point of view it should work. They use some sort of locking to control access to the file, so multiple processes can update the file.
Should it work from Electric Make point of view?
The coverage file itself is on NFS share outside of EMAKE_ROOT, so I would have expected Electric Make will not interfere with file content or locking of the file.
We are on version 9 of Electric Make.
Can emake run a cluster build under a chroot environment? 2 Answers
Long serial chain - how to make it start building earlier in the build? 1 Answer
Is there a way to give different groups priority access to resources? 2 Answers
Is there any way to designate a makefile as a "critical section" with ElectricAccelerator? 3 Answers
Can I use my build machine as an ElectricAccelerator agent host? 1 Answer
Electric Cloud powers Continuous Delivery, helping organizations developing deliver better software faster by automating and accelerating build, test, and deployment processes at scale. Industry leaders like Qualcomm, SpaceX, Cisco, GE, Gap, and E*TRADE use Electric Cloud solutions to boost DevOps productivity and Agile throughput.