Re: Remove job from queue via groovy
Dang. Forget it. I found like 2 seconds after I posted this. There is a "doCancelQueue()" function. I don't know why I missed it. I was staring at the list of functions for so long :) -- View this message in context: http://jenkins.361315.n4.nabble.com/Remove-job-from-queue-via-groovy-tp4558034p4558047.html Sent from the Jenkins users mailing list archive at Nabble.com.
Remove job from queue via groovy
Hi,
Is there a way to remove a job from the job queue using a groovy api?
Right now, if I hover my mouse over the red "x" button of a job in the
queue, I can see the remove-from-queue-URL is something like:
http://my.jenkins:8080/queue/item/15/cancelQueue
If I print out all methods and properties for an item of a queue, nothings
stands out to me as the cancel action:
for (anItem in hudson.model.Hudson.instance.getQueue().getItems()) {
anItem.metaClass.methods.each{ p ->
println(p);
}
anItem.metaClass.properties.each { p ->
println("==");
println p.name;
println p.type;
}
}
Any ideas how to do this?
Thanks!
--
View this message in context:
http://jenkins.361315.n4.nabble.com/Remove-job-from-queue-via-groovy-tp4558034p4558034.html
Sent from the Jenkins users mailing list archive at Nabble.com.
Re: Unsubscribe
You unsubscribe the same way you subscribed: Go to groups.google.com -- Sami 2012/4/14 Anton Zavrin : > Unsubscribe doesn't work... > Please, let me know how to unsubscribe ? > > > On Apr 14, 2012, at 12:33 PM, Chuck Doucette wrote: > >> >> >> Sent from my iPhone
Re: Unsubscribe
Unsubscribe doesn't work... Please, let me know how to unsubscribe ? On Apr 14, 2012, at 12:33 PM, Chuck Doucette wrote: > > > Sent from my iPhone
Re: How do I get Jenkins to skip failed branches till they change?
Ok, I've made progress on this. It turns out it was only failing because the git plugin would throw an exception when a submodule couldn't be checked out. I think this is a problem but should basically mark the build as an error and move on, not kill the whole process and thus keep trying to redo the build over and over. On Fri, Apr 13, 2012 at 1:00 PM, fREW Schmidt wrote: > I'm using Jenkins with the Multiple SCMs + Git plugin. Jenkins is > correctly doing a new build for each branch, but for some reason when it > fails a build it just keeps trying to redo the build, even if the branch > has not changed. How can I fix it so that Jenkins will move on to the next > branch and only try to rebuild if the current branch changes? > > Note, I originally asked this question on ServerFault (it's since been > migrated to StackOverflow) so if you answer and also want credit on SO feel > free to copy paste your answer to there: > http://stackoverflow.com/questions/10144733/how-do-i-get-jenkins-to-skip-failed-branches-till-they-change > > -- > fREW Schmidt > http://blog.afoolishmanifesto.com > -- fREW Schmidt http://blog.afoolishmanifesto.com
Re: Jenkins fails to run silently, any tips? (Fedora 7)
The java interpreter is using too much memory, the following works better: nohup java -Xms128m -Xmx256m -jar jenkins.war & On Apr 14, 10:21 am, Erwin Coumans wrote: > I tried to manually start Jenkins by invoking the java interpreter > directory instead of using a service: > It was not clear where jenkins.war is installed using yum, so > searching for it: > > yum install yum-utils > repoquery --list jenkins > /usr/lib/jenkins/jenkins.war > > Now manually running > java -jar jenkins.war > > and all works well, visitinghttp://localhost:8080locally or remotely > works fine. > > Unfortunately we need to run nohup to keep the process running after > logging out from the shell, and now it seems the service is running > out of memory: > > nohup java -jar jenkins.war > nohup: ignoring input and appending output to `nohup.out' > > cat nohup.out > Error occurred during initialization of VM > Could not reserve enough space for object heap > Could not create the Java virtual machine. > > I'll figure out how to deal with the lack of RAM memory. Hopefully > this helps someone else. > Thanks, > Erwin > > On Apr 14, 9:42 am, Erwin Coumans wrote: > > > > > > > > > I installed jenkins (as root) and start the service but I cannot > > connect to the service: > > > wgethttp://localhost:8080/jenkins > > --09:31:54-- http://localhost:8080/jenkins > > => `jenkins' > > Resolving localhost... 127.0.0.1 > > Connecting to localhost|127.0.0.1|:8080... failed: Connection refused. > > > I installed as follows: > > > sudo wget -O > > /etc/yum.repos.d/jenkins.repohttp://pkg.jenkins-ci.org/redhat/jenkins.repo > > sudo rpm --importhttp://pkg.jenkins-ci.org/redhat/jenkins-ci.org.key > > yum install jenkins > > > This is a virtual private server from Godaddy with Fedora release 7. > > It could be that port 8080 is blocked. > > I checked the port in /etc/sysconfig/jenkins and tried "8080" or "80" > > or "8081" without luck. Are there other ways to try it locally, in > > case some ports are blocked? Should I somehow route jenkins through > > Apache so that it doesn't require special 8080 ports? > > > Disabling the local Apache server, httpd, doesn't help either > > /sbin/service httpd stop > > > The Jenkins service can be started: > > /sbin/service jenkins start > > Starting Jenkins [ OK ] > > ls /var/run/jenkins > > /var/run/jenkins.pid > > > So there seems to be a jenkins process started. > > > /sbin/service jenkins stop > > Shutting down Jenkins [FAILED] > > > ls /var/run/jenkins > > reports no file. > > > Unfortunately there is no log file in /var/log/jenkins (the directory > > is empty) > > > cat /etc/*-release reports > > Fedora release 7 (Moonshine) > > > Is there a more verbose way to run Jenkins so that I can figure out > > what it wrong? > > Thanks a lot, > > Erwin
Unsubscribe
Sent from my iPhone
Re: Jenkins fails to run silently, any tips? (Fedora 7)
I tried to manually start Jenkins by invoking the java interpreter directory instead of using a service: It was not clear where jenkins.war is installed using yum, so searching for it: yum install yum-utils repoquery --list jenkins /usr/lib/jenkins/jenkins.war Now manually running java -jar jenkins.war and all works well, visiting http://localhost:8080 locally or remotely works fine. Unfortunately we need to run nohup to keep the process running after logging out from the shell, and now it seems the service is running out of memory: nohup java -jar jenkins.war nohup: ignoring input and appending output to `nohup.out' cat nohup.out Error occurred during initialization of VM Could not reserve enough space for object heap Could not create the Java virtual machine. I'll figure out how to deal with the lack of RAM memory. Hopefully this helps someone else. Thanks, Erwin On Apr 14, 9:42 am, Erwin Coumans wrote: > I installed jenkins (as root) and start the service but I cannot > connect to the service: > > wgethttp://localhost:8080/jenkins > --09:31:54-- http://localhost:8080/jenkins > => `jenkins' > Resolving localhost... 127.0.0.1 > Connecting to localhost|127.0.0.1|:8080... failed: Connection refused. > > I installed as follows: > > sudo wget -O > /etc/yum.repos.d/jenkins.repohttp://pkg.jenkins-ci.org/redhat/jenkins.repo > sudo rpm --importhttp://pkg.jenkins-ci.org/redhat/jenkins-ci.org.key > yum install jenkins > > This is a virtual private server from Godaddy with Fedora release 7. > It could be that port 8080 is blocked. > I checked the port in /etc/sysconfig/jenkins and tried "8080" or "80" > or "8081" without luck. Are there other ways to try it locally, in > case some ports are blocked? Should I somehow route jenkins through > Apache so that it doesn't require special 8080 ports? > > Disabling the local Apache server, httpd, doesn't help either > /sbin/service httpd stop > > The Jenkins service can be started: > /sbin/service jenkins start > Starting Jenkins [ OK ] > ls /var/run/jenkins > /var/run/jenkins.pid > > So there seems to be a jenkins process started. > > /sbin/service jenkins stop > Shutting down Jenkins [FAILED] > > ls /var/run/jenkins > reports no file. > > Unfortunately there is no log file in /var/log/jenkins (the directory > is empty) > > cat /etc/*-release reports > Fedora release 7 (Moonshine) > > Is there a more verbose way to run Jenkins so that I can figure out > what it wrong? > Thanks a lot, > Erwin
Jenkins fails to run silently, any tips? (Fedora 7)
I installed jenkins (as root) and start the service but I cannot connect to the service: wget http://localhost:8080/jenkins --09:31:54-- http://localhost:8080/jenkins => `jenkins' Resolving localhost... 127.0.0.1 Connecting to localhost|127.0.0.1|:8080... failed: Connection refused. I installed as follows: sudo wget -O /etc/yum.repos.d/jenkins.repo http://pkg.jenkins-ci.org/redhat/jenkins.repo sudo rpm --import http://pkg.jenkins-ci.org/redhat/jenkins-ci.org.key yum install jenkins This is a virtual private server from Godaddy with Fedora release 7. It could be that port 8080 is blocked. I checked the port in /etc/sysconfig/jenkins and tried "8080" or "80" or "8081" without luck. Are there other ways to try it locally, in case some ports are blocked? Should I somehow route jenkins through Apache so that it doesn't require special 8080 ports? Disabling the local Apache server, httpd, doesn't help either /sbin/service httpd stop The Jenkins service can be started: /sbin/service jenkins start Starting Jenkins [ OK ] ls /var/run/jenkins /var/run/jenkins.pid So there seems to be a jenkins process started. /sbin/service jenkins stop Shutting down Jenkins [FAILED] ls /var/run/jenkins reports no file. Unfortunately there is no log file in /var/log/jenkins (the directory is empty) cat /etc/*-release reports Fedora release 7 (Moonshine) Is there a more verbose way to run Jenkins so that I can figure out what it wrong? Thanks a lot, Erwin
Re: Artifact Deployment
For the first case, there is a bug on the artifactdeployer plugin : promoted variables are not interpreted. Please raise a bug report for the artifactdeployer component. For the second case, you have to prefile with file:// because a URI is expected by the artifactdeployer plugin. On Sat, Apr 7, 2012 at 7:26 PM, Vikas Kansal wrote: > can someone help me please > > -- > View this message in context: > http://jenkins.361315.n4.nabble.com/Artifact-Deployment-tp4538406p4539778.html > Sent from the Jenkins users mailing list archive at Nabble.com. >
Re: clean up maven repo in Jenkins slave
It's not jenkins who copies the dependencies to this location, its maven. There are multiple reasons which could cause this: - you have configured /opt to be the home directory of your user you running jenkins with. - this location is configured in your settings.xml If you delete all these, maven will just download them the next time again (and slow down the build). If you have multiple maven jobs running at the same time, you should also not delete the directory/repository while a build is running, this would just remove the needed libraries and the build will fail. I recommend you use the 'Config File Provide Plugin' [1] - this will allow you to configure your settings.xml at a central place and select one within your job configuration from a drop down menu. regards Domi [1] https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin On 13.04.2012, at 20:43, JasonX wrote: > I saw maven repo is copied to /opt/.m2 directory on Jenkins slave from > maven server and it fills up Jenkins slave disk. I wanna clean it up. > How can I do it? can I remove all of the repos from Jenkins slave > after each build? is that necessary to keep all dependencies on > Jenkins slave but they are already existing in maven server.
