[JIRA] (JENKINS-35906) Exception saving jobs using ClearCase after update to Jenkins Core 2.9 (Our case 14788)
Title: Message Title satish k closed an issue as Done i had made an alternative solution for this.. Jenkins / JENKINS-35906 Exception saving jobs using ClearCase after update to Jenkins Core 2.9 (Our case 14788) Change By: satish k Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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:/
[JIRA] (JENKINS-40889) cannot apply and save base clearcase dynamic views
Title: Message Title satish k created an issue Jenkins / JENKINS-40889 cannot apply and save base clearcase dynamic views Issue Type: Bug Assignee: Praqma Support Attachments: Clearcase posted in JIRA issues.docx Components: clearcase-plugin Created: 2017/Jan/09 12:33 AM Environment: Jenkins 2.19.1; Clear case 8, Base clear case , Dynamic views Labels: jenkins clearcaseplugin Priority: Blocker Reporter: satish k Helllo Team, I'm trying to implement "Pipeline as a code" with "Pipeline script from SCM" Base Clear case; Dynamic views. I'm wondering when save or apply worked for free style project with same configurations didn't work for "pipeline script from SCM" PFA for more information on configuration and error screen shots.
[JIRA] (JENKINS-35985) no @DataBoundConstructor on any constructor of class com.amazonaws.codepipeline.jenkinsplugin.AWSCodePipelineSCM
Title: Message Title desh hari commented on JENKINS-35985 Re: no @DataBoundConstructor on any constructor of class com.amazonaws.codepipeline.jenkinsplugin.AWSCodePipelineSCM Hello Team, Still this is a Bug or is its something wrong with our config steps as I'm also getting same issue while using Base Clear Case with dynamic views plugin config steps with Jenkinsfile [Pipeline as code] leading to : When saving the job we get the following error: Caused by: java.lang.IllegalArgumentException: Caused by: java.lang.IllegalArgumentException: Failed to instantiate class hudson.scm.SCM from View Tag: Core_view View path: Core_view configSpec: element * CHECKEDOUT element * ...\Core_view_test\LATEST mkbranch Core_view_test element * /main/LATEST LoadRules: load M:\Core_view\ changeset: current branch Branches: Core_view_test use dynmic view--> view root: M:\ [advanced options] Di not reset config spec : checked Script path: Jenkinsfile [this is placed in Clearcase with simple echo command] comments or resolutions are appreciated, thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36179) Not able to save job config if used aws-code pipeline plugin
Title: Message Title desh hari commented on JENKINS-36179 Re: Not able to save job config if used aws-code pipeline plugin Hello Team, Still this is a Bug or is its something wrong with our config steps as I'm also getting same issue while using Base Clear Case with dynamic views plugin config steps with Jenkinsfile [Pipeline as code] leading to : When saving the job we get the following error: Caused by: java.lang.IllegalArgumentException: Caused by: java.lang.IllegalArgumentException: Failed to instantiate class hudson.scm.SCM from View Tag: Core_view View path: Core_view configSpec: element * CHECKEDOUT element * ...\Core_view_test\LATEST mkbranch Core_view_test element * /main/LATEST LoadRules: load M:\Core_view\ changeset: current branch Branches: Core_view_test use dynmic view--> view root: M:\ [advanced options] Di not reset config spec : checked Script path: Jenkinsfile [this is placed in Clearcase with simple echo command] comments or resolutions are appreciated, thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-27409) adding base clearcase on multiple scm plugin causes exceptions even for basic configuration
Title: Message Title desh hari commented on JENKINS-27409 Re: adding base clearcase on multiple scm plugin causes exceptions even for basic configuration Hello Team, Still this is a Bug or is its something wrong with our config steps as I'm also getting same issue while using Base Clear Case with dynamic views plugin config steps with Jenkinsfile [Pipeline as code] leading to : When saving the job we get the following error: Caused by: java.lang.IllegalArgumentException: Caused by: java.lang.IllegalArgumentException: Failed to instantiate class hudson.scm.SCM from View Tag: Core_view View path: Core_view configSpec: element * CHECKEDOUT element * ...\Core_view_test\LATEST mkbranch Core_view_test element * /main/LATEST LoadRules: load M:\Core_view\ changeset: current branch Branches: Core_view_test use dynmic view--> view root: M:\ [advanced options] Di not reset config spec : checked Script path: Jenkinsfile [this is placed in Clearcase with simple echo command] comments or resolutions are appreciated, thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36192) Can't save project settings due to LoadRules issue (Our case 14808)
Title: Message Title desh hari commented on JENKINS-36192 Re: Can't save project settings due to LoadRules issue (Our case 14808) Hello Team, Still this is a Bug or is its something wrong with our config steps as I'm also getting same issue while using Base Clear Case with dynamic views plugin config steps with Jenkinsfile [Pipeline as code] leading to : When saving the job we get the following error: Caused by: java.lang.IllegalArgumentException: Caused by: java.lang.IllegalArgumentException: Failed to instantiate class hudson.scm.SCM from View Tag: Core_view View path: Core_view configSpec: element * CHECKEDOUT element * ...\Core_view_test\LATEST mkbranch Core_view_test element * /main/LATEST LoadRules: load M:\Core_view\ changeset: current branch Branches: Core_view_test use dynmic view--> view root: M:\ [advanced options] Di not reset config spec : checked Script path: Jenkinsfile [this is placed in Clearcase with simple echo command] comments or resolutions are appreciated, thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32551) Pipeline script from SCM: ClearCase not available
Title: Message Title desh hari commented on JENKINS-32551 Re: Pipeline script from SCM: ClearCase not available Hello Team, Still this is a Bug or is its something wrong with our config steps as I'm also getting same issue while using Base Clear Case with dynamic views plugin config steps with Jenkinsfile [Pipeline as code] leading to : When saving the job we get the following error: Caused by: java.lang.IllegalArgumentException: Caused by: java.lang.IllegalArgumentException: Failed to instantiate class hudson.scm.SCM from View Tag: Core_view View path: Core_view configSpec: element * CHECKEDOUT element * ...\Core_view_test\LATEST mkbranch Core_view_test element * /main/LATEST LoadRules: load M:\Core_view\ changeset: current branch Branches: Core_view_test use dynmic view--> view root: M:\ [advanced options] Di not reset config spec : checked Script path: Jenkinsfile [this is placed in Clearcase with simple echo command] comments or resolutions are appreciated, thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32551) Pipeline script from SCM: ClearCase not available
Title: Message Title desh hari started work on JENKINS-32551 Change By: desh hari Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-35906) Exception saving jobs using ClearCase after update to Jenkins Core 2.9 (Our case 14788)
Title: Message Title satish k started work on JENKINS-35906 Change By: satish k Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-35906) Exception saving jobs using ClearCase after update to Jenkins Core 2.9 (Our case 14788)
Title: Message Title satish k reopened an issue hello Team I was getting the same issue and Im in Jenkins 2.19.1 version do I have to downgrade it to 2.8? to resovle this issue. I dont think so as Jenkins might had fixed in this version what could be other reasons for this issue in My current version 2.19.1 Jenkins ? It would be a great help as this piece of Load rules and config specs are working in conventional Jenkins plugins where as its not working with Jenkins Pipeline blue Ocean way and leading with the same below :RuntimeException: Failed to instantiate class. Your reply is well appreciated. Haritha Jenkins / JENKINS-35906 Exception saving jobs using ClearCase after update to Jenkins Core 2.9 (Our case 14788) Change By: satish k Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39729) build issue when file name as spaces
Title: Message Title desh hari assigned an issue to desh hari Jenkins / JENKINS-39729 build issue when file name as spaces Change By: desh hari Assignee: Kohsuke Kawaguchi desh hari Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39729) build issue when file name as spaces
Title: Message Title desh hari created an issue Jenkins / JENKINS-39729 build issue when file name as spaces Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: _unsorted, sonar Created: 2016/Nov/14 8:39 PM Environment: sonarqube plugin Labels: jenkins Priority: Blocker Reporter: desh hari I created a job where sonar pulls the required jobs from jenkins workspace, but couple of files has spaces in it and its considering as "MSBUILD : error MSB1008: Only one project can be specified." I realized that i need to write a script or update jenkins to take files from workspace irrespective of spaces or special characters, that files should undergo sonar. Kindly suggest how this can be done. INFO: Start | Analysis | C:/Users/tcepoc/.jenkins/jobs/ClearcaseSonar/workspace/eng_kpi.udf_ProjectX_P4_Report_Rev_12 12 11.UserDefinedFunction.sql INFO: Location | Output Report | C:\Users\tcepoc\.jenkins\jobs\ClearcaseSonar\workspace\.sonar\sqlcodeguard_report.xml INFO: Start | Execution | C:\sonarqube-5.6\extensions\plugins\TechCognia-Tsql-Plugin-1.5.1\TechCognia-Tsql-Plugin-1.5.1\Attachments\TechCognia\SqlCodeGuard.msbuild INFO: Executing command: C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe "C:\sonarqube-5.6\extensions\plugins\TechCognia-Tsql-Plugin-1.5.1\TechCognia-Tsql-Plugin-1.5.1\Attachments\TechCognia\SqlCodeGuard.msbuild" /p:SourcePath="C:/Users/tcepoc/.jenkins/jobs/ClearcaseSonar/workspace/eng_kpi.udf_ProjectX_P4_Report_Rev_12 12 11.UserDefinedFunction.sql";Rules="PE007;ST004;PE008;ST003;PE009;ST006;ST005;ST008;ST007;ST009;PE001;PE002;PE003;PE004;PE005;ST
