[JIRA] [core] (JENKINS-27219) Job generator config loses "Custom Workspace" everytime the configuration is edited
Karsten Günther updated JENKINS-27219 Job generator config loses "Custom Workspace" everytime the configuration is edited Change By: Karsten Günther (03/Mar/15 1:25 PM) Summary: Job generator config loses " Costom Custom Workspace" everytime the configuration is edited 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/d/optout.
[JIRA] [core] (JENKINS-27219) Job generator config loses "Costom Workspace" everytime the configuration is edited
Karsten Günther created JENKINS-27219 Job generator config loses "Costom Workspace" everytime the configuration is edited Issue Type: Bug Assignee: Unassigned Components: core, jobgenerator-plugin Created: 03/Mar/15 1:25 PM Description: I updated my Jenkins LTS installation from version 1.580.3 (LTS) to 1.596.1 (LTS). With both version I used/use the Job Generator plugin 1.22. After the update I am facing the problem, that everytime I configure a Job Generator via the web interface, the Job Generator loses its "Custom Workspace" setting. This bug is fully reproducible with 1.596.1: Just create a Job Generator and configure a Custom Workspace for it. When you save the configuration, the config.xml has the correct element and value. When you configure it again, the value is not loaded into the configuration formular. When hitting "Save", the value disappears from the config.xml. It is not reproducible with 1.580.3. For me this is a real showstopper as I cannot edit my Job Generators without copying the value of "Custom Workspace" from the config.xml into the formular everytime (my whole project setup depends on it). This bug may be related to https://issues.jenkins-ci.org/browse/JENKINS-23390. Environment: Jenkins LTS 1.596.1, Job Generator 1.22, Windows 2008 Server Project: Jenkins Priority: Blocker 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 -- 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/d/optout.
[JIRA] (JENKINS-16713) Mask Passwords config does not work in Hudson 3.0.0
Karsten Günther created JENKINS-16713 Mask Passwords config does not work in Hudson 3.0.0 Issue Type: Bug Affects Versions: current Assignee: Daniel Petisme Components: mask-passwords Created: 08/Feb/13 3:39 PM Description: I am not sure, whether this is the right place for reporting bugs related to Hudson. But the plugin is hosted here, so I report here. Hope, that does not offend anyone. In the global Hudson config no name/value pairs are accepted for masked environment variables. Log file has the following entry: Feb 08, 2013 3:40:02 PM com.michelin.cio.hudson.plugins.maskpasswords.MaskPasswordsConfig load WARNING: No configuration found for Mask Passwords plugin Feb 08, 2013 3:43:04 PM com.michelin.cio.hudson.plugins.maskpasswords.MaskPasswordsBuildWrapper$DescriptorImpl configure SEVERE: Failed to save Mask Passwords plugin configuration net.sf.json.JSONException: JSONObject["maskedParamDefs"] is not a JSONArray. at net.sf.json.JSONObject.getJSONArray(JSONObject.java:2038) at com.michelin.cio.hudson.plugins.maskpasswords.MaskPasswordsBuildWrapper$DescriptorImpl.configure(MaskPasswordsBuildWrapper.java:226) at hudson.model.Hudson.configureDescriptor(Hudson.java:2525) at hudson.model.Hudson.doConfigSubmit(Hudson.java:2480) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:274) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:141) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:80) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:95) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:45) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:565) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:650) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:481) at org.kohsuke.stapler.Stapler.service(Stapler.java:152) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:648) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1336) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:86) 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:89) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:89) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:78) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1307) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:81) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:73) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1307) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:70) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1307) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:453) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:534) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.je
[JIRA] (JENKINS-16275) PTC Integrity Plugin throws exception in case of strange revision comments
Karsten Günther
updated JENKINS-16275
PTC Integrity Plugin throws exception in case of strange revision comments
Change By:
Karsten Günther
(08/Jan/13 8:30 AM)
Description:
Due to some unknown reason (I think it is a simple copy and paste) the check-in comments of me and my colleagues contain symbols the integrity plugin does not like:{code:title=changelog.xml}some checkin comment]]> some file path SomeUser 1.345 Nov 06, 2012 6:23:44 PM ... {code}
This results in the following exception:{code}?[0mhudson.util.IOException2: Failed to parse j:\Jenkins\jobs\xxx\builds\2012-11-07_02-05-12\changelog.xmlat hudson.scm.IntegrityChangeLogParser.parse(IntegrityChangeLogParser.java:73)at hudson.scm.IntegrityChangeLogParser.parse(IntegrityChangeLogParser.java:20)at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:925)at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:899)at hudson.model.View$People.getUserInfo(View.java:682)at hudson.model.View$People.(View.java:672)at hudson.model.View$AsynchPeople.getApi(View.java:837)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)at java.lang.reflect.Method.invoke(Unknown Source)at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)at org.apache.commons.jexl.parser.ASTNENode.value(ASTNENode.java:55)at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54)at org.apache.commons.jexl.parser.ASTExpressionExpression.value(ASTExpressionExpression.java:56)at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsBoolean(ExpressionSupport.java:71)at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:97)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:107)at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)at o
[JIRA] (JENKINS-16275) PTC Integrity Plugin throws exception in case of strange revision comments
Karsten Günther created JENKINS-16275 PTC Integrity Plugin throws exception in case of strange revision comments Issue Type: Bug Affects Versions: current Assignee: Cletus D'Souza Components: integrity-plugin Created: 08/Jan/13 8:27 AM Description: Due to some unknown reason (I think it is a simple copy and paste) the check-in comments of me and my colleagues contain symbols the integrity plugin does not like: changelog.xml some checkin comment ]]> "update"> some file path SomeUser 1.345 Nov 06, 2012 6:23:44 PM ... "update"> Environment: Windows 7 Enterprise 64bit, Jenkins 1.497 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-14594) MKS polling becomes unresponsive
Karsten Günther commented on JENKINS-14594 MKS polling becomes unresponsive @Cletus: I have the same polling problem from time to time. I would like to provide further information but I am not sure how to get it. My Jenkins machine is not writing any log files (Don't know why) and the system log is not old enough. Can you give me a hint or a link? 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-15316) Jenkins tries to create symbolic links on Windows system
Karsten Günther created JENKINS-15316 Jenkins tries to create symbolic links on Windows system Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: build-flow, build-pipeline Created: 26/Sep/12 10:45 AM Description: Not sure if the assigned components are correct. Please correct them if necessary. After update to jenkins 1.483 I get an error message at the beginning of each build: Build wurde durch eine SCM-Änderung ausgelöst. ln 2012-09-26_12-23-54 f:\Jenkins\jobs\xxx\builds\1 failed java.nio.file.FileSystemException: f:\Jenkins\jobs\xxx\builds\1: Dem Client fehlt ein erforderliches Recht. at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.createSymbolicLink(Unknown Source) at java.nio.file.Files.createSymbolicLink(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.Util.createSymlinkJava7(Util.java:1065) at hudson.Util.createSymlink(Util.java:1009) at hudson.model.Run.execute(Run.java:1500) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Environment: Windows 7 64bit Project: Jenkins Labels: build scm 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-14704) PTC Integrity Plugin throws/catches SQL Exception in case of too long revision number
Karsten Günther commented on JENKINS-14704 PTC Integrity Plugin throws/catches SQL Exception in case of too long revision number YMMD! Works great for me. Great community! 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 commented on JENKINS-14705 Jenkins' built-in Variables should be useable in Integrity Plugin's Configuration Fields Maybe my description was a little bit misleading, I do not want to change the JOB_NAME after the job was created. Nevertheless I think it is a good idea to use Jenkins' built-in variables in configuration fields wherever it is possible. My major work rule: DRY (Don't Repeat Yourself) 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 commented on JENKINS-14703 PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin First: Thanks for your fast responses! Second: I updated the description with Integrity debug output. It is copied from command line as Jenkins is not creating log files anymore. Don't know why, maybe because I start it manually as a logged in user (I had some problems with Windows service in the past). Can someone tell me how to create the log files? Piping in the command line? Thanks, Karsten 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
(13/Aug/12 2:01 PM)
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:{quote}Started by an SCM changeBuilding in workspace d:\Jenkins\jobs\xxx\workspaceChange Log: http://xxxjenkinsxxx/job/xxx/38/changesBuild Log: http://xxxjenkinsxxx/job/xxx/38/consolePreparing to execute si projectinfo for #p=d:/mks/archives/src/xxx.pj#d=xxxBALPreparing to execute si viewproject for #p=d:/mks/archives/src/xxx.pj#d=xxxBAL{color:red}A SQL Exception was caught!{color}Failed to create database 'd:/Jenkins/jobs/xxx/builds/2012-08-06_11-02-18/IntegritySCM', see the next exception for details.Archiving artifactsSkipping Cobertura coverage report as build was not UNSTABLE or better ...Recording test resultsFinished: FAILURE{quote}
Here the requested debug output:{quote}Aug 13, 2012 3:56:09 PM [DEBUG] IntegritySCM - Start execution of checkout() routine...!Aug 13, 2012 3:56:09 PM [DEBUG] IntegritySCM - Creating Integrity API Session...Aug 13, 2012 3:56:09 PM [DEBUG] IntegritySCM - api ping --user=xxx --port=xxx --hostname=xxx -- returned exit code 0Aug 13, 2012 3:56:09 PM [DEBUG] IntegritySCM - Successfully established connection xxx@xxx:xxxAug 13, 2012 3:56:09 PM [DEBUG] IntegritySCM - Preparing to execute si projectinfo for #p=d:/mks/archives/src/xxx.pj#d=xxAug 13, 2012 3:56:10 PM [DEBUG] IntegritySCM - si projectinfo --user=xxx --port=xxx --hostname=xxx --project=#p=d:/mks/archives/src/xxx.pj#d=xxx -- returned exit code 0Aug 13, 2012 3:56:10 PM [DEBUG] IntegritySCM - si projectinfo --user=xxx --port=xxx --hostname=xxx --project=#p=d:/mks/archives/src/xxx.pj#d=xx -- returned 0Aug 13, 2012 3:56:10 PM [DEBUG] IntegritySCM - Preparing to execute si viewproject for #p=d:/mks/archives/src/xxx.pj#d=xxAug 13, 2012 3:56:10 PM [DEBUG] IntegritySCM - Executed si viewproject --user=xxx --port=7001 --hostname=xxx --recurse --project=#p=d:/mks/archives/src/xxx.pj#d=xx --fields=name,context,cpid,memberrev,membertimestamp,memberdescription -- with interimAug 13, 2012 3:56:10 PM [DEBUG] IntegritySCM - Attempting to open connection to database: d:\Jenkins\jobs\xxx\builds\2012-08-13_15-56-09\IntegritySCMAug 13, 2012 3:56:10 PM [INFO] IntegritySCM - SQL Exception caught...Aug 13, 2012 3:56:10 PM [INFO] IntegritySCM - java.sql.SQLException: Failed to create database 'd:/Jenkins/jobs/xxx/builds/2012-08-13_15-56-09/IntegritySCM', see the next exception for details.Aug 13, 2012 3:56:10 PM [DEBUG] IntegritySCM - Attempting to shut down database: d:\Jenkins\jobs\xxx\builds\2012-08-13_15-56-09\IntegritySCMAug 13, 2012 3:56:10 PM [INFO] IntegritySCM - Failed to shutdown database connection!Aug 13, 2012 3:56:10 PM [INFO] IntegritySCM - Database 'd:/Jenkins/jobs/xxx/builds/2012-08-13_15-56-09/IntegritySCM' not found.Aug 13, 2012 3:56:10 PM [INFO] IntegritySCM - java.sql.SQLException: Database 'd:/Jenkins/jobs/xxx/builds/2012-08-13_15-56-09/IntegritySCM' not found.?[33mAug 13, 2012 3:56:10 PM org.apache.commons.httpclient.HttpMethodBase readResponseBodyWARNING: Unsupported transfer encoding:?[0mAug 13, 2012 3:56:10 PM org.apache.commons.httpclient.HttpMethodBase readResponseBodyINFO: Response content is not chunk-encodedAug 13, 2012 3:56:10 PM [DEBUG] IntegritySCM - Successfully disconnected connection xxx@xxx:7001{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-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 D'Souza 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-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 Plugin's Configuration Fields
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Cletus D'Souza
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-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 D'Souza 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-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:
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:{
{
quote}
Started by an SCM change
}}
{{
Building in workspace d:\Jenkins\jobs\xxx\workspace
}}
{{
Change Log: http://xxxjenkinsxxx/job/xxx/38/changes
}}
{{
Build Log: http://xxxjenkinsxxx/job/xxx/38/console
}}
{{
Preparing to execute si projectinfo for #p=d:/mks/archives/src/xxx.pj#d=xxxBAL
}}
{{
Preparing to execute si viewproject for #p=d:/mks/archives/src/xxx.pj#d=xxxBAL
}}
{
{{
color:red}A SQL Exception was caught!{color}
}}
{{
Failed to create database 'd:/Jenkins/jobs/xxx/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
}}
{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-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:
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\xxx\workspace}}{{Change Log: http://xxxjenkinsxxx/job/xxx/38/changes}}{{Build Log: http://xxxjenkinsxxx/job/xxx/38/console}}{{Preparing to execute si projectinfo for #p=d:/mks/archives/src/xxx.pj#d=xxxBAL}}{{Preparing to execute si viewproject for #p=d:/mks/archives/src/xxx.pj#d=xxxBAL}}{{{color:red}A SQL Exception was caught!{color}}}{{Failed to create database 'd:/Jenkins/jobs/xxx/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}}
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:
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:{{
monospaced}}
Started by an SCM change
}}
{{
Building in workspace d:\Jenkins\jobs\xxx\workspace
}}
{{
Change Log: http://xxxjenkinsxxx/job/xxx/38/changes
}}
{{
Build Log: http://xxxjenkinsxxx/job/xxx/38/console
}}
{{
Preparing to execute si projectinfo for #p=d:/mks/archives/src/xxx.pj#d=xxxBAL
}}
{{
Preparing to execute si viewproject for #p=d:/mks/archives/src/xxx.pj#d=xxxBAL
}}
{
{{
color:red}A SQL Exception was caught!{color}
}}
{{
Failed to create database 'd:/Jenkins/jobs/xxx/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
{{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:26 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:{{
monospaced}}
Started by an SCM changeBuilding in workspace d:\Jenkins\jobs\
CT_ZT6BAL
xxx
\workspaceChange Log: http://
frl1dtwg.auto.contiwan.com
xxxjenkinsxxx
/job/
CT_ZT6BAL
xxx
/38/changesBuild Log: http://
frl1dtwg.auto.contiwan.com
xxxjenkinsxxx
/job/
CT_ZT6BAL
xxx
/38/consolePreparing to execute si projectinfo for #p=d:/mks/archives/src/
CT_ZT6
xxx
.pj#d=
ZT6BAL
xxxBAL
Preparing to execute si viewproject for #p=d:/mks/archives/src/
CT_ZT6
xxx
.pj#d=
ZT6BAL
xxxBAL
{color:red}A SQL Exception was caught!{color}Failed to create database 'd:/Jenkins/jobs/
CT_ZT6BAL
xxx
/builds/2012-08-06_11-02-18/IntegritySCM', see the next exception for details.Archiving artifactsSkipping Cobertura coverage report as build was not UNSTABLE or better ...Recording test resultsFinished: 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
created JENKINS-14703
PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Issue Type:
Bug
Affects Versions:
current
Assignee:
Cletus D'Souza
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
