On Tue, Oct 29, 2013 at 4:16 AM, James Nord (jnord) wrote:
> The changes I have put in to support this are not in a release version
> of the buildflow – so you will need to download source and compile, or grab
> it from the Jenkins ci instance.
>
I forgot to state that I am did this. Sorry abou
Hi,
I struggled with a similar problem for a long time, and in the end it was
ruby-runtime plugin which prevented my SSH connections to work. As I don't
use that plugin I uninstalled it and SSH started to work for some reason.
Here's the original Google Groups discussion about my issue:
https:
The changes I have put in to support this are not in a release version of the
buildflow - so you will need to download source and compile, or grab it from
the Jenkins ci instance.
/James
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Åsmund Østvol
If you have a heap dump, please send it to us. If you can take two heap
dumps, one with 1.535 and another with 1.537, it'd be even better.
On 10/28/2013 09:02 AM, David Gang wrote:
Hi all,
I have with jenkins 1.537 a much higher memory consumption than with
jenkins 1.535.
I also noticed that
Hi, Just upgraded Jenkins to pickup some bug fixes (disappearing job log).
Rekey process is running in the background. Is it not done yet and causing this?
Every single slave failed to launch with this error:
[10/28/13 16:47:39] [SSH] Opening SSH connection to
batvm06.perf.lab.tripwire.com:22.
I started using folders around seven months ago. The following is based on the
advantages I experience in using folders, as well as the problems I've
encountered. It's not a high level overview. Some of this will probably already
be obsolete, but it should still serve to illustrate the kind of i
Thank you James,
I finally freed up some time and was able do a new stab at this. I have
inlined some questions and feedback.
On Fri, Oct 25, 2013 at 6:33 AM, James Nord (jnord) wrote:
> KillRunningjobs is called internally if the flow is aborted (or one of
> the jobs is aborted).
>
> Interna
I bumped into an "out of PermGen space" report on Jenkins 1.509.4 recently,
though mine was after upgrading the Git plugin to 2.0. Are you using Git
plugin 2.0 as a new part of that upgrade, or were you already running Git
plugin 2.0 before you upgraded?
Mark Waite
On Mon, Oct 28, 2013 at 10:02
things were fine last week, not sure why this is happening now
INFO: Completed initialization
Oct 28, 2013 3:23:04 PM hudson.TcpSlaveAgentListener
INFO: JNLP slave agent listener started on TCP port 50336
Exception in thread "Executor #0 for master"
java.lang.NumberFormatException: For inpu
Have you seen
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+behind+an+NGinX+reverse+proxy?
Not sure if it helps but could be a starting point to see what someone else
has done.
Richard
On Friday, October 25, 2013, Philipp Kraus wrote:
> Hello,
>
> I would like to configure ngix with jenki
I'm wondering what tips can be offered for different ways of implementing
the organization of builds using the CloudBees Folders plugin and any tips
on migrating builds into a nested folders/namespaces structure?
Regards,
Joshua @ blog.milehighcode.com
--
You received this message because you
Would like to know how others have implemented the Cloudbees Folders plugin
into an existing Jenkins system. Easiest way to migrate builds into the new
namespace structure, best practices for using Folders to organize builds,
etc.
Any links to blogs or web info in addition to any mailing list r
Hello,
I would like to configure ngix with jenkins, nginx should be a proxy for
the jenkins instance. I have configuration the proxy pass options in this
way:
location /jenkins {
proxy_pass http://localhost:8080/;
proxy_redirect off;
proxy_set_header
Hi all,
I have with jenkins 1.537 a much higher memory consumption than with
jenkins 1.535.
I also noticed that the PS Old gen is full.
I had to raise the xmx from 2G to 3G in order that jenkins should be
responsive.
Did anyone also notice this issue?
Thanks,
David
--
You received this messa
You can use property expression in mailing recipients field.
If you combine this feature with Token Macro Plugin
(https://wiki.jenkins-ci.org/display/JENKINS/Token+Macro+Plugin) you should
be able to retrieve recipient list from property file under source control.
--
You received this message b
Hello,
We're hitting this with Windows slaves as well - with the Windows service
type of connection.
No slave log, local or remote, just the throbber again.
Basically only JNLP connections are working right now :/
_
Costin Caraivan
On Thu, Oct 24, 2013 at 7:35 PM, Costin Caraivan
wr
In case it matters, my problem configuration is a Windows 8 machine. The
Windows Server 2011 machine that is also in that configuration does not
show the problem, nor do any of the Debian Linux machines that are in the
configuration.
Mark Waite
On Mon, Oct 28, 2013 at 7:49 AM, Mark Waite wrote:
I've seen a similar message in one of my git plugin 2.0 test configurations
without using the Gerrit trigger. One of my jgit trivial test jobs was
passing happily (though executing more builds than it should due to
https://issues.jenkins-ci.org/browse/JENKINS-20286), when it suddenly began
reporti
I'm not sure -- it's not the SHA1 that should be built (it's not the ID of
the SHA1 of the change set).
It feels like jenkins is asking gerrit for a SHA that doesn't exist (or
perhaps - does not exist any longer, as it's been GCed out of the gerrit
repo).
The git plugin also seems to be stamping
Does it succeed with the command line git provider, or is it failing with
both command line and jgit?
I thought "missing commit" usually meant that the git repository was
corrupt and needed to be rebuilt.
Which of the repositories contain that SHA1? (Is it in the Gerrit repo and
not in the Jenki
Has anyone got the above combination to work?
Our jenkins seems obsessed with building wrong versions. I'm not sure which
of the vague "Usage with the Git plugin" options (here
https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger) are valid, and
our gerrit server is spitting errors such as:
Yes and it still doesn't start
Il giorno venerdì 25 ottobre 2013 15:44:54 UTC+2, Stephen Connolly ha
scritto:
>
> have you tried wiping out $JENKINS_HOME/war as that may not be fully clean
> (it's where the .jar extracts all of the .war contents to?
>
>
--
You received this message because you
As someone else said, this is a bug in 1.536. Quite a few things were broken in
1.536, you should probably roll back.
Incidentally, Jenkins has a bug tracker (Jira) at
https://issues.jenkins-ci.org/browse/JENKINS. It’s always worth looking to see
if a problem has already been reported before as
Same exact problem here, also with version 1.536 (Ubuntu 13.04).
On Friday, October 25, 2013 8:05:11 PM UTC+2, jserene wrote:
>
> OS: Ubuntu 12.04
>
> Jenkins version: 1.536
>
> STEPS:
>
> 1) create a new 'free-style' project
>
> 2) add build step -> execute shell
>
> 3) enter whoami command in s
24 matches
Mail list logo
