email-ext plugin
Hi,
I want to use a groovy script in the email-ext plugin, but when I put this
in the Default Subject field:
$DEFAULT_SUBJECT % def tr = build.testResultAction; if (tr?.failCount) {
%(${tr?.failCount} failures ${tr?.failureDiffString}) % } %
In my mail, the groovy code is not interpreted and thus I get following as
mail subject:
pr_7315 - Build # 46 - Still Failing! % def tr = build.testResultAction;
if (tr?.failCount) { %(${tr?.failCount} failures
${tr?.failureDiffString}) % } %
Do I have to install an extra plugin for the groovy code to be interpreted?
Kind regards,
stijn.
--
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.
Checkstyle apparently totally broken
Hey guys, All of my projects are showing stack traces on the Post-build Actions. If I uninstall Checkstyle the problem goes away. Here is the Stack trace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.526.jar!/lib/form/block.jelly:32:22: d:invokeBody hudson/maven/AbstractMavenProject at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at
Archiving artifacts can hang when used with Naginator
If you use the Naginator plugin, and also archive artifacts, you might want to look at a ticket I've just opened: https://issues.jenkins-ci.org/browse/JENKINS-19071 The ticket describes how the Naginator plugin can cause archiving to hang under certain circumstances. Since there seem to be a number of open tickets to do with archiving hanging, I thought I should mention this on the list. Matthew -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom -- 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: Trigger a downstream job which is on another Jenkins instance
I'm trying to use the URLTrigger. I am able to successfully parse the JSON results and get the build number, SCC change number and result out of the JSON http response. My question is this: How to I access these parsed values in my Ant script? On Sunday, 22 April 2012 11:28:30 UTC-4, Steven wrote: I usually use the url trigger for any remote process triggering. But there are a number of triggers that could be used as well as the cli or the build url. I like the url trigger because I can pass parameters and what triggered the build. Steven From: jenkins...@googlegroups.com javascript: [ jenkins...@googlegroups.com javascript:] On Behalf Of buildit [ arvin...@gmail.com javascript:] Sent: Tuesday, April 17, 2012 4:35 PM To: jenkins...@googlegroups.com javascript: Subject: Trigger a downstream job which is on another Jenkins instance Hi All, I have 2 Jenkins instances.I have Jenkins for different projects.I need to kick of a downstream project which is on a different Jenkins instance once the upstream project build is successful. For example project B is downstream to project A.I have project A on jenkins:8080 and project B on jenkins2:8180 I want project B to trigger automatically after project A is build is sucessful. -- View this message in context: http://jenkins.361315.n4.nabble.com/Trigger-a-downstream-job-which-is-on-another-Jenkins-instance-tp4566275p4566275.html Sent from the Jenkins users mailing list archive at Nabble.com. -- 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.
Automatically creating a job inside a folder
I'm working on a script right now to create a new job whenever a new branch
is added to our git repo. I have the python code that will post a job, but
I would like to post a job inside a folder because our Jenkins CI is
already fairly cluttered at the moment due to the large number of projects
we currently have running. The code I currently have is:
import requests
xml_data=open(config_template.xml,'r').read()
headers = {'Content-Type': 'text/xml'}
jenkins_url=http://jenkins_server/createItem;
keyargs= {'params':{'name': 'TEST_JOB_2.0'}, headers :
headers,auth:('user','password'),data:xml_data}
response=requests.post(jenkins_url,**keyargs)
This works fine to post a job, but I couldn't find any parameters I could
pass to create it inside a folder. Is there another rest command that will
move a job to a folder that I could execute afterwards.
--
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: email-ext plugin
You need to use the SCRIPT token and put the script into a file in the
email-templates directory under $JENKINS_HOME.
You can't put groovy directly in the field.
slide
On Tue, Aug 6, 2013 at 12:16 AM, Stijn Deroo-Van Maele
stijn.deroovanma...@gmail.com wrote:
Hi,
I want to use a groovy script in the email-ext plugin, but when I put this
in the Default Subject field:
$DEFAULT_SUBJECT % def tr = build.testResultAction; if (tr?.failCount) {
%(${tr?.failCount} failures ${tr?.failureDiffString}) % } %
In my mail, the groovy code is not interpreted and thus I get following as
mail subject:
pr_7315 - Build # 46 - Still Failing! % def tr = build.testResultAction;
if (tr?.failCount) { %(${tr?.failCount} failures
${tr?.failureDiffString}) % } %
Do I have to install an extra plugin for the groovy code to be interpreted?
Kind regards,
stijn.
--
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.
--
Website: http://earl-of-code.com
--
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.
incremental push of JUnit test results to Jenkins
Hi, I'm looking to find if there is any existing method for incrementally pushing Junit results to Jenkins. For example: A test suite is started, which is described by a JUnit Test Report. As each test case is run, it posts the results of the test back to Jenkins. (Perhaps via REST or some other API). From what I understand, this more usual process is that a TestReport is generated after all test cases in the test suite have run, and is then published as a single XML file for Jenkins to consume. Description of the situation: Currently, triggering a test suite is simply sending the test set to our internal job management system, which handles the scheduling of them against a large compute cluster. If the test suite is successfully scheduled to be run, then the step is marked as having succeeded. We have it setup this way because the test suites are very intensive -- depending on the run it can take over a week to complete. Rather than waiting until the end of the test suite to publish results, we would like each test case to push its result up to Jenkins. This incremental progress reporting would allow better monitoring of jobs throughout the week. Are there any existing plugins or tools associated which allow such a work flow? Cheers, Tom -- 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: Automatically creating a job inside a folder
By folder, do you mean a view created with the View plugin ? If so, you can use a regex in the view definition that selects jobs by a substring in their name, as there will be no need to do anything extra in your script. -- 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: Checkstyle apparently totally broken
Is your maven plugin installed and enabled? Am 06.08.2013 um 15:06 schrieb fREW Schmidt fri...@gmail.com: Hey guys, All of my projects are showing stack traces on the Post-build Actions. If I uninstall Checkstyle the problem goes away. Here is the Stack trace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.526.jar!/lib/form/block.jelly:32:22: d:invokeBody hudson/maven/AbstractMavenProject at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at
Re: Automatically creating a job inside a folder
It's actually a folder plugin offered through cloudbees, which I hadn't realized prior to posting this question. Looking at the documentation for it there probably isn't the available functionality to do what I want it to do. Your view suggestion is a good alternative though. Thank you. On Tuesday, August 6, 2013 1:27:14 PM UTC-4, Gareth Bowles wrote: By folder, do you mean a view created with the View plugin ? If so, you can use a regex in the view definition that selects jobs by a substring in their name, as there will be no need to do anything extra in your script. -- 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.
Cancel a Queue via Jenkins API
Hello, I want to cancel a queue item in a Job that has permissions set. I have tried for example to cancel a queue item with ID 65 (I get the ID from the Queue Api: queue/api/json?pretty=true): http://jenkins_server/queue/cancelItem?id=65 or using the token that job has set: http://jenkins_server/queue/cancelItem?token=myTokenid=65 but both throws an error: javax.servlet.ServletException: java.lang.IllegalAccessException: POST is required for public org.kohsuke.stapler.HttpResponse hudson.model.Queue.doCancelItem(int) throws java.io.IOException,javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:693) How should I use the API to cancel an specific item of a Queue? Is token necessary since is Jenkins with permissions set? Thanks for the help. -- 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: Automatically creating a job inside a folder
Try http://jenkins/job/foldername/createItem.
On 06.08.2013, at 17:17, Jacob Schlather jacob.schlat...@gmail.com wrote:
I'm working on a script right now to create a new job whenever a new branch
is added to our git repo. I have the python code that will post a job, but I
would like to post a job inside a folder because our Jenkins CI is already
fairly cluttered at the moment due to the large number of projects we
currently have running. The code I currently have is:
import requests
xml_data=open(config_template.xml,'r').read()
headers = {'Content-Type': 'text/xml'}
jenkins_url=http://jenkins_server/createItem;
keyargs= {'params':{'name': 'TEST_JOB_2.0'}, headers :
headers,auth:('user','password'),data:xml_data}
response=requests.post(jenkins_url,**keyargs)
This works fine to post a job, but I couldn't find any parameters I could
pass to create it inside a folder. Is there another rest command that will
move a job to a folder that I could execute afterwards.
--
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: Automatically creating a job inside a folder
Great. That worked.
Do you by chance know why my jobs would spawn as disabled rather than
enabled?
On Tuesday, August 6, 2013 2:59:18 PM UTC-4, Daniel Beck wrote:
Try http://jenkins/job/foldername/createItem.
On 06.08.2013, at 17:17, Jacob Schlather jacob.s...@gmail.comjavascript:
wrote:
I'm working on a script right now to create a new job whenever a new
branch is added to our git repo. I have the python code that will post a
job, but I would like to post a job inside a folder because our Jenkins CI
is already fairly cluttered at the moment due to the large number of
projects we currently have running. The code I currently have is:
import requests
xml_data=open(config_template.xml,'r').read()
headers = {'Content-Type': 'text/xml'}
jenkins_url=http://jenkins_server/createItem;
keyargs= {'params':{'name': 'TEST_JOB_2.0'}, headers :
headers,auth:('user','password'),data:xml_data}
response=requests.post(jenkins_url,**keyargs)
This works fine to post a job, but I couldn't find any parameters I
could pass to create it inside a folder. Is there another rest command that
will move a job to a folder that I could execute afterwards.
--
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-use...@googlegroups.com javascript:.
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: Cancel a Queue via Jenkins API
Send a POST request. https://en.wikipedia.org/wiki/POST_%28HTTP%29 How this works depends on how you send the requests in the first place. Example using the `curl` command line program: curl --data '' 'http://jenkins/queue/cancelItem?id=65' `--data` causes the request to be sent as POST, '' means simply that we send an empty POST body. On 06.08.2013, at 20:37, tiago fernandez tiaguin12...@gmail.com wrote: Hello, I want to cancel a queue item in a Job that has permissions set. I have tried for example to cancel a queue item with ID 65 (I get the ID from the Queue Api: queue/api/json?pretty=true): http://jenkins_server/queue/cancelItem?id=65 or using the token that job has set: http://jenkins_server/queue/cancelItem?token=myTokenid=65 but both throws an error: javax.servlet.ServletException: java.lang.IllegalAccessException: POST is required for public org.kohsuke.stapler.HttpResponse hudson.model.Queue.doCancelItem(int) throws java.io.IOException,javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:693) How should I use the API to cancel an specific item of a Queue? Is token necessary since is Jenkins with permissions set? Thanks for the help. -- 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: Automatically creating a job inside a folder
Can't think of a reason other than possibly 'disabledtrue/disabled' in your
template.
Are your template file and the config.xml of the created job different in any
way?
What happens when you create a new freestyle job using the UI, get its
config.xml after it's saved, and post that? Still disabled?
On 06.08.2013, at 21:05, Jacob Schlather jacob.schlat...@gmail.com wrote:
Great. That worked.
Do you by chance know why my jobs would spawn as disabled rather than enabled?
On Tuesday, August 6, 2013 2:59:18 PM UTC-4, Daniel Beck wrote:
Try http://jenkins/job/foldername/createItem.
On 06.08.2013, at 17:17, Jacob Schlather jacob.s...@gmail.com wrote:
I'm working on a script right now to create a new job whenever a new branch
is added to our git repo. I have the python code that will post a job, but
I would like to post a job inside a folder because our Jenkins CI is
already fairly cluttered at the moment due to the large number of projects
we currently have running. The code I currently have is:
import requests
xml_data=open(config_template.xml,'r').read()
headers = {'Content-Type': 'text/xml'}
jenkins_url=http://jenkins_server/createItem;
keyargs= {'params':{'name': 'TEST_JOB_2.0'}, headers :
headers,auth:('user','password'),data:xml_data}
response=requests.post(jenkins_url,**keyargs)
This works fine to post a job, but I couldn't find any parameters I could
pass to create it inside a folder. Is there another rest command that will
move a job to a folder that I could execute afterwards.
--
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-use...@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.
--
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: Automatically creating a job inside a folder
Very strange disabled true /disabled was in my template. I had made a
jenkins job as my template and copied that config.xml for my template.
Changing that to false fixed the issue. Perhaps the project was disabled at
the time I copied it without realizing. Thanks a lot.
On Tuesday, August 6, 2013 3:10:50 PM UTC-4, Daniel Beck wrote:
Can't think of a reason other than possibly 'disabledtrue/disabled' in
your template.
Are your template file and the config.xml of the created job different in
any way?
What happens when you create a new freestyle job using the UI, get its
config.xml after it's saved, and post that? Still disabled?
On 06.08.2013, at 21:05, Jacob Schlather jacob.s...@gmail.comjavascript:
wrote:
Great. That worked.
Do you by chance know why my jobs would spawn as disabled rather than
enabled?
On Tuesday, August 6, 2013 2:59:18 PM UTC-4, Daniel Beck wrote:
Try http://jenkins/job/foldername/createItem.
On 06.08.2013, at 17:17, Jacob Schlather jacob.s...@gmail.com wrote:
I'm working on a script right now to create a new job whenever a new
branch is added to our git repo. I have the python code that will post a
job, but I would like to post a job inside a folder because our Jenkins CI
is already fairly cluttered at the moment due to the large number of
projects we currently have running. The code I currently have is:
import requests
xml_data=open(config_template.xml,'r').read()
headers = {'Content-Type': 'text/xml'}
jenkins_url=http://jenkins_server/createItem;
keyargs= {'params':{'name': 'TEST_JOB_2.0'}, headers :
headers,auth:('user','password'),data:xml_data}
response=requests.post(jenkins_url,**keyargs)
This works fine to post a job, but I couldn't find any parameters I
could pass to create it inside a folder. Is there another rest command that
will move a job to a folder that I could execute afterwards.
--
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-use...@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-use...@googlegroups.com javascript:.
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: Checkstyle apparently totally broken
According to the wiki [1, 2], Maven plugin is an _optional_ dependency of both Checkstyle and its (only, besides Ant) mandatory dependency, Analysis Core. Is this information correct? So far, JENKINS-18922/19000 seemed to only happen when missing mandatory dependencies, like jobConfigHistory - Maven... 1: https://wiki.jenkins-ci.org/display/JENKINS/Checkstyle+Plugin#CheckstylePlugin-PluginInformation 2: https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-PluginInformation On 06.08.2013, at 19:30, Ulli Hafner ullrich.haf...@gmail.com wrote: Is your maven plugin installed and enabled? Am 06.08.2013 um 15:06 schrieb fREW Schmidt fri...@gmail.com: Hey guys, All of my projects are showing stack traces on the Post-build Actions. If I uninstall Checkstyle the problem goes away. Here is the Stack trace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.526.jar!/lib/form/block.jelly:32:22: d:invokeBody hudson/maven/AbstractMavenProject at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at
Build Flow Plugin - reporting capability
Hi, The Jenkins Build Flow Plugin is replacing our massive home grown build system. A couple of times a year, our build team will create a Build Flow job from a template to perform the massive build which can last for several days. The build team will execute the Build Flow job until all sub-jobs have been successfully built. The build team can choose to build 50% of the jobs on a given day and then build the other 50% the next day (or however they decide to break it up)... That leads to my question I'd like to be able to inform the builders which sub-jobs have been completed within the context of the massive Build Flow job. Currently, that information is written to the Console Log as shown below: ## ###RESULTS ### ## SUCCESS : JOB1 JOB2 JOB3 SKIPPED : NAF_WPF_NET ABORTED : FAILURE : GERMAINE UNSTABLE : NOT BUILT: MIDTIER ESL XRDS1 RULES NAF_NET ## ###END RESULTS ### ## Currently, the build team must scan all the console logs in order to determine what has/has not been built, and to figure out what they still need to build. This is difficult for them since there are about 50 different projects that must be built. I am trying to find a solution that would allow them to determine what still needs to be built. Here are a couple of ideas: 1) In the Build History, change the job names to include all of the sub-jobs that were successfully built for that job run (e.g. change #21 to #21 JOB1 JOB2 JOB3). But, I don't think there is a way to do that for Build Flow jobs. Does anyone know if this is possible? 2) Write a shell script that reads the console log files. However, this is a poor solution since it does not integrate with Jenkins (i.e. run some script outside of Jenkins). 3) Other??? Q. Can anyone think of a good way to report all of the sub-jobs that have successfully completed within the context of multiple Build Flow job runs? Thank you for taking the time to read this. Bob *** *** *** This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message. -- 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: Trigger a downstream job which is on another Jenkins instance
You might have an easier time parsing the XML results and using those in an Ant script. Ant works with XML much better than it does with JSON. http://ant.apache.org/manual/Tasks/xmlproperty.html -- Jerry On Tuesday, August 6, 2013 11:15:17 AM UTC-4, Stephen Tunney wrote: I'm trying to use the URLTrigger. I am able to successfully parse the JSON results and get the build number, SCC change number and result out of the JSON http response. My question is this: How to I access these parsed values in my Ant script? On Sunday, 22 April 2012 11:28:30 UTC-4, Steven wrote: I usually use the url trigger for any remote process triggering. But there are a number of triggers that could be used as well as the cli or the build url. I like the url trigger because I can pass parameters and what triggered the build. Steven From: jenkins...@googlegroups.com [jenkins...@googlegroups.com] On Behalf Of buildit [arvin...@gmail.com] Sent: Tuesday, April 17, 2012 4:35 PM To: jenkins...@googlegroups.com Subject: Trigger a downstream job which is on another Jenkins instance Hi All, I have 2 Jenkins instances.I have Jenkins for different projects.I need to kick of a downstream project which is on a different Jenkins instance once the upstream project build is successful. For example project B is downstream to project A.I have project A on jenkins:8080 and project B on jenkins2:8180 I want project B to trigger automatically after project A is build is sucessful. -- View this message in context: http://jenkins.361315.n4.nabble.com/Trigger-a-downstream-job-which-is-on-another-Jenkins-instance-tp4566275p4566275.html Sent from the Jenkins users mailing list archive at Nabble.com. -- 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.
hopefully simple pipeline question
Hi All, Job A is a build job that is triggered by SCM changes, and Job B is a downstream test job configured to use the same node and same workspace. If Job A #1 is currently running, and Job A receives another trigger from SCM (Job A #2), how do I ensure that Job B #1 (which hasn't been triggered yet) takes precedence over Job A #2 for that one executor spot available on the machine? Thanks, Mishael -- 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.
maven release plugin and multi-module releases with Sonar
I have a post-build action that runs Sonar analysis on our projects. I can't say that I know whether this worked before since we have very few multi-module projects but after the release:perform phase when doing a Maven release, it updates and checks in the POMs with the next DEV version and then immediately calls the Sonar action. When Sonar attempts to run, it can't find some JAR's that are part of the multi-module project because it actually hasn't done a build yet for the new DEV version. Am I doing something wrong or is this a problem with the release process or am I missing something simple? -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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: hopefully simple pipeline question
You could use the parameterized trigger plugin and use the build step as the first action in the upstream build. That way, B will be queued before A polls SCM again. If necessary, add a Quiet Period to A in its advanced project options for the time it takes A to check out from SCM (or rather, to offset the delay from build start to first build step). On 06.08.2013, at 22:55, Mishael Kim mish...@gmail.com wrote: Hi All, Job A is a build job that is triggered by SCM changes, and Job B is a downstream test job configured to use the same node and same workspace. If Job A #1 is currently running, and Job A receives another trigger from SCM (Job A #2), how do I ensure that Job B #1 (which hasn't been triggered yet) takes precedence over Job A #2 for that one executor spot available on the machine? Thanks, Mishael -- 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: Checkstyle apparently totally broken
Right, I have not instaled Maven, though I'll try it tomorrow and see if it fixes the problem I guess. On Tue, Aug 06, 2013 at 09:37:46PM +0200, Daniel Beck wrote: According to the wiki [1, 2], Maven plugin is an _optional_ dependency of both Checkstyle and its (only, besides Ant) mandatory dependency, Analysis Core. Is this information correct? So far, JENKINS-18922/19000 seemed to only happen when missing mandatory dependencies, like jobConfigHistory - Maven... 1: https://wiki.jenkins-ci.org/display/JENKINS/Checkstyle+Plugin#CheckstylePlugin-PluginInformation 2: https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-PluginInformation -- fREW Schmidt http://blog.afoolishmanifesto.com pgprIOcGs_4ae.pgp Description: PGP signature
Re: maven release plugin and multi-module releases with Sonar
If it helps...here is the Jenkins console output from the failed release. I've removed much of the nitty gritty details until the end portion that fails. Hopefully it makes sense. In all steps, the reactor build order is: *apps-thor -- thor-models -- thor-service-wrapper -- thor-web*. However, in the step that fails, it shows the correct order, then appears to do: *apps-thor -- thor-web* and skips models and wrapper and shows them as skipped. During a normal build of the apps-thor parent pom, I don't see it attempt to resolve any POM or JAR from any of the modules, but in the end failure case it does. *Deleting project workspace... done* *Checkout:* *Parsing POMs* *Executing Maven: -B -f /home/adminuser/.jenkins-slave/workspace/apps-THOR/pom.xml -DdevelopmentVersion=1.6.6-SNAPSHOT -DreleaseVersion=1.6.5 -Dresume=false release:prepare release:perform -Darguments=-DskipTests* *[INFO] Scanning for projects...* *[INFO] * *[INFO] Reactor Build Order:* *[INFO] * *[INFO] apps-thor* *[INFO] thor-models* *[INFO] thor-service-wrapper* *[INFO] thor-web* *[INFO] * *[INFO] * *[INFO] Building apps-thor 1.6.5-SNAPSHOT* *[INFO] * *[INFO] * *[INFO] --- maven-release-plugin:2.4.1:prepare (default-cli) @ apps-thor --- * *[INFO] [INFO] * *[INFO] [INFO] Reactor Build Order:* *[INFO] [INFO] * *[INFO] [INFO] apps-thor* *[INFO] [INFO] thor-models* *[INFO] [INFO] thor-service-wrapper* *[INFO] [INFO] thor-web* *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] Building apps-thor 1.6.5* *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] Building thor-models 1.6.5* *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] Building thor-service-wrapper 1.6.5* *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] Reactor Summary:* *[INFO] [INFO] * *[INFO] [INFO] apps-thor . SUCCESS [1.772s]* *[INFO] [INFO] thor-models ... SUCCESS [7.621s]* *[INFO] [INFO] thor-service-wrapper .. SUCCESS [2.794s]* *[INFO] [INFO] thor-web .. SUCCESS [1:57.294s]* *[INFO] [INFO] * *[INFO] [INFO] BUILD SUCCESS* *[INFO] [INFO] * *[INFO] [INFO] Total time: 2:10.135s* *[INFO] [INFO] Finished at: Tue Aug 06 11:17:35 MDT 2013* *[INFO] [INFO] Final Memory: 44M/265M* *[INFO] [INFO] * *[INFO] Checking in modified POMs...* *[INFO] --- maven-release-plugin:2.4.1:perform (default-cli) @ apps-thor --- * *[INFO] [INFO] * *[INFO] [INFO] Reactor Build Order:* *[INFO] [INFO] * *[INFO] [INFO] apps-thor* *[INFO] [INFO] thor-models* *[INFO] [INFO] thor-service-wrapper* *[INFO] [INFO] thor-web* *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] Building apps-thor 1.6.5* *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] Building thor-models 1.6.5* *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] Building thor-service-wrapper 1.6.5* *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] Building thor-web 1.6.5* *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] * *[INFO] [INFO] Reactor Summary:* *[INFO] [INFO] * *[INFO] [INFO] apps-thor . SUCCESS
Best way to get have Jenkins use OpenJDK on Ubuntu 12.04 Server
I have a Jenkins server that has been running well with various versions of the Sun Java 7 JDK for a while now, although I am not that familiar with Jenkins. However, my project would also like to officially support OpenJDK now. I'd like to install and configure jobs to use multiple specific versions of OpenJDK. Because of this, I can't install from the Ubuntu repository...I need fine grained control and don't want a system update to modify my builds. The only other installer options are extract zip file and run command. There is an OpenJDK Installer plugin, but it is for RedHat/Centos and is repo based, which (again) won't work. I cannot locate zip files for versions of the 64 bit OpenJDK on the internet. Can anyone tell me a good way to get specific versions of those? Also, whats the best way to configure Jenkins to use those? Put them on a server and use the extract from zip installer? It seems easier to just unzip on the build machine and configure Jenkins to use that as the JAVA_HOME for certain jobs, but I don't see any way to do that. What are folks doing in this regard? I'll also have the same issue if the decision to support the IBM JRE happens too. Thanks, Dave -- 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: Best way to get have Jenkins use OpenJDK on Ubuntu 12.04 Server
Assuming that you can get a JAVA_HOME per version (can't help with that one at the moment I'm afraid), then I think you'll need to set up each version in the Manage Jenkins / Configure System (look under JDK to find the JDK entries). You can then either stick the JAVA_HOME for each version in on that page. Hope that helps point you in the right direction on that part... (and hopefully I'm correct! :) ) Richard. On Wed, Aug 7, 2013 at 3:05 PM, David Vree david.h.v...@gmail.com wrote: I have a Jenkins server that has been running well with various versions of the Sun Java 7 JDK for a while now, although I am not that familiar with Jenkins. However, my project would also like to officially support OpenJDK now. I'd like to install and configure jobs to use multiple specific versions of OpenJDK. Because of this, I can't install from the Ubuntu repository...I need fine grained control and don't want a system update to modify my builds. The only other installer options are extract zip file and run command. There is an OpenJDK Installer plugin, but it is for RedHat/Centos and is repo based, which (again) won't work. I cannot locate zip files for versions of the 64 bit OpenJDK on the internet. Can anyone tell me a good way to get specific versions of those? Also, whats the best way to configure Jenkins to use those? Put them on a server and use the extract from zip installer? It seems easier to just unzip on the build machine and configure Jenkins to use that as the JAVA_HOME for certain jobs, but I don't see any way to do that. What are folks doing in this regard? I'll also have the same issue if the decision to support the IBM JRE happens too. Thanks, Dave -- 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: Best way to get have Jenkins use OpenJDK on Ubuntu 12.04 Server
omg!! - you have to uncheck the Install automatically boxand then you can enter the JAVA_HOME. Doh! That answers part two of my question. Now I just need to find OpenJDK 7 JDK/JRE Ubuntu zip files. On Tuesday, August 6, 2013 11:11:47 PM UTC-4, Richard Bywater wrote: Assuming that you can get a JAVA_HOME per version (can't help with that one at the moment I'm afraid), then I think you'll need to set up each version in the Manage Jenkins / Configure System (look under JDK to find the JDK entries). You can then either stick the JAVA_HOME for each version in on that page. Hope that helps point you in the right direction on that part... (and hopefully I'm correct! :) ) Richard. On Wed, Aug 7, 2013 at 3:05 PM, David Vree david@gmail.comjavascript: wrote: I have a Jenkins server that has been running well with various versions of the Sun Java 7 JDK for a while now, although I am not that familiar with Jenkins. However, my project would also like to officially support OpenJDK now. I'd like to install and configure jobs to use multiple specific versions of OpenJDK. Because of this, I can't install from the Ubuntu repository...I need fine grained control and don't want a system update to modify my builds. The only other installer options are extract zip file and run command. There is an OpenJDK Installer plugin, but it is for RedHat/Centos and is repo based, which (again) won't work. I cannot locate zip files for versions of the 64 bit OpenJDK on the internet. Can anyone tell me a good way to get specific versions of those? Also, whats the best way to configure Jenkins to use those? Put them on a server and use the extract from zip installer? It seems easier to just unzip on the build machine and configure Jenkins to use that as the JAVA_HOME for certain jobs, but I don't see any way to do that. What are folks doing in this regard? I'll also have the same issue if the decision to support the IBM JRE happens too. Thanks, Dave -- 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-use...@googlegroups.com javascript:. 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: Is there a way to make discard old builds happen right now?
This worked for me except for one thing. In a multi-module Maven project
the child modules still have all their builds on the filesystem, even
though they are gone in the UI.
On Friday, October 7, 2011 6:58:50 PM UTC-4, jdhein wrote:
On Oct 7, 4:11 am, Christopher Orr ch...@orr.me.uk wrote:
On 06/10/11 21:19, jdhein wrote:
My organization has just tons of projects in Jenkins, many of which
are not active and have not built in some time, some of them haven't
built in over 17 months. I have gone through and turned on discard
old builds with a max of 10 builds. However, it has been weeks since
changing this setting and Jenkins has not deleted the excess builds. I
am guessing I have to poke the bear by kicking off a build... only, I
don't want to do this for projects I am not directly involved with.
Is there a way to tell Jenkins to go ahead and discard the old builds
right now?
You can use the Script Console to fetch the jobs you want, and then call
logRotate() on each of them.
Probably something like this should work, not that I've tested it:
for(job in Hudson.instance.items) {
job.logRotate()
}
Take a look at the examples on the wiki for more info, and if you come
up with something good, you can add it to the list:
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Script+Console
Regards,
Chris
Thanks, the groovy script you gave me worked like a champ with the
only change I made being to add an import:
import hudson.model.*
for(job in Hudson.instance.items) {
job.logRotate()
}
Honestly, without the groovy script you gave me I would not have been
able to come up with this without investing a bunch of time
researching how Jenkins works and how to write groovy scripts. So
thanks a bunch!
--
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.
User account considered for execution
Hi Team, I am new user of Jenkins and have a question. 1. I created job which executes the shell script. 2. Configured users using Jenkins own database and was able to login to Jenkins and execute the job. Now when the shell execution is happening which User is considered for execution? - Is this going to be login user? if yes do this user credentials should match the credentials of the enterprise user.? - Is this going to be the user who installed Jenkins? or by default will it be administrator. Thanks in advance for help. Thanks, Rudra -- 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: Is there a way to make discard old builds happen right now?
Interesting - do they get cleaned up under normal circumstances? (i.e. when
a normal discard is done)
Richard.
On Wed, Aug 7, 2013 at 4:24 PM, David Vree david.h.v...@gmail.com wrote:
This worked for me except for one thing. In a multi-module Maven project
the child modules still have all their builds on the filesystem, even
though they are gone in the UI.
On Friday, October 7, 2011 6:58:50 PM UTC-4, jdhein wrote:
On Oct 7, 4:11 am, Christopher Orr ch...@orr.me.uk wrote:
On 06/10/11 21:19, jdhein wrote:
My organization has just tons of projects in Jenkins, many of which
are not active and have not built in some time, some of them haven't
built in over 17 months. I have gone through and turned on discard
old builds with a max of 10 builds. However, it has been weeks since
changing this setting and Jenkins has not deleted the excess builds.
I
am guessing I have to poke the bear by kicking off a build... only, I
don't want to do this for projects I am not directly involved with.
Is there a way to tell Jenkins to go ahead and discard the old builds
right now?
You can use the Script Console to fetch the jobs you want, and then
call
logRotate() on each of them.
Probably something like this should work, not that I've tested it:
for(job in Hudson.instance.items) {
job.logRotate()
}
Take a look at the examples on the wiki for more info, and if you come
up with something good, you can add it to the list:
https://wiki.jenkins-ci.**org/display/JENKINS/Jenkins+**Script+Consolehttps://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Script+Console
Regards,
Chris
Thanks, the groovy script you gave me worked like a champ with the
only change I made being to add an import:
import hudson.model.*
for(job in Hudson.instance.items) {
job.logRotate()
}
Honestly, without the groovy script you gave me I would not have been
able to come up with this without investing a bunch of time
researching how Jenkins works and how to write groovy scripts. So
thanks a bunch!
--
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: User account considered for execution
login user no need to match with enterprise user On Wed, Aug 7, 2013 at 10:02 AM, Raghava Rudrakanth P V potturu.ru...@gmail.com wrote: Hi Team, I am new user of Jenkins and have a question. 1. I created job which executes the shell script. 2. Configured users using Jenkins own database and was able to login to Jenkins and execute the job. Now when the shell execution is happening which User is considered for execution? - Is this going to be login user? if yes do this user credentials should match the credentials of the enterprise user.? - Is this going to be the user who installed Jenkins? or by default will it be administrator. Thanks in advance for help. Thanks, Rudra -- 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. -- Bala.ch -- 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: User account considered for execution
If you are referring to which user will the shell execution happen under, it will be the user which Jenkins is running as. Richard. On Wed, Aug 7, 2013 at 4:32 PM, Raghava Rudrakanth P V potturu.ru...@gmail.com wrote: Hi Team, I am new user of Jenkins and have a question. 1. I created job which executes the shell script. 2. Configured users using Jenkins own database and was able to login to Jenkins and execute the job. Now when the shell execution is happening which User is considered for execution? - Is this going to be login user? if yes do this user credentials should match the credentials of the enterprise user.? - Is this going to be the user who installed Jenkins? or by default will it be administrator. Thanks in advance for help. Thanks, Rudra -- 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: User account considered for execution
Hi Richard, Thanks for reply, I am bit confused again. - Consider I Logged-In to Jenkins with User account Test1 (this account is not existed on network). - When job is called, batch script will create folders remove. But Test1 doesn't have permissions (this user itself not existed on the system). Will this be successful execution if yes considering which user Jenkins created the folders? I tried this on windows, but who ever user logged in the create and deletion of folders is successful. - Started by user test user http://localhost:8080/user/testUser Building in workspace C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspace [workspace] $ cmd /c call C:\Windows\TEMP\hudson7256762012989360322.bat C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspaceecho Test Call from Jenkins Test Call from Jenkins C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspaceecho user executing - user executing - C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspacemkdir c:\JenkinsCreatedFolder C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspacermdir c:\JenkinsCreatedFolder1 C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspaceexit 0 Finished: SUCCESS - Thanks, Rudra On 7 August 2013 10:16, Richard Bywater rich...@byh2o.com wrote: If you are referring to which user will the shell execution happen under, it will be the user which Jenkins is running as. Richard. On Wed, Aug 7, 2013 at 4:32 PM, Raghava Rudrakanth P V potturu.ru...@gmail.com wrote: Hi Team, I am new user of Jenkins and have a question. 1. I created job which executes the shell script. 2. Configured users using Jenkins own database and was able to login to Jenkins and execute the job. Now when the shell execution is happening which User is considered for execution? - Is this going to be login user? if yes do this user credentials should match the credentials of the enterprise user.? - Is this going to be the user who installed Jenkins? or by default will it be administrator. Thanks in advance for help. Thanks, Rudra -- 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 a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/tqc-8EytDmc/unsubscribe. To unsubscribe from this group and all its topics, 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.
