Try using port 465 instead of 587 in the SMTP Port field. That's the
usual direct SSL port for SMTP.
Regards
Richard
On 02/07/2015 13:34, ozcaaa...@gmail.com wrote:
Hey!
You are right. But whch one is the correct port, how do I choose?
Thanks,
Ozcan
On Thursday, July 2, 2015 at
Hi,
On 16/01/2015 15:16, Aaron Johnson wrote:
Can someone please verify this:
I am unable to download RPMs from archives.jenkins-ci.org, example:
http://archives.jenkins-ci.org/redhat-stable/jenkins-1.424.2-1.1.noarch.rpm
The download starts, and goes very slow (less than 5Kbps) and never
On 07/05/2014 10:44, Arnaud Héritier wrote:
thus the winstone jar is useless ?
No. winstone.jar is the thing that wraps Jetty and provides the same
features as the old winstone based winstone.jar.
https://github.com/jenkinsci/winstone
Regards
Richard
On Wed, May 7, 2014 at 9:37 AM,
On 01/04/2014 19:19, Daniel Beck wrote:
https://issues.jenkins-ci.org/browse/JENKINS-17526
Fixed in 1.549.
There are a few other JIRA entries related to this (sorry don't have the
list to hand) but I did notice that yesterday Kohsuke made a fix that
should fix all of these.
Hi,
On 20/03/2014 16:05, Dennis Jacobfeuerborn wrote:
Hi,
I just installed a fresh Jenkins behind Apache httpd and while Jenkins
is available it tells me It appears that your reverse proxy set up is
broken. but I don't know why.
I came across the same problem earlier today. My setup had been
Hi Abhijith,
I think you need to read about chains of trust. Everything that you
suggest below is at best hiding what you are downloading from an
observer. It doesn't stop man in the middle attacks or guarantee that
the contents were not corrupted during transit.
As James suggested all you
On 01/11/2013 14:28, Mark Waite wrote:
It appears you're not the only one encountering the problem.
https://groups.google.com/d/msg/jenkinsci-users/QDkVHmHnI-U/6cnw4RAvNQIJ
seems to be another example of a similar stack trace
Unfortunately, I have no hint as to the root of the problem.
I
On 20/02/2013 17:01, Les Mikesell wrote:
On Wed, Feb 20, 2013 at 10:53 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 20 February 2013 16:43, Les Mikesell lesmikes...@gmail.com wrote:
On Wed, Feb 20, 2013 at 10:26 AM, Fisher, Allen afis...@makemusic.com
wrote:
... snip ...
I suspect it is
https://issues.jenkins-ci.org/browse/JENKINS-15156
Builds disappear from build history after completion
Regards
Richard
On 06/02/2013 05:18, Daniel Becroft wrote:
Further information: Restarting Jenkins makes the builds display again,
but that's not an ideal solution. There
Hi,
On 22/01/2013 00:02, BobTheBuilder wrote:
Hello,
I have a long running build that never runs to completion on the slave
computer, it gets Maven JVM terminated unexpectedly with exit code 143.
Exit codes over 128 signify that the process died due to a signal.
exitcode = 128 + signal
kernels.
ftp://ftp.kernel.org/pub/linux/kernel/people/marcelo/linux-2.4/mm/oom_kill.c
Anyhow the solution will likely lie in finding the cause/source of the
SIGTERM.
Regards
Richard
Richard
On 2013-01-22, at 04:13, Richard Mortimer ri...@oldelvet.org.uk wrote:
Hi,
On 22/01/2013 00:02
Hi,
I managed to fix this fairly simply on my windows slaves (tested on XP,
Vista Win 7). The fix should be similar for Linux slaves but I use a
home-cooked script to start those so you'll have to adapt the solution
as appropriate.
1 - autheticate as a Jenkins admin in a browser of your
Hi Mark,
On 07/01/2013 18:21, Mark Waite wrote:
I upgraded my Debian Jenkins LTS from 1.480.1 to 1.480.2 today using the
Debian package manager. The machine was running with authentication
enabled and was using Debian, CentOS, Red Hat, and Windows slave agents.
The Linux slave agents are
On 21/10/2012 10:52, David Resnick wrote:
Since upgrading to 1.486 I've noticed long load times for some views on
our Jenkins instance. Longest load times are for the main dashboard
(which includes over 100 jobs and thousands of builds) -- I just timed 4
minutes 45 seconds for the page to load.
Hi,
On 11/10/2012 15:58, teilo wrote:
*Hello,*
getProject*().*getBuilds*() is returning a list which contains a null
entry which is just not good.*
*This appears on first inspection to be a Jenkins core issue – can you
try with earlier cores to track down when this was introduced?*
This is
On 18/08/2012 00:46, Mani wrote:
Hi All,
I'm running Jenkins instance under https but I'm unable to connect to it
with CLI. I have two questions on this. I would appreciate if you could
give me some pointers on this.
1. If Jenkins CLI has the support to connect to https?
yes
2. If yes,
Hi,
On 03/07/2012 10:16, B.Latinville wrote:
Hi all,
I'm running Jenkins under debian and I've just upgraded to 1.473.
I have a lot of jobs missing in the interface. They are all Matrix jobs.
Issue 14273 http://jenkins-ci.org/issue/14273
Will be fixed in 1.475.
Regards
Richard
In the
It could be the kernel running out of virtual memory and the OOM (out of
memory) killer is killing jenkins. Run the dmesg command in a terminal
window on your jenkins server and see if the OOM kill has been active.
Also see.
Hi,
You question is best addressed to jenkinsci-users@googlegroups.com.
jenkinsci-issues@ is used for automated JIRA messages.
That said I've answered your question below etc. and posted to -users
for others to comment as appropriate.
On 20/03/2012 11:39, Programie wrote:
Hi,
I'm using
Hi,
On 20/03/2012 11:52, Wilfred Springer wrote:
It turns out that mod_proxy is dropping the 'n' header on its way out. I
tried a number of things to make sure it's getting preserved, but it
isn't. After that, I tried nginx. On the plus side, nginx *does*
preserve the n header on its way out.
Tim,
From what you have said there doesn't seem to be any obvious user error
and it does look like some form of bug to me.
Before reporting it in JIRA it would be a good idea to follow the advice
at https://wiki.jenkins-ci.org/display/JENKINS/Build+is+hanging to see
if there are any threads
On 27/02/2012 09:40, Nord, James wrote:
If jenkins runs out of file descriptors whilst trying to accept a socket
connection this will (in my experience) cause the winstone listener to die.
See the last comment on https://issues.jenkins-ci.org/browse/JENKINS-9882
That would be consistent
Hi,
(moving thread back to -users@ instead of -dev@)
On 15/02/2012 05:05, sureshkumar nandakumar wrote:
Hi,
Really thanks for your reply.
I didn’t get any issues in server. It is working well.
The log file that you supplied is where issues in the server are
generally reported. In your case
23 matches
Mail list logo
