nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Compare version and import source code with colour formatting in excel sheet

CharuS

Could you please advise it is possible to import the source code comparison results from a file versions in a excel sheet without losing the highlighted red colour differences of the file?

regards

Charu Sachdeva

Find more posts tagged with

Comments

Adam Stoller

probably not - at least not using TeamSite's diff-tool. You might be able to do it using something like Beyond Compare, though putting it into an Excel spreadsheet seems dubious / questionable.

CharuS

Ok. Thanks for the reply.

But I need details in spread sheet only. I will try what can be done or alternate to this

regards

Charu

Rick Poulin

Can you explain why? It doesn't really make any sense to be putting source code in a spreadsheet* format.

Adam Stoller

I think you meant "spreadsheet" not "stylesheet" - but more to the point what does the OP mean by "detail"?

CharuS

Sorry for delay in reply. I was in training so couldn’t able to reply.

Basically, my client have 2 different vendors, one handles the production website using production TeamSite and other (my company) handles all the pre-production websites using pre-production TeamSite.

The production and pre-production TeamSite have exactly same files, branches, structure and content but managed using different TeamSite servers, users and companies.
I recently joined this company so don’t know much working details yet.

Now, the changes (frontend/backend/java) go in every 3 months planned release cycle and multiple releases are being worked upon in parallel.

The development team of our company make the changes and test on development, UAT and Prelive environment and provide all the details of the changes done in TeamSite properties file on pre-production TeamSIte to other vendor (company) to update the files on production TeamSite and promote to Live.

As it is 3 months release cycle and multiple releases are being worked upon in parallel so for development team it is too much work to update TeamSite files and also maintain a spread sheet with all the changes.

It prone to mistakes as well...sometimes the development team doesn’t remember what changes were done 3 months ago or they forgotten to update the spreadsheet.

That’s the reason we want the view source of TeamSite files to be copied in a spreadsheet.
As it was not getting possible to copy voew source of TeamSite files in a spreadsheet using TeamSite provided features or CLTS so we wrote a perl script to achieve that.

The perl script works as follows:

For example we have two files attached in a workflow 'old.properties' and 'new.properties'

1) Read all the files having .properties extension from a workflow and store in a array.

2) Copy .properties files from array to a new workarea called "CompareFileDifference". In this case it will copy old.properties and new.properties in "CompareFileDifference" workarea

3) Now rename old.properties and new.properties to old_new.properties and new_new.properties i.e. append “_new” to all the properties files in that workarea ‘CompareFileDifference’.

4) Now search for the same files old.properties and new.properties in the STAGING path corresponding to the files attached in the workflow

5) If the same files exist in STAGING, then copy staging version of the files i.e. old.properties and new.properties into that same workarea "CompareFileDifference"

6) Now "CompareFileDifference" workarea has a two version of files i.e. a STAGING version (old.properties and new.properties) and workarea version (where the developer made the changes and attached in the workflow and we rename it to old_new.properties and new_new.properties) to compare the files

7) The script will compare the difference in the files and create a .cvs file listing all the differences
The script executes 100% fine when I executed on the server directly but as soon as I attached the script in workflow and executing via workflow it is getting stuck at point number 3 which is rename old.properties and new.properties to old_new.properties and new_new.properties i.e. append “_new” to all the properties files in that workarea ‘CompareFileDifference’.

The logger in the script shows that the file has been renamed but in the workarea it is not showing the renamed files.

I have attached the script which I used for executing on server and which I used for executing via workflow

Could you please have a look and advise why the script is not executing via workflow.

Do we have some limitation in renaming the file in a workarea via teamsite workflows?

Please advice

Regards
Charu Sachdeva

Rick Poulin

http://en.wikipedia.org/wiki/Revision_control

Adam Stoller

The scripts are pretty badly written IMO - and as such, I'd be highly skeptical of the skill set of the person who wrote them (if that's you - sorry, but I call them as I see them)
The logic behind the scripts seems rather questionable too - specifically steps 2-6. Why not just compare the files where they actually are rather than copying and renaming them all over the place?
The rationale behind the need for the script appears to be that you have a bunch of unskilled and/or lazy developers who don't know how to keep track of their changes or record their changes when submitting them - and thus you need to re-list the differences in a file (why a spreadsheet?) in order to help them do the work they should have been doing all along. This seems like a poor approach to react to the effects of the problem rather than trying to actually solve the causes.

Why the script doesn't work when called from with the workflow I have no idea, and I'm not going to spend a bunch of my time - for free - trying to diagnose badly written code outside of the environment in which it is being run (including the fact that the code relies on custom modules that I don't have).

If you want to hire me (or someone else who's skilled in these matters) to come in and attempt to fix the problem - fine - but I think this is a much bigger issue than can be resolved in the forums.

CharuS

Please ignore, i have resolved the issue myself

Thanks for your time and suggestions.

regards

Charu Sachdeva