Hi,
I'm using Jenkins 1.614, and I have a job which seems to be stuck, and I
can't stop it:
https://jenkins.freebsd.org/job/FreeBSD_HEAD-scan-build/124/
I tried clicking the X (
https://jenkins.freebsd.org/job/FreeBSD_HEAD-scan-build/124/stop)
to stop the job, but that didn't stop it.
An hints
Hi,
JENKINS-25583 (Unexpected error in launching a slave. This is probably a
bug in Jenkins.) is observed for Jenkins ver. 1.614. On which build i can
get fixed for issue https://issues.jenkins-ci.org/browse/JENKINS-25583.
I am blocked due to this issue.
--
You received this message
On Tue, May 26, 2015 at 11:01 PM, Kavitha Bhaskaran
kukki.kanch...@gmail.com wrote:
Hello There:
Not sure if this is possible but is it possible to migrate Jenkins from one
OS to another. Lets say I have Jenkins right now on RHEL and I would like to
move it to CentOS. Is there a way to do it?
I have a job
I try to modify the slave name of job in job's config.xml
Then reload jenkins
After above all, the slave label in job is not be changed into my
expected.
How can i do it ?
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To
Hi,
I had pretty much the same issue and the problem resolved after changing
the Job's JDK setting (in the Job configuration page) from default (which
on that machine points to a Java 6 JDK) to a Java 7 JDK. After that the
build started to work again without any issues.
Hope this helps.
My jenkins have configured to use OpenID SSO to login.
My question is how to use a *Jenkins normal user* to login without changing
the Security Realmfrom OpenID SSO to Jenkins’ own user database.
By saying *Jenkins normal user*, I mean those who signs up from the jenkins
signup
As far as I am aware, you can’t do this. Jenkins only supports using one
authentication method at a time.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of icetree521
Sent: 26 May 2015 10:11
To: jenkinsci-users@googlegroups.com
Subject: How can I use
It sounds like you want the promotion job to be reading files from the
workspace of the parent build that is being promoted.
If so, that’s the wrong way to do it. From
https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin:
Do not rely on files in the workspace
The promotion action
If the label you use to restrict the parent build the promotion build will
use the same label.
The best practice for promotion is to save artifacts during build so that
the artifacts can be retrieved during promotion. This will allow you to
perform promotions on historical builds as well and you
An alternate way to ensure you use a specific version of Gradle that may
not be available yet is to add the gradle wrapper to your project and to
configure the Jenkins plugin to use the wrapper.
https://docs.gradle.org/current/userguide/gradle_wrapper.html
If you don't want the wrapper to be
Yeah, that is not a scalable solution. That very effectively limits the build
and promotion to only run on one host, completely defeating the purpose of
having a cluster of slave build machines. Maybe it works ok for sites that do
not have enough peak workload to need slave machines.
It
On 26 May 2015 at 14:00, John Mellor john.mel...@esentire.com wrote:
Yeah, that is not a scalable solution. That very effectively limits the
build and promotion to only run on one host, completely defeating the
purpose of having a cluster of slave build machines. Maybe it works ok for
On 25/05/15 11:25, Carlo Lupo wrote:
We are using since some weeks Gradle version 2.4 in our build scripts.
But when we want upgrade the Gradle version used vai Jenkins at Jenkins'
system page (install from gradle.org), it only displays the Gradle
release candidates 2.4-rc-1 and 2.4-rc-2 in the
I recently set up a new Jenkins server on a 64 bit Centos 6 server, and when I
attempted to compile one of my existing Java projects I came across this
Jenkins internal NPE. I've updated Jenkins to the latest stable build, and I've
updated Maven to version 3.3.3 and Java is version 1.7.0_79.
Hi,
I have had a similar problem. Had multiple Jenkins instances where a build
farm had to be shared between them. We used Mesos as a cluster manager and
Jenkins Mesos plugin to spawn slaves from the cluster when there is a
demand(build in queue). After configured idle timeout, slave is
Hi,
First I want to thank everyone who helped me in a previous post.
I am using the plugin Publish over SSH Linux for Linux operation is
perfect.
Now I have a Linux machine where it is installed jenkins and Windowns
machine where I installed a SSH server, openssh via the terminal
connection
I'm trying to set up a build project using the P4 plugin in Jenkins.
Specifically, I'm using the following Source Code Management settings:
- Workspace Behavior: Template
- Template workspace: client-jenkins-template
- Workspace Name Format: client-jenkins-${NODE_NAME}
Essentially, I
Stefan, are you still trying to do this? Though I do not know how to use
selenium I do know how to provision a testing environment with docker from
a workflow script using simple shell commands. If I can help out here I
would like to.
On Saturday, January 24, 2015 at 9:55:26 AM UTC-7, Stefan
+1 to using Gradle wrappers. Given how much Gradle build files can be
affected by version changes, allowing the two to be out of sync is likely
to have problems down the road :)
Richard.
On Wed, 27 May 2015 at 00:01 corneil.duples...@gmail.com
corneil.duples...@gmail.com wrote:
An alternate
It looks like this has already been reported here:
https://issues.jenkins-ci.org/browse/JENKINS-28341
But if you could add your Jenkins version, and the other version info
you mentioned here to that issue, that would be useful.
Regards,
Chris
On 26/05/15 20:18, Dippoakabob wrote:
I
I share that pain too - cannot find a good fix.
The wake-up function appears to start only one node per minute even if
there are five jobs in the queue.
Best
Peter
On Monday, July 21, 2014 at 9:27:49 AM UTC+2, Susanne Lindgren wrote:
Short version
I'm experiencing somewhat slow slave start
Browsing to:
http://ci.example.com:8080/jenkins/configureSecurity/api/xml
reports:
*description* *The requested resource is not available.*
which leads me to wonder if it is possible to manage the base configuration
of a jenkins installation over the RESTful API.
I am using the puppetlabs
Hi.
Been running entagen/jenkins-build-per-branch.git for a while and its been
working fine.
Some point over the weekend its stopped working and now throws /createItem:
HTTP/1.1 400 Bad Request 400
Any idea on how to work out why it's dying?
I can't find anything in the logs to suggest why
23 matches
Mail list logo
