[JIRA] (JENKINS-58914) plugin does not show correctly result of code metrics generated by Visual Studio 2019
Title: Message Title Grigoriy Milman created an issue Jenkins / JENKINS-58914 plugin does not show correctly result of code metrics generated by Visual Studio 2019 Issue Type: Bug Assignee: Unassigned Components: vs-code-metrics-plugin Created: 2019-08-13 21:01 Priority: Major Reporter: Grigoriy Milman Visual Studio 2019 generates code metrics result file as described here: https://docs.microsoft.com/en-us/visualstudio/code-quality/how-to-generate-code-metrics-data?view=vs-2019 . Unfortunately this plugin shows empty results for xml file containing metrics results generated by the roslyn compilers, new way how to calculate code metrics in Visual Studio 2019! Add Comment
[JIRA] (JENKINS-41054) PTC plugin failed to timeout
Title: Message Title Grigoriy Milman commented on JENKINS-41054 Re: PTC plugin failed to timeout Some clarifications. After upgrade 1. When all old jobs are re-saved with new "Timeout parameter" and no new job is created, all of them works. 2. When a new build job is created based on the re-saved old one, all build jobs started to failed "si" command, including just created and and re-saved ones. 3. When a new build job is created from scratch, all old re-saved build jobs started to failed "si" command, but brand new build job works. 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-41195) Managed script visualisation/uusage
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-41195 Managed script visualisation/uusage Change By: Grigoriy Milman Summary: Managed script visualisation /uusage Component/s: config-file-provider-plugin Jenkins was upgraded from 1.644 TO 2.40Managed Scripts plugin was upgraded to 1.3 Config File Provider Plugin 2.15.4 During job config creation the following was found: Two Windows batch scripts have been set up for execution during Build step (see attached [^ManagedPluginIssue.PNG]) * first named "Prepare Target only";* second named "Release note in Target"1. The "view selected script" became visible only for the first script.2. When "view selected script" is clicked for the first script, it shows the second script (see attached [^ManagedPluginIssue.PNG]) ! 3. Required arguments are not visible as before !!! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41195) Managed script visualisation/usage
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-41195 Managed script visualisation/usage Change By: Grigoriy Milman Summary: Managed script visualisation/ uusage usage 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-41054) PTC plugin failed to timeout
Title: Message Title
Grigoriy Milman edited a comment on JENKINS-41054
Re: PTC plugin failed to timeout
1. We can't recreate all jobs because in this case the jobs history will be lost.2. Something new: It looks like after creation of the new build job based on the one which already exit does not work any more.Both jobs original and new fail "si" step:Original job related log:{quote}Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults/project.pjPreparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Tools/Tools.pj#BuildProcess/JenkinsMSEI/GetBuildResultsCheckout directory is D:\Jenkins_ROOT\NGMP.DIRECT.Sandbox\SWProduction\Tools\BuildProcess\JenkinsMSEI\GetBuildResultsA clean copy is requested; deleting contents of D:\Jenkins_ROOT\NGMP.DIRECT.Sandbox\SWProduction\Tools\BuildProcess\JenkinsMSEI\GetBuildResultsPopulating clean workspace...A Timeout Exception was caught. Failed to checkout contents of file!nullERROR: Failed to synchronize workspace!{quote} New build job related log entry:{quote}Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults4.6/project.pjPreparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Tools/Tools.pj#BuildProcess/JenkinsMSEI/GetBuildResults4.6A SQL Exception was caught!Table/View 'SCM_6A71D9B4_FDA4_41C2_9E2E_B2B64C882F9E' does not exist.ERROR: Caught Derby SQLException!Retrying after 10 seconds{quote}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41054) PTC plugin failed to timeout
Title: Message Title Grigoriy Milman commented on JENKINS-41054 Re: PTC plugin failed to timeout 1. We can't recreate all jobs because in this case the jobs history will be lost. 2. Something new: It looks like after creation of the new build job based on the one which already exit does not work any more. Both jobs original and new fail "si" step: Original job related log: Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults/project.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Tools/Tools.pj#BuildProcess/JenkinsMSEI/GetBuildResults Checkout directory is D:\Jenkins_ROOT\NGMP.DIRECT.Sandbox\SWProduction\Tools\BuildProcess\JenkinsMSEI\GetBuildResults A clean copy is requested; deleting contents of D:\Jenkins_ROOT\NGMP.DIRECT.Sandbox\SWProduction\Tools\BuildProcess\JenkinsMSEI\GetBuildResults Populating clean workspace... A Timeout Exception was caught. Failed to checkout contents of file! null ERROR: Failed to synchronize workspace! New build job related log entry: Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults4.6/project.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Tools/Tools.pj#BuildProcess/JenkinsMSEI/GetBuildResults4.6 A SQL Exception was caught! Table/View 'SCM_6A71D9B4_FDA4_41C2_9E2E_B2B64C882F9E' does not exist. ERROR: Caught Derby SQLException! Retrying after 10 seconds Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41195) Managed script visualisation
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-41195 Managed script visualisation Change By: Grigoriy Milman Jenkins was upgraded from 1.644 TO 2.40Managed Scripts plugin was upgraded to 1.3During job config creation the following was found: Two Windows batch scripts have been set up to for execution during Build step (see attached [^ManagedPluginIssue.PNG]) * first named "Prepare Target only";* second named "Release note in Target"1. The "view selected script" became visible only for the first script.2. When "view selected script" is clicked it shows the second script (see attached [^ManagedPluginIssue.PNG]) ! 3. Required arguments are not visible as before 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,
[JIRA] (JENKINS-41195) Managed script visualisation
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-41195 Managed script visualisation Change By: Grigoriy Milman Summary:
[JIRA] (JENKINS-41195)
Title: Message Title Grigoriy Milman created an issue Jenkins / JENKINS-41195 Issue Type: Bug Assignee: Dominik Bartholdi Attachments: ManagedPluginIssue.PNG Components: managed-scripts-plugin Created: 2017/Jan/19 1:31 AM Environment: Windows, Firefox as browser; Jenkins 2.40 Config File Provider Plugin 2.15.4 Managed Scripts 1.3 Priority: Major Reporter: Grigoriy Milman Jenkins was upgraded from 1.644 TO 2.40 Managed Scripts plugin was upgraded to 1.3 During job config creation the following was found: Two Windows batch scripts have been set up to during Build step (see attached ManagedPluginIssue.PNG) first named "Prepare Target only"; second named "Release note in Target" 1. The "view selected script" became visible only for the first script. 2. When "view selected script" is clicked it shows the second script (see attached ManagedPluginIssue.PNG) ! 3. Required arguments not visible as before
[JIRA] (JENKINS-32903) Build-Blocker-Plugin does not block
Title: Message Title Grigoriy Milman commented on JENKINS-32903 Re: Build-Blocker-Plugin does not block The same problem on Jenkins 2.40. The job A is configured to be blocked on upstream and downstream build jobs. Another job B, upstream to job A appeared in the queue. Job A is started without wait for start and end of the job B! 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-41054) PTC plugin failed to timeout
Title: Message Title
Grigoriy Milman edited a comment on JENKINS-41054
Re: PTC plugin failed to timeout
It first I did re-saved not all of the build jobs but just some of them with new PTC timeout settings.At that moment I have seen the issue I have reported for one of the re-saved job.Now I have all of the build jobs re-saved with new PTC timeout settings. I can't say for sure that I have seen failure to timeout. what I have found today that one build job did perform "si" resync successfully but at checkpoint failed:{quote}Preparing to execute si checkpoint for #/repository/Operations#ESS/Application Software/SWCode/Scanner/pcProxFATAL: Failed to checkpoint /repository/Operations/ESS/Application Software/SWCode/Scanner/pcProx/project.pj: MKS125210: The project history is being changed by another user.Build step 'Integrity - CM Checkpoint' marked build as failure{quote}By the way, for PTC plugin upgrade 2.0.2 is it enough to re-save build job config with new PTC timeout parameter or build job should be re-created from scratch? Can it be recreated based on the original one of absolutely brand new?If re-created, that means job history will be lost... May be it it is possible just to add something to job config manually?The attached file [^config.xml] is config for some of ours build job re-saved after upgrade.
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
[JIRA] (JENKINS-41054) PTC plugin failed to timeout
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-41054 PTC plugin failed to timeout Change By: Grigoriy Milman Summary: PTC pplugin plugin failed to timeout 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-41054) PTC pplugin failed to timeout
Title: Message Title
Grigoriy Milman edited a comment on JENKINS-41054
Re: PTC pplugin failed to timeout
It first I did re-saved not all of the build jobs but just some of them with new PTC timeout settings.At that moment I have seen the issue I have reported for one of the re-saved job.Now I have all of the build jobs re-saved with new PTC timeout settings. I can't say for sure that I have seen failure to timeout. what I have found today that one build job did perform "si" resync successfully but at checkpoint failed:{quote}Preparing to execute si checkpoint for #/repository/Operations#ESS/Application Software/SWCode/Scanner/pcProxFATAL: Failed to checkpoint /repository/Operations/ESS/Application Software/SWCode/Scanner/pcProx/project.pj: MKS125210: The project history is being changed by another user.Build step 'Integrity - CM Checkpoint' marked build as failure{quote}By the way, for PTC plugin upgrade 2.0.2 is it enough to re-save build job config with new PTC timeout parameter or build job should be re-created from scratch? Can it be recreated based on the original one of absolutely brand new?If re-created, that means job history will be lost... May be it it is possible just to add something to job config manually?The [^config.xml] is config for some of ours build job re-saved after upgrade.
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
[JIRA] (JENKINS-41054) PTC pplugin failed to timeout
Title: Message Title
Grigoriy Milman edited a comment on JENKINS-41054
Re: PTC pplugin failed to timeout
It first I did re-saved not all of the build jobs but just some of them with new PTC timeout settings.At that moment I have seen the issue I have reported for one of the re-saved job.Now I have all of the build jobs re-saved with new PTC timeout settings. I can't say for sure that I have seen failure to timeout. what I have found today that one build job did perform "si" resync successfully but at checkpoint failed:{quote}Preparing to execute si checkpoint for #/repository/Operations#ESS/Application Software/SWCode/Scanner/pcProxFATAL: Failed to checkpoint /repository/Operations/ESS/Application Software/SWCode/Scanner/pcProx/project.pj: MKS125210: The project history is being changed by another user.Build step 'Integrity - CM Checkpoint' marked build as failure{quote}By the way, for PTC plugin upgrade 2.0.2 is it enough to re-save build job config with new PTC timeout parameter or build job should be re-created from scratch? Can it be recreated based on the original one of absolutely brand new?If re-created, that means job history will be lost... May be it it is possible just to add something to job config manually?The [^config.xml] is config for some of ours build job re-saved after upgrade. Is
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
[JIRA] (JENKINS-41054) PTC pplugin failed to timeout
Title: Message Title Grigoriy Milman commented on JENKINS-41054 Re: PTC pplugin failed to timeout It first I did re-saved not all of the build jobs but just some of them with new PTC timeout settings. At that moment I have seen the issue I have reported for one of the re-saved job. Now I have all of the build jobs re-saved with new PTC timeout settings. I can't say for sure that I have seen failure to timeout. what I have found today that one build job did perform "si" resync successfully but at checkpoint failed: Preparing to execute si checkpoint for #/repository/Operations#ESS/Application Software/SWCode/Scanner/pcProx FATAL: Failed to checkpoint /repository/Operations/ESS/Application Software/SWCode/Scanner/pcProx/project.pj: MKS125210: The project history is being changed by another user. Build step 'Integrity - CM Checkpoint' marked build as failure By the way, for PTC plugin upgrade 2.0.2 is it enough to re-save build job config with new PTC timeout parameter or build job should be re-created from scratch? Can it be recreated based on the original one of absolutely brand new? If re-created, that means job history will be lost... May be it it is possible just to add something to job config manually? The config.xml is config for some of ours build job re-saved after upgrade. Is 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
[JIRA] (JENKINS-41054) PTC pplugin failed to timeout
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-41054 PTC pplugin failed to timeout Change By: Grigoriy Milman Attachment: config.xml 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-39403) Problem with path separators with jenkins 2.28 on windows
Title: Message Title Grigoriy Milman edited a comment on JENKINS-39403 Re: Problem with path separators with jenkins 2.28 on windows Windows does not understand "/" slash.Jenkins system variables (JENKINS_HOME and other), machine specific variables like PATH, TIMEZONE, etc. all are in the Windows format.Jenkins file separator on Windows is "\", and all properties holding files or directories location can't be used with "1.93.1" way of properties parsing.So it became impossible to create combined path when environment variables coming from system and coming from build job through the Env,inject plugin! What is more, we have some build jobs that create files containing files locations for another build jobs. These files are generated by Windows tools and contains Windows file separators. In "1.93.1" way these files can't be read back correctly! Without possibility to specify location of the input files relative to the work space in different stages of the build and location of the output files, how Jenkins can be used? 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-39403) Problem with path separators with jenkins 2.28 on windows
Title: Message Title Grigoriy Milman commented on JENKINS-39403 Re: Problem with path separators with jenkins 2.28 on windows Windows does not understand "/" slash. Jenkins system variables (JENKINS_HOME and other), machine specific variables like PATH, TIMEZONE, etc. all are in the Windows format. Jenkins file separator on Windows is "\", and all properties holding files or directories location can't be used with "1.93.1" way of properties parsing. So it became impossible to create combined path when environment variables coming from system and coming from build job through the Env,inject plugin! What is more, we have some build jobs that create files containing files locations for another build jobs. These files are generated by Windows tools and contains Windows file separators. In "1.93.1" way these files can't be read back correctly! 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-39403) Problem with path separators with jenkins 2.28 on windows
Title: Message Title Grigoriy Milman edited a comment on JENKINS-39403 Re: Problem with path separators with jenkins 2.28 on windows Yes, changelog for 1.93 says the format of property parsing has changed.What it does not say that the change make Jenkins impossible to use on Windows.When somebody will start to create a new Jenkins system on Windows platform, the latest version of the plugin will be installed automatically and system will be impossible to use.Consider the case when some property is set based on some Windows system command.When this property should be used its value (string) is changed because of some interpretation?I think that there should be at least possibility to switch between "direct" mode and strict "JAVA property" mode, and it should be done not globally for entire job config from the beginning to the end but for but for each plugin usage. For example, there are 2 usage of env. var injection plugin:- First at the beginning defining variables A and B, set as "direct" . - Another somewhere in the middle defining variables C and D, set as "JAVA file property " . Values of properties variables A and B not changed by plugin interpretation and injected everywhere as they are.Values of properties variables C and D are parsed according to the "JAVA file property" and injected based on the new rule. 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
[JIRA] (JENKINS-39403) Problem with path separators with jenkins 2.28 on windows
Title: Message Title Grigoriy Milman edited a comment on JENKINS-39403 Re: Problem with path separators with jenkins 2.28 on windows Yes, changelog for 1.93 . It explicitly says the format of property parsing has changed.What it does not say that the change make Jenkins impossible to use on Windows .When somebody will start to create a new Jenkins system on Windows platform, the latest version of the plugin will be installed automatically and system will be impossible to use . 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-39403) Problem with path separators with jenkins 2.28 on windows
Title: Message Title Grigoriy Milman commented on JENKINS-39403 Re: Problem with path separators with jenkins 2.28 on windows Yes, changelog for 1.93. It explicitly says the format of property parsing has changed. What it does not say that the change make Jenkins impossible to use on Windows system. 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-41054) PTC pplugin failed to timeout
Title: Message Title Grigoriy Milman created an issue Jenkins / JENKINS-41054 PTC pplugin failed to timeout Issue Type: Bug Assignee: PTC ALM Components: integrity-plugin Created: 2017/Jan/13 1:08 AM Environment: Windows server 2012 Jenkins 2.40 PTC integrity Plugin 2.0.2 Priority: Major Reporter: Grigoriy Milman I just upgraded system from Jenkins 1.644 to 2.40 At the same time I have upgraded PTC integrity Plugin from 1.3.6 to 2.0.2 I have updated config of some build job (at timeout condition) and started to test. Unfortunately, synchronizing workspace failed buy timeout did not happened after specified time! Below part of the corresponding log: Time Elapsed 00:00:02.45 Success build fororg.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder@f00640 Change Log: http://ds-jenk2-1.biotronik.com:8080/job/TDE.Common_Libraries-ECM_Utilities/343/changes Build Log: http://ds-jenk2-1.biotronik.com:8080/job/TDE.Common_Libraries-ECM_Utilities/343/console Preparing to execute si projectinfo for /repository/TDE/Common_Libraries/ECM_Storage/project.pj Preparing to execute si viewproject for #/repository/TDE#Common_Libraries/ECM_Storage Checkout directory is D:\Jenkins_ROOT\TDE\Common_Libraries\ECM_Storage A clean copy is requested; deleting contents of D:\Jenkins_ROOT\TDE\Common_Libraries\ECM_Storage Populating clean workspace... A Timeout Exception was caught. Failed to checkout contents of file! null ERROR: Failed to synchronize workspace! Retrying after 10 seconds Change Log: http://ds-jenk2-1.biotronik.com:8080/job/TDE.Common_Libraries-ECM_Utilities/343/changes Build Log: http://ds-jenk2-1.biotronik.com:8080/job/TDE.Common_Libraries-ECM_Utilities/343/console Preparing to execute si projectinfo for
[JIRA] (JENKINS-39131) Backslashes are removed from injected environment variables
Title: Message Title Grigoriy Milman reopened an issue Unfortunately, such behavior makes usage of the environment variables impossible in Windows batch scripts. See my comments related to the JENKINS-39403 Jenkins / JENKINS-39131 Backslashes are removed from injected environment variables Change By: Grigoriy Milman Resolution: Not A Defect Status: Resolved Reopened 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
[JIRA] (JENKINS-39403) Problem with path separators with jenkins 2.28 on windows
Title: Message Title Grigoriy Milman edited a comment on JENKINS-39403 Re: Problem with path separators with jenkins 2.28 on windows I just have seen the same issue during upgrading Jenkins from version 1.644 to 2.40Environment Injector Plugin was upgraded from 1.92.1 to 1.93.1The problem is the following: When environment variable contains directory or file path with Windows slash as path separator, the injected value of the variable will be string without slashes.Here is an exampleProperties Content are set as following in the job config: see [^PropertiesContent.PNG] Corresponding fragment of the Console Output (see [^ConsoleOutput.PNG]) with result of injection.The interesting thing is that "\target" became " arget" ( marked by yellow background).It should be mentioned here that usage forward slashes is not supported in Windows batch commands and windows command prompt, so replacements back slashes to forward slashes not an option in Windows environment.There is a related issue JENKINS-39131, which was set as "resolved". Unfortunately, such resolving behavior makes Jenkins unusable in Windows environment : it is impossible to inject path related environment variables to any batch command or script where directory or file path is used! The problem disappeared after downgrading back Environment Injector Plugin from 1.93.1 to 1.92.1 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
[JIRA] (JENKINS-39403) Problem with path separators with jenkins 2.28 on windows
Title: Message Title Grigoriy Milman edited a comment on JENKINS-39403 Re: Problem with path separators with jenkins 2.28 on windows I just have seen the same issue during upgrading Jenkins from version 1.644 to 2.40Environment Injector Plugin was upgraded from 1.92.1 to 1.93.1The problem is the following: When environment variable contains directory or file path with Windows slash as path separator, the injected value of the variable will be string without slashes.Here is an exampleProperties Content are set as following in the job config: see [^PropertiesContent.PNG] Corresponding fragment of the Console Output (see [^ConsoleOutput.PNG]) with result of injection.The interesting thing is that "\target" became " arget" ( marked by yellow background).It should be mentioned here that usage forward slashes is not supported in Windows batch commands and windows command prompt, so replacements back slashes to forward slashes not an option in Windows environment.There is a related issue JENKINS-39131, which was set as "resolved". Unfortunately, such resolving makes Jenkins unusable in Windows environment The problem disappeared after downgrading back Environment Injector Plugin from 1.93.1 to 1.92.1 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-39403) Problem with path separators with jenkins 2.28 on windows
Title: Message Title Grigoriy Milman edited a comment on JENKINS-39403 Re: Problem with path separators with jenkins 2.28 on windows I just have seen the same issue during upgrading Jenkins from version 1.644 to 2.40 Environment Injector Plugin was upgraded from 1.92.1 to 1.93.1 The problem is the following: When environment variable contains directory or file path with Windows slash as path separator, the injected value of the variable will be string without slashes.Here is an exampleProperties Content are set as following in the job config: see [^PropertiesContent.PNG] !PropertiesContent.PNG|thumbnail! Corresponding fragment of the Console Output (see [^ConsoleOutput.PNG] ) with result of injection. The interesting thing is that "\target" became " arget" ( marked by yellow background). It should be mentioned here that usage forward slashes is not supported in Windows batch commands and windows command prompt , so replacements back slashes to forward slashes not an option in Windows environment .There is a related issue JENKINS-39131, which was set as "resolved". Unfortunately, such resolving makes Jenkins unusable in Windows environment 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-39403) Problem with path separators with jenkins 2.28 on windows
Title: Message Title Grigoriy Milman edited a comment on JENKINS-39403 Re: Problem with path separators with jenkins 2.28 on windows I just have seen the same issue during upgrading Jenkins from version 1.644 to 2.40The problem is the following: When environment variable contains directory or file path with Windows slash as path separator, the injected value of the variable will be string without slashes.Here is an exampleProperties Content are set as following in the job config: [^PropertiesContent.PNG] !PropertiesContent.PNG|thumbnail! Corresponding fragment of the Console Output [^ConsoleOutput.PNG] with result of injection.It should be mentioned here that usage forward slashes is not supported in Windows commands, so replacements back slashes to forward slashes not an option in Windows environment 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-39403) Problem with path separators with jenkins 2.28 on windows
Title: Message Title Grigoriy Milman reopened an issue I just have seen the same issue during upgrading Jenkins from version 1.644 to 2.40 The problem is the following: When environment variable contains directory or file path with Windows slash as path separator, the injected value of the variable will be string without slashes. Here is an example Properties Content are set as following in the job config: PropertiesContent.PNG Corresponding fragment of the Console Output ConsoleOutput.PNG with result of injection. It should be mentioned here that usage forward slashes is not supported in Windows commands, so replacements back slashes to forward slashes not an option in Windows environment Jenkins / JENKINS-39403 Problem with path separators with jenkins 2.28 on windows Change By: Grigoriy Milman Resolution: Cannot Reproduce Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39403) Problem with path separators with jenkins 2.28 on windows
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-39403 Problem with path separators with jenkins 2.28 on windows Change By: Grigoriy Milman Attachment: ConsoleOutput.PNG Attachment: PropertiesContent.PNG 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] [build-blocker-plugin] (JENKINS-32903) Build-Blocker-Plugin does not block
Title: Message Title Grigoriy Milman created an issue Jenkins / JENKINS-32903 Build-Blocker-Plugin does not block Issue Type: Bug Assignee: Unassigned Components: build-blocker-plugin Created: 11/Feb/16 6:08 PM Environment: Jenkins 1.644 Priority: Critical Reporter: Grigoriy Milman Job A trigger 8 other, secondary jobs. Each secondary jobs has other 7 jobs referenced in the blocking list of jobs. All secondary jobs have exactly the same waiting period before start. Our Jenkins has 4 executors. Some how multiple (more than one) build jobs picked up for execution at very beginning, than remaining ones executed one by one. We have seen for Throttle concurrent builds plugin the same problem also Add Comment
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-32888) Throttle Concurrent Builds plugin doesn't work
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-32888 Throttle Concurrent Builds plugin doesn't work Change By: Grigoriy Milman One job at the end started 8 other jobs.All jobs belong to the same category.Maximum Total Concurrent Builds is set to 0 and Maximum Concurrent Builds Per Node to is set 1. 3 jobs started simultaneously * (I have 4 executors on the system)! Than only one was executed ! sequentially, as it should. I need to have only one job running from this category at any time! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [throttle-concurrent-builds-plugin] (JENKINS-32888) Throttle Concurrent Builds plugin doesn't work
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-32888 Throttle Concurrent Builds plugin doesn't work Change By: Grigoriy Milman One job at the end started 8 other jobs.All jobs belong to the same category.Maximum Total Concurrent Builds is set to 0 and Maximum Concurrent Builds Per Node to is set 1. 3 jobs started simultaneously * (I have 4 executors on the system)! Than only one was executed sequentially, as it should.I need to have only one job running from this category at any time! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [throttle-concurrent-builds-plugin] (JENKINS-32888) Throttle Concurrent Builds plugin doesn't work
Title: Message Title Grigoriy Milman created an issue Jenkins / JENKINS-32888 Throttle Concurrent Builds plugin doesn't work Issue Type: Bug Assignee: Oleg Nenashev Components: throttle-concurrent-builds-plugin Created: 11/Feb/16 5:24 AM Environment: Jenkins 1.644 Priority: Major Reporter: Grigoriy Milman One job at the end started 8 other jobs. All jobs belong to the same category. Maximum Total Concurrent Builds is set to 0 and Maximum Concurrent Builds Per Node to is set 1. 3 jobs started simultaneously (I have 4 executors on the system)! Than only one was executed! I need to have only one job running from this category at any time! Add Comment
[JIRA] [integrity-plugin] (JENKINS-31588) "No space left on device" when there is near 100 GB abavilable
Title: Message Title Grigoriy Milman created an issue Jenkins / JENKINS-31588 "No space left on device" when there is near 100 GB abavilable Issue Type: Bug Assignee: Cletus D'Souza Components: integrity-plugin Created: 17/Nov/15 3:56 AM Environment: Windows. Jenkins ver. 1.637 PTC Integrity plug-in for Jenkins ver. 1.36 Priority: Critical Reporter: Grigoriy Milman ov 16, 2015 7:35:55 PM hudson.scm.IntegrityCheckoutTask invoke SEVERE: ExecutionException java.util.concurrent.ExecutionException: java.lang.Exception: ESSLoadUnloadStation/Header/UserDetailsViewModel.cs: No space left on device at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source) at java.util.concurrent.FutureTask.get(Unknown Source) at hudson.scm.IntegrityCheckoutTask.invoke(IntegrityCheckoutTask.java:382) at hudson.scm.IntegrityCheckoutTask.invoke(IntegrityCheckoutTask.java:33) at hudson.FilePath.act(FilePath.java:991) at hudson.FilePath.act(FilePath.java:969) at hudson.scm.IntegritySCM.checkout(IntegritySCM.java:864) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at
[JIRA] [integrity-plugin] (JENKINS-31588) "No space left on device" when there is near 100 GB available
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-31588 "No space left on device" when there is near 100 GB available Change By: Grigoriy Milman Summary: "No space left on device" when there is near 100 GB abavilable available Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman commented on JENKINS-28633 Re: Plugin update does not work any more 1. I did not use a custom update center. 2. This issue looks like is related to the JENKINS-28544 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-28633 Plugin update does not work any more Change By: Grigoriy Milman Labels: core pluginsupdate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-28633 Plugin update does not work any more Change By: Grigoriy Milman JustswitchedfromJenkins1.611to1.614.Jenkins1.615hasthesameissueJenkinsPluginManager,inUpdatestabIhaveselectedall3pluginstoupdateandstartedtheupdateby clickning clicking Downloadnowandinstallafterrestart(seepicture!Plugin1.png|thumbnail!),butupdatedidnotperformed!IcamebacktothePluginManager.Selectedthesamepluginsandstartedtheupdate(seepicture!Plugin2.png|thumbnail!).Thesamepluginsappearedwithstatuspendingtwiceandstillnowanyactivity! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-28633 Plugin update does not work any more Change By: Grigoriy Milman Labels: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28631) java.util.ConcurrentModificationException during si viewproject
Title: Message Title Grigoriy Milman created an issue Jenkins / JENKINS-28631 java.util.ConcurrentModificationException during si viewproject Issue Type: Bug Assignee: Cletus D'Souza Components: integrity-plugin Created: 28/May/15 6:09 PM Environment: Jenkins 1.614 on Windows PTC Integrity CM plugin version 1.33 Priority: Major Reporter: Grigoriy Milman Fragment of the log: Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Drivers/NiFpga/NiFpga.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#Drivers#s=NiFpga/NiFpga.pj Checkout directory is D:\Jenkins_ROOT\NGMP.DIRECT.Sandbox\SWProduction\Drivers\NiFpga A clean copy is requested; deleting contents of D:\Jenkins_ROOT\NGMP.DIRECT.Sandbox\SWProduction\Drivers\NiFpga Populating clean workspace... java.lang.Exception: Failed to create APISession! FATAL: null java.util.ConcurrentModificationException at java.util.Vector$Itr.checkForComodification(Unknown Source) at java.util.Vector$Itr.next(Unknown Source) at hudson.scm.IntegrityCheckoutTask$ThreadLocalAPISession.remove(IntegrityCheckoutTask.java:157) at hudson.scm.IntegrityCheckoutTask.invoke(IntegrityCheckoutTask.java:430) at
[JIRA] [core] (JENKINS-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-28633 Plugin update does not work any more Change By: Grigoriy Milman JustswitchedfromJenkins1.611to1.614.Jenkins1.615hasthesameissueJenkinsPluginManager,inUpdatestabIhaveselectedall3pluginstoupdateandstartedtheupdatebyclickningDownloadnowandinstallafterrestart(seepicture!Plugin1.png|thumbnail!),butupdatedidnotperformed!IcamebacktothePluginManager. Select Selected thesamepluginsandstartedtheupdate(seepicture!Plugin2.png|thumbnail!).Thesamepluginsappearedwithstatuspendingtwiceand still nowanyactivity . ! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-28633 Plugin update does not work any more Change By: Grigoriy Milman Attachment: Plugin0.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman created an issue Jenkins / JENKINS-28633 Plugin update does not work any more Issue Type: Bug Assignee: Unassigned Attachments: Plugin1.png, Plugin2.png Components: core Created: 28/May/15 7:36 PM Environment: Jenkins 1.614 and 1.615 on Windows Priority: Critical Reporter: Grigoriy Milman Just switched from Jenkins 1.611 to 1.614. Jenkins 1.615 has the same issue Jenkins Plugin Manager, in Updates tab I have selected all 3 plugins to update and started the update by clickning Download now and install after restart (see picture ), but update did not performed! I came back to the Plugin Manager. Select the same plugins and started the update (see picture ). The same plugins appeared with status pending twice and now any activity.
[JIRA] [integrity-plugin] (JENKINS-28584) Error during Si command execution. It usually cleaned up by jenkins reset
Title: Message Title Grigoriy Milman created an issue Jenkins / JENKINS-28584 Error during Si command execution. It usually cleaned up by jenkins reset Issue Type: Bug Assignee: Cletus D'Souza Components: integrity-plugin Created: 26/May/15 6:56 PM Environment: Windows, Jenkins 1.611, PTC plugin 1.33 Priority: Major Reporter: Grigoriy Milman Log: ??Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Drivers/DMM/General/project.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#Drivers/DMM/General Checkout directory is http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct-Drivers.DMM.General/ws/ A clean copy is requested; deleting contents of http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct-Drivers.DMM.General/ws/ Populating clean workspace... java.lang.Exception: Failed to create APISession! FATAL: null java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(Unknown Source) at java.util.AbstractList$Itr.next(Unknown Source) at hudson.scm.IntegrityCheckoutTask$ThreadLocalAPISession.remove(IntegrityCheckoutTask.java:157) at hudson.scm.IntegrityCheckoutTask.invoke(IntegrityCheckoutTask.java:430) at hudson.scm.IntegrityCheckoutTask.invoke(IntegrityCheckoutTask.java:28) at
[JIRA] [prioritysorter-plugin] (JENKINS-27987) Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.6
Grigoriy Milman resolved JENKINS-27987 as Duplicate Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609 It looks like it is duplicate of the JENKINS-27957 Version 2.12 which has a fix for the JENKINS-27957does not show the problem Change By: Grigoriy Milman (20/Apr/15 5:55 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] [prioritysorter-plugin] (JENKINS-27987) Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.6
Grigoriy Milman edited a comment on JENKINS-27987 Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609 It looks like it is duplicate of the JENKINS-27957 Version 2.12 which has a fix for the JENKINS-27957 does not repeat the problem This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-27987) Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.6
Grigoriy Milman commented on JENKINS-27987 Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609 We are using 2.11 It could be the same issue as in JENKINS-27957, so I will try 2.12, may be it is already fixed. I will try it today. 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-27987) Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609
Grigoriy Milman commented on JENKINS-27987 Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609 I have reproduced the error again: Job A has been started by manually and executed. After execution it triggered ((placed to the queue) another 3 build jobs. At the same time other 5 build jobs have been triggered (placed to the queue) by SCM, 4 of the last 5 jobs are downstream to the first 3 build jobs but one independent (does not have upstream job at all)! No job except job A has been processed. all other are in the queue for ever. By the way there are multiple strange log entries in jenkins.err.log like the following Apr 17, 2015 9:19:45 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.model.Queue$MaintainTask@f79885 failed java.lang.NullPointerException at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:99) at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:81) at java.util.Arrays.mergeSort(Unknown Source) at java.util.Arrays.sort(Unknown Source) at java.util.Collections.sort(Unknown Source) at jenkins.advancedqueue.sorter.AdvancedQueueSorter.sortBuildableItems(AdvancedQueueSorter.java:81) at hudson.model.Queue.maintain(Queue.java:1337) at hudson.model.Queue$MaintainTask.doRun(Queue.java:2435) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 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-27987) Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609
Grigoriy Milman created JENKINS-27987 Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609 Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Apr/15 8:25 PM Description: Just migrated from Jenkins 1.606 to 1.609 One build jobs started simultaneously 8 downstream jobs. All 8 jobs are in the waiting queue waiting for next available executor for very long time (hours!) but there is no one executor is running from total four! Environment: Windows Server 2008 Project: Jenkins Priority: Blocker 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 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-27061) Strange exceptions whern performaing si in plugin 1.31
Grigoriy Milman commented on JENKINS-27061 Strange exceptions whern performaing si in plugin 1.31 There is at least one error present but a different one - - see JENKINS-27370. That error is related to particular new build job. Another build job was created about at the same time and workes fine! 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-27370) IntegritySCM checkout failure due to the java.sql.SQLException: Java exception: ': java.lang.NullPointerException
Grigoriy Milman commented on JENKINS-27370 IntegritySCM checkout failure due to the java.sql.SQLException: Java exception: : java.lang.NullPointerException 1. Our Jenkins filesystem is local to the server. 2. That error is related to this/such particular new build job. Another build job was created about at the same time and work fine! Question, this PTC project has space character in the middle: /repository/TDE/QARI/Capacitor Test/Tantalum Capacitors/5160209/project.pj Is it OK? 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-27370) IntegritySCM checkout failure due to the java.sql.SQLException: Java exception: ': java.lang.NullPointerException
Grigoriy Milman created JENKINS-27370 IntegritySCM checkout failure due to the java.sql.SQLException: Java exception: : java.lang.NullPointerException Issue Type: Bug Assignee: Cletus DSouza Attachments: SQLException_NULLPointer.txt Components: integrity-plugin Created: 11/Mar/15 7:19 PM Description: New build job was created and executed. During resynchronization error appeared. Fragment of the console log: Preparing to execute si projectinfo for /repository/TDE/QARI/Capacitor Test/Tantalum Capacitors/5160209/project.pj Preparing to execute si viewproject for #/repository/TDE#QARI/Capacitor Test/Tantalum Capacitors/5160209 A SQL Exception was caught! Java exception: ': java.lang.NullPointerException'. Fragment of the jenkins.err.log - see attached log file SQLException_NULLPointer.txt Another build job for another PTC project was created and executed just fine. Environment: Jenkins 1.599 Integrity PTC plugin 1.31 Windows server 2008 Project: Jenkins Priority: Minor 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 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-27370) IntegritySCM checkout failure due to the java.sql.SQLException: Java exception: ': java.lang.NullPointerException
Grigoriy Milman commented on JENKINS-27370 IntegritySCM checkout failure due to the java.sql.SQLException: Java exception: : java.lang.NullPointerException I have restarted Jenkins but it does not help. What I have realized that the old build jobs that were functional before now failing with the same issue! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing si in plugin 1.31
Grigoriy Milman commented on JENKINS-27061 Strange exceptions whern performaing si in plugin 1.31 What I did: Our previous version of the plugin on production Jenkins was 1.28. I have deleted all PTC Integrity entries in configs for all build jobs (near hundred of them), saved all configs, restarted Jenkins (just in case), installed PTC plugin version 1.31 (the official version), restarted Jenkins, updated configs for all jobs with required PTC Integrity information, saved them, restarted Jenkins (just in case); started rebuilding entire tree of the build jobs - errors appeared. I have decreased decrease quantity of executors to one, and this helped. Questions: 1. You have mentioned before turning loose polling. What is loose polling and where I should turn it on/off? 2. new cache entries - should I restart entire computer for clean up cache? 3. I don't understand that errors: Syntax error: Encountered "WHERE" ... java.lang.NullPointerException java.sql.SQLSyntaxErrorException: Table/View 'SCM_42320538_D24A_465E_A61D_4D1D6E1E3E8C' does not exist. 4. Another interesting thing: our PTC communication is slow, and it looks like when multiple jobs pulling data from server, the errors happened about instantly. 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-27061) Strange exceptions whern performaing si in plugin 1.31
Grigoriy Milman edited a comment on JENKINS-27061 Strange exceptions whern performaing si in plugin 1.31 It looks like there are different errors here (see attached error log file) Syntax error: Encountered "WHERE" ... java.lang.NullPointerException java.sql.SQLSyntaxErrorException: Table/View 'SCM_42320538_D24A_465E_A61D_4D1D6E1E3E8C' does not exist. The bad thing is that problem intermittent, sometimes it works, sometimes does not This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing si in plugin 1.31
Grigoriy Milman edited a comment on JENKINS-27061 Strange exceptions whern performaing si in plugin 1.31 I decrease quantity of executors to one. Thus allow only execute one build job art time. It works much more reliable, but, of course, very slow. We have hundreds build job, to rebuild entire tree with only one executor, it will take about a day! The SQL exception related to the Table/View, still appeared like the following A SQL Exception was caught! Table/View 'SCM_8804D8BF_B059_4FCE_AD3C_93A872EEC42A' does not exist. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing si in plugin 1.31
Grigoriy Milman created JENKINS-27061 Strange exceptions whern performaing si in plugin 1.31 Issue Type: Bug Assignee: Cletus DSouza Components: integrity-plugin Created: 21/Feb/15 4:37 AM Description: PTC plugin 1.31 - generally works but suddenly we have observed a strange bug: Multiple build jobs started about simultaneously (not sure is it important or not) Time Elapsed 00:00:00.95 Success build fororg.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder@e4f765 Change Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/943/changes Build Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/943/console Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Components/Sequencer/Sequencer.pj An API Exception was caught! Authentication failed for TE_build_process on mks1.biotronik.de:7001 si projectinfo --user=TE_build_process --port=7001 --hostname=mks1.biotronik.de --project=/repository/CorporateMeasurementTechnologies/SWProduction/Components/Sequencer/Sequencer.pj returned exit code 128 Retrying after 10 seconds Change Log: http://-.com:8080/job/NGMP.Direct.Components.Sequencer/943/changes Build Log: http://-.com:8080/job/NGMP.Direct.Components.Sequencer/943/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! Table/View 'SCM_18987648_BDEE_4233_9A45_E1E0A4B3DE60' does not exist. Retrying after 10 seconds Build was aborted Environment: Windows, Jenkins 1.598 PTC plugin 1.31 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 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-27061) Strange exceptions whern performaing si in plugin 1.31
Grigoriy Milman commented on JENKINS-27061 Strange exceptions whern performaing si in plugin 1.31 I have tried again to build the same build job alone: Time Elapsed 00:00:00.22 Success build fororg.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder@e4f765 Change Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/changes Build Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/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! Table/View 'SCM_974E0F36_678A_4802_AE9C_0FA142C071CA' does not exist. Retrying after 10 seconds Change Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/changes Build Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/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! Table/View 'SCM_974E0F36_678A_4802_AE9C_0FA142C071CA' does not exist. Retrying after 10 seconds Change Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/changes Build Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/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! Table/View 'SCM_974E0F36_678A_4802_AE9C_0FA142C071CA' does not exist. Retrying after 10 seconds Change Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/changes Build Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/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! Table/View 'SCM_974E0F36_678A_4802_AE9C_0FA142C071CA' does not exist. Archiving artifacts Publishing Javadoc Recording fingerprints 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 -- 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-27061) Strange exceptions whern performaing si in plugin 1.31
Grigoriy Milman commented on JENKINS-27061 Strange exceptions whern performaing si in plugin 1.31 I just decrease quantity of executors to one. Thus allow only execute one build job art time. It works much more reliable, but, of course, very slow. We have hundreds build job, to rebuild entire tree with only one executor, it will take about a day! 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-27061) Strange exceptions whern performaing si in plugin 1.31
Grigoriy Milman commented on JENKINS-27061 Strange exceptions whern performaing si in plugin 1.31 10 minutes later, this build job was successfully done when was started and running stand alone! It is very strange. 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-27061) Strange exceptions whern performaing si in plugin 1.31
Grigoriy Milman updated JENKINS-27061 Strange exceptions whern performaing si in plugin 1.31 Change By: Grigoriy Milman (21/Feb/15 5:19 AM) Priority: Major Blocker 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-27061) Strange exceptions whern performaing si in plugin 1.31
Grigoriy Milman edited a comment on JENKINS-27061 Strange exceptions whern performaing si in plugin 1.31 10 minutes later, this build job was successfully done when was started and running stand alone! It is very strange. By the way (just observation), it looks like "Preparing to execute si projectinfo for..." only running for one build job a time, and if in parallel another build job already doing this operation, everything stack 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-27061) Strange exceptions whern performaing si in plugin 1.31
Grigoriy Milman edited a comment on JENKINS-27061 Strange exceptions whern performaing si in plugin 1.31 It looks like there are different errors here (see attached error log file) Syntax error: Encountered "WHERE" ... java.lang.NullPointerException java.sql.SQLSyntaxErrorException: Table/View 'SCM_42320538_D24A_465E_A61D_4D1D6E1E3E8C' does not exist. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing si in plugin 1.31
Grigoriy Milman updated JENKINS-27061 Strange exceptions whern performaing si in plugin 1.31 It looks like there are different errors here Syntax error: Encountered "WHERE" ... java.lang.NullPointerException java.sql.SQLSyntaxErrorException: Table/View 'SCM_42320538_D24A_465E_A61D_4D1D6E1E3E8C' does not exist. Change By: Grigoriy Milman (21/Feb/15 5:19 AM) Attachment: jenkins.err.log 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] [managed-scripts-plugin] (JENKINS-27044) Add support for the python scripts with arguments
Grigoriy Milman created JENKINS-27044 Add support for the python scripts with arguments Issue Type: New Feature Assignee: Dominik Bartholdi Components: managed-scripts-plugin Created: 19/Feb/15 10:04 PM Description: Execution of the centralized maintained python scripts with arguments, and if possible, with python version selection. 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 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-26770) 'Apply' doesn't work in version 1.29 of the plugin
Grigoriy Milman resolved JENKINS-26770 as Fixed Apply doesnt work in version 1.29 of the plugin I have tested it. It works! Thanks for fast responses! Change By: Grigoriy Milman (11/Feb/15 7:02 PM) Status: Reopened 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 -- 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-26770) 'Apply' doesn't work in version 1.29 of the plugin
Grigoriy Milman commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin Just tested. Hpi for JENKINS-26906 works fine. 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-26770) 'Apply' doesn't work in version 1.29 of the plugin
Grigoriy Milman commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin By the way, on our production Jenkins server we will use the official plugin version 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! Because I am using a clone build system for testing, I have a luxury to delete some jobs. I deleted all that not converted, and now only 5 converted left. The 'Apply' error is still present. I have created a new build job, saved it, change config - The 'Apply' error is still present there too. 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! I have tried to see how "Apply" issue looks in Chrome browser: When click "Apply", error dialog does not appear but changed data is not saved, and green bar confirmation does not appear also! 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! Usage of the integrity-plugin.hpi helps, but there is still a strange issue. There are two buttons on the config editing screen, "Save" and "Apply". Now by using "Save", config is saved and build job is executed OK (finally!). By using button "Apply" - grey empty screen appeared with "Error"on it (see attached picture ^ptc.jpg .). I have tried to "Save" and then "Apply" - "Apply" button does not work, always error screen, but "Save" works. It looks like it is last issue that need to be resolved 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/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman updated JENKINS-26770 version 1.29 of the plugin does not work! Change By: Grigoriy Milman (09/Feb/15 8:04 PM) Attachment: ConfigHistory.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 -- 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! But the config has been already saved by "Save" button just a second before! It very simple: open config, save by "Save" button, than open config again and click "Apply" - error screen appeared. By the way, I have tried to see job config history by clicking "config changed since last build" at "Build history" (see ConfigHistory.JPG) and the following error appeared: HTTP ERROR 404 Problem accessing /view/BurnIn/job/NGMP.BurnIn.BoardScanner/jobConfigHistory/showDiffFiles. Reason: Not Found Powered by Jetty:// 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! But the config has been already saved by "Save" button just a second before! It very simple: open config, save by "Save" button, than open config again and click "Apply" - error screen appeared. By the way, I have tried to see job config history by clicking "config changed since last build" at "Build history" (see) HTTP ERROR 404 Problem accessing /view/BurnIn/job/NGMP.BurnIn.BoardScanner/jobConfigHistory/showDiffFiles. Reason: Not Found Powered by Jetty:// 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman updated JENKINS-26770 version 1.29 of the plugin does not work! Change By: Grigoriy Milman (09/Feb/15 8:08 PM) Attachment: NewConfigHistory.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 -- 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! Usage of the integrity-plugin.hpi helps, but there is still a strange issue. There are two buttons on the config editing screen, "Save" and "Apply". Now by using "Save", config is saved and build job is executed OK (finally!). By using button "Apply" - grey empty screen appeared with "Error"on it (see attached picture). I have tried to "Save" and then "Apply" - "Apply" button does not work, always error screen, but "Save" works. It looks like it is last issue that need to be resolved 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/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! Usage of the integrity-plugin.hpi helps, but there is still a strange issue. There are two buttons on the config editing screen, "Save" and "Apply". Now by using "Save", config is saved and build job is executed OK (finally!). By using button "Apply" - grey empty screen appeared with "Error" on it (see attached picture ptc.JPG .). I have tried to "Save" and then "Apply" - "Apply" button does not work, always error screen, but "Save" works. It looks like it is last issue that need to be resolved 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/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! But the config has been already saved by "Save" button just a second before! It very simple: open config, save by "Save" button, than open config again and click "Apply" - error screen appeared. By the way, I have tried to see job config history by clicking "config changed since last build" at "Build history" (see ConfigHistory.JPG) HTTP ERROR 404 Problem accessing /view/BurnIn/job/NGMP.BurnIn.BoardScanner/jobConfigHistory/showDiffFiles. Reason: Not Found Powered by Jetty:// 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! I have tried to migrate from 1.28 to 1.30 by doing the following: Turning off Integrity CM usage in the build jobs configurations, than saving build job configuration; Performing upgrade to the 1.30 plugin. Restarting Jenkins. Setting required PTC settings in Jenkins system configuration (old ones did disappear); For each build job configuration turning on Integrity CM usage, setting PTC project. Save configuration - null pointer exception happened! Good thing is that I have tried this experiment on the clone of the virtual system where Jenkins is running, so our production Jenkins server is still fine. Bad thin is that I still don't know how to migrate to new plugin from 1.28 with saving build history! What is more, creation of the new build job based on the old one does not work either! Any idea? 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! We have moved to 1.598 Jenkins version last week. The 1.598 Jenkins with PTC plugin 1.28 does not have "Apply" error. The 1.598 Jenkins with PTC plugin 1.31 (special version) has "Apply" error. The "Job Configuration History" "ShowDiffs" works fine, only "Apply" in configuration editing has the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! We have moved to 1.598 Jenkins version last week. The 1.598 Jenkins with PTC plugin 1.28 does not have "Apply" error. The 1.598 Jenkins with PTC plugin 1.31 (special version) has "Apply" error. The "Job Configuration History" "ShowDiffs" works fine, only "Apply" in configuration editing has the issue. Thus, I can't say that this is general Jenkins issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! I have just tried again execute "Apply", and confirming the following jenkins.error.log entry as result: Feb 9, 2015 2:38:03 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@16ab8d1Embedded.UP java.lang.NullPointerException at hudson.scm.APISession.create(APISession.java:54) at hudson.scm.IntegritySCM.compareRemoteRevisionWith(IntegritySCM.java:833) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1446) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) The build job has been saved multiple times today by using SAVE button. Job configuration works fine - I have build it a couple of time. It looks like the only issue we see now - one related to the APPLY button 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman updated JENKINS-26770 version 1.29 of the plugin does not work! Change By: Grigoriy Milman (10/Feb/15 12:21 AM) Attachment: Console.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 -- 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! I have just tried again execute "Apply", and confirming the following jenkins.error.log entry as result: Feb 9, 2015 2:38:03 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@16ab8d1Embedded.UP java.lang.NullPointerException at hudson.scm.APISession.create(APISession.java:54) at hudson.scm.IntegritySCM.compareRemoteRevisionWith(IntegritySCM.java:833) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1446) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) The build job has been saved multiple times today by using SAVE button. Job configuration works fine - I have build it a couple of time. It looks like the only issue we see now - one related to the APPLY button. By the way, my console: Console.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 -- 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman updated JENKINS-26770 version 1.29 of the plugin does not work! Change By: Grigoriy Milman (09/Feb/15 7:13 PM) Attachment: ptc.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 -- 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! Usage of the integrity-plugin.hpi helps, but there is still a strange issue. There are two buttons on the config editing screen, "Save" and "Apply". Now by using "Save", config is saved and build job is executed OK (finally!). By using button "Apply" - grey empty screen appeared with "Error" on it (see attached picture ^ptc.jpg .). I have tried to "Save" and then "Apply" - "Apply" button does not work, always error screen, but "Save" works. It looks like it is last issue that need to be resolved 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/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! Here is correspondent fragment of the log file jenkins.err.log: Feb 9, 2015 11:23:00 AM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@ddb923TDE.MES_DataViewer java.lang.NullPointerException at hudson.scm.APISession.create(APISession.java:54) at hudson.scm.IntegritySCM.compareRemoteRevisionWith(IntegritySCM.java:833) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1446) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! I have tried to migrate to 1.30. It does not work! Any idea how to migrate current build jobs with keeping build history? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! Another option is creating unique value of the Integrity - CM Configuration Name each time when build job config is saved, just new UUID or new GUID value, which will be saved in the job config.xml but not available for editing. This will require to re save all build jobs configurations after migration to the new plugin version but the jobs build history will be not affected! If version 1.30 will help us - sure we will wait. 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! 1. By doing recreating build jobs based on the their config.xml files we will loose build history for all jobs, right? That is very bad news for us. 2. Question: as I understand from your description, the goal here to have unique value of the Integrity - CM Configuration Name, right? In this case why not to use name of the build job as value for Integrity - CM Configuration Name? It is unique for sure between all build jobs 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! By doing recreating build jobs based on the their config.xml files we will loose build history for all jobs, right? That is very bad news for us. Very often in our practice we create new build job based on the existing similar one. There is corresponding option in Jenkins new build job creation. I have tried create new build job based on the old one with new value of the Integrity - CM Configuration Name and new build job name. The saving of the updated config failed with error. Does it mean that we can't create new build jobs based on the old one? Question: as I understand from your description, the goal here to have unique value of the Integrity - CM Configuration Name, right? In this case why not to use name of the build job as value for Integrity - CM Configuration Name? It is unique for sure between all build jobs. In this case Integrity - CM Configuration Name entry in the config editing could be removed or made fixed. Migration to the new plugin will require just re save configs and the jobs builds history will be still available. Another option is creating unique value of the Integrity - CM Configuration Name each time when build job config is saved, just new UUID or new GUID value, which will be saved in the job config.xml but not available for editing. This will require to re save all build jobs configurations after migration to the new plugin version but the jobs build history will be not affected! 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! Saving again is not a problem. Job re-creation of the jobs is a problem. Can you confirm the following steps related to your proposal for migration to new version of the plugin with keeping build history: While the 1.28 version of the plugin still active, we should do the following: For each build job configuration - turn off Integrity CM usage. Save configuration; upgrade to the 1.29 plugin. Restart Jenkins For each build job configuration turn on Integrity CM usage. Save configuration; Is it correct? 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-25629) Checkpoints are done against wrong project!
Grigoriy Milman
commented on JENKINS-25629
Checkpoints are done against wrong project!
By the way, is it now OK to use Integrity - CM Configuration Name set as _${env['JOB_NAME']}_
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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! It does not work with old build jobs. But new build job configuration can't be saved! Just take a look on the second part of the log, one with header "NullPointerException during saving of the new job 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 -- 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! It does not work with old build jobs. But new build job configuration can't be saved! Just take a look on the second part of the log, one with header "NullPointerException during saving of the new job configuration". What migration from using old version of the plugin to the new one? Resaving configs of the already created build jobs impossible - (see "NullPointerException during saving of the new job configuration".) Creating new build jobs based on the old ones leads to the same exception as it is described at "NullPointerException during saving of the new job configuration". How it possible to make work with Jenkins server with already hundreds build jobs set? It is Windows-based Jenkins 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-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! It does not work with old build jobs. But new build job configuration can't be saved! Just take a look on the second part of the log, one with header "NullPointerException during saving of the new job configuration". What migration from using old version of the plugin to the new one? Resaving configs of the already created build jobs impossible - (see "NullPointerException during saving of the new job configuration".) Creating new build jobs based on the old ones leads to the same exception as it is described at "NullPointerException during saving of the new job 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 -- 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-25629) Checkpoints are done against wrong project!
Grigoriy Milman reopened JENKINS-25629 Checkpoints are done against wrong project! I have tried new version of the Plugin today. It does not work at all. Attempt to build old build jobs fails because of the NullPointerException during beginning of the build. Configuration of the new jobs impossible to save because of the another NullPointerException which happened during attempt to save! Old build jobs NullPointerException happend during the build: EnvInject - Loading node environment variables. EnvInject - Preparing an environment for the build. EnvInject - Keeping Jenkins system variables. EnvInject - Keeping Jenkins build variables. EnvInject - Injecting as environment variables the properties content . . . EnvInject - Variables injected successfully. EnvInject - Injecting contributions. BuildingFATAL: null java.lang.NullPointerException at hudson.scm.IntegritySCM.buildEnvVars(IntegritySCM.java:463) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:910) at hudson.model.AbstractBuild$AbstractBuildExecution.decideWorkspace(AbstractBuild.java:477) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:517) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) NullPointerException during saving of the new job configuration Stack trace javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) 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 jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) 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:67) 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
[JIRA] [integrity-plugin] (JENKINS-26770) .29 version of the Plugin does not work
Grigoriy Milman created JENKINS-26770 .29 version of the Plugin does not work Issue Type: Bug Assignee: Cletus DSouza Components: integrity-plugin Created: 04/Feb/15 12:10 AM Description: I have tried 1.29 version of the Plugin today, just after . It does not work at all. Attempt to build old build jobs fails because of the NullPointerException during beginning of the build. Configuration of the new jobs impossible to save because of the another NullPointerException which happened during attempt to save! By the way, why Configuration Name is required at all? may be the instead the Project name (build job name) could be used here? It is unique! Old build jobs NullPointerException happend during the build: EnvInject - Loading node environment variables. EnvInject - Preparing an environment for the build. EnvInject - Keeping Jenkins system variables. EnvInject - Keeping Jenkins build variables. EnvInject - Injecting as environment variables the properties content . . . EnvInject - Variables injected successfully. EnvInject - Injecting contributions. BuildingFATAL: null java.lang.NullPointerException at hudson.scm.IntegritySCM.buildEnvVars(IntegritySCM.java:463) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:910) at hudson.model.AbstractBuild$AbstractBuildExecution.decideWorkspace(AbstractBuild.java:477) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:517) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) NullPointerException during saving of the new job configuration Stack trace javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) 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 jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman updated JENKINS-26770 version 1.29 of the plugin does not work! Change By: Grigoriy Milman (04/Feb/15 12:10 AM) Summary: version1 .29 version ofthe Plugin plugin doesnotwork ! Priority: Minor Critical 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] [disk-usage-plugin] (JENKINS-26496) Trying to get the DateFormat as build ID
Grigoriy Milman commented on JENKINS-26496 Trying to get the DateFormat as build ID On the system where Jenkins is installed, the URL of the Jenkins is http://localhost:8080 I have tried http://localhost:8080/JENKINS-24380 I have tried http://localhost:8080/jenkins/JENKINS-24380 Result the same! 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.
