/cc @bitshiftmask might know
-
-
-
I've built some of these as internal tools, I don't have a great answer for this. I think Jenkins has a notion of resources, or tags you can filter you test targets for. Then you can have multiple test runner workers that can pick up jobs one at a time.
- Još 7 drugih odgovora
Novi razgovor -
-
-
More info What we're testing essentially an operating system, so any experience with doing hardware test coverage and resource management would probably be most relevant.
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Gitlab CI can be configured like this. You install the runner software on each hardware configuration with a concurrency of 1, tag that runner indicating its hardware configuration, then each job in your CI flow can specify required tags.
-
It's not an uncommon way to handle prod backend deployments. You have a tagged runner with concurrency 1 on single machine that has keys for your production servers, and your final deploy job has a dependency on that tag. Concurrency 1 stops simultaneous conflicting deployments.
- Još 1 odgovor
Novi razgovor -
-
-
https://autotest.github.io is the only one coming to mind. Maintenance was an issue last time I looked at it.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
