Hello, I guess what I'm thinking is - would it be possible for an agent to self-identify a bunch of these resources to the server when connecting, or when the server polls for resources?
If you are familiar with puppet - kind of like puppet facts. Regards, -Roy *What man is a man who does not make the world better?* *- Balien of Ibelin, Kingdom of Heaven* On Mon, Jun 19, 2017 at 8:06 AM, Roy Nielsen <roy.nielse...@gmail.com> wrote: > Hello, > > I'm new to good - maybe this question is clearly answered elsewhere, but a > quick search didn't find the answer. > > If I were to say a job needs 16 Gb of memory, or 24, or 64 memory > available, I could create a tag/resource, right? What about hard drive, # > of CPUs, CPU properties, network capability, operating system, os version, > etc, etc. > > That starts to be a lot of tags/resources. > > Would it be possible to have some json or yaml describe the requirements > for a specific job, Maybe it already is available? > > Is it or could it be possible to have gocd understand an extended set of > environmental (HW/OS/compiler availability/etc) conditions when choosing an > agent to run jobs on? Using resources/tags could get complicated fast. > > Thank you, > -Roy Nielsen > > -- > You received this message because you are subscribed to a topic in the > Google Groups "go-cd" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/go-cd/LToOPUdoXgs/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > go-cd+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
