Hi,
> The upper left line tells me:
> Jobs:2 GB, Builds:2 GB, Locked builds:-, Workspace:10 GB
>
> The actual size of the workspace folder is around 11.6 GB.
>
> The graphical Disk usage trend report shows me a workspaces
> size of 2 GB.
there could be some issues with calculation of disk usage
On Tuesday 23 April 2013 14:58:10 Kohsuke Kawaguchi wrote:
> Thanks for posting this!
+1 thanks!
Just a notice: we have part of these test already automated as Selenium test
[1], so if you don't want to do any manual testing, you can download the tests
and run them (however, some manual test of
Hi,
> It now states "This view has no jobs associated with it."
I was able to reproduce this by removing read permission for jobs for
anonymous user, so this doesn't seems to be related to the issue.
Unfortunately, I still cannot reproduce the issue itself. Are you running
Jenkins on some
> Automatic fail-over adds a lot of complexity and a lot of new things
> to go wrong. An easier approach would be a moderately frequent rsync
> of the jenkins data to a backup server where you would manually change
you can also use e.g. NFS volume mounted to both slaves so that everything is
up
Hi,
> After the update I
> noticed that logged out users have broken CSS. Has anyone else had any
> issues with their CSS after the upgrade?
no, I didn't spot any such issue. Could you check if you are able to load the
CSS directly by browser?
E.g. if the link is
then check if $JENKINS_URL//
Hi,
this is for a plugin you develops, right? In such case jenkins-dev would be
more appropriate list ...
> 1. Where do i copy the .js files ?
usually into src/main/webapp
> 2. This needs to be self updating , How do i achieve that ?
check jelly ajax tag [1] (and reference therein how to use it
Hi Mark,
> I've logged several of the tests I performed on various configurations and
> added an additional section "exploratory tests". I wanted a place to
> record "creative tests I've never tried before". Those types of tests
> aren't as helpful for detecting regressions, but may discover bug
> Should I post this to the jenkins blog?
as you want. If you do so, you can stress that we would appreciate some
Windows testes as our test coverage on windows is exactly 0% right now
Hi,
LTS 1.480.1 RC is now available for download [1].
As usual, I would like to ask for your help. If you stage RC in you stage
environment or just download RC and try to run it, please drop a note on wiki
page [2], shortly describe what you've tested, where it was done (OS, JDK
version) and the
Hi,
(CC dev list)
it seems the latest LTS rpm is missing in yum repo [1], can someone with admin
right take a look please? Thanks
Meanwhile, you can download rpm from mirrors [2] and install manually.
Cheers
Vojta
[1] http://pkg.jenkins-ci.org/redhat-stable-rc/
[2] http://mirrors.jenkins-ci.org
Hi,
the groovy script has to be available on all slaves where you execute your
jobs under same path. You can use e.g. NFS drive mounted to the same location,
another (probably better) way is to keep script in the SCM and checkout it
into workspace and there are other ways how to achieve it.
Ano
Hi,
I'm not sure how to fix changelog for already release version, but the only
change was security bug fix, for details see [1]
Vojta
[1] https://wiki.jenkins-
ci.org/display/SECURITY/Jenkins+Security+Advisory+2012-09-17
On Tuesday 18 September 2012 07:51:44 David Aldrich wrote:
> I would also
ndrew Melo wrote:
> On Wed, Aug 1, 2012 at 10:36 AM, Vojtech Juranek
wrote:
> > On Wednesday 01 August 2012 10:07:15 Andrew Melo wrote:
> >> On Wed, Aug 1, 2012 at 9:48 AM, Vojtech Juranek
wrote:
> >> > quick way how to look what the thread consuming CPU is doing is to
On Wednesday 01 August 2012 10:07:15 Andrew Melo wrote:
> On Wed, Aug 1, 2012 at 9:48 AM, Vojtech Juranek wrote:
> > quick way how to look what the thread consuming CPU is doing is to do
> > thread dump (e.g. using jstack $PID) and use top with threads on (H
> > option) and
quick way how to look what the thread consuming CPU is doing is to do thread
dump (e.g. using jstack $PID) and use top with threads on (H option) and then
look up, see e.g.
http://code.nomad-labs.com/2010/11/18/identifying-which-java-thread-is-
consuming-most-cpu/
On Wednesday 01 August 2012 09:
> I'm not clear how a new user installing Jenkins LTS will be able to choose
> the 1.1.20 release of the git plugin. I had to download it separately,
> name it appropriately (replace .hpi with .bak), copy it into the plugins
> directory, then restart Jenkins. Once that was done, Jenkins core
> r
ct: Re: LTS 1.466.1 RC1 testing
> >
> >It could be https://issues.jenkins-ci.org/browse/JENKINS-14480, probably
> >nothing wrong with Jenkins. Mark, could you check if you have
> >repository/branchname in the "Branch to build" setting?
> >
> >-- Sami
>
:
> I used the script console at http://localhost:8080/script to run the
> command Functions.isWindows() and it reports Result: false
> >
> >
> > From: Vojtech Juranek
> >
> >To: jenkinsci-users@googlegroups.com
> >Sent: Satu
sting installation. Unfortunately, it is not that
> simple with a new installation.
>
> Mark Waite
>
> >____________
> >
> > From: Vojtech Juranek
> >
> >To: jenkinsci-...@googlegroups.com; jenkinsci-users@googlegroups.com
> >Sent:
Hi,
LTS 1.466.1 RC1 is now available for download [1], thus we can start testing.
As usual, I would like to ask for your help. If you stage RC in you stage
environment or just download RC and try to run it, please drop a note on wiki
page [2], shortly describe what you tested, where it was done
Hi,
could you please provide some more info - e.g. output of slave console log (if
there is any), check jenkins log is there is some error etc.
Thanks
Vojta
On Wednesday 11 July 2012 05:21:44 Suri wrote:
> Hi
>
> Recently I have upgraded LTS version 1.447.2 in my Jenkins server.
> After upgrade
great job, no rendering problems spotted in Opera and Konqueror.
The only thing I spot, which work on jenkins-ci.org and doesn't on jekyll
stage server, is redirect to JIRAs, e.g.
http://jenkins-ci.org/issue/14113 redirects to JENKINS-14113, while on jekyll
results into HTTP 404
On Saturday 07 J
On Tuesday 26 June 2012 19:56:10 Varghese Renny wrote:
> My system user is sigma.but i am running jenkins on tomcat6 user and
> tomcat6 group. So which user i have to specify in sudeors file.
> Thanks
then you have to grand sudo for tomcat6 user, as the build process runs under
this user (if you
On Tuesday 26 June 2012 06:28:29 Varghese Renny wrote:
> Hi,
>
> sudo: sorry, you must have a tty to run sudo
>
> What to do for this erro?
comment Defaultsrequiretty :-)
if you are getting
sudo: no tty present and no askpass program specified
make sure, that it run under sigma user. If you
make sure that in /etc/sudoers this line is commented out
#Defaultsrequiretty
On Tuesday 26 June 2012 05:57:41 Varghese Renny wrote:
> #!/bin/sh
> pid=$(pidof postgres)
> echo $pid
> sudo kill $pid
> pg_ctlcluster 8.4 main start
>
>
> This script is just for killing processid using postgres
I guess turning off tty (at least on RHEL like distors switched on by default)
should solve the problem, just comment line
Defaultsrequiretty
in /etc/sudoers
Of course you should have setup sudo not to ask passwd (NOPASSWD option)
On Tuesday 26 June 2012 08:23:19 Stanley, Jason wrote:
> Ah...
On Tuesday 26 June 2012 03:10:53 Varghese Renny wrote:
> In jenkins Whether any config file related to project? I am not getting you
> which project config file you are mentioning?
I mean job configuration page, i.e. $JENKINS_URL/job/$JON_NAME/configure
Lets assume it a maven project. In "Advanced
isn't it possible, that it still runs some post-build action which gets stuck?
You can check $JENKINS_URL/threadDump what it waits for
On Tuesday 26 June 2012 02:58:24 Dio wrote:
> All command has been done, but job doesn't finish and hold job continuously.
>
> so, I restarted Jenkins and it see
you have to setup permgen size in project config page. The permgen size
specified in catalina opts for jenkins applies only to jenkins server itself
and doesn't affect permgen size of built project - it run in different JVM
On Tuesday 26 June 2012 02:13:06 Varghese Renny wrote:
> No, the whole p
On Tuesday 26 June 2012 19:28:19 Dies Koper wrote:
> Hi,
>
> I downloaded it only a few days ago, so that would be 1.472 or 1.471, I'll
> can check tomorrow.
> Looks like the issue crept in again?
probably yes, if so, please log a JIRA request in https://issues.jenkins-
ci.org in core component
Hi,
which Jenkins version do you use? This was fixed in Jenkins 1.418
Vojta
On Tuesday 26 June 2012 00:59:26 dkoper wrote:
> Hi,
>
> I've configured Jenkins to be served through https (to be precise, jenkins
> is running on its web server on http which is fronted by Apache HTTP Server
> only has
Hi,
this plugin is not supported on 1.424. The plugin states that ir requires
1.432, but it also requires ruby-runtime:0.9, which requires 1.447. So
probably the best way is to upgrade you Jenkins to 1.447 if you want to use
this plugin
Vojta
On Tuesday 26 June 2012 00:26:04 Suri wrote:
> Hi
>
Hi,
is this failure of one particular build or whole Jenkins? Do you increase
pergem size for jenkins of in setup of the build?
Vojta
On Tuesday 26 June 2012 01:28:49 Varghese Renny wrote:
> While doing build, i am started getting this error,
> i increased the heap size and permgen size to 1024
Hi,
LTS 1.447.1 RC1 is now available for download [1] (thanks Kohsuke for
backports), thus we can start testing. As usual, I would like to ask for your
help. If you stage RC in you stage environment or just download RC and try to
run it, please drop a note on wiki page [2], shortly describe what
> I have there more than a half year old builds. When I set 30 days then
> I would like to ask you if the older builds are deleted when jenkins
> is starting or when the same job is building?
the builds are deleted after next build is run and finished. If you want to
delete them without running
Hi,
> I would like to ask you how jenkins and hudson community cooperates or
> where is the main development.
just compare git repos,
https://github.com/jenkinsci/
vs.
https://github.com/hudson
+
https://github.com/hudson-plugins
and make your own conclusion. IMHO it's pretty clear where the mai
Do you run it withing a Jenkins build in master JVM? For me still works fine
> This use to work for me:
>
> def build = Thread.currentThread().executable
>
> Now I get this error:
>
> Caught: groovy.lang.MissingPropertyException: No such property:
> executable for class: java.lang.Thread
>
> On Mon, Mar 5, 2012 at 10:19 AM, Vojtech Juranek
wrote:
> >> I was just missing something obvious. Along with checking the
> >> 'Install automatically' box in the global config (which might have
> >> been set by default) you have to give it a name and
> I was just missing something obvious. Along with checking the
> 'Install automatically' box in the global config (which might have
> been set by default) you have to give it a name and then you have to
> pick that name in the job config. Before getting this right, the job
> config only offere
> On Thu, Feb 23, 2012 at 5:43 PM, Vojtech Juranek
wrote:
> >> Does the groovy plugin need anything special installed on the slaves?
> >
> > there are two options, groovy script and system groovy script. First one
> > requires groovy installation o
Hi,
as auto update mechanism for LTS is broken in some cases (hopefully will be
fixed in the next release), I'd like to announce release of LTS 1.424.3 this
way. So thanks to Kohsuke for the release and if you are affected by this bug,
you can download new release manually from usual location [
What exactly are you trying to achieve? And where do you run groovy script
using your Test class?
In general, compiles Test class need to be in groovy class path.
Usually it's -cp option when running from command line, in Jenkins Groovy
plugin there's special column in Advanced options to set up
> Hi,
> this doesn't looks like Jenkins issue, it's more likely some problem in
> your git setup. Are you able to run successfully following command
> manually?
send too early:-) Are you able to run this command manually?
C:/msysgit/msysgit/bin/git.exe clone -o files-plugin
g...@github.com:arrk/
Hi,
this doesn't looks like Jenkins issue, it's more likely some problem in your
git setup. Are you able to run successfully following command manually?
> I am receiving following error while integration Jenkins with Github.
> I have following all steps mentioned in
> http://help.github.com/mac-
> Does the groovy plugin need anything special installed on the slaves?
there are two options, groovy script and system groovy script. First one
requires groovy installation on slaves (check global jenkins configuration,
auto-install can be used), second doesn't, however it's not executed on sla
45 matches
Mail list logo
