[travis-ci] dtolabs/rundeck#194 (development - 3434b35 : Greg Schueler): The build passed.
[travis-ci] Change view : https://github.com/dtolabs/rundeck/compare/9bd6f887ac06…3434b3573c7b
[travis-ci] Build details : http://travis-ci.org/dtolabs/rundeck/builds/6577988
[travis-ci] dtolabs/rundeck#196 (development - c0abc05 : Greg Schueler): The build passed.
[travis-ci] Change view : https://github.com/dtolabs/rundeck/compare/3434b3573c7b…c0abc05ba024
[travis-ci] Build details : http://travis-ci.org/dtolabs/rundeck/builds/6583661
So i think this is a bad idea, but im trying to find documentation to agree with me. Is it a Bad Idea to define the same node in multiple projects?
Im trying to find reference to only running a single job on a single node at a given time…. I thought I read it but cant find it again.
no it’s not uncommon to represent the same host in more than one project
there are a couple ways to run a job on a single node
cool. was it my imagination that thought there was some locking internal to rundeck to prevent clashing job executions?
yes, you can declare a job to allow multiple executions or not
and thats the issue
well, i think it is
if I put a common host into X projects, then each one would need a seperate job?
(ie jobs are scoped to projects)
[travis-ci] dtolabs/rundeck#198 (development - cec8720 : Greg Schueler): The build passed.
[travis-ci] Change view : https://github.com/dtolabs/rundeck/compare/c0abc05ba024…cec87202638f
[travis-ci] Build details : http://travis-ci.org/dtolabs/rundeck/builds/6585490
silk: yes, jobs and nodes are both contained within a project, so they do not interact.
right, so by putting a node into multiple projects there is no way to prevent a job clobbering another one if run from seperate projects (well, within Rundeck anyway)