Help needed in Gearman implementation
I am a fan of gearman since it's the only way to use multiple jenkins master . Please assist me on below - I am using gearman (server,plugin,client) & jenkins job builder to create jobs . I have two jenkins master instances & major goal is to keep both of them in sync & share the load . I have few queries - 1. Alternative to jenkins job builder , since it's tough for users to write yaml for every job they create . Any possiblity that we can use the jenkins UI to create the jobs which ultimately gets synced with the other jenkins instance . 2. When i send build request through gearman client to gearman server, only in this case it will use gearman workers to execute the build on both masters . If i use jenkins UI of one instance to build a job, it remains in queue & not shared with the other jenkins instance since i guess gearman server doesn't know about the request . I don't want to give two dashboard to the users . 3. Is there any way we can get the build logs ( Console output of the build that i ran ) on the client side i.e from where we are using the gearman client ? I understand the few things are little obvious but still i need the best way to deal with gearman . I repeat I have two jenkins master instances & major goal is to keep both of them in sync & share the load . If i am doing something wrong & there is a much better way to do this as well, please do suggest me . Thanks in advance for your help ! -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c7b2c3ee-0dc4-4068-8f26-68fd3e356cd7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Help needed in Gearman/jenkins-job-builder implementation
I am using gearman (server,plugin,client) & jenkins job builder to create jobs . I have two jenkins master instances & major goal is to keep both of them in sync & share the load . I have few queries - 1. Alternative to jenkins job builder , since it's tough for users to write yaml for every job they create . Any possiblity that we can use the jenkins UI to create the jobs which ultimately gets synced with the other jenkins instance . 2. When i send build request through gearman client to gearman server, only in this case it will use gearman workers to execute the build on both masters . If i use jenkins UI of one instance to build a job, it remains in queue & not shared with the other jenkins instance since i guess gearman server doesn't know about the request . I don't want to give two dashboard to the users . 3. Is there any way we can get the build logs ( Console output of the build that i ran ) on the client side i.e from where we are using the gearman client ? I understand the few things are little obvious but still i need the best way to deal with gearman . I repeat I have two jenkins master instances & major goal is to keep both of them in sync & share the load . If i am doing something wrong & there is a much better way to do this as well, please do suggest me . Thanks in advance for your help ! -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/faae8d06-e903-4adc-a64e-d64a9f549fde%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Job Import Plugin
Hi Guys, I am using Gearman to run the jobs to multiple jenkins master but both dashboards are different since jobs are different on both of them . I used jenkins-job-builder to keep them in sync but it's tough to generate yaml for complex jobs( specially for newcomers ) . I used jobs import plugin which is awesome for importing jobs . *How can i sync the jobs between both jenkins instances using job import plugin API ?* *For an API, could you please assist me with some set of examples ?* I will use those APIs on both jenkins instances & use cron jobs to pull & push jobs on both the servers to keep both of them in sync probably every 2 or 3 minutes . Thanks in advance for your help ! -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bf089861-e432-4f76-8c24-88ab79b7023a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Share same jenkins home directory across multiple jenkins master in AWS environment
Hi Guys, I am trying to share same home directory across multiple jenkins master in AWS environment using ELB ( Load balancer ) & EFS ( NFS server ) to keep the jenkins home in sync & share the load across multiple masters . Sometime i get an error like you have shared a home directory across multiple instances . I understand that it doesn't support that but is there any way to make this possible ? Jobs get created inside the home folder but only shows up on the instance we created the job using UI even the home is synced & contains that job on both instances . Is there any way to fix this issue ? If not then what could be the best way to use jenkins in autoscaling environment with same home directory since i don't want different jobs on the masters ? If this is not the right place to post this issue, please guide me . -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2b0b5eeb-da3a-46f5-a75d-0fc08bd5a227%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
