how to implement an invisible job property plugin

2013-02-03 Thread Shen,Hui
Hi,
I need to write a plugin to add some job property, but I don't want this 
property can been seen by users, in other words they are invisible in job's 
configure screen.
How should I do that, I have tried use style="display:none" for the element in 
jelly file, but there is still a blank line left on the screen.
Can anybody help me ?
Thanks very much.

Hui

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: "don't keep this build forever" button does nothing

2013-02-03 Thread Bruno Cunha
Yeah. Forcing logRotate will do that for you.

I use this script with try/catch, because sometimes I got some IOExceptions
on run without it, and the script scops:

Jenkins.instance.items.each {
  try {
println(it.name);
it.logRotate();
  } catch(Exception e) {
println(e);
  }
}




"Reload configuration from disk" on a running instance deletes old builds
as well.


Regards,
Bruno Candido Volpato da Cunha

On Sun, Feb 3, 2013 at 9:13 PM, Sami Tikka  wrote:

> Jenkins only deletes builds when it runs the job. If you need the disk
> space vacated immediately, you can script it like described here:
>
>
> http://jenkins.361315.n4.nabble.com/Is-there-a-way-to-make-quot-discard-old-builds-quot-happen-right-now-td3879634.html
>
> -- Sami
>
> Chris Withers  kirjoitti 20.1.2013 kello 0.43:
>
> > Hi All,
> >
> > I'd like to delete this build:
> >
> > http://jenkins.simplistix.co.uk/job/testfixtures-tox/83/
> >
> > ...however clicking the "don't keep this build forever" button does
> nothing.
> >
> > What am I doing wrong?
> >
> > Chris
> >
> > --
> > Simplistix - Content Management, Batch Processing & Python Consulting
> >   - http://www.simplistix.co.uk
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: "don't keep this build forever" button does nothing

2013-02-03 Thread Sami Tikka
Jenkins only deletes builds when it runs the job. If you need the disk space 
vacated immediately, you can script it like described here:

http://jenkins.361315.n4.nabble.com/Is-there-a-way-to-make-quot-discard-old-builds-quot-happen-right-now-td3879634.html

-- Sami

Chris Withers  kirjoitti 20.1.2013 kello 0.43:

> Hi All,
> 
> I'd like to delete this build:
> 
> http://jenkins.simplistix.co.uk/job/testfixtures-tox/83/
> 
> ...however clicking the "don't keep this build forever" button does nothing.
> 
> What am I doing wrong?
> 
> Chris
> 
> -- 
> Simplistix - Content Management, Batch Processing & Python Consulting
>   - http://www.simplistix.co.uk

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: I did not spawn a child process to build my project, why am I getting this: Process leaked file descriptors. See wiki.jenkins-ci.org/display/JENKINS/… for more information ERROR: Failed to clean t

2013-02-03 Thread Sami Tikka
Well, everything is more difficult on Windows.

I do not use Windows but I work in an organization where people have to do 
battle with the same issues you are fighting with.

I think your issues might be caused by the "git" command not being a .exe but a 
.bat. 

-- Sami

hong...@steward.org kirjoitti 21.1.2013 kello 22.29:

>  have never configured a system as hard as this combination, Jenkins (1.499), 
> Git (1.8.0.msysgit.0), and Windows 7 32 bit. I have been stumped for three 
> days, did not make any progress. I have been googling crazily and all the 
> answers found here and there seemed to help me a little, ex: no space for Git 
> home. In Jenkins, for Git installation it is C:\Git\cmd\gitk.cmd, notice, 
> there is no space in the path (I reinstalled Git from Program Files\Git to 
> C:\Git to get rid of the space issue). My repository is a private one, so I 
> need to use an SSH protocol. I am able to do this git command in a command 
> line using my Windows account: git clone g...@github.com:mygitproject.git. I 
> have C:/Users/myaccount/.ssh/known_hosts, id_rsa, and id_rsa.pub. Since my 
> Jenksin is a Windows service, it runs under Local System Account, but the 
> known_hosts was generated when I logged in Windows using my Windows account, 
> so I thought I needed to change the Jenkins running user to my Windows 
> account and I did it. However nothing seems working.
>  
> When I try to build a job from a remote private Github repository, I get this 
> exception:
>  
> Started by user anonymous
> Building in workspace C:\Jenkins\workspace\Test
> Checkout:Test / C:\Jenkins\workspace\Test - hudson.remoting.LocalChannel@6846c
> Using strategy: Default
> Cloning the remote Git repository
> Cloning repository g...@github.com:stewardconnect/CARE.git
> git --version
> Process leaked file descriptors. See 
> http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for 
> more information
> ERROR: Failed to clean the workspace
> java.io.IOException: Unable to delete C:\Jenkins\workspace\Test
> at hudson.Util.deleteFile(Util.java:243)
> at hudson.Util.deleteRecursive(Util.java:293)
> at hudson.FilePath$11.invoke(FilePath.java:983)
> at hudson.FilePath$11.invoke(FilePath.java:981)
> at hudson.FilePath.act(FilePath.java:852)
> at hudson.FilePath.act(FilePath.java:825)
> at hudson.FilePath.deleteRecursive(FilePath.java:981)
> at hudson.plugins.git.GitAPI.clone(GitAPI.java:241)
> at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1044)
> at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986)
> at hudson.FilePath.act(FilePath.java:852)
> at hudson.FilePath.act(FilePath.java:825)
> at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:986)
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1142)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1325)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682)
> at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587)
> at hudson.model.Run.execute(Run.java:1543)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:236)
> ERROR: Error cloning remote repo 'origin' : Failed to delete workspace
> hudson.plugins.git.GitException: Failed to delete workspace
> at hudson.plugins.git.GitAPI.clone(GitAPI.java:244)
> at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1044)
> at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986)
> at hudson.FilePath.act(FilePath.java:852)
> at hudson.FilePath.act(FilePath.java:825)
> at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:986)
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1142)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1325)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682)
> at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587)
> at hudson.model.Run.execute(Run.java:1543)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:236)
> Caused by: java.io.IOException: Unable to delete C:\Jenkins\workspace\Test
> at hudson.Util.deleteFile(Util.java:243)
> at hudson.Util.deleteRecursive(Util.java:293)
> at hudson.FilePath$11.invoke(FilePath.java:983)
> at hudson.FilePath$11.invoke(FilePath.java:981)
> at hudson.FilePath.act(FilePath.java:852)
> at hudson.FilePath.act(FilePath.java:825)
> at hudson.FilePath.deleteRecursive(FilePath.java:981)
> at hudson.plugins.git.GitAPI.clone(GitAPI.java:241)
> ... 14 more
> Trying next repository
> ERROR: Could not clone repository
> FATAL: Could not clone
> hudson.plugins.git.GitEx

