[JIRA] [integrity-plugin] (JENKINS-21968) A SQL Exception was caught! Schema 'DBUSER' does not exist
Cletus DSouza resolved JENKINS-21968 as Duplicate A SQL Exception was caught! Schema DBUSER does not exist This is a duplicate of JENKINS-14675 Change By: Cletus DSouza (04/Sep/14 5:58 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/d/optout.
[JIRA] [integrity-plugin] (JENKINS-21968) A SQL Exception was caught! Schema 'DBUSER' does not exist
Cletus DSouza commented on JENKINS-21968 A SQL Exception was caught! Schema DBUSER does not exist Did you set a 'Configuration Name' for each project here? 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] [integrity-plugin] (JENKINS-21968) A SQL Exception was caught! Schema 'DBUSER' does not exist
Grigoriy Milman commented on JENKINS-21968 A SQL Exception was caught! Schema DBUSER does not exist Yes. This exception is intermittent and happened with probability near 20% By the way, thank you for your explanation related to the meaning of Configuration Name. I have setup the Configuration Name for each build job based on the build job name. By the way, some times no we see the Failed to create APISession exception in the similar way: EnvInject - Variables injected successfully. EnvInject - Injecting contributions. Building in workspace ... EnvInject - Unset unresolved 'USERNAME' variable. Change Log: http://.../job/NGMP.Validation.Tachy/104/changes Build Log: http:///job/NGMP.Validation.Tachy/104/console Preparing to execute si projectinfo for /.../project.pj Preparing to execute si viewproject for #/.. Checkout directory is .. A clean copy is requested; deleting contents of .. Populating clean workspace... java.lang.Exception: Failed to create APISession! Retrying after 10 seconds Change Log: http://.../job/NGMP.Validation.Tachy/104/changes Build Log: http:///job/NGMP.Validation.Tachy/104/console Preparing to execute si projectinfo for //project.pj Preparing to execute si viewproject for #/.. Checkout directory is A clean copy is requested; deleting contents of Populating clean workspace... java.lang.Exception: Failed to create APISession! Retrying after 10 seconds Change Log: http://./job/NGMP.Validation.Tachy/104/changes Build Log: http://../job/NGMP.Validation.Tachy/104/console Preparing to execute si projectinfo for /.../project.pj Preparing to execute si viewproject for #/. Checkout directory is ... A clean copy is requested; deleting contents of . Populating clean workspace... java.lang.Exception: Failed to create APISession! Retrying after 10 seconds Change Log: http://../job/NGMP.Validation.Tachy/104/changes Build Log: http://.../job/NGMP.Validation.Tachy/104/console Preparing to execute si projectinfo for /.../project.pj Preparing to execute si viewproject for #/... Checkout directory is .. A clean copy is requested; deleting contents of .. A clean copy is requested; deleting contents of . Populating clean workspace... java.lang.Exception: Failed to create APISession! 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] [integrity-plugin] (JENKINS-21968) A SQL Exception was caught! Schema 'DBUSER' does not exist
Grigoriy Milman created JENKINS-21968 A SQL Exception was caught! Schema DBUSER does not exist Issue Type: Bug Assignee: Cletus DSouza Components: integrity-plugin Created: 26/Feb/14 10:16 PM Description: Jenkins ver. 1.552, PTC plugin ver. 1.23 With better logging , this issue became visible very often! About each other build now reporting it! EnvInject - Variables injected successfully. EnvInject - Injecting contributions. Building in workspace . EnvInject - Unset unresolved 'USERNAME' variable. Running Prebuild steps Run condition File exists enabling prebuild for step Build a Visual Studio project or solution using MSBuild File exists check if file exists SequencerComponents.sln Run condition File exists preventing perform for step Build a Visual Studio project or solution using MSBuild Success build fororg.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder@1100245 Change Log: http://../job/NGMP.Direct.Components.Sequencer/632/changes Build Log: http://../job/NGMP.Direct.Components.Sequencer/632/console Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Components/Sequencer/Sequencer.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Components/Components.pj#s=Sequencer/Sequencer.pj A SQL Exception was caught! Schema 'DBUSER' does not exist Retrying after 10 seconds Change Log: http:///job/NGMP.Direct.Components.Sequencer/632/changes Build Log: http:///job/NGMP.Direct.Components.Sequencer/632/console Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Components/Sequencer/Sequencer.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Components/Components.pj#s=Sequencer/Sequencer.pj A SQL Exception was caught! Schema 'DBUSER' does not exist Retrying after 10 seconds Change Log: http:///job/NGMP.Direct.Components.Sequencer/632/changes Build Log: http:///job/NGMP.Direct.Components.Sequencer/632/console Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Components/Sequencer/Sequencer.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Components/Components.pj#s=Sequencer/Sequencer.pj A SQL Exception was caught! Schema 'DBUSER' does not exist Retrying after 10 seconds Change Log: http://./job/NGMP.Direct.Components.Sequencer/632/changes Build Log: http://../job/NGMP.Direct.Components.Sequencer/632/console Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Components/Sequencer/Sequencer.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Components/Components.pj#s=Sequencer/Sequencer.pj A SQL Exception was caught! Schema 'DBUSER' does not exist Archiving artifacts Publishing Javadoc Recording fingerprints Sending e-mails to: .. Finished: FAILURE Project: Jenkins Priority: Major Reporter: Grigoriy 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 -- You received this message because you are subscribed to the Google Groups
