Hi, I'd like to build software on Windows using vcpkg, which keeps a per-node repository of software up to date.
Given: - job A requires foo:x86 and bar:x86 in the repo - job B requires bar:x86 and bar:amd64 in the repo - job C requires foo:amd64 and bar:amd64 in the repo Requirements: - no two vcpkg invocations at the same time - no vcpkg invocation that modifies an item that is in use by a currently running job - one vcpkg repository per node Ideally, I'd like to have a declarative syntax that lets me list dependencies, and these would be turned into reader/writer locks -- writer locks for the vcpkg invocation, and reader locks for the actual build process (multiple processes can share dependencies, but they should not be modified during the build). Is there something existing that already covers this use case? Simon -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20190710161144.GA30074%40psi5.com. For more options, visit https://groups.google.com/d/optout.
