This works pretty well:
https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin
Rock
-Original Message-
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Fabricio Leotti
Sent: Monday, November 23, 2015 5:29 PM
To: jenkinsci-users@googlegrou
Maybe this helps?
https://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin
On 24.11.2015, at 00:29, Fabricio Leotti wrote:
> Hello!
>
> Normally I use the USAGE strategy of my nodes as "utilize this node as
> much as possible" and group labels (in this case 2 nodes).
>
> I am getting too
Hello!
Normally I use the USAGE strategy of my nodes as "utilize this node as
much as possible" and group labels (in this case 2 nodes).
I am getting too much difference between the loads of the 2 nodes. I
was thinking if the balancing strategy would change if I keep the
labels and change the str
On Monday 23 November 2015, Francois Marot wrote:
> Thanks Mark and Stephen for your detailed responses.
> So in the end, I think that Jenkins has a problem because a user that can
> create a job has access to ALL credentials. So by default, any user able to
> create one job may steal any source
Response in-line.
On Mon, Nov 23, 2015 at 10:41 AM Francois Marot
wrote:
> Thanks Mark and Stephen for your detailed responses.
> So in the end, I think that Jenkins has a problem because a user that can
> create a job has access to ALL credentials.
>
I'm not clear why you think that a user tha
Hi there,
Have you asked Cloudbees whether they support that feature as part of the
enterprise version yet?
It might help you
Cheers
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails f
Thanks Mark and Stephen for your detailed responses.
So in the end, I think that Jenkins has a problem because a user that can
create a job has access to ALL credentials. So by default, any user able to
create one job may steal any source code located on a git repo whose
Jenkins has the credenti
Typically one executor per CPU core works well. Some people do two executors
per CPU core. The other issue you need to consider is your I/O performance.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Vanetta Floyd
Sent: Monday, November 23, 2015 1
I would like to verify - a good rule of thumb for how many executors to set
on each build node is relative to the number of processors the build server
has.
Example -
Server A:
Number of Processors = 4
# of Executors = 4
Is this a good rule, or should I be looking at other factors?
Hi,
I have a contract job position open for you. Please send me updated resume
with the details below requested,
*Job Description:*
*WebMethod Developer*
*Location: Bala Cynwyd, PA*
*Duration: 6+months*
Web Methods Developer will be responsible for the implementation of
different serv
Is the build running on a VM slave and you're trying to revert to a
snapshot of that particular VM slave?
If so - that's not supported. Jenkins requires that the slave doing a
build be up and running for the entire duration of the build. If you
revert your slave while it's doing a build (sort
Hello World,
We have Jenkins set up to build our product in a virtual machine. This
works so far.
Now I set the "Use Snapshot" checkbox and wanted to revert the VM to the
snapshot "production". This snapshot exists, I double checked:
root@buildserver:~# virsh snapshot-list build-vm2
Name
Anyone knows why the workflow load step cannot load from the "Workflow from
SCM" checkout? I am struggling to understand why this is not allowed. Why
does it need to load from another SCM checkout?
Thanks,
Martin
--
You received this message because you are subscribed to the Google Groups
"Je
On 11/23/15, 1:03 PM, "Ruslan Zasukhin"
wrote:
> ===
> Also about HISTORY I see that
>
> - some company have powerful own plugins,
> - in 2013 was made OSS
> - this plugin now is the part of Jenkins (I have no need install it)
Aha, It seems some time ago I did install
CloudBees Fold
On 11/23/15, 12:47 PM, "Stephen Connolly"
wrote:
Well, in Jenkins itself, I do not such options in the
"Edit Folder" screen
May be it is in other place?
===
Also about HISTORY I see that
- some company have powerful own plugins,
- in 2013 was made OSS
- this plugin now is the part o
On 23.11.2015, at 11:47, Stephen Connolly
wrote:
> closed source folders-plus plugin
It's in that.
--
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 jenkinsc
I am unable to hide my AWS secret key in the AWS elastic beanstalk plugin
which helps in automatic deployment in Elastic beanstalkPlease
help
Its urgent
Thanks
Amrita
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To u
I can't recall if it is in the OSS plugin or our closed source folders-plus
plugin, but you can define environment variables that are common to all
jobs in a folder
On 22 November 2015 at 18:35, Ruslan Zasukhin <
ruslan_zasuk...@valentina-db.com> wrote:
> Hi,
>
> As I understand, folder A can hav
18 matches
Mail list logo