Hi,
Jenkins 1.468 crashes at startup:
Running from: /usr/share/jenkins/jenkins.war
12.06.2012 08:09:45 winstone.Logger logInternal
INFO: Beginning extraction from war file
Jenkins home directory: /srv/jenkins/jenkins found at:
EnvVars.masterEnvVars.get(JENKINS_HOME)
12.06.2012 08:09:46
Hi,
It seems that 'push' automatically updates of Jenkins and its plugins from
pre-production to production is difficult.
However, it would be interesting to know how to create a sort of continuous
integration of the continuous integration environment :)
Thank you for your answer.
Le lundi
I'm trying again today to upgrade jenkins without any success :-(
$ sudo apt-get update
...
$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
jenkins
1
So, I tried again with the new Active Directory plugin.
When using our Service_Build user, there is no authentication request coming
into Active Directory, which is how it should be.
So the problem was the old, buggy Active Directory plugin.
Thanks for the help best regards,
Eric
Dear all,
I have a Maven project with two jobs:
1) Test - runs all tests (with surefire), and runs on every SCM commit
2) Deploy - deploys the new version on a server, and runs once at midnight
Everything is running great. However, we're now on a phase where changes
don't happen very often.
Hello,
I saw this in the change log:
Added a new hook to enable matrix project axes to change its values per
build.
Does this mean that we will be able to use environment variables and/or
parameters (i.e.${MY_VAR}) to change the axes before launching the build?
This would be awesome in
Strange: not even a forced install proceeds for me ;(
best
Jan
Same here on yum repo, following these
instructions
https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+RedHat+distributions
is throwing
Error Downloading Packages:
jenkins-1.469-1.1.noarch: failure: jenkins-1.469-1.1.noarch.rpm from
jenkins: [Errno 256] No more mirrors to
We recently upgraded from Hudson 1.385 to Jenkins 1.467. On Hudson, we had
a plugin that we used to create jobs, which had a predetermined set of
criteria for how a job was set up. The create permission was revoked
across almost every ACL, and people that did not have create permission
could
Hi Tim,
The following page should give detailed information about this:
https://wiki.jenkins-ci.org/display/JENKINS/Standard+Security+Setup
Specifically Within the Job”permission group there will be a permission
called“Release”
/James
From: jenkinsci-users@googlegroups.com
There are some way to do that?
I'm trying to do find some plugin or solution since yesterday.
Can someone help me?
On 12-06-12 02:10 PM, Roy wrote:
There are some way to do that?
I'm trying to do find some plugin or solution since yesterday.
Can someone help me?
I don't know about anyone else but I don't think I really understand
what it is you want.
b.
signature.asc
Description: OpenPGP digital
see https://issues.jenkins-ci.org/browse/JENKINS-14080
my shortterm-solution : complete disable security and LDAP ( in config.xml
).
On Tuesday, June 12, 2012 9:09:42 AM UTC+2, MR wrote:
I've got the same problem - currently testing with different
jenkins-versions -- but still the same
The docs make reference to a Push GIT tags back to origin repository
option but we're on 1.1.19 version of the plugin and I'm looking at the
Post Build options that appear when you add a Post-build Action for Git
Publisher:
Git Publisher
Push Only If Build Succeeds
Merge Results
I've found a partial solution, at least.
I installed the Groovy Post-build plugin and for every job add a Groovy script:
manager.build.getBuiltOn().toComputer.setTemporarilyOffline(true)
-- Sami
Sami Tikka kirjoitti 11.6.2012 kello 21.24:
Can I pick your brains for a moment? I have
Did you come up with a good solution to this? I am on a tram in the same
situation.
Thanks,
James
Try 1.469.
-- Sami
Ove Ranheim kirjoitti 12.6.2012 kello 15.44:
Hi,
I experience this strange problem with Jenkins (build: #1468). It's running
under its own non-privileged user on Centos 6. During execution of Maven 3
tests, all of a sudden the Jenkins process gets killed. I'm clueless
Configure the Deploy job to also check out source code from SCM (even though it
would not use it) and make it poll only at midnight.
Alternatively, make the Test job trigger a job which waits until next midnight
and then triggers Deploy.
-- Sami
Miguel Almeida kirjoitti 12.6.2012 kello 14.30:
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.
19 matches
Mail list logo