- Status:Open(View Workflow)
- Resolution: Unresolved
- Labels:
- Environment:Windows server 2012
Jenkins 2.40
PTC integrity Plugin 2.0.2
- Hides 2 0 – Keep A Squeaky Clean Workspace Cabinets
- Hides 2 0 – Keep A Squeaky Clean Workspace Floor
- Hides 2 0 – Keep A Squeaky Clean Workspace Clean
- Hides 2 0 – Keep A Squeaky Clean Workspace Jpmc
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!
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!
Next, decide when you plan to remove these properties. Try to pick a date 2-3 months away, so that your team has enough time to reach out if they are still using one of those marked properties. For the properties that you would like to retire, modify the property label to say 'DELETING ON DATE' after the property label. Keep all your installed software applications up to date using this simple app that automatically scans the computer and reveals available updates. Hide active windows with the. Precision-fit for Pro Series 3.0 and Performance Plus Series 2.0 cabinet systems; 84 in. Width spans three floor cabinets perfectly; Powder coat paint finish with diamond plate pattern is rust resistant and easy to keep clean; Store and organize frequently used tools for a functional workspace.
Here's how to design and create an attractive desktop with built-in organization to keep your workspace nice, clean, and productive with minimal effort. Advertisement Color Study Suggests Red Aids.
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_ROOTTDECommon_LibrariesECM_Storage
A clean copy is requested; deleting contents of D:Jenkins_ROOTTDECommon_LibrariesECM_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 /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_ROOTTDECommon_LibrariesECM_Storage
A clean copy is requested; deleting contents of D:Jenkins_ROOTTDECommon_LibrariesECM_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 /repository/TDE/Common_Libraries/ECM_Storage/project.pj
Preparing to execute si viewproject for #/repository/TDE#Common_Libraries/ECM_Storage
A SQL Exception was caught!
Table/View 'SCM_C380AD5E_FCBF_4350_8B88_0FE304E3C602' does not exist.
ERROR: Caught Derby SQLException!
Retrying after 10 seconds
Build was aborted
Aborted by Grigoriy Milman
Archiving artifacts
Recording fingerprints
Build failed! Skipping Integrity Checkpoint step!
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Finished: ABORTED
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_ROOTTDECommon_LibrariesECM_Storage
A clean copy is requested; deleting contents of D:Jenkins_ROOTTDECommon_LibrariesECM_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 /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_ROOTTDECommon_LibrariesECM_Storage
A clean copy is requested; deleting contents of D:Jenkins_ROOTTDECommon_LibrariesECM_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 /repository/TDE/Common_Libraries/ECM_Storage/project.pj
Preparing to execute si viewproject for #/repository/TDE#Common_Libraries/ECM_Storage
A SQL Exception was caught!
Table/View 'SCM_C380AD5E_FCBF_4350_8B88_0FE304E3C602' does not exist.
ERROR: Caught Derby SQLException!
Retrying after 10 seconds
Build was aborted
Aborted by Grigoriy Milman
Archiving artifacts
Recording fingerprints
Build failed! Skipping Integrity Checkpoint step!
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Finished: ABORTED
Attachments
PTC ALM added a comment -
Hi Grigoriy,
Have you re-created the build jobs post the upgrade to 2.0.2?
ShowHave you re-created the build jobs post the upgrade to 2.0.2?
PTC ALM added a comment - Hi Grigoriy, Have you re-created the build jobs post the upgrade to 2.0.2?
Hide Grigoriy Milman added a comment - - edited
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.
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
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 attached file config.xml is config for some of ours build job re-saved after upgrade.
ShowIf 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.
Grigoriy Milman added a comment - - edited 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 attached file config.xml is config for some of ours build job re-saved after upgrade.
Hide PTC ALM added a comment -
Its recommended to recreate the jobs, since we changed some of the code that relate to how the jobs are referred to in the Derby database. Not doing so may result in the 'Table/View 'SCM_C380AD5E_FCBF_4350_8B88_0FE304E3C602' does not exist.' sort of errors, that was there in the log you posted. We did put some precaution in for this error not to happen, if we did just a re-save, but not completely guaranteed.
The checkpoint error looks to be because because si checkpoint is happening at the time of some other operation that might be affecting the repository at the same time. The stacktrace on the Integrity Server would be more helpful in this case to diagnose (if this happening frequently).
Show PTC ALM added a comment - Its recommended to recreate the jobs, since we changed some of the code that relate to how the jobs are referred to in the Derby database. Not doing so may result in the 'Table/View 'SCM_C380AD5E_FCBF_4350_8B88_0FE304E3C602' does not exist.' sort of errors, that was there in the log you posted. We did put some precaution in for this error not to happen, if we did just a re-save, but not completely guaranteed. The checkpoint error looks to be because because si checkpoint is happening at the time of some other operation that might be affecting the repository at the same time. The stacktrace on the Integrity Server would be more helpful in this case to diagnose (if this happening frequently).
Hide Grigoriy Milman added a comment -
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:
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_ROOTNGMP.DIRECT.SandboxSWProductionToolsBuildProcessJenkinsMSEIGetBuildResults
A clean copy is requested; deleting contents of D:Jenkins_ROOTNGMP.DIRECT.SandboxSWProductionToolsBuildProcessJenkinsMSEIGetBuildResults
Populating clean workspace..
A Timeout Exception was caught. Failed to checkout contents of file!
null
ERROR: Failed to synchronize workspace!
Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Tools/Tools.pj#BuildProcess/JenkinsMSEI/GetBuildResults
Checkout directory is D:Jenkins_ROOTNGMP.DIRECT.SandboxSWProductionToolsBuildProcessJenkinsMSEIGetBuildResults
A clean copy is requested; deleting contents of D:Jenkins_ROOTNGMP.DIRECT.SandboxSWProductionToolsBuildProcessJenkinsMSEIGetBuildResults
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
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
![Hides 2 0 – keep a squeaky clean workspace cabinets Hides 2 0 – keep a squeaky clean workspace cabinets](https://cdn.fstoppers.com/styles/large-16-9/s3/lead/2018/02/fstoppers_photography_workstation_lead_1_0.jpg)
Grigoriy Milman added a comment - 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_ROOTNGMP.DIRECT.SandboxSWProductionToolsBuildProcessJenkinsMSEIGetBuildResults A clean copy is requested; deleting contents of D:Jenkins_ROOTNGMP.DIRECT.SandboxSWProductionToolsBuildProcessJenkinsMSEIGetBuildResults 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
Hide PTC ALM added a comment -
Based on the first exception(original job), can you try increasing the Checkout thread timeout parameter in the old job configuration to something greater than the default 5 mins? Say 10 mins or 15 mins and recheck.
I am not entirely sure why a new job would throw a Derby SQL exception. Just a couple of things for my understanding: did you 'copy' the existing job or created a brand new one from scratch? Also can you send across the IntegritySCM log for this scenario, if you can. The IntegritySCM logger setup can be found here: https://wiki.jenkins-ci.org/display/JENKINS/PTC+Integrity+Plugin#PTCIntegrityPlugin-Troubleshooting
Show PTC ALM added a comment - Based on the first exception(original job), can you try increasing the Checkout thread timeout parameter in the old job configuration to something greater than the default 5 mins? Say 10 mins or 15 mins and recheck. I am not entirely sure why a new job would throw a Derby SQL exception. Just a couple of things for my understanding: did you 'copy' the existing job or created a brand new one from scratch? Also can you send across the IntegritySCM log for this scenario, if you can. The IntegritySCM logger setup can be found here: https://wiki.jenkins-ci.org/display/JENKINS/PTC+Integrity+Plugin#PTCIntegrityPlugin-Troubleshooting
Hide Grigoriy Milman added a comment -
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.
Show1. 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.
Hides 2 0 – Keep A Squeaky Clean Workspace Cabinets
Grigoriy Milman added a comment - 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.
Hide Paul Sharpe added a comment -
I have exactly the same problem when upgrading my jobs from 1.36 to 2.2. Xnconvert.
As mentioned, it is not acceptable to create new jobs as we need to keep the history.
But as Grigoriy has stated, just updating the timeout parameter in the old jobs, seems to allow the checkout to proceed on the old jobs, without creating new ones.
Thanks Grigoriy!
So the solution to this issue, could be: Update the upgrade documentation and change the default timeout to not be 0?
ShowHides 2 0 – Keep A Squeaky Clean Workspace Floor
Paul Sharpe added a comment - I have exactly the same problem when upgrading my jobs from 1.36 to 2.2. As mentioned, it is not acceptable to create new jobs as we need to keep the history. But as Grigoriy has stated, just updating the timeout parameter in the old jobs, seems to allow the checkout to proceed on the old jobs, without creating new ones. Thanks Grigoriy! So the solution to this issue, could be: Update the upgrade documentation and change the default timeout to not be 0?
- Assignee:
- PTC ALM
- Reporter:
- Grigoriy Milman
- Votes:
- 0Vote for this issue
- Watchers:
- 3Start watching this issue
- Created:
- Updated:
Is your desk clean, right now?
Would it be something you would want your boss (or team members) to see?
It is easier than you think to keep your area clean and tidy.
The simplest way to keep your workspace in order is to practice the ABC method of organization.
Creating a Cluttered Workspace
A cluttered workspace is not productive. And piles are not organization.
Hides 2 0 – Keep A Squeaky Clean Workspace Clean
Yet, you are so busy, you never get around to cleaning up. Soon, your desk has turned into a large stack of miscellaneous stuff. Cleaning it up not only scares you, but could take several hours. (Or days???)
I challenge you to look at your desk right now.
What would it take to clean it up?
Keeping Your Desk Organized as Easy as ABC
Today, I want to share an organization strategy called the “ABC Method.”
Hides 2 0 – Keep A Squeaky Clean Workspace Jpmc
Quite simply, ABC stands for Always Be Cleaning. Ummy video downloader 1 53.
Keeping your desk clutter-free shouldn’t be an event that happens once in a blue moon. Rather, it must be an ongoing, constant activity that you do every day.
“Cleaning should be a habit, not a task.” (Tweet this Quote)
Here are some tips to Always Be Cleaning:
- Put Things in Their Place – A key habit to keeping your space organized is to have a “designated home” for each item that needs to be put away. Not only will it be easier to put things away, but you will know right where they are when you need an item again.
- Throw Things Out – Disposing of clutter needs to be a regular habit in your clean-up process. You simply cannot keep everything that comes your way. Most of the items you are keeping have no further use. Don’t be a packrat when it comes to papers, trinkets, and more. “When in doubt, throw it out.”
- Don’t Leave a Mess for Later – It can be tempting to tell yourself that you will “put things away later or tomorrow.” Resist that excuse, and always clean up immediately after finishing a task or project. Otherwise, you are compounding the amount of cleaning you will have to do in the future.
- Have a Chore List – A chores schedule can help keep you in regular clean-up mode. Designate routine maintenance tasks for specific days of the week. Maybe Monday is your clean off your desk day. Tuesday is your document scanning day. And so on.
- Eat Those Elephants – Big clean up tasks are easily attacked a little bit at a time. Spend 15 minutes catching up on that big task and soon you will have whittled it down to a manageable task. Of course, after cleaning becomes a habit, you should have less “elephant” tasks.
- Designate Clean Zones – Clean Zones are areas that you pledge to always keep clean. Designate trouble spots as clean zones and never allow clutter to be placed in these areas. This tactic works well for desktops, file cabinets or any other horizontal surface where clutter tends to pile up.
- Have Clean Up Time Every Day – Schedule 15 minutes of cleanup time each day. Perhaps, first thing when you come in. Or if you are really disciplined, before heading home. Put it right on your calendar so that you allocate time for it.
Always Be Cleaning
Don’t let your workspace build up clutter until cleaning it becomes an all-day endeavor.
It’s much easier and more productive to clean and organize as you go.
Always Be Cleaning and you will find that keeping your work area clean is much easier and productive than you thought.
Question: How do you keep your workspace clean? Are you always cleaning? You can leave a comment by clicking here.