That brings up another point...how does handling growth and implementing
cloud (private or public) play a part as well?
On Thursday, July 28, 2016 at 9:53:35 AM UTC-7, rqui wrote:
>
> I am seeking some advice/tips. Our group is experiencing fast growth and
> changes and I am trying to architect
Yes, we have 10+ nodes; nothing builds on the master.
On Thursday, July 28, 2016 at 1:37:29 PM UTC-7, Baptiste Mathus wrote:
>
> The question is also: do you have agents, as hinted by Tyler, or do you
> build all ze things on that sole machine.
>
> If no agent, or anyway, see also the recent
The question is also: do you have agents, as hinted by Tyler, or do you
build all ze things on that sole machine.
If no agent, or anyway, see also the recent thread:
Also, how many users do you have in your Jenkins?
On Thursday, July 28, 2016 at 11:31:42 AM UTC-7, Simona Avornicesei wrote:
>
> We have a single Jenkins master.
> Depending on the needs of each team/project, they either have one or more
> slaves/agents assigned exclusively for their jobs or
Do you only have the two teams? How do you manage the multiple nodes? Also
how many users do you have using Jenkins?
On Thursday, July 28, 2016 at 12:34:02 PM UTC-7, R Tyler Croy wrote:
>
> (replies inline)
>
> On Thu, 28 Jul 2016, rqui wrote:
>
> > I am seeking some advice/tips. Our group is
How many teams use Jenkins and how many total nodes are used?
On Thursday, July 28, 2016 at 11:31:42 AM UTC-7, Simona Avornicesei wrote:
>
> We have a single Jenkins master.
> Depending on the needs of each team/project, they either have one or more
> slaves/agents assigned exclusively for
(replies inline)
On Thu, 28 Jul 2016, rqui wrote:
> I am seeking some advice/tips. Our group is experiencing fast growth and
> changes and I am trying to architect a solution for managing it.
>
> We currently have a single master handling various types of jobs: ci,
> nightlies, releases,
We have a single Jenkins master.
Depending on the needs of each team/project, they either have one or more
slaves/agents assigned exclusively for their jobs or they share the same
agent with other projects (usually projects from the same client).
--
You received this message because you are
I am seeking some advice/tips. Our group is experiencing fast growth and
changes and I am trying to architect a solution for managing it.
We currently have a single master handling various types of jobs: ci,
nightlies, releases, personal dev builds, etc.
Using OSS, does anyone have experience
