[JIRA] (JENKINS-6965) GT seems to loose it's connection to Gerrit without re-connecting
Ola Sandstrom reopened JENKINS-6965 GT seems to loose it's connection to Gerrit without re-connecting Yesterday, we stopped and started gerrit/git. >From that point, gerrit never triggered Jenkins, until we restarted the gerrit-trigger. We're using v 2.5.1 of the plugin, 1.456 of Jenkins. Change By: Ola Sandstrom (06/Sep/12 6:52 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15057) manual plugin upload doesn't follow plugin dependencies
Max Spring created JENKINS-15057 manual plugin upload doesn't follow plugin dependencies Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 06/Sep/12 4:33 AM Description: When manually uploading a plugin X (Manage Plugins -> Advanced -> Upload Plugin) Jenkins does not automatically install plugins which X depends on, unlike with the regular plugin installation from the catalog (Manage Plugins -> Available). Environment: Linux Project: Jenkins Priority: Minor Reporter: Max Spring This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15053) Add parameter substitution for p4 user config field
SCM/JIRA link daemon resolved JENKINS-15053 as Fixed Add parameter substitution for p4 user config field Change By: SCM/JIRA link daemon (06/Sep/12 3:34 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15053) Add parameter substitution for p4 user config field
SCM/JIRA link daemon commented on JENKINS-15053 Add parameter substitution for p4 user config field Code changed in jenkins User: Rob Petti Path: src/main/java/hudson/plugins/perforce/PerforceSCM.java http://jenkins-ci.org/commit/perforce-plugin/07728739877255e61f634e32b6bd002f4dde97d6 Log: [FIXED JENKINS-15053] add parameter substitution support for P4USER and P4PORT This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15053) Add parameter substitution for p4 user config field
Colin Johnson commented on JENKINS-15053 Add parameter substitution for p4 user config field Thanks for picking up the ticket so quickly - tomorrow I will give try the same global parameter substitution with the P4PORT and password fields as well to see if these fields have problems. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15053) Add parameter substitution for p4 user config field
Rob Petti commented on JENKINS-15053 Add parameter substitution for p4 user config field Problem does not seem specific to global parameters, but is related to the P4USER field itself. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15053) Add parameter substitution for p4 user config field
Rob Petti updated JENKINS-15053 Add parameter substitution for p4 user config field Change By: Rob Petti (06/Sep/12 3:26 AM) Summary: Add support parameter substitution for Global Properties in Perforce Plugin p4 user config field This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15053) Add support for Global Properties in Perforce Plugin
Rob Petti assigned JENKINS-15053 to Rob Petti Add support for Global Properties in Perforce Plugin Change By: Rob Petti (06/Sep/12 3:20 AM) Assignee: Rob Petti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14759) Job created by posting config.xml to /createItem does not set GitHub webhook
dogfood commented on JENKINS-14759 Job created by posting config.xml to /createItem does not set GitHub webhook Integrated in jenkins_main_trunk #1895 [FIXED JENKINS-14759] Job created by posting config.xml to /createItem does not set GitHub webhook. (Revision 597ea1e6a2c8ec9aac432b6955417afb76588398) Result = SUCCESS Jesse Glick : 597ea1e6a2c8ec9aac432b6955417afb76588398 Files : core/src/main/java/hudson/triggers/Trigger.java test/src/test/java/hudson/triggers/TriggerStartTest.java test/pom.xml core/src/main/java/hudson/model/ItemGroupMixIn.java core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/model/AbstractItem.java core/src/main/java/hudson/model/Items.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14759) Job created by posting config.xml to /createItem does not set GitHub webhook
SCM/JIRA link daemon resolved JENKINS-14759 as Fixed Job created by posting config.xml to /createItem does not set GitHub webhook Change By: SCM/JIRA link daemon (06/Sep/12 12:31 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14759) Job created by posting config.xml to /createItem does not set GitHub webhook
SCM/JIRA link daemon commented on JENKINS-14759 Job created by posting config.xml to /createItem does not set GitHub webhook Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/AbstractItem.java core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/model/ItemGroupMixIn.java core/src/main/java/hudson/model/Items.java core/src/main/java/hudson/triggers/Trigger.java test/pom.xml test/src/test/java/hudson/triggers/TriggerStartTest.java http://jenkins-ci.org/commit/jenkins/597ea1e6a2c8ec9aac432b6955417afb76588398 Log: [FIXED JENKINS-14759] Job created by posting config.xml to /createItem does not set GitHub webhook. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15056) Performance plugin should create one plot per test method
Frank Ren created JENKINS-15056 Performance plugin should create one plot per test method Issue Type: Bug Affects Versions: current Assignee: Manuel Carrasco Components: performance-plugin Created: 05/Sep/12 11:52 PM Description: Performance plugin currently create one plot graph per TEST-xxx.xml file, which is not meaningful when there are multiple methods inside one file, the average will be calculated across all the test methods. Each test method are testing stuff on different things, so plot on the average of all of them doesn't make sense. The table under performance graph is good, as it shows each method's result, I wish it could be displayed as graph plot as well(one graph per method). Project: Jenkins Priority: Major Reporter: Frank Ren This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12610) java.io.IOException: Unable to delete - Deleting Project
cowwoc commented on JENKINS-12610 java.io.IOException: Unable to delete - Deleting Project Ah. It turns out that under OSX 10.7 (which is what I'm using) file.encoding is set to US-ASCII (in spite of encoding being set to UTF-8 in the OS). See http://java.net/jira/browse/MACOSX_PORT-165 for the related bug report. NOTE: This does not solve the problem reported by Rafael since he was running under Linux. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14912) Gradle plugin - Permission denied when running gradlew
Justin Ryan commented on JENKINS-14912 Gradle plugin - Permission denied when running gradlew I'm seeing the make executable functionality turned on by default, which then changes the permissions to something like this on Amazon Linux AMI 2011.09: --wxr-x--T 1 builds nac 5064 Sep 5 16:28 gradlew Then I get a permission denied error. I think the what chmod is being run is wrong. The first fix is to stop setting executable by default. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12610) java.io.IOException: Unable to delete - Deleting Project
cowwoc commented on JENKINS-12610 java.io.IOException: Unable to delete - Deleting Project I have the same problem (unicode characters and LANG set to UTF8). I can delete these files from a linux shell. Why can't Java delete these files? What can I do to troubleshoot this further and/or fix the problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14144) Build config history getting spammed
Gregory Boissinot commented on JENKINS-14144 Build config history getting spammed Hugo, Darragh, Is the issue happens for all your jobs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14272) allow defining custom path to gradlew (gradle wrapper) scipt
Justin Ryan resolved JENKINS-14272 as Duplicate allow defining custom path to gradlew (gradle wrapper) scipt Duplicate of JENKINS-12769. (The one without spelling mistakes) Change By: Justin Ryan (05/Sep/12 9:28 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13857) Publish Build - Discard Old Builds Status Code: 500 Caused by: java.lang.IllegalArgumentException: Specified type class hudson.plugins.build_publisher.BuildPublisher is not assi
SCM/JIRA link daemon commented on JENKINS-13857 Publish Build - Discard Old Builds Status Code: 500 Caused by: java.lang.IllegalArgumentException: Specified type class hudson.plugins.build_publisher.BuildPublisher is not assignable to the expected class hudson.tasks.LogRotator Code changed in jenkins User: Vojtech Juranek Path: src/main/java/hudson/plugins/build_publisher/BuildPublisher.java http://jenkins-ci.org/commit/build-publisher-plugin/b6578a22c58afb40aaa21988891aaa13860494c4 Log: [FIXED JENKINS-13857] Changes in 1.463 requires select LogRotator JSON from the request This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13857) Publish Build - Discard Old Builds Status Code: 500 Caused by: java.lang.IllegalArgumentException: Specified type class hudson.plugins.build_publisher.BuildPublisher is not assi
SCM/JIRA link daemon resolved JENKINS-13857 as Fixed Publish Build - Discard Old Builds Status Code: 500 Caused by: java.lang.IllegalArgumentException: Specified type class hudson.plugins.build_publisher.BuildPublisher is not assignable to the expected class hudson.tasks.LogRotator Change By: SCM/JIRA link daemon (05/Sep/12 9:01 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-4029) Maven 2 Extra Steps does not use private Maven repository if set on project
Erich Eichinger commented on JENKINS-4029 Maven 2 Extra Steps does not use private Maven repository if set on project actually in v1.480 using an maven2 job, I see the opposite problem: when checked "use private repository" on a pre/post build extra step, the repo gets properly passed on. But... The problem is 1) uncheck the box and "Save" the job configuration the build properly using the global repo 2) open the job configuration again -> the checkbox is ticked again! after saving the job config with unchecked "use private repo" the job.xml correctly shows false. When you reopen the configuration the boxes are magically checked again - unfortunately that is hidden because it is an advanced setting This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13552) Provide extended 'injected environment variables' view
Gregory Boissinot commented on JENKINS-13552 Provide extended 'injected environment variables' view Please make a new issue and provide an isolated scenario? Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14097) Allow Script Path/Content to add/override environment variables for the build job
David Ehrenberger commented on JENKINS-14097 Allow Script Path/Content to add/override environment variables for the build job Sure, no problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13764) CVS authentication failure while running rlog command (Windows master / Unix slave)
Michael Clarke resolved JENKINS-13764 as Fixed CVS authentication failure while running rlog command (Windows master / Unix slave) Re-closing defect as fixed since initial issue is resolved. Secondary issue can be resolved by following above comment. Change By: Michael Clarke (05/Sep/12 8:46 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14097) Allow Script Path/Content to add/override environment variables for the build job
Gregory Boissinot commented on JENKINS-14097 Allow Script Path/Content to add/override environment variables for the build job I have difficulty implementing this feature in this current EnvInject plugin version. EnvInject plugin has to be refactored before I am able to provide this feature. Please could you wait for it again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13764) CVS authentication failure while running rlog command (Windows master / Unix slave)
Michael Clarke commented on JENKINS-13764 CVS authentication failure while running rlog command (Windows master / Unix slave) Daniel: this is expected behaviour - Rlog activities (polling and changelog generation) happen on the Master which is why the path is converted to contain Windows separators in your case. Polling isn't given a workspace so there would be no way to execute polling on a slave. Changelog generation could potentially be done on the same machine as the checkout, but this wouldn't fix the polling issue. This therefore isn't a suitable solution as polling would still fail for any users with a similar setup to yours. To fix this properly, you'll have to copy your private key file to \home\myUser\.ssh\id_dsa on your master (or set environmental variables that specify where it is on each machine and then copy it to the relevant location). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14623) EnvInject ignores changes in system configuration
Gregory Boissinot commented on JENKINS-14623 EnvInject ignores changes in system configuration Is it possible to help me? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14739) EnvInject params are overwritten by default string params
Gregory Boissinot commented on JENKINS-14739 EnvInject params are overwritten by default string params Is it possible to help me to provide a simpler example? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14930) Can't overload/update PYTHONPATH
Gregory Boissinot resolved JENKINS-14930 as Fixed Can't overload/update PYTHONPATH Change By: Gregory Boissinot (05/Sep/12 8:39 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14930) Can't overload/update PYTHONPATH
Gregory Boissinot commented on JENKINS-14930 Can't overload/update PYTHONPATH without any response from you, I release a new version This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15055) Cannot modify job configuration when custom MatrixExecutionStrategy is selected
Michal Baranowski
created JENKINS-15055
Cannot modify job configuration when custom MatrixExecutionStrategy is selected
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
05/Sep/12 8:07 PM
Description:
I created a custom MatrixExecutionStrategy (QAMatrixExecutionStrategyImpl) and when it is selected and the given job is already saved with QAMatrixExecutionStrategyImpl, error occurs when I modify job configuration and try to save the job.
Exception: java.lang.IllegalArgumentException: Failed to instantiate class hudson.matrix.MatrixExecutionStrategy from {"stapler-class":["hudson.matrix.DefaultMatrixExecutionStrategyImpl","hudson.plugins.qamatrix.QAMatrixExecutionStrategyImpl"]}
Stacktrace:
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to instantiate class hudson.matrix.MatrixExecutionStrategy from {"stapler-class":["hudson.matrix.DefaultMatrixExecutionStrategyImpl","hudson.plugins.qamatrix.QAMatrixExecutionStrategyImpl"]}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1074)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:146)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:285)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:765)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:628)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
Caused by: java.lang.IllegalArgumentException: Failed to instantia
[JIRA] (JENKINS-14681) Constrain the list of artifacts deployed
Gregory Boissinot commented on JENKINS-14681 Constrain the list of artifacts deployed Do you have visibility to your schedule for achieving this feature? Thanks in advance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15054) Add support for Global Properties in Build Triggers for Jobs
Colin Johnson
created JENKINS-15054
Add support for Global Properties in Build Triggers for Jobs
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
05/Sep/12 7:36 PM
Description:
Steps to Reproduce:
1. Click "Manage Jenkins" -> Global Properties
2. Create an Environment Variable as follows: name: POLL_SCM_SCHEDULE value: 0 23,13,19 * * * (or any other value such as @hourly)
3. Select an Existing Job that uses either the "Build Periodically" or "Poll SCM" build triggers.
4. In the "Schedule" field enter
Result:
Validation Below Schedule Reads:
Invalid input: "${POLL_SCM_SCHEDULE}": line 1:1: unexpected char: '$'
When "Save" is clicked a status code 500 is returned with the following error:
Status Code: 500
Exception: java.lang.RuntimeException: Failed to instantiate class hudson.triggers.SCMTrigger from {"scmpoll_spec":"${POLL_SCM_SCHEDULE}"}
Stacktrace:
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.triggers.SCMTrigger from {"scmpoll_spec":"${POLL_SCM_SCHEDULE}"}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
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 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
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:173)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63)
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:66)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at hudson.security.ChainedServletFilter.doFil
[JIRA] (JENKINS-15045) Support Github commit status API
Kohsuke Kawaguchi commented on JENKINS-15045 Support Github commit status API I'm adding the base functionalities in github-api now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15034) Sepeda Motor Bebek Injeksi Kencang dan Irit Jupiter Z1
Kohsuke Kawaguchi deleted JENKINS-15034 Sepeda Motor Bebek Injeksi Kencang dan Irit Jupiter Z1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled
Michael Clarke commented on JENKINS-14141 CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled Sorry, my fault. Fixed now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled
SCM/JIRA link daemon commented on JENKINS-14141 CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled Code changed in jenkins User: mc1arke Path: src/main/java/hudson/scm/CVSSCM.java src/test/java/hudson/scm/CVSSCMTest.java http://jenkins-ci.org/commit/cvs-plugin/d7a1ee21db9fb641d504d6d180c900f064624042 Log: [FIXED JENKINS-14141] Fix legacy mode disable and added unit test Compare: https://github.com/jenkinsci/cvs-plugin/compare/bfc1a2dd6034...d7a1ee21db9f This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15053) Add support for Global Properties in Perforce Plugin
Colin Johnson
created JENKINS-15053
Add support for Global Properties in Perforce Plugin
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Unassigned
Components:
perforce
Created:
05/Sep/12 7:03 PM
Description:
Steps to Reproduce:
1. Click "Manage Jenkins" -> Global Properties
2. Create an Environment Variable as follows: name: P4USER value: p4service (or another P4 Username)
3. Select an Existing Job that uses Perforce for Source Code Management
4. Select the Username field and enter "${P4USER}"
Result:
Result: build fails as follows:
Started by user Administrator
Building in workspace /usr/share/tomcat6/.jenkins/jobs/dpapi-int/workspace
Using master perforce client: jenkins-dpapi-int
[workspace] $ /usr/local/bin/p4 workspace -o jenkins-dpapi-int
Caught exception communicating with perforce. Access for user 'com.tek42.perforce.PerforceException: Access for user '
at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:382)
at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292)
at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61)
at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1461)
at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1422)
at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:793)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1256)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494)
at hudson.model.Run.execute(Run.java:1502)
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: Unable to communicate with perforce. Access for user '
Sending e-mails to: eng-...@netshelter.com
Finished: FAILURE
As you can see by the above: "Caught exception communicating with perforce. Access for user 'com.tek42.perforce.PerforceException: Access for user '"
Use Case:
If a user wishes to use exactly one user for all Jobs that use Perforce for SCM, he could enter this user in the Global Properties and then change the credentials user to poll Perforce at any time across all Jobs.
Environment:
Jenkins Version: 1.480
Perforce Plugin: 1.3.17
OS: Amazon Linux 2012.03
Project:
Jenkins
Labels:
perforce
Priority:
Minor
Reporter:
Colin Johnson
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6703) Allow for selection of Cc:, Bcc: fields for email recipients on global recipient list
Gene Liu commented on JENKINS-6703 Allow for selection of Cc:, Bcc: fields for email recipients on global recipient list Please just ignore my previous report. The email CC function works as expected. After a clean up of my jenkins, I did a successful email sending out with cc:(lower case) prefix Good job Slide, thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15052) RPC failed should not block the build indefinitely
Krinkle Krinkle created JENKINS-15052 RPC failed should not block the build indefinitely Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 05/Sep/12 5:55 PM Description: Look at this build: https://integration.mediawiki.org/ci/job/MediaWiki-GIT-Fetching/4730/console (it uses Git and Gerrit plugins) At some point it does an RPC, which results in a 503 (perhaps our Gerrit install was being updated or there might have been an intermediate issue). However nothing happened after that in Jenkins for over an hour. The build wasn't marked FAILED, it didn't (appear to) try again, nothing. No builds happened for over an hour because that build was stuck (we have parallel builds disabled). Project: Jenkins Priority: Major Reporter: Krinkle Krinkle This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15051) menu added on the left side of a build makes screen looks bad
Yi Wen created JENKINS-15051 menu added on the left side of a build makes screen looks bad Issue Type: Bug Assignee: Nicolas De Loof Attachments: Screen Shot 2012-09-05 at 11.59.59 AM.png Components: git Created: 05/Sep/12 5:04 PM Description: Please see the attached screenshot. The menu being added is to long so all the right pane content is being pushed away. I think there are 2 solutions: 1. The menu just say "Git Build Data" 2. Give user an option to turn off this menu. Thanks Project: Jenkins Labels: ui Priority: Minor Reporter: Yi Wen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14727) Make dependency to bundled maven-plugin optional
Ben Golding closed JENKINS-14727 as Fixed Make dependency to bundled maven-plugin optional "Works for me" Jenkins 1.480, warnings 4.16, analysis-core 1.46 Many thanks for the fix! Change By: Ben Golding (05/Sep/12 4:52 PM) Status: Resolved Closed Assignee: Ulli Hafner Ben Golding This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled
Jordan Grant edited a comment on JENKINS-14141 CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled Closing due to fix in CVS plugin 2.5 This was still an issue in CVS plugin 2.6-SNAPSHOT as of 27 AUG 2012 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14680) CVS Plugin v2.5 throws NPE
Jordan Grant commented on JENKINS-14680 CVS Plugin v2.5 throws NPE cforce: I had to check out the CVS plugin from Github (https://github.com/jenkinsci/cvs-plugin), since SNAPSHOT versions are not in the Jenkins Repo. I then build the plugin from source using Maven (i.e. mvn hpi:hpi), but Jenkins provides a Gradle build if you prefer. I then stopped our Jenkins service and deleted from JENKINS_HOME/plugins any of: cvs.hpi, cvs.jpi, cvs.jpi.pinned, cvs.jpi.pinned and the cvs directory. Finally, I copied the HPI that was built by Maven to the plugins directory and created an empty file named cvs.hpi.pinned to prevent Jenkins from overwriting our new custom plugin. Now you can restart Jenkins. I verified in Jenkins -> Manage Plugins that I was running CVS plugin 2.6-SNAPSHOT, and found that the undesirable behavior of another closed issue (https://issues.jenkins-ci.org/browse/JENKINS-14141) is still in place. If you succeed in building/installing the SNAPSHOT, please post back whether you experience the same issues or not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15050) Add timeout option for Deploy Plugin
Jonathan Sternberg created JENKINS-15050 Add timeout option for Deploy Plugin Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: deploy Created: 05/Sep/12 4:39 PM Description: If it's possible, could a timeout option be added to the Deploy Plugin? We recently had an issue where the Tomcat server that was being deployed to was down when deployment started, and it took about an hour before the connection timed out. I would like to lower this time (for example, 10 minutes should easily be long enough). Thanks. Environment: Deploys WAR container to Tomcat 7.x. Project: Jenkins Priority: Major Reporter: Jonathan Sternberg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14759) Job created by posting config.xml to /createItem does not set GitHub webhook
jglick assigned JENKINS-14759 to jglick Job created by posting config.xml to /createItem does not set GitHub webhook Change By: jglick (05/Sep/12 4:13 PM) Assignee: Nicolas De Loof jglick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Yep, you are right. the full path need to be also for the "Class directory" and "Source directory" columns. I recommend you to add more error/debug messages with explanations, It's makes life easier for the end user troubleshooting. Ok now its working But now the "Coverage Breakdown by Module" and the total result tables graphics look weird (text exceeds the limit of the column), take a look on this snapshot: http://192.117.122.51/Coverage_Summary.jpg. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Yep, you are right. the full path need to be also for the "Class directory" and "Source directory" columns. I recommend you to add more error/debug messages with explanations, It's makes life easier for the end user troubleshooting. Ok now its working But now the "Coverage Breakdown by Module" and the total result tables graphics look weird (text exceeds the limit of the column), take a look on this snapshot: http://192.117.122.51/Coverage_Summary.jpg. Maybe disable/enable option for Class/Module counter? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg commented on JENKINS-14896 java.io.FileNotFoundException when saving module data Yep, you are right. the full path need to be also for the "Class directory" and "Source directory" columns. Ok now its working, but now the total result and the "Coverage Breakdown by Module" table graphics look weird, take a look on this snapshot: "http://192.117.122.51/Coverage_Summary.jpg" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15049) New column: Number of FindBugs issues
Sebastian Schuberth created JENKINS-15049 New column: Number of FindBugs issues Issue Type: New Feature Assignee: Fred G Components: extra-columns Created: 05/Sep/12 3:08 PM Description: If the FindBugs plug-in is installed, it would be nice to have a column showing the number of FindBugs issues in the last build. Project: Jenkins Priority: Minor Reporter: Sebastian Schuberth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15048) Git Build Data menu items shows repo URL which kind of disturb the layout
Bue Petersen created JENKINS-15048 Git Build Data menu items shows repo URL which kind of disturb the layout Issue Type: Bug Assignee: Nicolas De Loof Attachments: Screenshot-693.png Components: git Created: 05/Sep/12 2:45 PM Description: As screenshots shows the URL showed are pretty long. Didn't notice this before, seems like a little new bug. Using github as repository browser with the https URL for my github project, and the repository url is the one shown in the picture. Environment: Jenkins 1.480, firefox browser, linux Project: Jenkins Priority: Major Reporter: Bue Petersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15047) Red Hat package for Jenkins lacks Java runtime require in specfile
Brenton Leanhardt created JENKINS-15047 Red Hat package for Jenkins lacks Java runtime require in specfile Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: other Created: 05/Sep/12 2:37 PM Description: One reasonably flexible way to solve this issue is to add "Requires: java" to the specfile. At install time it will resolve to whatever version of java ships with RHEL or an EL rebuild. Project: Jenkins Priority: Trivial Reporter: Brenton Leanhardt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15043) Changelist parsing fails when description contains jobs without fix status
Ajay Kanade commented on JENKINS-15043 Changelist parsing fails when description contains jobs without fix status Oh - May be because I cloned & then modified the description. Thanks for the fast turn around. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15043) Changelist parsing fails when description contains jobs without fix status
SCM/JIRA link daemon resolved JENKINS-15043 as Fixed Changelist parsing fails when description contains jobs without fix status Change By: SCM/JIRA link daemon (05/Sep/12 2:09 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15043) Changelist parsing fails when description contains jobs without fix status
Rob Petti commented on JENKINS-15043 Changelist parsing fails when description contains jobs without fix status Ok, I was confused since the original description on this ticket described that problem, not this one. I'll take a look. From your description it sounds like a simple fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15043) Changelist parsing fails when description contains jobs without fix status
SCM/JIRA link daemon commented on JENKINS-15043 Changelist parsing fails when description contains jobs without fix status Code changed in jenkins User: Rob Petti Path: src/main/java/com/tek42/perforce/parse/ChangelistBuilder.java http://jenkins-ci.org/commit/perforce-plugin/0e5b7c4d1d94e0c614873d66f9d3197e23ed9500 Log: [FIXED JENKINS-15043] 'status' field in perforce job descriptions is now optional This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14647) VMs will be started until a job is waiting in the queue
Jason Swager commented on JENKINS-14647 VMs will be started until a job is waiting in the queue Upgrade to Jenkins 1.468 or higher. Your solution for a suggestion is correct, but unfortunately, the plugins are not responsible for determining which slave gets which job. That's a Jenkins core issue. And there was a bug in this particular area that was fixed in 1.468. So upgrading should resolve your problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14647) VMs will be started until a job is waiting in the queue
Jason Swager assigned JENKINS-14647 to Jason Swager VMs will be started until a job is waiting in the queue Change By: Jason Swager (05/Sep/12 1:58 PM) Assignee: Jason Swager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15046) Trend graph scales do not adapt - 5 of 6 values are not displayed
Cyril Picat created JENKINS-15046 Trend graph scales do not adapt - 5 of 6 values are not displayed Issue Type: Bug Assignee: Unassigned Attachments: cppncss trend graph.png, cppncss.xml Components: cppncss Created: 05/Sep/12 1:28 PM Description: On my project, only the number of files was displayed on cppncss trend graph. After a bit of investigation and by removing files I realized that the scale was either not automatic or not handling different orders in the values (because the screenshot on cppncss plugin suggest the scale could change). All the measurements like NCSS, CCN, total functions, CCN violations and NCSS violations are not displayed in my case. I have attached the picture of my trend graph and the sample file on which it is failing. Project: Jenkins Priority: Major Reporter: Cyril Picat This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ognjen Bubalo commented on JENKINS-14896 java.io.FileNotFoundException when saving module data Hmm. Can you please check if the exec files are copied to the right place? Also check if the class and source directory path for each module is ok (like at the exec file). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15036) [jenkins-multijob-plugin] Multijob Freeze after first phase and all Executors are becoming Dead (!)
Rotem G reopened JENKINS-15036 [jenkins-multijob-plugin] Multijob Freeze after first phase and all Executors are becoming Dead (!) Multijob freeze after first phase when needed to transfer parameters to second phase job. Change By: Rotem G (05/Sep/12 1:19 PM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15036) [jenkins-multijob-plugin] Multijob Freeze after first phase and all Executors are becoming Dead (!)
Rotem G updated JENKINS-15036 [jenkins-multijob-plugin] Multijob Freeze after first phase and all Executors are becoming Dead (!) Change By: Rotem G (05/Sep/12 1:16 PM) Summary: [jenkins-multijob-plugin] Multijob Freeze after first phase and all Executors are becoming Dead (!) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14999) Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter
Martin d'Anjou commented on JENKINS-14999 Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter Thank you. It works now. My only comment is that the documentation could be clearer. It says "...the source project must be accessible to all authenticated users;..." May I suggest instead something like "you must have a group called 'authenticated' and grant the Job Read permission to this group". What confounded me is that I did have the Job Read permission granted for all the users and the group defined in the screenshot, so to me, I was not missing anything. Maybe the error message could say something along these lines as well. Thank you for the help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15043) Changelist parsing fails when description contains jobs without fix status
Ajay Kanade commented on JENKINS-15043 Changelist parsing fails when description contains jobs without fix status Rob, No. There is no issue with the reserved phrases. I see it handled in ChangelistBuilder.Build. Below is fixed by you (if that's your concern) https://issues.jenkins-ci.org/browse/JENKINS-7679 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15036) [jenkins-multijob-plugin]
hagzag resolved JENKINS-15036 as Incomplete [jenkins-multijob-plugin] Please be more verbose in the Jira description. Change By: hagzag (05/Sep/12 1:06 PM) Status: Open Resolved Fix Version/s: current Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15012) CVS Plugin doesn't detect labeled changes on a branch
Cédric Jonas commented on JENKINS-15012 CVS Plugin doesn't detect labeled changes on a branch Steps: Create a Job for a CVS branch (see configuration below). Commit some changes directly to the branch -> Jenkins will trigger a build once the polling was done. To get a change from HEAD to the branch, move the branch tag (we "merge" our changes to the branch by moving the branch tag, if possible) -> the polling will not discover any changes. This worked in old versions which used 'cvs update' for polling. The CVS rlog output shows nothing, since it doesn't find any changes on the branch (excepted the change was commit directly on the branch, then it works) Started on 05.09.2012 14:01:24 cvs rlog -S -d05 Sep 2012 12:03:00 +0200<05 Sep 2012 14:01:24 +0200 WISKI/java cvs rlog: Logging WISKI/java cvs rlog: Logging WISKI/java/base ... Done. Took 43 Sekunden No changes Here's the job config: ... true :pserver:xxx@xxx:/cvssrc WISKI/java BRANCH Br_Release_WISKI7_7_2_1 false -1 xxx true true false true false true ... 0 * * * * ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Thanks Ognjen One more question please: After the Jacoco plugin successfully finished to collect the modules data (*.exec) and the build successfully finished, I go back to my Jenkins Job -> last Build -> "Coverage Report" and on this screen all the column with 0.0% M:0 C: 0 (See snapshot: http://192.117.122.51/coverage_empty.jpg), Why? What am I missing? The Console Log: [JaCoCo plugin] Reports added [JaCoCo plugin] Storing properties file.. [JaCoCo plugin] Loading EXEC files.. [JaCoCo plugin] Publishing the results.. [JaCoCo plugin] Loading module: . . . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13823) Changing the configuration of any project results in "Connection Reset" Error
davidmc24 commented on JENKINS-13823 Changing the configuration of any project results in "Connection Reset" Error I ran into a similar issue at my employer yesterday. For us, saving job configurations failed with a "connection reset" when I had a Groovy command embedded in the configuration that used "&&". The root cause ended up being an Intrusion Prevention System that our networking team had set up which was blocking the traffic. For us, at least, the problem wasn't with Jenkins at all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13590) Trigger build when new pull request occurs in github
Honza Brázdil commented on JENKINS-13590 Trigger build when new pull request occurs in github I've released the plugin: https://wiki.jenkins-ci.org/display/JENKINS/Github+pull+request+builder+plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8035) Unable to apply Russians translations using http://wiki.jenkins-ci.org/display/HUDSON/Translation+Assistance+Plugin
evernat resolved JENKINS-8035 as Incomplete Unable to apply Russians translations using http://wiki.jenkins-ci.org/display/HUDSON/Translation+Assistance+Plugin no response, so closing as incomplete (and the issue may be fixed with a newer version of the translation assistance plugin) Change By: evernat (05/Sep/12 12:06 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg commented on JENKINS-14896 java.io.FileNotFoundException when saving module data Thanks Ognjen One more question please: After the Jacoco plugin successfully finished to collect the modules data (*.exec) and the build successfully finished, I go back to my Jenkins job -> last build -> "Coverage Report" and on this screen all the column with %0 M:0 C: 0, Why? The Console Log: [JaCoCo plugin] Reports added [JaCoCo plugin] Storing properties file.. [JaCoCo plugin] Loading EXEC files.. [JaCoCo plugin] Publishing the results.. [JaCoCo plugin] Loading module: . . . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ognjen Bubalo commented on JENKINS-14896 java.io.FileNotFoundException when saving module data Yes! That will be the next feature. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
Lars Bilke commented on JENKINS-10405 Post-receive hook doesn't work I have also setup a logger which outputs this on every push to GitHub: Sep 5, 2012 12:21:34 PM com.cloudbees.jenkins.GitHubWebHook processGitHubPayload INFO: Received POST for https://github.com/ufz/ogs But unfortunately no build is triggered. I am using the latest Jenkins and GitHub-plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg commented on JENKINS-14896 java.io.FileNotFoundException when saving module data I checked it and yes its working now! I had to enter the full path in each module. Tell me Ognjen, Are you planning to support **/ option in the "Exec file relative path" column? (For example: **/target/jacoco/jacoco.exec) Thank You This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-17) Finishing with a Null Pointer Exception after a successful build.
evernat resolved TEST-17 as Duplicate Finishing with a Null Pointer Exception after a successful build. Change By: evernat (05/Sep/12 9:52 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-18) Finishing with a Null Pointer Exception after a successful build.
evernat resolved TEST-18 as Duplicate Finishing with a Null Pointer Exception after a successful build. Change By: evernat (05/Sep/12 9:53 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-15) Finishing with a Null Pointer Exception after a successful build.
evernat resolved TEST-15 as Duplicate Finishing with a Null Pointer Exception after a successful build. Change By: evernat (05/Sep/12 9:51 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-16) Finishing with a Null Pointer Exception after a successful build.
evernat resolved TEST-16 as Duplicate Finishing with a Null Pointer Exception after a successful build. Change By: evernat (05/Sep/12 9:52 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7079) java.net.BindException: Address already in use
wernight commented on JENKINS-7079 java.net.BindException: Address already in use Check Jenkins SSH port. This error should really display what is trying to connect and to which port number on which IP. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
slave in Jenkins
Hello, I try to conntect my slave to master I created. I click on launch, it open the window, but stuck in the middle. In the logs: ava.net.SocketException: Socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:146) at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) at java.io.BufferedInputStream.read(BufferedInputStream.java:254) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2265) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2558) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2568) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1127) In other slave, it connect but terminate immediately. What can be the reasons? -- View this message in context: http://jenkins.361315.n4.nabble.com/slave-in-Jenkins-tp4639220.html Sent from the Jenkins issues mailing list archive at Nabble.com.
[JIRA] (JENKINS-14680) CVS Plugin v2.5 throws NPE
cforce commented on JENKINS-14680 CVS Plugin v2.5 throws NPE I can't find org.jenkins-ci.plugins.csv 2.6-SNAPSHOT on http://repo.jenkins-ci.org http://repo.jenkins-ci.org/webapp/search/artifact?4&q=org.jenkins-ci.plugins+cvs Btw. whats the difference between http://repo.jenkins-ci.org and http://maven.jenkins-ci.org/content/repositories/ ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11507) Single-sign-on isn't working correctly in the Crowd 2 plugin
Thorsten Heit closed JENKINS-11507 as Fixed Single-sign-on isn't working correctly in the Crowd 2 plugin Change By: Thorsten Heit (05/Sep/12 8:50 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11418) Crowd2 doesn't always show full user name
Thorsten Heit closed JENKINS-11418 as Fixed Crowd2 doesn't always show full user name Change By: Thorsten Heit (05/Sep/12 8:50 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9211) Rebuild Plugin does not work for Subversion List Parameter
Rino Kadijk updated JENKINS-9211 Rebuild Plugin does not work for Subversion List Parameter patch attached Change By: Rino Kadijk (05/Sep/12 8:16 AM) Attachment: JENKINS-9211-_Rebuild_Plugin_does_not_work_for_Subversion_List_Parameter.patch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6230) Display job-description also on parameters page when starting a parametrized job
Sven Appenrodt commented on JENKINS-6230 Display job-description also on parameters page when starting a parametrized job This improvement is useful fur me too. I'm working with different security-settings and different 'launcher-jobs', but for some jobs it will be nice having the html-based job-description when launching the build (e.g. red letter hint). But i don't know if the prio should be Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15045) Support Github commit status API
David Henderson created JENKINS-15045 Support Github commit status API Issue Type: New Feature Assignee: Unassigned Components: github Created: 05/Sep/12 8:12 AM Description: Github have announced support for a commit status API. Each SHA can have one or more build statuses attached to it. https://github.com/blog/1227-commit-status-api http://developer.github.com/v3/repos/statuses/ Project: Jenkins Priority: Major Reporter: David Henderson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Vlado Pakan commented on JENKINS-14896 java.io.FileNotFoundException when saving module data I'm getting this error [JaCoCo plugin] Loading EXEC files.. FATAL: org.objectweb.asm.ClassReader.accept(Lorg/objectweb/asm/ClassVisitor;I)V java.lang.NoSuchMethodError: org.objectweb.asm.ClassReader.accept(Lorg/objectweb/asm/ClassVisitor;I)V at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:94) at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:115) at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:155) at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:183) Need to investigate how to fix it first therefore I will check if issue is fixed afterwards. I have tested it on my local jenkins installation when job run on master and everything worked. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13764) CVS authentication failure while running rlog command (Windows master / Unix slave)
Daniel Schaarschmidt commented on JENKINS-13764 CVS authentication failure while running rlog command (Windows master / Unix slave) Jenkins 1.465, CVS Plugin 2.5, Master: Windows Server 2003, Slave Linux Jenkins is running on the master, the build is done on the Linux slave. SSH-Key-Location is configured as "/home/myUser/.ssh/id_dsa" The checkout from CVS works fine, but when the rlog command is executed I get the following error: cvs rlog -S -d05 Sep 2012 09:51:41 +0200<05 Sep 2012 09:53:54 +0200 project2 FATAL: CVS authentication failure while running rlog command java.lang.RuntimeException: CVS authentication failure while running rlog command at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:537) at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:419) at hudson.scm.CVSSCM.checkout(CVSSCM.java:853) at hudson.model.AbstractProject.checkout(AbstractProject.java:1218) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475) at hudson.model.Run.run(Run.java:1434) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: org.netbeans.lib.cvsclient.connection.AuthenticationException: SSH connection failed. at org.netbeans.lib.cvsclient.connection.SSHConnection.open(SSHConnection.java:141) at org.netbeans.lib.cvsclient.Client$1.run(Client.java:374) at java.lang.Thread.run(Thread.java:662) Caused by: com.jcraft.jsch.JSchException: java.io.FileNotFoundException: \home\myUser\.ssh\id_dsa (Das System kann den angegebenen Pfad nicht finden) at com.jcraft.jsch.IdentityFile.newInstance(IdentityFile.java:98) at com.jcraft.jsch.JSch.addIdentity(JSch.java:224) at com.jcraft.jsch.JSch.addIdentity(JSch.java:218) at org.netbeans.lib.cvsclient.connection.SSHConnection.open(SSHConnection.java:135) ... 2 more Caused by: java.io.FileNotFoundException: \home\myUser\ssh\id_dsa (Das System kann den angegebenen Pfad nicht finden) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:106) at java.io.FileInputStream.(FileInputStream.java:66) at com.jcraft.jsch.IdentityFile.newInstance(IdentityFile.java:83) ... 5 more Do you notice the different file separators? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ognjen Bubalo commented on JENKINS-14896 java.io.FileNotFoundException when saving module data What happens if you set your Exec file relative path column to: Platform/trunk/Application/Wizard/target/jacoco/jacoco.exec ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg
edited a comment on JENKINS-14896
java.io.FileNotFoundException when saving module data
Yes in every module there is direcotry called: "*/target/jacoco" including the "jacoco.exec" file ("*/target/jacoco/jacoco.exec"), I checked it.
For example let's take the "Wizard" module:
Full Jacoco path on slave machine: "C:\Jenkins\workspace\Continuous_Build\Platform\trunk\Application\Wizard\target\jacoco"
Full build path on master machine: "D:\Jenkins\jobs\Continuous_Build"
I also checked and the build without Jacoco Jenkins plugin is stable (fully succeed).
Deubg:
execfile = c:\Jenkins\workspace\Continuous_Build\target\jacoco\jacoco.exec
seged = D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_XX-XX-XX\jacoco\module0\jacoco.exec
actualBuildDirRoot = D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_XX-XX-XX\jacoco
actualBuildModuleDir = D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_XX-XX-XX\jacoco\module0
getWorkspace = c:\Jenkins\workspace\Continuous_Build
moduleName = Wizard
Please tell me if you need more information...
Thank You.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
