[JIRA] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
xu dong commented on JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 Same here on Windows xp X86 SP2 with java version "1.7.0_11", run by java -jar jenkins.war 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10524) winstone.ClientSocketException: Failed to write to client
xu dong commented on JENKINS-10524 winstone.ClientSocketException: Failed to write to client Same here on Windows xp X86 SP2 with java version "1.7.0_11", run by java -jar jenkins.war 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Reynald Borer commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly Same issue here with Jenkins 1.514. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/run/jenkins/war/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/model/View/sidepanel.jelly:75:50: st:include No signature of method: java.lang.String.queue() is applicable for argument types: (java.util.LinkedHashMap) values: [[items:[hudson.model.Queue$BlockedItem:hudson.model.FreeStyleProject@4e416cf7[_TnAT_at1_selenium_NTJ_IKKI]:A lready running 2 builds across all nodes, ...]]] Possible solutions: use([Ljava.lang.Object;), size(), next(), grep(), size(), every() at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:736) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) 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:95) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:36) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:32) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) 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 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) 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
[JIRA] [dry] (JENKINS-17958) Code duplication pairs not correcty mapped. A in B is correctly shown, but B in A stays empty. Simian
Patrick S updated JENKINS-17958 Code duplication pairs not correcty mapped. A in B is correctly shown, but B in A stays empty. Simian Change By: Patrick S (15/May/13 8:26 AM) Description: ImusingtheDRYplugintodisplayduplicatedcodefoundwithSimian.Theoverviewofallfoundcodeduplicationpairsisworkingcorrectly(see1).Thefirst occurance occurrence ofacodeduplicationpairA-Biscorrectlydisplayed(see2)howeverthesecond occurance occurrence (see3)B-Aisempty.Solutions:1.EitherfileBshouldbecompletelyremovedfromoverview1or2.ShouldcorrectlydisplaythelinktofileAIcheckedhttps://issues.jenkins-ci.org/browse/JENKINS-16688anditseemstobeasimilarissue.Thisisrelatedto■Ifaduplicationisintwofiles,thenontheleftonlyonefileisshownwhichIthinkmightbethebestsolution. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dry] (JENKINS-17959) Unable to view High and Normal Priority Duplicate Code details using Publish Duplicate Code analysis results plugin
Annamma Dominic created JENKINS-17959 Unable to view High and Normal Priority Duplicate Code details using Publish Duplicate Code analysis results plugin Issue Type: Bug Assignee: Ulli Hafner Attachments: result1.docx, step1.docx, summary window.docx Components: dry Created: 15/May/13 8:25 AM Description: Jenkins Version: 1.467 DRY Plugin Version: 2.33 In the new window Click on High Tab - NO DETAILS DISPLAYED EVEN THROUGH THERE IS A VALUE OF 1 WITH HIGH PRIORITY in the same window Click on Normal Tab - NO DETAILS DISPLAYED EVEN THROUGH THERE IS A VALUE OF 7 WITH NORMAL PRIORITY Could you please guide why this is happening and what is the solution for this Due Date: 05/Jun/13 12:00 AM Project: Jenkins Priority: Major Reporter: Annamma Dominic 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [performance-plugin] (JENKINS-17493) NullPointer Exception when parsing result report
Matthias Glastra commented on JENKINS-17493 NullPointer Exception when parsing result report I have the same issue on with getRootDir on the Static Analysis Core. But I can't figure out what the real problem is. It seems that the 'new File()' constructor is not getting a correct child parameter. http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/6-b14/java/io/File.java#320 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-17883) flags skipNoTestFiles and failIfNotNew are not saved properly [since xunit 1.56]
Jurgen Van Bouchaute commented on JENKINS-17883 flags skipNoTestFiles and failIfNotNew are not saved properly [since xunit 1.56] Noticed same problem behaviour in 1.55 as well (downgrade from 1.58) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis edited a comment on JENKINS-17831 Update to latest xTrigger great! that would do it Let me know when a new release of IvyTrigger is available to test 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis commented on JENKINS-17831 Update to latest xTrigger great! that would do it 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
xu dong edited a comment on JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 Same here on Windows xp X86 SP2 with java version "1.7.0_11", Jenkins ver: 1.488 ,build-pipeline: 1.3.4-snapshot,run by java -jar jenkins.war 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10524) winstone.ClientSocketException: Failed to write to client
xu dong updated JENKINS-10524 winstone.ClientSocketException: Failed to write to client Change By: xu dong (15/May/13 9:16 AM) Labels: build-pipeline 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10524) winstone.ClientSocketException: Failed to write to client
xu dong edited a comment on JENKINS-10524 winstone.ClientSocketException: Failed to write to client Same here on Windows xp X86 SP2 with java version "1.7.0_11", Jenkins ver: 1.488 ,build-pipeline: 1.3.4-snapshot,run by java -jar jenkins.war 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
xu dong reopened JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 I encounter this problem.On Windows xp X86 SP2 with java version "1.7.0_11", Jenkins ver: 1.488 ,build-pipeline: 1.3.4-snapshot,run by java -jar jenkins.war Change By: xu dong (15/May/13 9:19 AM) Resolution: Duplicate 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [repository] (JENKINS-17756) The jenkins repository is in the jenkins RPM
E Kastelijn commented on JENKINS-17756 The jenkins repository is in the jenkins RPM I fully agree. Yum repository information should not be stored in the main jenkins RPM. A unwelcome side-effect of this is that the file /etc/yum.repos.d/jenkins.repo is removed when the Jenkins RPM is removed from the system. This forces a server-administrator to (manually) place the jenkins.repo file on the server again. Most of the time this kind yum repository information is stored in a separate *-release.rpm For jenkins this RPM would be named as: jenkins-release.rpm A nice example for this can be fedora-release-18-1.noarch.rpm or rpmfusion-free-release-18-3.noarch 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan
James Howe created JENKINS-17960 Indicate if tests dont go to plan Issue Type: New Feature Assignee: Bruno P. Kinoshita Components: tap Created: 15/May/13 10:02 AM Description: One of the major features of TAP is that you have a test plan. If my TAP starts 1..100, but only 5 results are recorded before something broke, then I want to know about it. Likewise, if 105 results are recorded, I want some kind of error indication. I suggest counting this as 95 skipped tests by default, possibly with an config option to treat them as failed instead. Project: Jenkins Priority: Critical Reporter: James Howe 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Jenkins console logs issue-1.500
Hi, I am using jenkins-1.500. In this the job output is not listing in the main page. It is displaying in the link called default. Once the checkout is happened in the main page. It is not taking that one for build. It is once again checkout in the default link and start build. Kindly let me know what changes needs to be done to write the ouput and build should happend in the main directory not in the default. Thanks in advance. Regards, Karthik -- View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-console-logs-issue-1-500-tp4666211.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-17954) UI show next build will have a changed config
Kathi Stutz assigned JENKINS-17954 to Kathi Stutz UI show next build will have a changed config Change By: Kathi Stutz (15/May/13 10:47 AM) Assignee: MirkoFriedenhagen KathiStutz 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jquery] (JENKINS-17310) URL in the project description without https:// don't work
Andrey Sorokovikov started work on JENKINS-17310 URL in the project description without https:// dont work Change By: Andrey Sorokovikov (15/May/13 10:59 AM) Status: Open InProgress 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17838) full build log not in content of email
Alex Earl commented on JENKINS-17838 full build log not in content of email I just tried this again, it looks like because I am running under the Netbeans debugger it causes an issue with running the Maven. When I just run (without the debugger) I am still not able to reproduce this issue with the Maven job. I get the following output in the email that is sent to me. Started by user anonymous Building in workspace /home/USER/Projects/email-ext-plugin/work/workspace/JENKINS-17838 No emails were triggered. Parsing POMs [JENKINS-17838] $ java -cp /home/USER/Projects/email-ext-plugin/./work/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/home/USER/Projects/email-ext-plugin/work/tools/hudson.tasks.Maven_MavenInstallation/Default/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /home/USER/Projects/email-ext-plugin/work/tools/hudson.tasks.Maven_MavenInstallation/Default /home/USER/Projects/email-ext-plugin/target/work/webapp/WEB-INF/lib/remoting-2.23.jar /home/USER/Projects/email-ext-plugin/./work/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 47250 ===[JENKINS REMOTING CAPACITY]=== channel started log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter). log4j:WARN Please initialize the log4j system properly. Executing Maven: -B -f /home/USER/Projects/email-ext-plugin/work/workspace/JENKINS-17838/pom.xml test [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building foo 1.0 [INFO] [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ foo --- [debug] execute contextualize [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /home/USER/Projects/email-ext-plugin/work/workspace/JENKINS-17838/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ foo --- [INFO] No sources to compile [INFO] [debug] execute contextualize [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /home/USER/Projects/email-ext-plugin/work/workspace/JENKINS-17838/src/test/resources [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ foo --- [INFO] [INFO] No sources to compile [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ foo --- [INFO] [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ foo --- [INFO] No tests to run. [INFO] Surefire report directory: /home/USER/Projects/email-ext-plugin/work/workspace/JENKINS-17838/target/surefire-reports --- T E S T S --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 7.681s [INFO] Finished at: Wed May 15 04:37:41 MST 2013 [INFO] Final Memory: 8M/59M [INFO] [JENKINS] Archiving /home/USER/Projects/email-ext-plugin/work/workspace/JENKINS-17838/pom.xml to /home/USER/Projects/email-ext-plugin/work/jobs/JENKINS-17838/modules/foo$foo/builds/2013-05-15_04-37-27/archive/foo/foo/1.0/foo-1.0.pom Waiting for Jenkins to finish collecting data channel stopped Email was triggered for: Success Sending email for trigger: Success All done success! 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] [core] (JENKINS-17774) Testing plugin in Windows fails with requested operation can't be performed on file with user-mapped section open
ikedam commented on JENKINS-17774 Testing plugin in Windows fails with requested operation cant be performed on file with user-mapped section open Sent a pull request https://github.com/jenkinsci/jenkins/pull/773 . jglick pointed followings: Extracting createWebAppContext makes the interface of HudsonTestCase depend on Jetty. A same change should be applied to JenkinsRule. I found that JenkinsRule does not have this problem(JENKINS-17774). So this problem can be avoided by using a rule annotation with JenkinsRule, instead of deriving from HudsonTestCase. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix] (JENKINS-16521) Multi-Project Throttle Categories don't work with Matrix jobs
Ole Christian Langfjæran commented on JENKINS-16521 Multi-Project Throttle Categories dont work with Matrix jobs Same here. Version 1.72 and 1.513 of Jenkins. Is this, https://issues.jenkins-ci.org/browse/JENKINS-12240, supposed to fix it? It is included in version 1.72 according to commits. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven created JENKINS-17961 URLTrigger does not poll when URL starts with environment variable Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: urltrigger Created: 15/May/13 12:57 PM Description: If I define an environment variable NEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsg and use it in the following url to poll: $NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-library no polling happens. See the following log: prePolling started on May 15, 2013 2:51:04 PM Polling for the job playground_schommelschommel-2-release-_update_shared_library_versie Looking nodes where the poll can be run. Looking for a node to the restricted label master. Restrict on master label. Polling on master. Polling on master. Polling complete. Took 1 ms. No changes./pre The following workaround works. Define an environment variable NEXUS_HOST=l1-ibrprdmvn01.nl.rsg and use it in the url: http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-library prePolling started on May 15, 2013 2:57:04 PM Polling for the job playground_schommelschommel-2-release-_update_shared_library_versie Looking nodes where the poll can be run. Looking for a node to the restricted label master. Restrict on master label. Polling on master. Polling on master. Invoking the url: http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-library Inspecting the content Polling complete. Took 92 ms. No changes./pre Environment: Red Hat Enterprise Linux Server release 5.3 (Tikanga) java version 1.6.0_11 Java(TM) SE Runtime Environment (build 1.6.0_11-b03) Java HotSpot(TM) Server VM (build 11.0-b16, mixed mode) Jenkins ver. 1.509.1 Project: Jenkins Priority: Minor Reporter: Wilco Greven 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-17962) Support for Violations Plugin
Michael Klein created JENKINS-17962 Support for Violations Plugin Issue Type: New Feature Assignee: mdonohue Attachments: violationsPatch Components: configurationslicing Created: 15/May/13 12:59 PM Description: Added support for violation plugin. The necessary changes on the code are in the attached patch. It would be great, if these changes find the way in the next release of the slicer. Project: Jenkins Priority: Major Reporter: Michael Klein 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven updated JENKINS-17961 URLTrigger does not poll when URL starts with environment variable Change By: Wilco Greven (15/May/13 12:58 PM) Description: IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsganduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog: pre code PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges./ pre code Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryprePollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges./pre 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven
updated JENKINS-17961
URLTrigger does not poll when URL starts with environment variable
Change By:
Wilco Greven
(15/May/13 12:59 PM)
Description:
IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsganduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog:
code
{blockquote}
PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges.
/code
{blockquote}
Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryprePollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges./pre
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven
updated JENKINS-17961
URLTrigger does not poll when URL starts with environment variable
Change By:
Wilco Greven
(15/May/13 12:59 PM)
Description:
IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsganduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog:{
blockquote
quote
}PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges.{
blockquote
quote
}Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryprePollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges./pre
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven
updated JENKINS-17961
URLTrigger does not poll when URL starts with environment variable
Change By:
Wilco Greven
(15/May/13 1:00 PM)
Description:
IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsganduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog:{
quote
code
}PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges.{
quote
code
}Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryprePollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges./pre
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven
updated JENKINS-17961
URLTrigger does not poll when URL starts with environment variable
Change By:
Wilco Greven
(15/May/13 1:01 PM)
Description:
IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsganduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog:{code}
PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges.
{code}Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-library
pre
{code}
PollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges.
/pre
{code}
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven
updated JENKINS-17961
URLTrigger does not poll when URL starts with environment variable
Change By:
Wilco Greven
(15/May/13 1:02 PM)
Description:
IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsganduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog:{code}PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges.{code}Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-library
Seethelog:
{code}PollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges.{code}
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-14833) Jenkins variables are not expanded in Coverity plugin
Drew Reed commented on JENKINS-14833 Jenkins variables are not expanded in Coverity plugin I believe I've just sent a pull request on github for a patch that addresses this 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17838) full build log not in content of email
Alex Gray commented on JENKINS-17838 full build log not in content of email OK. It looks like you've done your due diligence on this, and if you're OK we can probably close this out. The workaround of attaching the log is more than acceptable. I noticed that Cloudbees is not using the latest and greatest version of the mail-ext plugin (2.2.8, not 2.2.9), so there may be other issues going on. Thank you so much for looking into this. I'll continue trying out some things and if I make any progress I'll update this Jira. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-17963) Links are broken
Drew Reed created JENKINS-17963 Links are broken Issue Type: Bug Assignee: Unassigned Components: coverity Created: 15/May/13 1:09 PM Description: If the configured coverity servers name, project name or stream name contains spaces or other characters that are not valid in links the generated links in a number of places throughout the plugin UI elements are broken. Project: Jenkins Priority: Minor Reporter: Drew Reed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven
updated JENKINS-17961
URLTrigger does not poll when URL starts with environment variable
Change By:
Wilco Greven
(15/May/13 1:20 PM)
Description:
IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsg
underJenkinsglobalproperties
anduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog:{code}PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges.{code}Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarySeethelog:{code}PollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges.{code}
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-17751) Link from triggering promotion to triggered build
Greg Smith commented on JENKINS-17751 Link from triggering promotion to triggered build This is great Thanks much. Is this now tracked to be included in an upcoming update? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-17963) Links are broken
Drew Reed commented on JENKINS-17963 Links are broken A pull request with a patch has been sent for this. Sorry about the pull request messup I believe the fix is now on it's own. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix] (JENKINS-16521) Multi-Project Throttle Categories don't work with Matrix jobs
Ole Christian Langfjæran commented on JENKINS-16521 Multi-Project Throttle Categories dont work with Matrix jobs Update: Cloned tag 1.7.1 and installed and it seems to work using Category. Created a "Matrix-job" category using "Maximum Total Concurrent Build = 4" and "Maximum Concurrent Builds Per Node = 4". The job itself is configured with "Maximum Concurrent Builds Per Node = 1" and "Maximum Total Concurrent Build = 4". I am not using any slaves though. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix-reloaded] (JENKINS-17964) NPE if one of the upstream builds is not found
Louis Roché created JENKINS-17964 NPE if one of the upstream builds is not found Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: matrix-reloaded Created: 15/May/13 2:29 PM Description: I have a nightly build who trigger a matrix and I have this error for every jobs in the matrix: Started by upstream project "Windows Results" build number 12418 originally caused by: Started by upstream project "Supervisor Test Windows Nightly" build number 615 originally caused by: Started by upstream project "Nightly Build Hoops 3DX main line Windows 64" build number 541 originally caused by: Started by an SCM change Building remotely on Slave2 FATAL: null java.lang.NullPointerException at net.praqma.jenkins.plugin.reloaded.Util.getUpstreamRebuildAction(Util.java:84) at net.praqma.jenkins.plugin.reloaded.Util.getDownstreamRebuildActionFromMatrixBuild(Util.java:63) at net.praqma.jenkins.plugin.reloaded.MatrixReloadedEnvironmentContributor.buildEnvironmentFor(MatrixReloadedEnvironmentContributor.java:44) at hudson.model.Run.getEnvironment(Run.java:2045) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:931) at hudson.matrix.MatrixRun$MatrixRunExecution.decideWorkspace(MatrixRun.java:175) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:567) at hudson.model.Run.execute(Run.java:1575) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) I don't have the problem with the daily build who trigger not all jobs in the matrix. So I was thinking about a heavy load problem, but it seems to be something different. the 3 upstream projects are still in jenkins. https://groups.google.com/forum/#!topic/jenkinsci-users/nXQQ0yLg238 Environment: windows 7 jenkins 1.511 Project: Jenkins Labels: plugin matrix exception Priority: Critical Reporter: Louis Roché 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix-reloaded] (JENKINS-17964) NPE if one of the upstream builds is not found
Louis Roché
updated JENKINS-17964
NPE if one of the upstream builds is not found
Change By:
Louis Roché
(15/May/13 2:34 PM)
Description:
IhaveanightlybuildwhotriggeramatrixandIhavethiserrorforeveryjobsinthematrix:{code}StartedbyupstreamprojectWindowsResultsbuildnumber12418originallycausedby:StartedbyupstreamprojectSupervisorTestWindowsNightlybuildnumber615originallycausedby:StartedbyupstreamprojectNightlyBuildHoops3DXmainlineWindows64buildnumber541originallycausedby:StartedbyanSCMchangeBuildingremotelyonSlave2FATAL:nulljava.lang.NullPointerException atnet.praqma.jenkins.plugin.reloaded.Util.getUpstreamRebuildAction(Util.java:84) atnet.praqma.jenkins.plugin.reloaded.Util.getDownstreamRebuildActionFromMatrixBuild(Util.java:63) atnet.praqma.jenkins.plugin.reloaded.MatrixReloadedEnvironmentContributor.buildEnvironmentFor(MatrixReloadedEnvironmentContributor.java:44) athudson.model.Run.getEnvironment(Run.java:2045) athudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:931) athudson.matrix.MatrixRun$MatrixRunExecution.decideWorkspace(MatrixRun.java:175) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:567) athudson.model.Run.execute(Run.java:1575) athudson.matrix.MatrixRun.run(MatrixRun.java:146) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:237){code}Idonthavetheproblemwiththedailybuildwhotriggernotalljobsinthematrix.SoIwasthinkingaboutaheavyloadproblem,butitseemstobesomethingdifferent.the3upstreamprojectsarestillinjenkins.
Butnoteveryworkspaces.
https://groups.google.com/forum/#!topic/jenkinsci-users/nXQQ0yLg238
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16474) Slow/hung web UI in 1.483+ (stuck in parseURI)
Marnix Klooster commented on JENKINS-16474 Slow/hung web UI in 1.483+ (stuck in parseURI) @jfigler: I just was pointed to this JIRA issue: we're running 1.480.1, experiencing very slow network connections to the Jenkins UI when a non-trivial number of users is using Jenkins, and until now (running for an afternoon) it looks like the Groovy script from this earlier comment from Feb 7 makes the problem go away. @Jesse Glick: Which LTS version will contain this fix? And is there a way to change the httpKeepAliveTimeout for Winstone more permanently, in 1.480.1? Thanks for your work on this! 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xshell] (JENKINS-13243) Do not replace slashes in URLs with backslashes on Windows
Andrew C reopened JENKINS-13243 Do not replace slashes in URLs with backslashes on Windows Git URLs are stlil affected: git://github.com/user/repo.git becomes git:\github.com\user\repo.git Change By: Andrew C (15/May/13 2:43 PM) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xshell] (JENKINS-13243) Do not replace slashes in URLs with backslashes on Windows
Andrew C edited a comment on JENKINS-13243 Do not replace slashes in URLs with backslashes on Windows Git URLs are still affected: git://github.com/user/repo.git becomes git:\github.com\user\repo.git 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14150) $NODE_NAME empty for master, exists in $NODE_LABELS
James Monroe
commented on JENKINS-14150
$NODE_NAME empty for master, exists in $NODE_LABELS
I'm having the same problem using ${NODE_NAME} as the perforce workspace name. it works for slaves, but when the job gets assigned to the master, it fails to poll:
Looking for changes...
Using node: Jenkins
Using master perforce client: ${NODE_NAME}
Jenkins $ p4 workspace -o ${NODE_NAME}
*** Perforce client workspace '${NODE_NAME}' doesn't exist.
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xshell] (JENKINS-13243) Do not replace slashes in URLs with backslashes on Windows
Andrew C commented on JENKINS-13243 Do not replace slashes in URLs with backslashes on Windows I have submitted a pull request with a suggested fix for this: https://github.com/jenkinsci/xshell-plugin/pull/7 One concern I have is that there might be other legitimate arguments beginning with git: that aren't git URLs but I can't think of any right now. So hopefully this is sufficient. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16474) Slow/hung web UI in 1.483+ (stuck in parseURI)
Jesse Glick commented on JENKINS-16474 Slow/hung web UI in 1.483+ (stuck in parseURI) @marnix_klooster: the latest fix is in 1.506 and therefore also 1.509.1 LTS; httpKeepAliveTimeout may be passed on the command line (see --help for options). 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cvs] (JENKINS-17965) CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8
Joel Wheeler created JENKINS-17965 CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8 Issue Type: Bug Assignee: Unassigned Components: cvs Created: 15/May/13 3:11 PM Description: I upgraded to CVS plugin version 2.8 from 1.6, and also ran the 'Manage Old Data' process from the Manage Jenkins screen. After the update, some projects were not retrieving changes that were committed to CVS and putting them into the workspace. If I clicked on the 'Recent Changes' link in Jenkins for the job, the changes would appear there, but they were not being pulled into the workspace and CVS polling log showed 'no changes'. For some projects this was not an issue, but for other projects it was. I checked the config files, and some had been updated to the 2.8 format and some still had the 1.6 format. The jobs that had been updated to the 2.8 format were the ones that were not pulling newly committed files into the workspace. It looks like the bug occurs when the config files use the 2.8 plugin format and the 'Use Update' option is selected (canUseUpdatetrue/canUseUpdate). I deselected this option, and also selected 'Force clean copy for locally modified files' (cleanOnFailedUpdatetrue/cleanOnFailedUpdate). The files then began to be correctly updated in the workspace. Here is a config file example where the 1.6 plugin format is used (and continues working with the 2.8 plugin installed): scm class="hudson.scm.CVSSCM" plugin="cvs@1.6" cvsroot:pserver:u...@server.com:/cvsroot/stuff/cvsroot moduleExModule/module canUseUpdatetrue/canUseUpdate useHeadIfNotFoundfalse/useHeadIfNotFound flattenfalse/flatten isTagfalse/isTag excludedRegions/excludedRegions /scm And here is a config file example where the 2.8 plugin format is used and the files do not get updated when there is a commit to CVS: scm class="hudson.scm.CVSSCM" plugin="cvs@2.8" flattentrue/flatten repositories hudson.scm.CvsRepository cvsRoot:pserver:u...@server.com:/cvsroot/stuff/cvsRoot repositoryItems hudson.scm.CvsRepositoryItem modules hudson.scm.CvsModule localName/localName remoteNameExJob2/remoteName /hudson.scm.CvsModule /modules location class="hudson.scm.CvsRepositoryLocation$HeadRepositoryLocation" locationTypeHEAD/locationType useHeadIfNotFoundfalse/useHeadIfNotFound /location /hudson.scm.CvsRepositoryItem /repositoryItems compressionLevel-1/compressionLevel excludedRegions hudson.scm.ExcludedRegion pattern/pattern /hudson.scm.ExcludedRegion /excludedRegions passwordiLig231CAGwVtdt2/P6vseSiX+rCNjWwXG4/sAyjj1c=/password passwordRequiredtrue/passwordRequired /hudson.scm.CvsRepository /repositories canUseUpdatetrue/canUseUpdate skipChangeLogfalse/skipChangeLog pruneEmptyDirectoriestrue/pruneEmptyDirectories disableCvsQuiettrue/disableCvsQuiet cleanOnFailedUpdatefalse/cleanOnFailedUpdate forceCleanCopytrue/forceCleanCopy /scm after changing to these values in the 2.8 plugin format: canUseUpdatefalse/canUseUpdate cleanOnFailedUpdatetrue/cleanOnFailedUpdate it appeared to start working again. I think it was because of the canUseUpdate flag. Environment: Jenkins 1.510, CVS plugin 2.8, Linux RHEL 5 Project: Jenkins Labels: plugin cvs update jenkins Priority: Major Reporter: Joel Wheeler
[JIRA] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
hardwickj closed JENKINS-14825 as Duplicate winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 @xu, this issue was closed because it's a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-10524. Please post any comments or further information there instead. Re-closing... Change By: hardwickj (15/May/13 3:13 PM) Status: Reopened Closed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dry] (JENKINS-17959) Unable to view High and Normal Priority Duplicate Code details using Publish Duplicate Code analysis results plugin
Ulli Hafner commented on JENKINS-17959 Unable to view High and Normal Priority Duplicate Code details using Publish Duplicate Code analysis results plugin Can you please replace your proprietary attachments with images? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-12010) manager.buildSuccess() doesn't work
Yaroslav Astafiev commented on JENKINS-12010 manager.buildSuccess() doesnt work use reflection something like manager.build.@result = hudson.model.Result.SUCCESS works for 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-4740) 404 when not logged in when clicking link in hudson-e-mail
sogabe commented on JENKINS-4740 404 when not logged in when clicking link in hudson-e-mail Adding "Job DISCOVER permission" to annonymous can resove this issue. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-4740) 404 when not logged in when clicking link in hudson-e-mail
sogabe edited a comment on JENKINS-4740 404 when not logged in when clicking link in hudson-e-mail Adding "Job DISCOVER" permission to annonymous can resove this issue. According to help, "Job DISCOVER" means "This permission grants discover access to jobs. Lower than read permissions, it allows you to redirect anonymous users to the login page when they try to access a job url. Without it they would get a 404 error and wouldnt be able to discover project names. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-4740) 404 when not logged in when clicking link in hudson-e-mail
sogabe edited a comment on JENKINS-4740 404 when not logged in when clicking link in hudson-e-mail Adding "Job DISCOVER" permission to anonymous can resolve this issue. According to help, "Job DISCOVER" means "This permission grants discover access to jobs. Lower than read permissions, it allows you to redirect anonymous users to the login page when they try to access a job url. Without it they would get a 404 error and wouldnt be able to discover project names. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-17952) java.lang.NoSuchMethodError: hudson.model.AbstractProject.doBuild(Lorg/kohsuke/stapler/StaplerRequest;Lorg/kohsuke/stapler/StaplerResponse;)
xu dong assigned JENKINS-17952 to Kohsuke Kawaguchi java.lang.NoSuchMethodError: hudson.model.AbstractProject.doBuild(Lorg/kohsuke/stapler/StaplerRequest;Lorg/kohsuke/stapler/StaplerResponse;) I found a similar issue assigned for you. https://issues.jenkins-ci.org/browse/JENKINS-12337 So I assigned this bug for. Change By: xu dong (15/May/13 3:34 PM) Assignee: KohsukeKawaguchi 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [pollscm] (JENKINS-17966) pollscm does not error when ssh auth cannot establish
Brian Buchalter created JENKINS-17966 pollscm does not error when ssh auth cannot establish Issue Type: Bug Affects Versions: current Assignee: Vincent Latombe Components: pollscm Created: 15/May/13 3:47 PM Description: When using Github SCM over SSH with polling, you must manually go into the work space and initiate the first "git fetch" so that the host is identified. It would be nice of the polling log captured this error to report to the user. Project: Jenkins Priority: Minor Reporter: Brian Buchalter 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-17946) Include a list of plugins installed
Samu Wikstedt
commented on JENKINS-17946
Include a list of plugins installed
I guess responsibility of scm-sync-configuration depends on the point of view: Meaning, if purpose is to have backup stored in a safe place, which can be restored after total disaster (for example disk failure, stolen hardware, fire ...) then list of installed plugins is needed. My experienses are that if you try to restore a xml files that have configuration of plugins not currently installed, Jenkins gets quite confused.
If the purpose is just to have SCM repository where old changes in working jenkins configuration can be fetched if needed, this plugin works just fine. And I am not intended to start a debate of the purpose of the plugin. After all it is great tool for my purposes already. So, I am just suggesting widening the scope of the plugin since I think that it could be done quite easily - However, since my java programming skills are severely limited , I might be mistaken on that one
Since I do lack java programming skills, developing plugin is out of my scope. However I do have done a Jenkins restore successfully with method that is more simple that your way of getting plugin list... Now I'm just wondering whether I had more simple plugins than you have had... So what information is lost with method described below:
Prerequisite are:
Jenkins installation, which have configuration backed up with scm-sync-configuration.
List of installed plugins is created with help of jenkins-cli and stripped to more simple list and included to backup:
java -jar jenkins-cli.jar -s http://yourjenkinsurl:8080/ list-plugins plugins.txt
awk '{print $1}' plugins.txt plugins_tripped.txt
Output is a simple list which have simple list of plugin names.
The actual restoring config has these steps:
have new HW-platform with working OS for your jenkins
install fresh jenkins on top of that
Install all plugins from jenkins update site, use the plugins-list from backup:
cat plugins_tripped.txt | xargs java -jar jenkins-cli.jar -s http://yourjenkinsurl:8080/ install-plugin
Shut down jenkins, do svn checkout (or GIT pull) to a temporary folder and copy everything to jenkins home folder, start jenkins and you should have working jenkins again up and running.
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-17815) Build Flow Plugin does not restrict node
Andreas Schmid commented on JENKINS-17815 Build Flow Plugin does not restrict node Even better would be to make it configurable at which node the jobs are executed (+ an option for "same node"). 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-17815) Build Flow Plugin does not restrict node
Andreas Schmid edited a comment on JENKINS-17815 Build Flow Plugin does not restrict node There is an easy workaround if one uses https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin, configures a "node parameter" and sets it's value to the node on which the job should run accordingly. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-17946) Include a list of plugins installed
Frédéric Camblor commented on JENKINS-17946 Include a list of plugins installed Using the jenkins-cli you need : To have an open Jenkins (no authent) : Using jenkins-cli doesn't seem to handle credentials, or have to set up a ssh private key which seems unsafe to me In your example, you don't retrieve plugins' versions, and it seems the install-plugin will install the latest version of every plugins, which is undesirable to my POV 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16474) Slow/hung web UI in 1.483+ (stuck in parseURI)
Jesse Glick commented on JENKINS-16474 Slow/hung web UI in 1.483+ (stuck in parseURI) If anyone encountering this issue is using an Apache proxy, JENKINS-10524 suggests Proxy-nokeepalive, though that is probably unrelated. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactory] (JENKINS-17967) Generic-Artifactory Integration Resolved Artifacts doesn't attach am artifact dependency in artifactory when using Regex
steven armstrong created JENKINS-17967 Generic-Artifactory Integration Resolved Artifacts doesnt attach am artifact dependency in artifactory when using Regex Issue Type: Bug Affects Versions: current Assignee: yossis Attachments: Jenkins_issue.png, Jenkins_issue2.png, Jenkins_issue3.png Components: artifactory Created: 15/May/13 5:08 PM Description: Hi, When using the Jenkins Artifactory plug-in Generic-Artifactory Integration I have set Resolved Artifacts to: repo_key:Builds/DevOps/DevOps_*/DevOps.zip@DevOps#LATEST as shown in the Jenkins_issue screenshot. This resolves an artifact and downloads it to the Jenkins workspace as expected and shown in Jenkins_Issue2. However for some reason it does not link it in Artifactory as a dependency as shown in Jenkins_Issue3 screenshot. It works as expected using a hard coded path and attaches the artifact dependency to artifactory using: repo_key:Builds/DevOps/DevOps_63/DevOps.zip This is shown in the expected screen shot but I can't hardcore the paths in my build as they continually update and I need to use he latest. If you need any further information please let me know. Thanks. Environment: Windows 2008 R2 Project: Jenkins Priority: Critical Reporter: steven armstrong 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10524) winstone.ClientSocketException: Failed to write to client
Jesse Glick commented on JENKINS-10524 winstone.ClientSocketException: Failed to write to client @hardwickj: very interesting, thanks for noting this. Might help reproduce the stack trace, and is a good tip for people encountering odd errors. (I am wondering whether some incidences of JENKINS-16474 are related.) Bizarre that Apache would produce the totally inappropriate 404 status code for this situation though; I would have expected a 504 here! If you can reproduce that, consider filing a bug for Apache. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactory] (JENKINS-17967) Generic-Artifactory Integration Resolved Artifacts doesn't attach an artifact dependency in artifactory when using Regex
steven armstrong updated JENKINS-17967 Generic-Artifactory Integration Resolved Artifacts doesnt attach an artifact dependency in artifactory when using Regex Change By: steven armstrong (15/May/13 5:08 PM) Summary: Generic-ArtifactoryIntegrationResolvedArtifactsdoesntattach am an artifactdependencyinartifactorywhenusingRegex 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17968) Unable to update plugins after the Jenkins 1.514 upgrade
Rakesh Kumar created JENKINS-17968 Unable to update plugins after the Jenkins 1.514 upgrade Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: plugin Created: 15/May/13 5:10 PM Description: Unable to update plugins after the Jenkins 1.514 upgrade. There is no proxy set up in Manage Plugins advanced tab. I get the below error for plugins update. I could access the link http://updates.jenkins-ci.org/update-center.json?uctest from a browser on the same machine without any issue. java.io.FileNotFoundException: http://updates.jenkins-ci.org/update-center.json?uctest at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1434) at hudson.model.UpdateCenter$UpdateCenterConfiguration.testConnection(UpdateCenter.java:862) at hudson.model.UpdateCenter$UpdateCenterConfiguration.checkUpdateCenter(UpdateCenter.java:711) at hudson.model.UpdateCenter$ConnectionCheckJob.run(UpdateCenter.java:1032) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) Due Date: 17/May/13 12:00 AM Project: Jenkins Labels: plugin jenkins Priority: Critical Reporter: Rakesh Kumar 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17969) Jelly Script not working
David Brossard
created JENKINS-17969
Jelly Script not working
Issue Type:
Bug
Affects Versions:
current
Assignee:
Alex Earl
Components:
email-ext
Created:
15/May/13 5:36 PM
Description:
Using the default Jelly Script template in the Extended Email notification sends the literal string rather than the Jelly content.
Setup:
Override Global Settings: Unchecked
Default Content Type: HTML (text/html)
Use List-ID Email Header: Unchecked
Add 'Precedence: bulk' Email Header: Unchecked
Default Recipients: m...@email.com
Reply To List,Emergency reroute,Excluded Committers: Unused
Default Subject:$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS!
Maximum Attachment Size: Unused
Default Content:
$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS:p
Check console output at $BUILD_URL to view the results.p
${CHANGES}p
${JELLY_SCRIPT,template=”html”}
Default Pre-send Script: Unused
Enable Debug Mode: Checked
Enable Security: Unchecked
Here are the results from a recent test:
DEV-Build and Deploy - Build # 210 - Successful:
Check console output at http://myserver:8080/job/DEV-Build%20and%20Deploy/210/ to view the results.
David Brossard test email only
${JELLY_SCRIPT,template=”html”}
Environment:
Ubuntu 12.04, Email-ext 2.29, Jenkins 1.514
Project:
Jenkins
Priority:
Major
Reporter:
David Brossard
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17970) Change-set Identity regex once broke against Swedish character
Marco Miller created JENKINS-17970 Change-set Identity regex once broke against Swedish character Issue Type: Bug Assignee: Marco Miller Components: git, plugin Created: 15/May/13 6:20 PM Description: Change-set's Identity regex once broke against a Swedish character, for us here at Ericsson. By "broke" I mean that for some reason, our Jenkins/Java stack was running latin-1 character set/encoding, instead of utf8. So our git handled that Swedish character as utf8 (2-bytes) but Jenkins/Java read it as latin-1 (1-byte) -through that "broken" change-set Id regex. What’s too bad is that the character in that Swedish user name takes 2 bytes in utf8: \303 \205 (octal). But \205 doesn’t exist in latin-1, so the regex dot didn’t want it and the match failed. Project: Jenkins Priority: Minor Reporter: Marco Miller 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [github] (JENKINS-17966) pollscm does not error when ssh auth cannot establish
Vincent Latombe updated JENKINS-17966 pollscm does not error when ssh auth cannot establish Change By: Vincent Latombe (15/May/13 6:30 PM) Component/s: github Component/s: pollscm 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [github] (JENKINS-17966) pollscm does not error when ssh auth cannot establish
Vincent Latombe updated JENKINS-17966 pollscm does not error when ssh auth cannot establish Change By: Vincent Latombe (15/May/13 6:31 PM) Assignee: VincentLatombe 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17970) Change-set Identity regex once broke against Swedish character
Marco Miller updated JENKINS-17970 Change-set Identity regex once broke against Swedish character Change By: Marco Miller (15/May/13 6:31 PM) Description: Change-setsIdentityregexoncebrokeagainstaSwedishcharacter,forushereatEricsson.BybrokeImeanthatforsomereason,ourJenkins/Javastackwasrunninglatin-1characterset/encoding,insteadofutf8.SoourgithandledthatSwedishcharacterasutf8(2-bytes)butJenkins/Javareaditaslatin-1(1-byte)-throughthatbrokenchange-setIdregex.What’stoobadisthatthecharacterinthatSwedishusernametakes2bytesinutf8:\303\205(octal).But\205doesn’texistinlatin-1,sotheregexdotdidn’twantitandthematchfailed. Neededthenisarobustnessfixsothatregex(GitChangeSetIDENTITYs)doesnotrejectsuchapossibly-desiredmatch.WesaysoeventhoughthereisnoguaranteethatsuchafixedregexwouldkeepmatchingourmistreatedSwedishnameinthefuture.Allweknowisthatweonceneededthatfixtosurviveanawkward-yetrealistic-Jenkins/Javastacksetup(intermsofdefaultlocaleand/orcharacter-setencoding). 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17411) Pushing a fast-forward merge does not trigger a build
Vincent Latombe updated JENKINS-17411 Pushing a fast-forward merge does not trigger a build Change By: Vincent Latombe (15/May/13 6:32 PM) Component/s: pollscm 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17970) Change-set Identity regex once broke against Swedish character
Marco Miller updated JENKINS-17970 Change-set Identity regex once broke against Swedish character Change By: Marco Miller (15/May/13 6:32 PM) Description: Change-setsIdentityregexoncebrokeagainstaSwedishcharacter,forushereatEricsson.BybrokeImeanthatforsomereason,ourJenkins/Javastackwasrunninglatin-1characterset/encoding,insteadofutf8.SoourgithandledthatSwedishcharacterasutf8(2-bytes)butJenkins/Javareaditaslatin-1(1-byte)-throughthatbrokenchange-setIdregex.What’stoobadisthatthecharacterinthatSwedishusernametakes2bytesinutf8:\303\205(octal).But\205doesn’texistinlatin-1,sotheregexdotdidn’twantitandthematchfailed.Neededthenisarobustnessfixsothatregex(GitChangeSetIDENTITYs)doesnotrejectsuchapossibly-desiredmatch.WesaysoeventhoughthereisnoguaranteethatsuchafixedregexwouldkeepmatchingourmistreatedSwedishnameinthefuture.Allweknowisthatweonceneededthatfixtosurviveanawkward - ( yetrealistic - ) Jenkins/Javastacksetup(intermsofdefaultlocaleand/orcharacter-setencoding). 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-17592) Testflight uploader plugin doesn't allow to upload multiple files
lacostej commented on JENKINS-17592 Testflight uploader plugin doesnt allow to upload multiple files Have you seen that by default, the plugin searches for all apks ? You shouldn't to have to specify any. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [bazaar] (JENKINS-17971) bzr switch does not work for anonymous http checkouts
Timotheus Pokorra created JENKINS-17971 bzr switch does not work for anonymous http checkouts Issue Type: Bug Assignee: Monty Taylor Components: bazaar Created: 15/May/13 7:37 PM Description: We wonder why there is the need to run bzr switch. This will not work if you checkout anonymously a branch from Launchpad, eg. lp:openpetraorg. It works for the first build and checkout: from the log: $ bzr checkout --lightweight lp:openpetraorg "C:\Program Files (x86)\Jenkins\workspace\OpenPetraBuildWinTimotheus" You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See "bzr help launchpad-login". Getting local revision... $ bzr revision-info -d "C:\Program Files (x86)\Jenkins\workspace\OpenPetraBuildWinTimotheus" info result: bzr revision-info -d C:\Program Files (x86)\Jenkins\workspace\OpenPetraBuildWinTimotheus returned 0. Command output: "2226 timotheus.poko...@solidcharity.com-20130515153627-dvnp06rop5rtzcfa " stderr: "" RevisionState revno:2226 revid:timotheus.poko...@solidcharity.com-20130515153627-dvnp06rop5rtzcfa No emails were triggered. and builds fine. The second build, no change on the code, same revision 2226: $ bzr revision-info -d "C:\Program Files (x86)\Jenkins\workspace\OpenPetraBuildWinTimotheus" info result: bzr revision-info -d C:\Program Files (x86)\Jenkins\workspace\OpenPetraBuildWinTimotheus returned 0. Command output: "2226 timotheus.poko...@solidcharity.com-20130515153627-dvnp06rop5rtzcfa " stderr: "" OpenPetraBuildWinTimotheus $ bzr update Tree is up to date at revision 2226 of branch http://bazaar.launchpad.net/~openpetracore/openpetraorg/trunkhosted OpenPetraBuildWinTimotheus $ bzr switch lp:openpetraorg bzr: ERROR: Cannot lock LockDir(http://bazaar.launchpad.net/~openpetracore/openpetraorg/trunkhosted/.bzr/branch/lock): Transport operation not possible: http does not support mkdir() ERROR: Failed to switch Since BZR itself isn't crash safe, we'll clean the workspace so that on the next try we'll do a clean pull... But then it does not recover from that, and the build fails. Environment: bzr plugin 1.22 Project: Jenkins Priority: Major Reporter: Timotheus Pokorra 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-17563) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
SCM/JIRA link daemon commented on JENKINS-17563 java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory) Code changed in jenkins User: Jerome Lacoste Path: src/main/java/testflight/TestflightRemoteRecorder.java http://jenkins-ci.org/commit/testflight-plugin/7aff00f73e6e0cf11744ea6d5dceaec858f917ec Log: JENKINS-17563 tentative fix for the file not found issue, potentially caused by some sort of non default workspace 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-17563) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
lacostej commented on JENKINS-17563 java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory) I noticed that for some reason your workspace isn't the workspace directory but a sub-directory /Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS I've made a tentative fix in 1.3.6 released tonight. See https://github.com/jenkinsci/testflight-plugin/commit/7aff00f73e6e0cf11744ea6d5dceaec858f917ec 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-17563) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
lacostej edited a comment on JENKINS-17563 java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory) I noticed that for some reason your workspace isn't the workspace directory but a sub-directory /Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS I've made a tentative fix in 1.3.6 released tonight. See https://github.com/jenkinsci/testflight-plugin/commit/7aff00f73e6e0cf11744ea6d5dceaec858f917ec Let me know if the issue is fixed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Ken Garland assigned JENKINS-17684 to Account App Run by Kohsuke Dashboard web pages dont render correctly in Chrome because of bad cache/session 15:51:06 +rpetti IMO, just assign it to kohsuke Change By: Ken Garland (15/May/13 7:53 PM) Assignee: AccountAppRunbyKohsuke 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17474) clicking Apply when renaming a project fails
owenmehegan resolved JENKINS-17474 as Duplicate clicking Apply when renaming a project fails Duplicate of JENKINS-17401. Change By: owenmehegan (15/May/13 8:00 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17401) Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window
owenmehegan updated JENKINS-17401 Renaming a job and clicking Apply shows an empty Error pop-over window Change By: owenmehegan (15/May/13 8:01 PM) Assignee: KohsukeKawaguchi Component/s: core Component/s: gui 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-17972) Skip certificate check
vjuranek created JENKINS-17972 Skip certificate check Issue Type: New Feature Assignee: vjuranek Components: build-publisher Created: 15/May/13 8:38 PM Description: Skip certificate check plugin doesn't seem to work with build publisher. Implement option to skip certificate check when publishing the build. Project: Jenkins Priority: Major Reporter: vjuranek 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Ross M. commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly My colleague at work installed groovy and restarted the apache2 service and that fixed the issue. Steps 1. apt-get install groovy 2. service apache2 restart 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-17751) Link from triggering promotion to triggered build
ikedam commented on JENKINS-17751 Link from triggering promotion to triggered build I'm not sure for I'm not a maintainer of Parametrized Trigger plugin. I sent a pull request https://github.com/jenkinsci/parameterized-trigger-plugin/pull/38 and anyone deos not yet respond it. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
wee thomas commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification I've been experiencing this issue as well. I found that it occurs with my build-pipeline. Initially, a clone is made from an Hg repository. This then kicks off a build of the source. If successful, I archive the workspace and then I trigger another job (to run lint). This downstream job uses the saved successful workspace. I've noticed that when I manually trigger builds within Jenkins, at that point, the email gets screwed up. This occurs with a fresh (1.514) Jenkins build with only the Mercurial and Clone Workspace plugins installed. This occurs whether I do it on the initial build job or the downstream lint job. I'd been doing this (triggering builds manually) to test job configuration. My current workaround is to make a small comment change in my source, commit and push. Both jobs have email user who broke the build as a post-build step. I didn't experience this bug when experimenting with build configurations using a project on a subversion repository. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
wee thomas edited a comment on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification I've been experiencing this issue as well. I found that it occurs with my build-pipeline. Initially, a clone is made from an Hg repository. This then kicks off a build of the source. If successful, I archive the workspace and then I trigger another job (to run lint). This downstream job uses the saved successful workspace. I've noticed that when I manually trigger builds within Jenkins, at that point, the email gets screwed up. This occurs with a fresh (1.514) Jenkins build with only the Mercurial and Clone Workspace plugins installed. This occurs whether I do it on the initial build job or the downstream lint job. I'd been doing this (triggering builds manually) to test job configuration. My current workaround is to make a small comment change in my source, commit and push. Both jobs have email user who broke the build as a post-build step. I didn't experience this bug when experimenting with build configurations using a project on a subversion repository. To fix the phantom invalid user which Jenkins then recognizes for future SCM changes, I have to delete history of all builds that involve that user (if the build was successful, all jobs builds that it triggered), then restart Jenkins. At this point, the invalid user disappears and I can proceed. The other option is to just clone the jobs, then delete the old ones and rename them back. The downside of both approaches is that you lose a bit (or a lot) of build history. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
wee thomas edited a comment on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification I've been experiencing this issue as well. I found that it occurs with my build-pipeline. Initially, a clone is made from an Hg repository. This then kicks off a build of the source. If successful, I archive the workspace and then I trigger another job (to run lint). This downstream job uses the saved successful workspace. I've noticed that when I manually trigger builds within Jenkins, at that point, the email gets screwed up. This occurs with a fresh (1.514) Jenkins build with only the Mercurial and Clone Workspace plugins installed. This occurs whether I do it on the initial build job or the downstream lint job. I'd been doing this (triggering builds manually) to test job configuration. My current workaround is to make a small comment change in my source, commit and push. Both jobs have email user who broke the build as a post-build step. I didn't experience this bug when experimenting with build configurations using a project on a subversion repository. To fix the phantom invalid user which Jenkins then recognizes for future SCM changes, I have to delete history of all builds that involve that user (if the build was successful, all jobs builds that it triggered), then restart Jenkins. At this point, the invalid user disappears and I can proceed. The other option is to just clone the jobs, then delete the old ones and rename them back (still requires a restart after this). The downside of both approaches is that you lose a bit (or a lot) of build history. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17969) Jelly Script not working
Alex Earl
commented on JENKINS-17969
Jelly Script not working
I just tested the exact text as you have it and it failed, but I then went in and made sure it the following (made sure curly quotes were not being used, added a space after the comma and so forth and it worked for me).
$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUSp
Check console output at $BUILD_URL to view the results.p
${CHANGES}p
${JELLY_SCRIPT, template="html"}
You can verify what (if any) bad tokens (like curly quotes and such) are in your template by viewing the config.xml for the job.
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-17563) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
Charles Doucette commented on JENKINS-17563 java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory) I believe the directory is fine. The file reference should be relative to the workspace directory. The job is running on a mac slave node. Apparently, unlike the directory organization on the master node, it uses workspace instead of jobs as a top-level directory. Also, instead of having a workspace subdirectory, the directory matching the jobname is the workspace. Anyhow, the new plugin works, so I believe the issue is resolved. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17968) Unable to update plugins after the Jenkins 1.514 upgrade
Rakesh Kumar closed JENKINS-17968 as Not A Defect Unable to update plugins after the Jenkins 1.514 upgrade Issue with VPN client Change By: Rakesh Kumar (16/May/13 12:23 AM) Status: Open Closed Resolution: NotADefect 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-17563) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
Charles Doucette
commented on JENKINS-17563
java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
FYI - I believe the configuration of the plugin (and the jobs that used it) have been completely changed.
Now the team token and api token is expected on the global jenkins configuration page (where you give every pair a name),
and on the job configuration, you select a token pair name.
On the old plugin, there was no global configuration and the team token and api token were listed in every project.
Anyhow, this is the current job output (with debug settings):
Started by user cdoucette
EnvInject - Loading node environment variables.
Building remotely on macmini-05 in workspace /Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS
Uploading to testflight
File: /Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS/Engineering/iOS/UScapeIt/UScapeIt.app.ipa
DSYM: /Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS/Engineering/iOS/UScapeIt/UScapeIt.app.dSYM.zip
POST Request: testflight.TestflightUploader$UploadRequest@f1f930c[filePath=Engineering/iOS/UScapeIt/UScapeIt.app.ipa,dsymPath=Engineering/iOS/UScapeIt/UScapeIt.app.dSYM.zip,apiToken=***,teamToken=***,notifyTeam=true,buildNotes=This is the latest build of UScapeit (for iOS) which was built by Jenkins UScapeit-TestFlight 3.0.130.3
,file=/Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS/Engineering/iOS/UScapeIt/UScapeIt.app.ipa,dsymFile=/Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS/Engineering/iOS/UScapeIt/UScapeIt.app.dSYM.zip,lists=UScapeIt,replace=false,proxyHost=,proxyUser=,proxyPass=,proxyPort=0,debug=true]
POST Answer: {
"bundle_version": "2.5 (87)",
"install_url": "https://testflightapp.com/install/52d0cb8f907775bb088ead1a407ab269-NDk1OTc5NQ/",
"config_url": "https://testflightapp.com/dashboard/builds/complete/4959795/",
"created_at": "2013-05-15 20:36:19",
"device_family": "iPhone",
"notify": true,
"team": "EveryScape",
"minimum_os_version": "4.3",
"release_notes": "This is the latest build of UScapeit (for iOS) which was built by Jenkins UScapeit-TestFlight 3.0.130.3\n",
"binary_size": 6580333
}
Testflight Upload speed: 4.54Mbps
Testflight Install Link: https://testflightapp.com/install/52d0cb8f907775bb088ead1a407ab269-NDk1OTc5NQ/
Testflight Configuration Link: https://testflightapp.com/dashboard/builds/complete/4959795/
Finished: SUCCESS
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-17973) TFS SCM Polling fails with :: FATAL: Parse error. Unable to find an item within a changeset
david clark created JENKINS-17973 TFS SCM Polling fails with :: FATAL: Parse error. Unable to find an item within a changeset Issue Type: Bug Affects Versions: current Assignee: redsolo Components: tfs Created: 16/May/13 1:24 AM Description: The SCM polling runs fine but then a tfs change is detected this error occurs: Started on May 16, 2013 11:17:30 AM}} [workspace] $ /Applications/TEE-CLC-10.0.0/tf history "$/Hotel Search iPhone" -noprompt -version:D2013-05-10T01:59:13Z~D2013-05-16T01:17:31Z -recursive -format:detailed -server:http://tfs2012:8080/tfs Changeset: 41150 User: AAA\DavidC Date: May 16, 2013 11:04:19 AM Comment: Commit 0ad1f0c (Thu May 16 08:39:06 2013 +1000) Author: David Clark david.cl...@hotelscombined.com Committer: David Clark david.cl...@hotelscombined.com - testing ci Items: edit $/Hotel Search iPhone/HCWeb/HCWeb-Info.plist FATAL: Parse error. Unable to find an item within a changeset. Please report this as a bug. Changesetdata = " Changeset: 41150 User: AAA\DavidC Date: May 16, 2013 11:04:19 AM Comment: Commit 0ad1f0c (Thu May 16 08:39:06 2013 +1000) Author: David Clark david.cl...@hotelscombined.com Committer: David Clark david.cl...@hotelscombined.com ". null FATAL: Aborted Done. Took 3.2 sec No changes The same error occurs when the build is triggered manually after a tfs checkin, however a second manual build will then succeed. Environment: Mac OSX Mountain Lion Project: Jenkins Labels: tfs scm mac osx Priority: Major Reporter: david clark 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-16208) TFS SCM Polling: FATAL: Parse error. Unable to find an item within a changeset
david clark edited a comment on JENKINS-16208 TFS SCM Polling: FATAL: Parse error. Unable to find an item within a changeset I am having the same issue, however the commit message is not the problem. Also: The TFS server poller fails forever after a tfs checkin. However, if I manually run the build it will fail once, then work on the next try. Here is the log: Started on May 3, 2013 5:38:07 PM [workspace] $ /Applications/TEE-CLC-10.0.0/tf history "$/Hotel Search iPhone" -noprompt -version:D2013-05-03T07:32:40Z~D2013-05-03T07:38:08Z -recursive -format:detailed -server:http://tfs2012:8080/tfs Changeset: 40495 User: AAA\DavidC Date: May 3, 2013 5:37:50 PM Comment: Commit 853906c (Fri May 03 17:37:43 2013 +1000) Author: David Clark david.cl...@hotelscombined.com Committer: David Clark david.cl...@hotelscombined.com - version bump to test CI Items: edit $/Hotel Search iPhone/HCWeb/HCWeb-Info.plist FATAL: Parse error. Unable to find an item within a changeset. Please report this as a bug. Changesetdata = " Changeset: 40495 User: AAA\DavidC Date: May 3, 2013 5:37:50 PM Comment: Commit 853906c (Fri May 03 17:37:43 2013 +1000) Author: David Clark david.cl...@hotelscombined.com Committer: David Clark david.cl...@hotelscombined.com ". null FATAL: Aborted Done. Took 4.1 sec No changes 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17569) False positive on git polling
Mark Waite commented on JENKINS-17569 False positive on git polling Can you provide any further details on the conditions which cause the false positive on git polling? Many users are using the Git plugin without seeing false positives as far as I can tell. My projects don't show false positives either. Even if few people see the problem, it is still likely a bug, but unless the bug can be duplicated, it is especially difficult to fix it. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17898) Git plugin: tags triggers don't work as expected
Mark Waite updated JENKINS-17898 Git plugin: tags triggers dont work as expected Change By: Mark Waite (16/May/13 3:47 AM) Issue Type: Bug Improvement 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-17563) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
lacostej commented on JENKINS-17563 java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory) Charles, yes the old configuration changed. Did you prefer having to enter all values in each job or do you prefer the new system ? Jerome 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-17563) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
lacostej resolved JENKINS-17563 as Fixed java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory) Change By: lacostej (16/May/13 5:27 AM) Status: Open Resolved Assignee: lacostej 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [postbuildscript] (JENKINS-11219) Add the option to run the script after all the sub elements of a matrix project build have finished
Markus Strand commented on JENKINS-11219 Add the option to run the script after all the sub elements of a matrix project build have finished To me it looks like the PostBuildScript execution happens only on the entire matrix build and not at all for the elements. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-17563) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
lacostej closed JENKINS-17563 as Fixed java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory) Change By: lacostej (16/May/13 5:30 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
