[JIRA] (JENKINS-14580) Configuration of Buildresult-Trigger remains unchanged, when saved.
Ramakrishna Bejawar commented on JENKINS-14580 Configuration of Buildresult-Trigger remains unchanged, when saved. Thanks for the update..I will implement and test it for my configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14702) Use the current streams project, if the jenkins build project is not found
Christian Wolfgang created JENKINS-14702 Use the current streams project, if the jenkins build project is not found Issue Type: Improvement Assignee: Christian Wolfgang Components: clearcase-ucm Created: 07/Aug/12 7:23 AM Project: Jenkins Priority: Major Reporter: Christian Wolfgang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Alex Birkett edited a comment on JENKINS-14201 Git submodules checked out in wrong place Thanks for your comment Matt Willsher. How would one add a git checkout as a manual step? I can make Jenkins build my project if I wipe the workspace before each build and disable internal tagging. Appart from the unnecessary strain this puts on the git server, it breaks polling - the project get built after each poll, not just when changes are detected. This issue is still blocking me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Alex Birkett commented on JENKINS-14201 Git submodules checked out in wrong place Thanks for your comment Matt Willsher. How would one add a git checkout as a manual step? I can make Jenkins build my project if I wipe the workspace before each build and disable internal tagging. Appart from the unnecessary strain this puts on the git server, it breaks polling - the project get built after each poll, not just when changes detected. This issue is still blocking me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13113) Xunit Plugin detects MSTEST NotExecuted as Passed instead of Skipped
Dirk Kuypers reopened JENKINS-13113 Xunit Plugin detects MSTEST NotExecuted as Passed instead of Skipped Hi Gregory, I came accross those two issues for mstest plugin. As the mstest plugin shows the same errors and there even exists a pull request with a fix in 11332, couldn't you just implement the fix for the xunit plugin? I could not see any progress in mstest plugin for ages now... https://issues.jenkins-ci.org/browse/JENKINS-8435 https://issues.jenkins-ci.org/browse/JENKINS-11332 Thanks Dirk Change By: Dirk Kuypers (07/Aug/12 9:02 AM) Resolution: Incomplete Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12231) RPM upgrade does not honor JENKINS_USER, and always resets files ownership to jenkins
Georg Sash commented on JENKINS-12231 RPM upgrade does not honor JENKINS_USER, and always resets files ownership to jenkins I have the exact same problem. this is very annoying. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14686) Fail evaluating Groovy script before job run
Peter S commented on JENKINS-14686 Fail evaluating Groovy script before job run Thanks for quick response and fast resolving. Bug fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14686) Fail evaluating Groovy script before job run
Peter S closed JENKINS-14686 as Fixed Fail evaluating Groovy script before job run Change By: Peter S (07/Aug/12 9:59 AM) Status: InProgress Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14703) PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Karsten Günther
created JENKINS-14703
PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Issue Type:
Bug
Affects Versions:
current
Assignee:
Cletus DSouza
Components:
integrity-plugin
Created:
07/Aug/12 10:21 AM
Description:
Company language is English so we want to use the locale plugin to force Jenkins frontend to English. But if we do so, we get the following error message during SCM polling with integrity plugin:
{{Started by an SCM change
Building in workspace d:\Jenkins\jobs\CT_ZT6BAL\workspace
Change Log: http://frl1dtwg.auto.contiwan.com/job/CT_ZT6BAL/38/changes
Build Log: http://frl1dtwg.auto.contiwan.com/job/CT_ZT6BAL/38/console
Preparing to execute si projectinfo for #p=d:/mks/archives/src/CT_ZT6.pj#d=ZT6BAL
Preparing to execute si viewproject for #p=d:/mks/archives/src/CT_ZT6.pj#d=ZT6BAL
A SQL Exception was caught!
Failed to create database 'd:/Jenkins/jobs/CT_ZT6BAL/builds/2012-08-06_11-02-18/IntegritySCM', see the next exception for details.
Archiving artifacts
Skipping Cobertura coverage report as build was not UNSTABLE or better ...
Recording test results
Finished: FAILURE}}
Environment:
Windows 7 64 bit, MKS Integrity Client 2009 (Build: 4.10.0.9049), Jenkins 1.476, integrity-plugin 1.14
Project:
Jenkins
Labels:
plugin
jenkins
Priority:
Major
Reporter:
Karsten Günther
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14703) PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Karsten Günther
updated JENKINS-14703
PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Change By:
Karsten Günther
(07/Aug/12 10:28 AM)
Description:
CompanylanguageisEnglishsowewanttousethelocaleplugintoforceJenkinsfrontendtoEnglish.Butifwedoso,wegetthefollowingerrormessageduringSCMpollingwithintegrityplugin:{{StartedbyanSCMchange}}{{Buildinginworkspaced:\Jenkins\jobs\xxx\workspace}}{{ChangeLog:http://xxxjenkinsxxx/job/xxx/38/changes}}{{BuildLog:http://xxxjenkinsxxx/job/xxx/38/console}}{{Preparingtoexecutesiprojectinfofor#p=d:/mks/archives/src/xxx.pj#d=xxxBAL}}{{Preparingtoexecutesiviewprojectfor#p=d:/mks/archives/src/xxx.pj#d=xxxBAL}}{{{color:red}ASQLExceptionwascaught!{color}}}{{Failedtocreatedatabased:/Jenkins/jobs/xxx/builds/2012-08-06_11-02-18/IntegritySCM,seethenextexceptionfordetails.}}{{Archivingartifacts}}{{SkippingCoberturacoveragereportasbuildwasnotUNSTABLEorbetter...}}{{Recordingtestresults}}{{Finished:FAILURE}}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14703) PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Karsten Günther
updated JENKINS-14703
PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Change By:
Karsten Günther
(07/Aug/12 10:27 AM)
Description:
CompanylanguageisEnglishsowewanttousethelocaleplugintoforceJenkinsfrontendtoEnglish.Butifwedoso,wegetthefollowingerrormessageduringSCMpollingwithintegrityplugin:{{
monospaced}}
StartedbyanSCMchange
}}
{{
Buildinginworkspaced:\Jenkins\jobs\xxx\workspace
}}
{{
ChangeLog:http://xxxjenkinsxxx/job/xxx/38/changes
}}
{{
BuildLog:http://xxxjenkinsxxx/job/xxx/38/console
}}
{{
Preparingtoexecutesiprojectinfofor#p=d:/mks/archives/src/xxx.pj#d=xxxBAL
}}
{{
Preparingtoexecutesiviewprojectfor#p=d:/mks/archives/src/xxx.pj#d=xxxBAL
}}
{
{{
color:red}ASQLExceptionwascaught!{color}
}}
{{
Failedtocreatedatabased:/Jenkins/jobs/xxx/builds/2012-08-06_11-02-18/IntegritySCM,seethenextexceptionfordetails.
}}
{{
Archivingartifacts
}}
{{
SkippingCoberturacoveragereportasbuildwasnotUNSTABLEorbetter...
}}
{{
Recordingtestresults
}}
{{
Finished:FAILURE
{{monospaced
}}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14703) PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Karsten Günther
updated JENKINS-14703
PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Change By:
Karsten Günther
(07/Aug/12 10:30 AM)
Description:
CompanylanguageisEnglishsowewanttousethelocaleplugintoforceJenkinsfrontendtoEnglish.Butifwedoso,wegetthefollowingerrormessageduringSCMpollingwithintegrityplugin:{
{
quote}
StartedbyanSCMchange
}}
{{
Buildinginworkspaced:\Jenkins\jobs\xxx\workspace
}}
{{
ChangeLog:http://xxxjenkinsxxx/job/xxx/38/changes
}}
{{
BuildLog:http://xxxjenkinsxxx/job/xxx/38/console
}}
{{
Preparingtoexecutesiprojectinfofor#p=d:/mks/archives/src/xxx.pj#d=xxxBAL
}}
{{
Preparingtoexecutesiviewprojectfor#p=d:/mks/archives/src/xxx.pj#d=xxxBAL
}}
{
{{
color:red}ASQLExceptionwascaught!{color}
}}
{{
Failedtocreatedatabased:/Jenkins/jobs/xxx/builds/2012-08-06_11-02-18/IntegritySCM,seethenextexceptionfordetails.
}}
{{
Archivingartifacts
}}
{{
SkippingCoberturacoveragereportasbuildwasnotUNSTABLEorbetter...
}}
{{
Recordingtestresults
}}
{{
Finished:FAILURE
}}
{quote}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14702) Use the current streams project, if the jenkins build project is not found
Christian Wolfgang resolved JENKINS-14702 as Fixed Use the current streams project, if the jenkins build project is not found Change By: Christian Wolfgang (07/Aug/12 10:32 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14704) PTC Integrity Plugin throws/catches SQL Exception in case of too long revision number
Karsten Günther created JENKINS-14704 PTC Integrity Plugin throws/catches SQL Exception in case of too long revision number Issue Type: Bug Affects Versions: current Assignee: Cletus DSouza Components: integrity-plugin Created: 07/Aug/12 11:37 AM Description: File revision number to be handled by integrity plugin seems to be limited to 30 characters. But the projects in my company simply have longer revision numbers. Building in workspace d:\Jenkins\jobs\xxx\workspace Change Log: http://xxxjenkinsxxx/job/xxx/112/changes Build Log: http://xxxjenkinsxxx/job/xxx/112/console Preparing to execute si projectinfo for #p=d:/mks/archives/src/xxx.pj Preparing to execute si viewproject for #p=d:/mks/archives/src/xxx.pj A SQL Exception was caught! A truncation error was encountered trying to shrink VARCHAR '1.17.4.3.3.7.1.3.1.2.1.1.1.5.4.1' to length 30. Retrying after 10 seconds Environment: Windows 7 64 bit, MKS Integrity Client 2009 (Build: 4.10.0.9049), Jenkins 1.476, integrity-plugin 1.14 Project: Jenkins Priority: Major Reporter: Karsten Günther This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14705) Jenkins' built-in Variables should be useable in Integrity Plugin's Configuration Fields
Karsten Günther
created JENKINS-14705
Jenkins built-in Variables should be useable in Integrity Plugins Configuration Fields
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Cletus DSouza
Components:
integrity-plugin
Created:
07/Aug/12 11:44 AM
Description:
Would be great to be able to use Jenkins' environment and built-in variables in the configuration fields of the integrity plugin.
E.g., my job names are equal to the project names in MKS and I just want to copy existing jobs in Jenkins to create new jobs for other projects just by changing the job name. Therefore I would like to use something like this in the "Integrity Project" configuration field:
#p=d:/mks/archives/src/${JOB_NAME}.pj
Environment:
All
Project:
Jenkins
Priority:
Major
Reporter:
Karsten Günther
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14706) Integrity Plugin should create *.pj files, too
Karsten Günther created JENKINS-14706 Integrity Plugin should create *.pj files, too Issue Type: Improvement Affects Versions: current Assignee: Cletus DSouza Components: integrity-plugin Created: 07/Aug/12 11:48 AM Description: In my Jenkins jobs I need to use some other tools for further creation of necessary sources for building. But these tools need access to the MKS project and therefore need the *.pj files, too. At the moment I am creating a new sandbox in the build step of my projects but I would like to use the sandbox already created by the plugin. Environment: All Project: Jenkins Priority: Minor Reporter: Karsten Günther This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14596) Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException
David Voillemin commented on JENKINS-14596 Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException Hi, I have the same error since I've upgraded to Jenkins ver. 1.476. Exception: org.apache.commons.jelly.JellyTagException: jar:file:/C:/JCI/DAT/war/WEB-INF/lib/jenkins-core-1.476.jar!/jenkins/model/Jenkins/configure.jelly:59:84: st:include java.lang.OutOfMemoryError: PermGen space Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/JCI/DAT/war/WEB-INF/lib/jenkins-core-1.476.jar!/jenkins/model/Jenkins/configure.jelly:59:84: st:include java.lang.OutOfMemoryError: PermGen space at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java: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 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:175) 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:47) 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:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at
[JIRA] (JENKINS-14707) Failed to instantiate class hudson.plugins.git.GitSCM
Olivier Vernin
created JENKINS-14707
Failed to instantiate class hudson.plugins.git.GitSCM
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git
Created:
07/Aug/12 11:58 AM
Description:
Status Code: 500
Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.git.GitSCM from {"":hudson.plugins.git.util.DefaultBuildChooser,auto,"authorOrCommitter":false,"branches":{"name":"**"},"buildChooser":{"stapler-class":"hudson.plugins.git.browser.GitoriousWeb"},"clean":false,"disableSubmodules":false,"excludedRegions":"","excludedUsers":"","gitConfigEmail":"jenk...@texttochange.com","gitConfigName":"jenkins","gitTool":"Default","ignoreNotifyCommit":false,"includedRegions":"","localBranch":"","pruneBranches":false,"recursiveSubmodules":false,"reference":"","relativeTargetDir":"","remotePoll":false,"scmName":"","skipTag":true,"userRemoteConfigs":{"name":"","refspec":"","url":"https://github.com/texttochange/vusion-frontend"},"value":"1","wipeOutWorkspace":false}
Stacktrace:
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.git.GitSCM from {"":hudson.plugins.git.util.DefaultBuildChooser,auto,"authorOrCommitter":false,"branches":{"name":"**"},"buildChooser":{"stapler-class":"hudson.plugins.git.browser.GitoriousWeb"},"clean":false,"disableSubmodules":false,"excludedRegions":"","excludedUsers":"","gitConfigEmail":"jenk...@texttochange.com","gitConfigName":"jenkins","gitTool":"Default","ignoreNotifyCommit":false,"includedRegions":"","localBranch":"","pruneBranches":false,"recursiveSubmodules":false,"reference":"","relativeTargetDir":"","remotePoll":false,"scmName":"","skipTag":true,"userRemoteConfigs":{"name":"","refspec":"","url":"https://github.com/texttochange/vusion-frontend"},"value":"1","wipeOutWorkspace":false}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java: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.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:47)
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:166)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
[JIRA] (JENKINS-14596) Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException
Vassilena Treneva edited a comment on JENKINS-14596 Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException I think it is some kind of problem caused by these new versions. Anyway, the situation for us was resolved when we edited /etc/sysconfig/Jenkins: JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true -XX:MaxPermSize=512M" Nasty but this is the fact This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14596) Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException
Vassilena Treneva commented on JENKINS-14596 Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException I think it is some kind of problem caused by these new versions. Anyway, the situation for us was resolved when we edited /etc/sysconfig/Jenkins: JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true -XX:MaxPermSize=512M" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14708) let user choose blue balls hue
Nicolas De Loof created JENKINS-14708 let user choose blue balls hue Issue Type: Improvement Assignee: asgeirn Components: greenballs Created: 07/Aug/12 12:03 PM Description: Based on http://en.wikipedia.org/wiki/Grue_and_bleen, concept of "blue" is not homogenous, and some may prefer "green" as greenballs plugin provide, but some may prefer some other color. Suggested improvement is to let jenkins admin define the balls color based on a hue selector, and dynamically generate the image file. Implementation notice : the svg for blue ball can be used to generate an image (as jenkins does during build), but let user tweak the gradient colors and generate custom variation for bleu/green, by select a point in http://en.wikipedia.org/wiki/RGB_color_space with only Green + Blue axis (I don't think red would make sense here) Project: Jenkins Priority: Major Reporter: Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14596) Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException
David Voillemin commented on JENKINS-14596 Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException Nice! That's seems OK. I have setted this argument: -Xrs -Xmx1024m -XX:PermSize=512m -XX:MaxPermSize=512m It remains to ensure that the problem has indeed disappeared. Best regards David This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14596) Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException
Vassilena Treneva commented on JENKINS-14596 Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException well, in my opinion there is definitely some kind of problem this is just a workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14709) Replace org.jenkins-ci:trilead-ssh2 with Orion SSH2
jglick updated JENKINS-14709 Replace org.jenkins-ci:trilead-ssh2 with Orion SSH2 Change By: jglick (07/Aug/12 1:25 PM) Issue Type: Bug Task This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14709) Replace org.jenkins-ci:trilead-ssh2 with Orion SSH2
jglick created JENKINS-14709 Replace org.jenkins-ci:trilead-ssh2 with Orion SSH2 Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: cli, core Created: 07/Aug/12 1:24 PM Description: The patches in https://github.com/jenkinsci/trilead-ssh2 seems to have been merged into the trunk of https://sourceforge.net/apps/mediawiki/orion-ssh2/ so we need an Orion 215 release to be published in Maven Central and replace our custom fork. Project: Jenkins Priority: Major Reporter: jglick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14710) net.sf.json.JSONException: JSONObject[cvspassFile] not found when saving main configuration
Max Burdge updated JENKINS-14710 net.sf.json.JSONException: JSONObject[cvspassFile] not found when saving main configuration Change By: Max Burdge (07/Aug/12 2:16 PM) Component/s: cvs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
uri milman created JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cvs Created: 07/Aug/12 3:16 PM Description: When creating a job using a cvs branch, and cvs plugin does the checkout and rlog, but finds nothing. Using the same parameters from the commandline, using linux cvs client, it does see the changes. From the log: cvs rlog -S -d07 Aug 2012 17:47:11 +030007 Aug 2012 18:12:20 +0300 base-iso cvs rlog: Logging base-iso cvs rlog: Logging base-iso/.disk cvs rlog: Logging base-iso/boot but from the commandline: cvs rlog -S -d"07 Aug 2012 17:47:11 +030007 Aug 2012 18:12:20 +0300" base-iso cvs rlog: Logging base-iso RCS file: /opt/cvsroot/base-iso/create_iso.sh,v head: 1.6 branch: locks: strict access list: symbolic names: keyword substitution: kv total revisions: 6; selected revisions: 1 description: revision 1.6 date: 2012/08/07 14:47:55; author: urim; state: Exp; lines: +1 -1 Changelog = cvs rlog: Logging base-iso/.disk cvs rlog: Logging base-iso/boot cvs rlog: Logging base-iso/boot/grub After downgrading to CVS plugin 1.6, the changes list is working, so it seems to be a problem with the cvs library. Project: Jenkins Priority: Major Reporter: uri milman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9264) Create a new job into a view via REST API
Simon Endele commented on JENKINS-9264 Create a new job into a view via REST API Found out how to achieve this: Instead of using /jenkins/createItem (as mentioned in the documentation), one can simply post a new job to /jenkins/view/myViewName/createItem (where myViewName is an existing view). Or in detail: wget --post-file=config.xml --header='Content-type: application/xml; charset=ISO-8859-1' http://.../jenkins/view/myViewName/createItem?name=newJobName Maybe this should be mentioned in the small Remote API Documentation reachable at /jenkins/api/ in every Jenkins installation, as it seems to work perfekt without any side effects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14712) Bulk Builder plugin doesn't show views created within a nested view
tillu sri created JENKINS-14712 Bulk Builder plugin doesnt show views created within a nested view Issue Type: Bug Assignee: Simon Westcott Components: bulk-builder Created: 07/Aug/12 4:12 PM Description: Bulk builder plugin doesn't show the subviews created within the nested view. This is causing me lot of work to start jobs individually. Can you please look into it. Project: Jenkins Priority: Major Reporter: tillu sri This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14713) Cancel permission is granted for users having build permission
drautureau created JENKINS-14713 Cancel permission is granted for users having build permission Issue Type: Bug Assignee: Unassigned Components: core Created: 07/Aug/12 4:29 PM Description: I expected that people need to have the "Cancel" permission to be able to cancel a build. That's right, unless they have the "Build" permission. I would like to be able to give "build" permission to some people without allowing them to abort a build. What do you think of it? Environment: Jenkins 1.465 Project: Jenkins Priority: Major Reporter: drautureau This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13774) Provide option for cloning all branches with Mercurial SCM
jglick commented on JENKINS-13774 Provide option for cloning all branches with Mercurial SCM Dave's reported case sounds a lot like the caching feature built in to the plugin, which would not require a special job or Copy Artifact - you just configure your Hg installation to use caching, and then any job using a given public repo location will automatically share the cache (and slaves do not need to make the remote connection). If you are trying to do something more subtle, such as archiving particular snapshots of the repository, then I guess a freeform build step with hg clone -U would be suitable, but I am not sure what trigger to use; the Mercurial plugin is designed to maintain a checkout of a particular branch and poll for changes in it, which is a quite different use case. You would really want a custom build trigger which just looked for activity of any kind in a given repo. Henrik's case is different and probably suited to Multiple SCMs - place a checkout of each named branch in its own subdirectory of the workspace. Each branch will be polled for changes. That ought to work fine with the current Mercurial plugin unless I am missing something. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14714) Discard normal build parameters
wernight created JENKINS-14714 Discard normal build parameters Issue Type: Bug Assignee: Peter Hayes Components: release Created: 07/Aug/12 5:03 PM Description: For Release builds we have one parameter less. That parameter gets filled via EnvInject. For that two things would be useful: Option to completely discard default parameters and only use those given to the Release build. Make Release define a parameter so that EnvInject and other elements can differentiate release builds from other builds. Project: Jenkins Priority: Major Reporter: wernight This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14467) Server login set by default to PircBotx
charles-erid dessart commented on JENKINS-14467 Server login set by default to PircBotx bump This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14565) Please add support for Cloudbees folder structure
Andreyev Melo commented on JENKINS-14565 Please add support for Cloudbees folder structure Even if all jobs where in the same folder? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14715) Unable to add new Trigger/call builds on other projects build step
Stephane Odul
created JENKINS-14715
Unable to add new Trigger/call builds on other projects build step
Issue Type:
Bug
Assignee:
huybrechts
Components:
parameterized-trigger, parameters
Created:
07/Aug/12 5:51 PM
Description:
This has started happening on our Jenkins instance a few weeks ago. We are running Jenkins 1.476 and Parameterized Trigger 2.15.
When I first try too add a trigger, the UI does not get any options, the second attempt give me one with invalid settings (non blocking should not show the Failure options).
When I try to save I get these exceptions in the master log.
Caused by: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder from {"configs":{"block":true,"buildStepFailureThreshold":"FAILURE","failureThreshold":"FAILURE","projects":"sandbox-sleep1m","unstableThreshold":"UNSTABLE"},"kind":"hudson.plugins.parameterizedtrigger.TriggerBuilder","stapler-class":"hudson.plugins.parameterizedtrigger.TriggerBuilder"}
at hudson.model.Descriptor.newInstance(Descriptor.java:575)
at hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:912)
at hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:899)
at hudson.util.DescribableList.rebuildHetero(DescribableList.java:203)
at hudson.model.Project.submit(Project.java:202)
at hudson.model.Job.doConfigSubmit(Job.java:990)
at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:699)
... 67 more
Existing jobs seems to run as expected, but we cannot update/add configuration that requires this feature.
Project:
Jenkins
Priority:
Major
Reporter:
Stephane Odul
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14716) link to latest Long-Term Support Release is broken on jenkins-ci.org
Clark Archer created JENKINS-14716 link to latest Long-Term Support Release is broken on jenkins-ci.org Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: other Created: 07/Aug/12 6:22 PM Description: The Long-Term Support Release link for downloading the WAR is broken on jenkins-ci.org. The link points to http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war which does not exist. Project: Jenkins Priority: Minor Reporter: Clark Archer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14715) Unable to add new Trigger/call builds on other projects build step
Stephane Odul updated JENKINS-14715 Unable to add new Trigger/call builds on other projects build step Added screenshot showing the unstable behavior when adding the build parameter to a job. Change By: Stephane Odul (07/Aug/12 6:35 PM) Attachment: screenshot-1.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8082) git plugin multi-repo can't work
Prasanna L commented on JENKINS-8082 git plugin multi-repo cant work abayer, The documentation on multiple scm plugins notes that it is tested only with Mercurial and Subversion plugins. Have you used it successfully with git repositories? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14550) Checksum mismatch while updating with Subversion Plugin 1.42
Chris Simmons commented on JENKINS-14550 Checksum mismatch while updating with Subversion Plugin 1.42 I can confirm that v1.39 appears to be the latest build that works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14721) 500 error switching to Pegdown
Charles Johnson created JENKINS-14721 500 error switching to Pegdown Issue Type: Bug Affects Versions: current Assignee: bap Attachments: stacktrace.out Components: pegdown-formatter-plugin Created: 07/Aug/12 11:58 PM Description: Attempting to use Pegdown formatter plugin. At /configure, select "enable security," realm "Jenkins's own user database," with "Project-based Matrix Authorization Strategy." Change Markup Formatter selector to "PegDown," hit save, get 500 error with stacktrace (attached). Jenkins version 1.476, PegDown formatter plugin 1.3. Project: Jenkins Priority: Major Reporter: Charles Johnson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14720) Fast remote polling setting does not save when selected in job config
owenmehegan commented on JENKINS-14720 Fast remote polling setting does not save when selected in job config This might not be a bug... I just read the help Will dig in some more. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14722) Save and Apply on the job config screen appears to do nothing
trejkaz created JENKINS-14722 Save and Apply on the job config screen appears to do nothing Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 08/Aug/12 1:38 AM Description: I'm trying to rename some of my jobs. So I go to the job configuration screen, change the name, scroll to the bottom and hit Save, and nothing happens. Chrome shows a red line in the debug console saying the request was "(canceled)", although it was certainly not canceled by me. Copying request headers or response headers from there seems to show no useful information either: POST http://[fe80::6d02:b73:b100:d2cc]:8080/job/commit-trigger-4.0/configSubmit HTTP/1.1 (newline here) I tried to get around this by disabling _javascript_, which seems to break Jenkins quite severely so I'll raise a separate ticket about that. The actual version this is reported against should be 1.466. I can see that 1.476 is available but "Or Upgrade Automatically" is not working either, so it's hard to upgrade. Funnily enough, the Save button on "Configure System" appears to work fine. Environment: Windows 7 SP1, Google Chrome 21.0.1180.60 Project: Jenkins Priority: Major Reporter: trejkaz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14723) Jenkins blocks editing configuration if JavaScript is disabled
trejkaz created JENKINS-14723 Jenkins blocks editing configuration if _javascript_ is disabled Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 08/Aug/12 1:40 AM Description: While I was trying to work around JENKINS-14722, I tried turning off _javascript_. The result was that the form I was on immediately disabled all controls and never finished loading, making it impossible to use Jenkins. Environment: Windows 7 SP1, Google Chrome 21.0.1180.60 Project: Jenkins Priority: Major Reporter: trejkaz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12051) Latest jenkins running on tomcat prevents me from configuring
Juanal F updated JENKINS-12051 Latest jenkins running on tomcat prevents me from configuring Problem in Jenkins 1.474 Change By: Juanal F (08/Aug/12 2:12 AM) Attachment: jenkins_error.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12051) Latest jenkins running on tomcat prevents me from configuring
Juanal F edited a comment on JENKINS-12051 Latest jenkins running on tomcat prevents me from configuring I've got the same in one of my projects with Jenkins 1.474. Window XP, java 7. It fails in Chrome 21 and IE 9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12051) Latest jenkins running on tomcat prevents me from configuring
Juanal F edited a comment on JENKINS-12051 Latest jenkins running on tomcat prevents me from configuring I've got the same in one of my projects with Jenkins 1.474 on Apache Tomcat/7.0.23. Window XP, java 7. It fails in Chrome 21 and IE 9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14724) set labels,rather than build #,date on x(Horizontal) axis
hiteswar kumar created JENKINS-14724 set labels,rather than build #,date on x(Horizontal) axis Issue Type: Improvement Affects Versions: current Assignee: nidaley Components: plot Created: 08/Aug/12 5:50 AM Description: currently plot plugin does not having capability - . Ability to set labels,rather than build #,date on x(Horizontal) axis. -labels means name of data which get at the job and it can be more than 1 also. Benefit: this feature can help to analyse the performance of build in graph with multiple x axis labels. please let me know if someone working on this feature at plot plugin and soon will be released. if not, Can you please consider this as major enhancement request in plot plugin. Project: Jenkins Priority: Major Reporter: hiteswar 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
