Hello everyone,
I did read that Java versions after 7u40 are not compatible with Integrity
older than 10.5
And I have two questions about it:
1) What is the reason of this issue ? Is this related to the Integrity
client or to the PTC plugin ?
2) We have now the following (everything is
After I upgraded to Jenkins 1.640 every time I save a project (any project)
is gives me an StackOverflowError
A problem occurred while processing the request. Please check our bug
tracker to see if a similar problem has already been reported. If it is
already reported, please vote and put a
When I removed Repository Browser GitWeb I was able to save the project
without any problems.
onsdag 9. desember 2015 11.34.11 UTC+1 skrev Sverre Moe følgende:
>
> After I upgraded to Jenkins 1.640 every time I save a project (any
> project) is gives me an StackOverflowError
>
> A problem
Hi,
I'm configuring my newly installed Jenkins server (v1.640, running in a
Tomcat 8 on an Ubuntu box) - and I'm trying to install the JDK within
Jenkins.
I went with the "Install from java.sun.com" installer, filled in my Oracle
account credentials, but now it's asking me to "Define JDK ID"
Tried hard. Still not working .
On 9 December 2015 at 10:05, Slide wrote:
> Looks like the permissions on /var/lib/jenkins/.ssh/config are too open,
> you should chmod 600 that file to make it more secure.
>
> On Tue, Dec 8, 2015 at 9:30 PM Sharon Francis
I assume it was a change between 1.639 and 1.640 that causes the problem.
Refer to https://issues.jenkins-ci.org/browse/JENKINS-31954 and
https://issues.jenkins-ci.org/browse/JENKINS-31954 for the latest
information.
Short term, either disable the repository browser in your jobs, or switch
back
I've seen a similar behavior with other tools and recent versions of Java
8. For example, when I define that maven 3.3.9 should be downloaded from
apache, sometimes it shows the pick list, and other times it does not.
Likewise, when I define that ant 1.9.6 should be downloaded from apache,
Didn't track it down, but as I was playing with something recently, I saw
this is working in 1.609.3 but not in the latest LTS.
I'll see if I can bisect it.
2015-12-09 16:23 GMT+01:00 Eugen Paraschiv :
> Yes, Maven is exactly in the same situation - I don't see any
Hi all,
I start to use jenkins+jmeter+performance plugin.
Plugin is installed and available in Post-build steps.
Jmeter is installed on remote server.
Jenkins has access to this remote server and can start test in non-gui
mode. Shell script looks so:
jmeter -n -t some.jmx -l some.jtl
Problem
This should be resolved since earlier today.
On 09.12.2015, at 18:24, Andrew Bayer wrote:
> I've seen it in the latest LTS - only thing I've found that clears it up is
> restarting a few times and force-updating. I think it might be the cert
> issues on tool installer
That's a bug introduced in git plugin 2.4.0. One way to avoid the bug is
to revert to git plugin 2.3.5.
The bug is only visible when the "sha1=xxx" parameter is included in the
notify commit URL. One way to avoid the bug is to configure Stash to not
include sha1=xxx in the notify commit
I do believe the plugin sets the var you want. have a look at
Environment variables here:
https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-AdvancedFeatures
On Thu, Nov 12, 2015 at 12:41 PM, Jens Wilke
wrote:
> Hi all,
>
> for extracting a git revision
Hi! Anyone know how I can retrieve the git revision from a job?
I can get to the build:
j = Jenkins.instance.getJob('render-master')
b475 = j.getBuildByNumber(475)
but I can't find a way to to get the git revision associated with that
build. Any thoughts would be appreciated!
Thanks a lot,
Running into a problem specifically with SCM change triggered builds
Specs:
Jenkins 1.596.2
Git Plugin 2.4.0
Git Client Plugin 1.19.0
Builds triggered via SCM change start normally-a commit notification is
displayed, the branches are pulled, and it runs smoothly until the build
step.
Hi there,
On 09/12/15 23:40, Guy Matz wrote:
> Hi! Anyone know how I can retrieve the git revision from a job?
>
> I can get to the build:
>
> j = Jenkins.instance.getJob('render-master')
> b475 = j.getBuildByNumber(475)
>
> but I can't find a way to to get the git revision associated with
Hello All,
I've run into a problem with my Windows slaves that are using ssh and
haven't been able to find a solution. The problem is that the command
shells I'm getting with these windows slaves are owned by the privileged
user (cyg_server) and not the slave user (jslave). When a job runs that
Thanks for the quick reply! We've reverted to 2.3.5 for the moment.
John C
On Wednesday, December 9, 2015 at 4:43:28 PM UTC-5, Mark Waite wrote:
>
> That's a bug introduced in git plugin 2.4.0. One way to avoid the bug is
> to revert to git plugin 2.3.5.
>
> The bug is only visible when the
I think I've found the fix. By adding the LSA authentication package I seem
to be getting the correct user.
$ cyglsa-config
Warning: Registering the Cygwin LSA authentication package requires
administrator privileges! You also have to reboot the machine to
activate the change.
Are you sure
I've seen it in the latest LTS - only thing I've found that clears it up is
restarting a few times and force-updating. I think it might be the cert
issues on tool installer metadata that Kohsuke's supposed to fix. =)
A.
On Wed, Dec 9, 2015 at 10:32 AM, Baptiste Mathus wrote:
>
19 matches
Mail list logo