confirming the build before starting
Hi, I have a parameterized build which accept string as parameter . I want to show user a message empty string in the form of alert box or simply showing Not entered anything.Do you want to continue with continue button below if he click on build button without entering string in text box. If he enters the string then i will start my build . How i can achieve this ? Any help would be greatly appreciated -- 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. For more options, visit https://groups.google.com/d/optout.
Re: LDAP Plugin authentication issue
,Hi Wanted to update - I have finally solved this issue I switched to Active Directory plugin + Matrix Authorization Strategy Plugin http://wiki.jenkins-ci.org/display/JENKINS/Matrix+Authorization+Strategy+Plugin Basically, you need help from your IT/Netwrork plp to know the Bind DN and Bind Password Use the matrix plugin to actually do something with the authorization and decide who can do what Many thanks Gil בתאריך יום רביעי, 29 באוקטובר 2014 13:04:44 UTC+2, מאת maciej: Gil Br (2014-10-29 08:51): Hi, Your answer relates to Active Directory, I'm using LDAP 389 on Linux. Any other idea? Depending on your LDAP configuration you should use correct search base and search filter... But I'm not sure how would you use NT password if LDAP is on Linux? Or what do you mean by NT? I though you meant Windows NT password (hence I mentioned Active Directory which is kind of built in Windows domain). Regards, Nux -- 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. For more options, visit https://groups.google.com/d/optout.
Cancelling a build doesn't seem to send a TERM signal to the running process
I have enabled xtrace in my shell script, which installs some files in xinetd and removes them when it exits, via an exit handler. My handlers use some exit handler functions that are included in all my build scripts. However, I've noticed clean up is not running for this particular script when I manually cancel the build. The output from the script just stops and none of the clean-up is executed, which would removed the xinetd configuration. Is Jenkins signalling its child processes to stop or is it KILLing them? -- 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. For more options, visit https://groups.google.com/d/optout.
AW: confirming the build before starting
Hi,
I don't think this can be easily done. You would need a parameter plugin that
runs a validator on its text field, and the validator would have to write
Javascript to its error message area.
A build run itself is not meant to be inveractive, you can't pause it to query
for some kind of user confirmation or any other interaction. So once the build
is running you've got to work with what you've got.
The only approach I can think of: Preset a default value like CHANGE_ME for
you text field and use flashy HTML markup in the parameter description to tell
your users to really change the field content.
As first build step of your job run a shell or batch step that makes sure that
your parameter is different from CHANGE_ME. Here's what I use to protect a
deployment job from accidental triggering, with a checkbox parameter for the
job:
if ! [[ ${CONFIRM_THE_DEPLOYMENT} == true ]]
then
echo Please confirm your deployment order by setting the checkbox!;echo
; exit 22
fi
I generally like the idea - some kind of validated parameter plugin than only
enables the build button if all parameters are in their expected ranges, not
empty etc. But then again this really is something you would expect your users
to take care of themselves. Just make sure to catch all input that might cause
damage.
Regards,
Felix
Von: jenkinsci-users@googlegroups.com [jenkinsci-users@googlegroups.com] im
Auftrag von niraj nandane [niraj.nand...@gmail.com]
Gesendet: Mittwoch, 12. November 2014 11:44
An: jenkinsci-users@googlegroups.com
Betreff: confirming the build before starting
Hi,
I have a parameterized build which accept string as parameter . I want to show
user a message empty string in the form of alert box or simply showing Not
entered anything.Do you want to continue with continue button below if he
click on build button without entering string in text box. If he enters the
string then i will start my build . How i can achieve this ?
Any help would be greatly appreciated
--
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.commailto:jenkinsci-users+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
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: confirming the build before starting
Hi,
I got one of the stackoverflow link which is doing exactly what i want. But
it is not working in my env.Could you please figure out this?
http://stackoverflow.com/questions/10865538/how-to-submit-jenkins-job-via-rest-api
On Wed, Nov 12, 2014 at 5:46 PM, Felix Nawroth f.nawr...@bigpoint.net
wrote:
Hi,
I don't think this can be easily done. You would need a parameter plugin
that runs a validator on its text field, and the validator would have to
write Javascript to its error message area.
A build run itself is not meant to be inveractive, you can't pause it to
query for some kind of user confirmation or any other interaction. So once
the build is running you've got to work with what you've got.
The only approach I can think of: Preset a default value like CHANGE_ME
for you text field and use flashy HTML markup in the parameter description
to tell your users to really change the field content.
As first build step of your job run a shell or batch step that makes sure
that your parameter is different from CHANGE_ME. Here's what I use to
protect a deployment job from accidental triggering, with a checkbox
parameter for the job:
if ! [[ ${CONFIRM_THE_DEPLOYMENT} == true ]]
then
echo Please confirm your deployment order by setting the
checkbox!;echo ; exit 22
fi
I generally like the idea - some kind of validated parameter plugin than
only enables the build button if all parameters are in their expected
ranges, not empty etc. But then again this really is something you would
expect your users to take care of themselves. Just make sure to catch all
input that might cause damage.
Regards,
Felix
--
*Von:* jenkinsci-users@googlegroups.com [jenkinsci-users@googlegroups.com]
im Auftrag von niraj nandane [niraj.nand...@gmail.com]
*Gesendet:* Mittwoch, 12. November 2014 11:44
*An:* jenkinsci-users@googlegroups.com
*Betreff:* confirming the build before starting
Hi,
I have a parameterized build which accept string as parameter . I want to
show user a message empty string in the form of alert box or simply
showing Not entered anything.Do you want to continue with continue button
below if he click on build button without entering string in text box. If
he enters the string then i will start my build . How i can achieve this ?
Any help would be greatly appreciated
--
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.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups Jenkins Users group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-users/wE0j_zojMQY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Thanks and regards--
Niraj Nandane(Vit pune)
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: confirming the build before starting
Hi,
I got one of the stackoverflow link which is doing exactly what i want. But
it is not working in my env.Could you please figure out this?
http://stackoverflow.com/questions/10865538/how-to-submit-jenkins-job-via-rest-api
On Wednesday, November 12, 2014 5:47:07 PM UTC+5:30, Felix Nawroth wrote:
Hi,
I don't think this can be easily done. You would need a parameter plugin
that runs a validator on its text field, and the validator would have to
write Javascript to its error message area.
A build run itself is not meant to be inveractive, you can't pause it to
query for some kind of user confirmation or any other interaction. So once
the build is running you've got to work with what you've got.
The only approach I can think of: Preset a default value like CHANGE_ME
for you text field and use flashy HTML markup in the parameter description
to tell your users to really change the field content.
As first build step of your job run a shell or batch step that makes sure
that your parameter is different from CHANGE_ME. Here's what I use to
protect a deployment job from accidental triggering, with a checkbox
parameter for the job:
if ! [[ ${CONFIRM_THE_DEPLOYMENT} == true ]]
then
echo Please confirm your deployment order by setting the
checkbox!;echo ; exit 22
fi
I generally like the idea - some kind of validated parameter plugin than
only enables the build button if all parameters are in their expected
ranges, not empty etc. But then again this really is something you would
expect your users to take care of themselves. Just make sure to catch all
input that might cause damage.
Regards,
Felix
--
*Von:* jenkins...@googlegroups.com javascript: [
jenkins...@googlegroups.com javascript:] im Auftrag von niraj nandane
[niraj@gmail.com javascript:]
*Gesendet:* Mittwoch, 12. November 2014 11:44
*An:* jenkins...@googlegroups.com javascript:
*Betreff:* confirming the build before starting
Hi,
I have a parameterized build which accept string as parameter . I want to
show user a message empty string in the form of alert box or simply
showing Not entered anything.Do you want to continue with continue button
below if he click on build button without entering string in text box. If
he enters the string then i will start my build . How i can achieve this ?
Any help would be greatly appreciated
--
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-use...@googlegroups.com javascript:.
For more options, visit https://groups.google.com/d/optout.
--
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.
For more options, visit https://groups.google.com/d/optout.
Master Slave - Jenkins
HI All, Currently for our Build , automation test execution , we use Jenkins. The current architecture doesn't scales well with respect to distributing test suites equally to the nodes and SUT's. So to get started with new architecture the first question is: 1. Can we have multiple masters in Single Instance of Jenkins? Scenario we are thinking off is : 1 Master Jenkins , 'n slave BSD machines for test executions and 'n SUT;s to the Master Jenkins . Similarly we can have multiple masters and same infrastructure for multiple release executions. IF the above question is doable , then i will have set of preceding questions will add up. Thanks and Looking for a positive feedback Sandeep -- 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. For more options, visit https://groups.google.com/d/optout.
RE: Master Slave - Jenkins
There is one master “slave” node, but you can set the number of executors on it like any other. I set up one slave node for each SUT, each node with one executor, and have that node run the tests. Anything that is done to the SUT must be done through the node, so Jenkins naturally prevents multiple jobs from interacting with the SUT simultaneously. These nodes are on dedicated Jenkins machines, not the SUTs themselves (this way, you don’t need to install test software on the SUT), but they each have environment variables (such as the DNS name of the SUT) set so that the tests know which SUT to run against. Actual builds and unit tests (which don’t need an SUT) are run on a different set of nodes. --Rob From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of sandeep s Sent: Wednesday, November 12, 2014 7:55 AM To: jenkinsci-users@googlegroups.com Subject: Master Slave - Jenkins HI All, Currently for our Build , automation test execution , we use Jenkins. The current architecture doesn't scales well with respect to distributing test suites equally to the nodes and SUT's. So to get started with new architecture the first question is: 1. Can we have multiple masters in Single Instance of Jenkins? Scenario we are thinking off is : 1 Master Jenkins , 'n slave BSD machines for test executions and 'n SUT;s to the Master Jenkins . Similarly we can have multiple masters and same infrastructure for multiple release executions. IF the above question is doable , then i will have set of preceding questions will add up. Thanks and Looking for a positive feedback Sandeep -- 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.commailto:jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. Click herehttps://www.mailcontrol.com/sr/G9Cd25!tqWLGX2PQPOmvUmkxeMeR4!Fm8ic!LfLuQHNmKcTtnGPHwAcHAjuCZGDyDZBLv8O0BTQNCU1!U1Tbvw== to report this email as spam. This e-mail and the information, including any attachments it contains, are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message. Thank you. Please consider the environment before printing this email. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: confirming the build before starting
What exactly didn't work about the solution you got from stack overflow? Are you creating a custom web service for submitting the builds from, or perhaps hosting an HTML page on the Jenkins server for this? -- 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. For more options, visit https://groups.google.com/d/optout.
Specs for new Master server
I have searched the archives and don't see a direct answer to this question. I apologize if this has already been asked and answered. My team currently runs a few Jenkins stand-alone build servers, lots of jobs each, some CI jobs, not a lot of concurrency in builds, but some. I have been asked to migrate our environment to a master/slave setup so the job management can be run from one server. My questions is this: what kind of hardware would a master-only machine need to be successful? The current stand-alone servers will become the slaves. So here are the questions I am starting with: - It seems from what I have read in this and other forums that it is a good idea to have one CPU core per executor. Is this true for the master as well as the server doing the builds? Or can we scale back? - I have also read that the master can become I/O bound while moving the logs and build results around. (I think I have that right but some threads suggest that Jenkins can become CPU bound as a result of being I/O bound, an interaction that I don't fully understand.) The network backbone isn't an issue but I can spec out a variety of different storage solutions. I would obviously like to avoid spending money on storage we don't need but I need to build something that will function. - How much RAM should this master-only machine have? - All of our servers are virtual. That helps in that they can be rescaled if needed, but are there any special considerations that a virtual master introduces that I should know about? - Is there anything that I should be thinking about when converting the stand-alone servers to slaves? I have already modeled the process of getting a Jenkins server to be both a stand-alone server and a slave so that I can do the migration without bringing the servers down. That works fine. But is there anything about being a slave server that would change the system requirements? I know I haven't provided enough details to come up with a spec, and that is sort of intentional. I hope to learn instead how to do the analysis, what the tradeoffs are, what the design considerations are, etc. so I can build the spec. This won't be the last time I have to visit this environment and I would like to build the knowledge and skills necessary to be able to manage it. Thanks for any suggestions! ~ Dave -- 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. For more options, visit https://groups.google.com/d/optout.
RE: Specs for new Master server
Dave, I am not as informed as others in this group, but my experience has been that the master does very little work as compared to the slaves. Yes, build logs and archived files are uploaded from a slave to the master, but I have not run into any issues with IO performance. I run a Windows master as a VM running Server 2008 R2 Enterprise, 16 Gb RAM, 4 CPUs, and a 250G disk. I do have to monitor the disk usage by setting build retention values and sizes of artifacts archived. We run 22 slaves (Mac and Windows) and perhaps another 20 on again, off again slaves and, I don’t know, 100’s of jobs. You will need to set executors numbers on your new slave build machines to match their capacity. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Brooks Sent: Wednesday, November 12, 2014 8:44 AM To: jenkinsci-users@googlegroups.com Subject: Specs for new Master server I have searched the archives and don't see a direct answer to this question. I apologize if this has already been asked and answered. My team currently runs a few Jenkins stand-alone build servers, lots of jobs each, some CI jobs, not a lot of concurrency in builds, but some. I have been asked to migrate our environment to a master/slave setup so the job management can be run from one server. My questions is this: what kind of hardware would a master-only machine need to be successful? The current stand-alone servers will become the slaves. So here are the questions I am starting with: * It seems from what I have read in this and other forums that it is a good idea to have one CPU core per executor. Is this true for the master as well as the server doing the builds? Or can we scale back? * I have also read that the master can become I/O bound while moving the logs and build results around. (I think I have that right but some threads suggest that Jenkins can become CPU bound as a result of being I/O bound, an interaction that I don't fully understand.) The network backbone isn't an issue but I can spec out a variety of different storage solutions. I would obviously like to avoid spending money on storage we don't need but I need to build something that will function. * How much RAM should this master-only machine have? * All of our servers are virtual. That helps in that they can be rescaled if needed, but are there any special considerations that a virtual master introduces that I should know about? * Is there anything that I should be thinking about when converting the stand-alone servers to slaves? I have already modeled the process of getting a Jenkins server to be both a stand-alone server and a slave so that I can do the migration without bringing the servers down. That works fine. But is there anything about being a slave server that would change the system requirements? I know I haven't provided enough details to come up with a spec, and that is sort of intentional. I hope to learn instead how to do the analysis, what the tradeoffs are, what the design considerations are, etc. so I can build the spec. This won't be the last time I have to visit this environment and I would like to build the knowledge and skills necessary to be able to manage it. Thanks for any suggestions! ~ Dave -- 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.commailto:jenkinsci-users+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 Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: Specs for new Master server
If you move most/all of the actual jobs off to slave nodes on other machines, then the Jenkins server host needs to: · Interact with the user (minimal hardware requirements if your users don’t use auto-refresh; auto-refresh could greatly increase CPU needs) · Retrieve data, artifacts, and logs from the slave machines (needs good network connectivity and large, fast storage capacity) · Hold data for every build (but not artifacts and logs) in core (requires great gobs of memory) You certainly don’t need one core per slave executor on the master, unless you expect all your jobs to be “chatty” all the time. Generally, capturing the data, logs, and artifacts from a build requires one or two orders of magnitude less CPU time than actually running the build. You’re likely to get bigger speed gains by increasing the speed of your disk than that of your CPU. Every build that your Jenkins server “remembers” will have its data stored on disk and in memory, and its artifacts and logs will remain on disk until and unless requested by a user or another job. If this was the whole story, then memory and disk needs would increase without bounds. However, you can set jobs to only remember a certain number of builds and/or a certain number of days of builds. You can separately limit how many logs and artifacts it will keep. Use this feature judiciously, preferably on every job you define. If you have a need to store results “since the beginning of time”, you have a big problem. At a previous job, I had that and had to parse my build logs and write the data required to a database, only using Jenkins to run builds and not to analyze the results. I currently run Jenkins servers and clients on VMs, and don’t have any problems with them. This might make it easier to do whole-host backups of your Jenkins system (if you have the space for that) for disaster recovery. Any combined master/slave machine can be converted to a slave-only machine without more hardware; you might even be able to increase the number of executors. In terms of server CPU and network use, adding executors to an existing node is slightly less expensive than adding nodes. Finally, you have said that you are running a small number of Jenkins standalone servers. I would suspect that a master-only machine needs no more CPU or disk than a standalone host, and may just need more disk capacity. You should be able to sacrifice one standalone system to serve as the master, and the rest of them can be converted to slave-only hosts. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Brooks Sent: Wednesday, November 12, 2014 8:44 AM To: jenkinsci-users@googlegroups.com Subject: Specs for new Master server I have searched the archives and don't see a direct answer to this question. I apologize if this has already been asked and answered. My team currently runs a few Jenkins stand-alone build servers, lots of jobs each, some CI jobs, not a lot of concurrency in builds, but some. I have been asked to migrate our environment to a master/slave setup so the job management can be run from one server. My questions is this: what kind of hardware would a master-only machine need to be successful? The current stand-alone servers will become the slaves. So here are the questions I am starting with: * It seems from what I have read in this and other forums that it is a good idea to have one CPU core per executor. Is this true for the master as well as the server doing the builds? Or can we scale back? * I have also read that the master can become I/O bound while moving the logs and build results around. (I think I have that right but some threads suggest that Jenkins can become CPU bound as a result of being I/O bound, an interaction that I don't fully understand.) The network backbone isn't an issue but I can spec out a variety of different storage solutions. I would obviously like to avoid spending money on storage we don't need but I need to build something that will function. * How much RAM should this master-only machine have? * All of our servers are virtual. That helps in that they can be rescaled if needed, but are there any special considerations that a virtual master introduces that I should know about? * Is there anything that I should be thinking about when converting the stand-alone servers to slaves? I have already modeled the process of getting a Jenkins server to be both a stand-alone server and a slave so that I can do the migration without bringing the servers down. That works fine. But is there anything about being a slave server that would change the system requirements? I know I haven't provided enough details to come up with a spec, and that is sort of intentional. I hope to learn instead how to do the analysis, what the tradeoffs are, what the design considerations are, etc. so I can
Re: Specs for new Master server
Hi Rob, rginga - Excellent information, exactly what I was hoping to see. For the RAM requirements, would it be safe to estimate the required RAM on the master by looking at the combined utilization of the build servers? For instance, I see that the Jenkins and Java processes combined are using about 8GB of ram on one of our build servers. Would this this translate directly to the master utilization? So just add up the utilization for the build servers and that is the baseline for the master? If so then this machine is going to need TONS of ram. Or I am going to have to start pruning how much Jenkins 'remembers' about builds. That may not go over very well with the teams. Thanks, ~ Dave On Wednesday, November 12, 2014 9:06:00 AM UTC-5, Rob Mandeville wrote: If you move most/all of the actual jobs off to slave nodes on other machines, then the Jenkins server host needs to: · Interact with the user (minimal hardware requirements if your users don’t use auto-refresh; auto-refresh could greatly increase CPU needs) · Retrieve data, artifacts, and logs from the slave machines (needs good network connectivity and large, fast storage capacity) · Hold data for every build (but not artifacts and logs) in core (requires great gobs of memory) You certainly don’t need one core per slave executor on the master, unless you expect all your jobs to be “chatty” all the time. Generally, capturing the data, logs, and artifacts from a build requires one or two orders of magnitude less CPU time than actually running the build. You’re likely to get bigger speed gains by increasing the speed of your disk than that of your CPU. Every build that your Jenkins server “remembers” will have its data stored on disk and in memory, and its artifacts and logs will remain on disk until and unless requested by a user or another job. If this was the whole story, then memory and disk needs would increase without bounds. However, you can set jobs to only remember a certain number of builds and/or a certain number of days of builds. You can separately limit how many logs and artifacts it will keep. Use this feature judiciously, preferably on every job you define. If you have a need to store results “since the beginning of time”, you have a big problem. At a previous job, I had that and had to parse my build logs and write the data required to a database, only using Jenkins to run builds and not to analyze the results. I currently run Jenkins servers and clients on VMs, and don’t have any problems with them. This might make it easier to do whole-host backups of your Jenkins system (if you have the space for that) for disaster recovery. Any combined master/slave machine can be converted to a slave-only machine without more hardware; you might even be able to increase the number of executors. In terms of server CPU and network use, adding executors to an existing node is slightly less expensive than adding nodes. Finally, you have said that you are running a small number of Jenkins standalone servers. I would suspect that a master-only machine needs no more CPU or disk than a standalone host, and may just need more disk capacity. You should be able to sacrifice one standalone system to serve as the master, and the rest of them can be converted to slave-only hosts. *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *David Brooks *Sent:* Wednesday, November 12, 2014 8:44 AM *To:* jenkins...@googlegroups.com javascript: *Subject:* Specs for new Master server I have searched the archives and don't see a direct answer to this question. I apologize if this has already been asked and answered. My team currently runs a few Jenkins stand-alone build servers, lots of jobs each, some CI jobs, not a lot of concurrency in builds, but some. I have been asked to migrate our environment to a master/slave setup so the job management can be run from one server. My questions is this: what kind of hardware would a master-only machine need to be successful? The current stand-alone servers will become the slaves. So here are the questions I am starting with: - It seems from what I have read in this and other forums that it is a good idea to have one CPU core per executor. Is this true for the master as well as the server doing the builds? Or can we scale back? - I have also read that the master can become I/O bound while moving the logs and build results around. (I think I have that right but some threads suggest that Jenkins can become CPU bound as a result of being I/O bound, an interaction that I don't fully understand.) The network backbone isn't an issue but I can spec out a variety of different storage solutions. I would obviously like to avoid spending
P4 plugin jenkins issue
I’ve a new challenge, figuring out how to use perforce; specifically to run against our Jenkins CI system. When I fire off my P4test job (using the P4 plugin) I get the following console output. [EnvInject] - Loading node environment variables. Building remotely on s in workspace /jenkins/workspace/p4ce Connected to server: perforce.server.com:1666 Connected to client: jenkins-machine-p4ce SCM Task: cleanup workspace: jenkins-machine-p4ce SCM Task: reverting all pending and shelved revisions. ... [list] = revert P4JAVA: Path 'D:/jenkins/workspace/p4ce/...' is not under client's root '/jenkins/workspace/p4ce'. ERROR: Unable to update workspace: hudson.AbortException: P4JAVA: Error(s) Finishedhttp://stacktrace.jenkins-ci.org/search?query=Finished: FAILURE So, does anyone use the P4 plugin and have any guidance/comments they can provide? I’m not hugely familiar with p4ce, so that may be a contributing factor… Jenkins 1.532.2.2 and P4Plugin 1.0.16 Jenkins is configured with a RHEL master; windows 2k8 and RHEL slaves; the job is running on the windows slave(supposedly). dD This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments. Internet communications are not guaranteed to be secure or virus-free. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group. Barclays Bank PLC. Registered in England and Wales (registered no. 1026167). Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom. Barclays Bank PLC is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority (Financial Services Register No. 122702). -- 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. For more options, visit https://groups.google.com/d/optout.
RE: P4 plugin jenkins issue
We use Jenkins and the Perforce plugin (Jenkins 1.565.2 P4 1.3.26) What are you using P4JAVA for? From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of david.doug...@barclays.com Sent: Wednesday, November 12, 2014 11:04 AM To: jenkinsci-users@googlegroups.com Subject: P4 plugin jenkins issue I’ve a new challenge, figuring out how to use perforce; specifically to run against our Jenkins CI system. When I fire off my P4test job (using the P4 plugin) I get the following console output. [EnvInject] - Loading node environment variables. Building remotely on s in workspace /jenkins/workspace/p4ce Connected to server: perforce.server.com:1666 Connected to client: jenkins-machine-p4ce SCM Task: cleanup workspace: jenkins-machine-p4ce SCM Task: reverting all pending and shelved revisions. ... [list] = revert P4JAVA: Path 'D:/jenkins/workspace/p4ce/...' is not under client's root '/jenkins/workspace/p4ce'. ERROR: Unable to update workspace: hudson.AbortException: P4JAVA: Error(s) Finishedhttp://stacktrace.jenkins-ci.org/search?query=Finished: FAILURE So, does anyone use the P4 plugin and have any guidance/comments they can provide? I’m not hugely familiar with p4ce, so that may be a contributing factor… Jenkins 1.532.2.2 and P4Plugin 1.0.16 Jenkins is configured with a RHEL master; windows 2k8 and RHEL slaves; the job is running on the windows slave(supposedly). dD This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments. Internet communications are not guaranteed to be secure or virus-free. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group. Barclays Bank PLC. Registered in England and Wales (registered no. 1026167). Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom. Barclays Bank PLC is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority (Financial Services Register No. 122702). -- 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.commailto:jenkinsci-users+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 Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: confirming the build before starting
Or some link which will decribe what is there did on posted stack overflow link ? On Nov 12, 2014 10:16 PM, niraj nandane niraj.nand...@gmail.com wrote: Could you please post a code to add continue button only ? On Nov 12, 2014 7:07 PM, Craig Phillips iwonbig...@gmail.com wrote: What exactly didn't work about the solution you got from stack overflow? Are you creating a custom web service for submitting the builds from, or perhaps hosting an HTML page on the Jenkins server for this? -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/wE0j_zojMQY/unsubscribe . To unsubscribe from this group and all its topics, send an email to jenkinsci-users+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 Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: confirming the build before starting
Could you please post a code to add continue button only ? On Nov 12, 2014 7:07 PM, Craig Phillips iwonbig...@gmail.com wrote: What exactly didn't work about the solution you got from stack overflow? Are you creating a custom web service for submitting the builds from, or perhaps hosting an HTML page on the Jenkins server for this? -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/wE0j_zojMQY/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+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 Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
How long does it take Jenkins to realize slaves are offline?
Hi, For our nightly testing, we revert slaves to a VMware snapshot before starting jobs. Most of the time this works, but sometimes the first job after the revert job fails. The weird part is that a downstream job that runs on the same slave will often succeed less than two minutes after the upstream failure. I'm guessing that Jenkins thinks the slave is still online and rejecting the connection and/or not connecting. My idea for a work-around is to add a snooze time after the revert. This way, Jenkins can figure out that the slave is offline. So, what amount of time is necessary for Jenkins to realize that a slave is offline? 5, 10, ?? minutes? Note that for non-windows slaves, I'm not disconnecting the slave prior to revert. I had a good reason for doing this at the time, but can not remember it. Below are some snippets of console output showing my situation. Running Jenkins ver. 1.509.1 Thanks, Dale http://jenkins/job/Job-A/549/console 21:45:38 NOT Disconnecting Hudson client before powering on machine: AT03-cent5. (non-Windows slave) 21:45:38 Revert vm 'AT03-cent5' to snapshot '2014-11-03'. 21:45:38 Power on vm AT03-cent5. 21:45:38 Spent 4.327958 seconds powering on. 21:45:38 Snooze an extra 180 seconds to allow boot completion... snip 21:48:40 Finished: SUCCESS - http://jenkins/job/Job-B/1109/console - 21:48:46 Started by upstream project Job-A build number 549 snip 21:48:49 Building remotely on AT03-cent5 in workspace /opt/hudson/workspace/Job-A 21:51:28 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel snip http://jenkins/job/Job-C/740/consoleFull 21:52:51 Started by upstream project Job-B build number 1109 21:52:54 Building remotely on AT03-cent5 in workspace /opt/hudson/workspace/Job-C snip 22:35:13 Finished: SUCCESS -- Dale Quigg Revolution Analytics, Inc. -- Revolution R Plus http://revolutionanalytics.com/plus Subscribe to Technical Support Indemnification for R -- 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. For more options, visit https://groups.google.com/d/optout.
Question on running simultaneous jobs in Jenkins
Hi All, I have a requirement where in I have Prameterized build project which acts as a master project. This job does a lot of pre scm steps after which is supposed to initiate other jobs simultanously based on a condition for which I am using the conditinal build srep plugin. But, when I have more than one condition to check and initiate the jobs based on both the conditions simultaneously, I am not able to proceed on it. So, lets say we have: condition A - triggers jobA, jobB condition B - triggers jobC, jobD What I would like is to execute these conditions at the same time so that all the jobs start together? Can anyone please help me achieve this? This will be really appreciated. Thanks, Alok -- 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. For more options, visit https://groups.google.com/d/optout.
RE: How long does it take Jenkins to realize slaves are offline?
I was just looking at out revert job. This is what we found works pretty reliably. We produce snapshots in powered down state. Issue the revert to snapshot command This waits for Jenkins to miss the slave java -jar C:\Tools\BuildTools\jenkins-cli.jar -s http://.net:8082/ wait-node-offline %VMNAME% power up the VM this waits for Jenkins to see the slave again java -jar C:\Tools\BuildTools\jenkins-cli.jar -s http://xx.net:8082/ wait-node-online %VMNAME% From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Dale Quigg Sent: Wednesday, November 12, 2014 12:39 PM To: jenkinsci-users@googlegroups.com Subject: How long does it take Jenkins to realize slaves are offline? Hi, For our nightly testing, we revert slaves to a VMware snapshot before starting jobs. Most of the time this works, but sometimes the first job after the revert job fails. The weird part is that a downstream job that runs on the same slave will often succeed less than two minutes after the upstream failure. I'm guessing that Jenkins thinks the slave is still online and rejecting the connection and/or not connecting. My idea for a work-around is to add a snooze time after the revert. This way, Jenkins can figure out that the slave is offline. So, what amount of time is necessary for Jenkins to realize that a slave is offline? 5, 10, ?? minutes? Note that for non-windows slaves, I'm not disconnecting the slave prior to revert. I had a good reason for doing this at the time, but can not remember it. Below are some snippets of console output showing my situation. Running Jenkins ver. 1.509.1 Thanks, Dale http://jenkins/job/Job-A/549/console 21:45:38 NOT Disconnecting Hudson client before powering on machine: AT03-cent5. (non-Windows slave) 21:45:38 Revert vm 'AT03-cent5' to snapshot '2014-11-03'. 21:45:38 Power on vm AT03-cent5. 21:45:38 Spent 4.327958 seconds powering on. 21:45:38 Snooze an extra 180 seconds to allow boot completion... snip 21:48:40 Finished: SUCCESS - http://jenkins/job/Job-B/1109/console - 21:48:46 Started by upstream project Job-A build number 549 snip 21:48:49 Building remotely on AT03-cent5 in workspace /opt/hudson/workspace/Job-A 21:51:28 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel snip http://jenkins/job/Job-C/740/consoleFull 21:52:51 Started by upstream project Job-B build number 1109 21:52:54 Building remotely on AT03-cent5 in workspace /opt/hudson/workspace/Job-C snip 22:35:13 Finished: SUCCESS -- Dale Quigg Revolution Analytics, Inc. Revolution R Plushttp://revolutionanalytics.com/plus Subscribe to Technical Support Indemnification for R -- 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.commailto:jenkinsci-users+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 Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins slave terminated error message
im seeing this same error and trying to diagnose the issue. in your response you mentioned you tried the trick before restarting the web server and resolving the issue. What was the trick? On Thursday, May 8, 2014 8:42:25 AM UTC-7, Lily Fu wrote: I setup a Jenkins slave (windows server 2008 R2 Standard, with Java 7 update 55JRE), and was running successfully for a week or so. Today, I had trouble to start the slave, I got the following error message when I tried to start the slave From command line ( from web browser, I got Jenkins slave Terminated): What is the problem? Thanks! Lily Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Jenkinsjava -jar slave.jar -jnlpUrl http://jenkinsmasterhost:8080/jenkins/compute r/TestNewNodeforPowerShell/slave-agent.jnlp -secret ………. May 08, 2014 11:20:30 AM hudson.remoting.jnlp.Main$CuiListener init INFO: Jenkins agent is running in headless mode. May 08, 2014 11:20:30 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [http:// jenkinsmasterhost:8080/jenkins/] May 08, 2014 11:20:30 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to jenkinsmasterhost:54807 May 08, 2014 11:20:30 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking May 08, 2014 11:20:30 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected May 08, 2014 11:20:30 AM hudson.remoting.SynchronousCommandTransport$ReaderThrea d run SEVERE: I/O error in channel channel java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(Synchron ousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Sourc e) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport. java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(Synchron ousCommandTransport.java:48) May 08, 2014 11:20:30 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Terminated -- 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. For more options, visit https://groups.google.com/d/optout.
RE: Specs for new Master server
There are some hairy reasons for running a job on the master, specifically if you need to mess with Jenkins internals. If you don't need to do that (and if you have to ask, you don't), just reduce the number of executors on the master node to zero and see what breaks ;^. Also (and you probably know this) you may have to explicitly set the memory settings on the JVM as well as the VM; Java won't take all your memory by default, and you might want to leave a GB or so free so that the OS can do its OS-y things. Basically, if the JVM gives an out of memory complaint, think about the JVM settings first--adding 64GB to your host won't help if Java is only taking 4GB of it. --Rob -Original Message- From: Les Mikesell [mailto:lesmikes...@gmail.com] Sent: Wednesday, November 12, 2014 12:12 PM To: jenkinsci-users Cc: Rob Mandeville Subject: Re: Specs for new Master server On Wed, Nov 12, 2014 at 8:21 AM, David Brooks dkbro...@gmail.com wrote: Hi Rob, rginga - Excellent information, exactly what I was hoping to see. For the RAM requirements, would it be safe to estimate the required RAM on the master by looking at the combined utilization of the build servers? For instance, I see that the Jenkins and Java processes combined are using about 8GB of ram on one of our build servers. Would this this translate directly to the master utilization? So just add up the utilization for the build servers and that is the baseline for the master? If so then this machine is going to need TONS of ram. Or I am going to have to start pruning how much Jenkins 'remembers' about builds. That may not go over very well with the teams. RAM use will have 'something' to do with the total number of jobs and the number of builds retained for each, but won't be equivalent to adding the whole JVM usage across multiple machines. But if you are using VMs you shouldn't have to be that precise in your initial setup as long as you don't overcommit the physical host. I'd just pick one of the existing servers as the master, move the jobs there and connect the others as slaves. You can do that piecemeal and adjust resources if you see a problem. And I'd recommend not running any jobs on the master itself, just on general principles. -- Les Mikesell lesmikes...@gmail.com Click https://www.mailcontrol.com/sr/o!P5to5kZQnGX2PQPOmvUjg7ce8j6mWJPVy6vlyKvt9qEDX2TVKozQAM3OsLei9cDZBLv8O0BTTBcfXS4znW5Q== to report this email as spam. -Original Message- From: Les Mikesell [mailto:lesmikes...@gmail.com] Sent: Wednesday, November 12, 2014 12:12 PM To: jenkinsci-users Cc: Rob Mandeville Subject: Re: Specs for new Master server On Wed, Nov 12, 2014 at 8:21 AM, David Brooks dkbro...@gmail.com wrote: Hi Rob, rginga - Excellent information, exactly what I was hoping to see. For the RAM requirements, would it be safe to estimate the required RAM on the master by looking at the combined utilization of the build servers? For instance, I see that the Jenkins and Java processes combined are using about 8GB of ram on one of our build servers. Would this this translate directly to the master utilization? So just add up the utilization for the build servers and that is the baseline for the master? If so then this machine is going to need TONS of ram. Or I am going to have to start pruning how much Jenkins 'remembers' about builds. That may not go over very well with the teams. RAM use will have 'something' to do with the total number of jobs and the number of builds retained for each, but won't be equivalent to adding the whole JVM usage across multiple machines. But if you are using VMs you shouldn't have to be that precise in your initial setup as long as you don't overcommit the physical host. I'd just pick one of the existing servers as the master, move the jobs there and connect the others as slaves. You can do that piecemeal and adjust resources if you see a problem. And I'd recommend not running any jobs on the master itself, just on general principles. -- Les Mikesell lesmikes...@gmail.com Click https://www.mailcontrol.com/sr/o!P5to5kZQnGX2PQPOmvUjg7ce8j6mWJPVy6vlyKvt9qEDX2TVKozQAM3OsLei9cDZBLv8O0BTTBcfXS4znW5Q== to report this email as spam. This e-mail and the information, including any attachments it contains, are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message. Thank you. Please consider the environment before printing this email. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from
Re: Specs for new Master server
On Wed, Nov 12, 2014 at 12:59 PM, Rob Mandeville rmandevi...@dekaresearch.com wrote: There are some hairy reasons for running a job on the master, specifically if you need to mess with Jenkins internals. If you don't need to do that (and if you have to ask, you don't), just reduce the number of executors on the master node to zero and see what breaks ;^. I'm not messing with jenkins internals in jobs, but I thought a 'system' groovy script could do that from a slave anyway. Is that not the case? I did at one point set up an executor on the master with the intent of forcing build_flow jobs there but haven't used it yet. All of our jobs are restricted by label so nothing runs there. Also (and you probably know this) you may have to explicitly set the memory settings on the JVM as well as the VM; Java won't take all your memory by default, and you might want to leave a GB or so free so that the OS can do its OS-y things. Basically, if the JVM gives an out of memory complaint, think about the JVM settings first--adding 64GB to your host won't help if Java is only taking 4GB of it. I never understand how to interpret the way 'top' shows java processes. Mine shows 2.3g as RES for jenkins but it also shows 4.9g as SWAP for the process while at the same time showing 0 Swap used in the global part. Does that mean it has memmap'd some other file but not paged it in - or is it in the 'casched' portion of swap? -- Les Mikesell lesmikes...@gmail.com -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Implementing Email-ext plugin
Awesome! Thanks for that! Makes sense that you can specify the template in specific jobs. For storing the templates, can the be stored in our build privately similar to how we store our own unit/int tests? Or does it have to be done on the home side of things? - Reason i ask is due to some users not having admin access. On Tuesday, November 11, 2014 5:12:04 PM UTC-8, slide wrote: I don't know anything about dotci, but you can have different templates for different jobs easily. The templates need to be put in either the config file provider or in JENKINS_HOME/email-templates. You can specify the template in the specific jobs. On Tue, Nov 11, 2014, 17:49 Jordan de Geus jordan...@gmail.com javascript: wrote: Hey everyone! My company is currently using Dotci/Jenkins for our CI setup. I am trying to figureout what is needed to edit the automated emails for failures to contain information regarding what exactly failed. I've been browsing through the email-ext plugin page for some time now and can't really figure out what is needed to really make use of this plugin so here i am with a few questions to everyone! Once the plugin is installed on our CI servers, what is needed next? Do i customize the email templates and reference the location in the .ci.yml file stored in the home dir? Does it matter where the email templates are stored? Also since the company i work for is fairly large, we have multiple slaves as many teams are using the Jenkins setup. Is it possible to customize the template specifically for my team and not other teams? Thanks! -- 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-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Question on running simultaneous jobs in Jenkins
Please, try ask it in users mail list. You can also try register http://devops.com/news/ci-and-cd-across-enterprise-jenkins/ where first topic - Orchestrate Continuous Delivery pipelines with the new workflow feature, may potentially help you. On Wednesday, November 12, 2014 8:39:54 PM UTC+3, alok kumar wrote: Hi All, I have a requirement where in I have Prameterized build project which acts as a master project. This job does a lot of pre scm steps after which is supposed to initiate other jobs simultanously based on a condition for which I am using the conditinal build srep plugin. But, when I have more than one condition to check and initiate the jobs based on both the conditions simultaneously, I am not able to proceed on it. So, lets say we have: condition A - triggers jobA, jobB condition B - triggers jobC, jobD What I would like is to execute these conditions at the same time so that all the jobs start together? Can anyone please help me achieve this? This will be really appreciated. Thanks, Alok -- 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. For more options, visit https://groups.google.com/d/optout.