Re: jenkins clustering

2013-02-03 Thread Sami Tikka
There is no such way. If this is critical to you, maybe you could check if you 
can turn your builds into "external jobs" like described in 
https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs

-- Sami

Matteo  kirjoitti 22.1.2013 kello 21.23:

> Hello,
> 
> first i'd like to thank developers for this great project.
> 
> I'm sorry if already asked but i'm new on this list and searching the web
> has produced no results.
> 
> We have a jenkins installation with 1 master and 5 slaves connected through 
> ssh.
> 
> We are mostly a java shop and jenkins is central to our infrastructure since 
> we
> build and deploy releases to servers from it.
> 
> For this reason slave resiliency in the face of master failure is paramount 
> to us.
> 
> My question:
> Is there a way, in a master/slave configuration, to have slave builds
> running to completion even in case of master failure (ideally refetching
> console logs once the master is back up :))?
> 
> In our current setup, we get a proxy error on master UI and builds are 
> aborted.
> 
> Thanks in advance for any hint,
> 
> -m

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Steps to Upgrade - quick question

2013-02-03 Thread Jesse Farinacci
Greetings,

On Sun, Feb 3, 2013 at 1:34 AM, Z W  wrote:
> Are there exact steps on how to upgrade (like what directories to copy
> after deploying a new Jenkins war file)
> so we don't miss any plugins, artifacts histories and job
> configurations, etc...) ?
> We like a smooth upgrade or migration.

https://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins

But as with anything you are relying on for your fame or fortune:
Practice, practice, practice.

-Jesse

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Jenkins/Slave connection via TelNet

2013-02-03 Thread Sami Tikka
Which Jenkins version are you using? Recent Jenkins versions allowed 
unauthenticated access to the slave-agent.jnlp URL, which makes starting JNLP 
slaves a bit more difficult.

I'm pretty sure the slave startup does not use -auth option to provide a 
username and password. Where did you pick that up?

You can use a browser to authenticate and download the slave-agent.jnlp and 
save file on the slave local disk. Then start the slave and profile a 
file://localhost/path/to/slave-agent.jnlp as URL on the slave command line.

-- Sami

Mehdi Hayani Soujaa  kirjoitti 1.2.2013 kello 11.38:

> Hii,
> 
> From the "Jenkins-The Definitive Guide" book we've tried to add the slave 
> based on the command line strategy. So, as mentioned in the book, we used the 
> following command: 
> 
> java -jar slave.jar -jnlpUrl 
> _http://**.**.**.**:/cip/computer/NewNode/slave-agent.jnlp -auth 
> user:password
> 
> But, the problem is that each time we execute this command, we get this error:
> 
> Failing to obtain 
> http://**.**.**.***:/cip/computer/NewNode/slave-agent.jnlp
> java.io.IOException: Failed to load 
> _http://**.**.**.***:/cip/computer/NewNode/slave-agent.jnlp: 404 Not Found
> at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:238)
> at hudson.remoting.Launcher.run(Launcher.java:200)
> at hudson.remoting.Launcher.main(Launcher.java:173)
> Waiting 10 seconds before retry
> 
> It seems that it can't find the slave agent file, But if we copy the URL in a 
> browser manually, the file is downloaded.
> 
> 
> Any idea about this issue ?? 
> 
> 
> Regards 
> Mehdi 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Steps to Upgrade - quick question

2013-02-03 Thread Peter Miklosko
All the plugins and other stuff is kept in hidden directory  .jenkins,
example Mac OS /Users/Peter/.jenkins. So yo need only to stop Jenkins, get
new war file and start Jenkins again.

As from migrating from Hudson to Jenkins I'm not sure. Never had to do such
thing...


Peter

On 3 February 2013 06:34, Z W  wrote:

> Hi All
>
> There are notes on how to install Jenkins.
> But there's not many notes on how to upgrade Jenkins or migrate from
> Hudson.
> Are there exact steps on how to upgrade (like what directories to copy
> after deploying a new Jenkins war file)
> so we don't miss any plugins, artifacts histories and job
> configurations, etc...) ?
>
> We like a smooth upgrade or migration.
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.