Common Problems Archives - scmGalaxy https://www.scmgalaxy.com/tutorials/tag/common-problems/ A Platform for Software Engineers Sat, 27 Feb 2021 09:55:39 +0000 en-US hourly 1 https://wordpress.org/?v=7.1 Common Problems in DevOps | DevOps Adoption Challenges https://www.scmgalaxy.com/tutorials/common-problems-in-devops/ https://www.scmgalaxy.com/tutorials/common-problems-in-devops/#comments Sun, 12 Mar 2017 23:55:44 +0000 http://www.scmgalaxy.com/tutorials/2017/03/12/common-problems-in-devops/ As 2017 has started, this the time everyone has tied up there shoes for the New Challenges that already has […]

The post Common Problems in DevOps | DevOps Adoption Challenges appeared first on scmGalaxy.

]]>
As 2017 has started, this the time everyone has tied up there shoes for the New Challenges that already has been knocked the door in 2016. Back last year, we heard from the industry itself, at a CIO engagement, that the biggest challenge for DevOps is keeping Ops a integral in DEV. According to him, to have a successful implementation was to complete cut Ops team out of the strategic leadership discussion. Someone raised the his voice and asked “will you be able to call it DevOps than ?” Without operations, DevOps will remain DEV only. So, Usage could a chance to be hindered Toward absence of inclusion starting with both the benefits of the business also engineering heading as the team initiates and creates the new DevOps Culture.
So Top challenges are Keeping up Silos, Starting for DEV and completion with ops as an bit of hindsight, Treating DevOps as a project rather than a culture shift, disengaging, delegating and disconnecting from the DevOps shift and also, starting with technology solutions.
1. Keeping up Silos – The political scene of an organization could altogether move slow your DevOps activity. DevOps usage might fizzle with figure it out their full possibility quality Assuming that those methodology is as well limited or if it supports the current silos As opposed to surveying how the new transform Further more harder to distinguish Furthermore unite copy sets for figure and information.
2. Starting for DEV and completion with OPS as an bit of hindsight – People who tried to develop their DevOps strategy within DEV, while not concluding Ops team, got failed. And, till the time operations team comes in picture or pulled operations team into it, time already has slipped out. Scalability, Reliability, Serviceability and Security which comes into operation and are known for expert of these area has not been consulted. Result implementation fell apart.
To ensure success, consult the right people. Seat together and discuss. In order to reduce the political friction that can lead to failure, re-imaging the software development life-cycle process as one technology initiative.
3. Treating DevOps as a project rather than a culture shift – In IT industry where DevOps exists, it become a point of political friction within a company with different teams. This proceed towards often fails because DevOps is a culture shift. Importantly cutting out one team or keeping DevOps in a vacuum does not gonna change the outcome which is Failed. This only increase the friction but also introduce the risk factor.
CI/CD process from development having remarkable impact on the network performance and ISP costs. Treating DevOps as a DEV project will result failure of the project without getting support from Operations and their knowledge.
4. Disengaging, Delegating and Disconnecting from the DevOps Shift – DevOps did not catch on as there was too much resistance to the cultural shift. Technology leadership must stay completely engaged and involved to ensure the success of both DevOps and the overarching Digital Transformation the company is going through.
5. Starting with Technology Solutions – One of the important and notable mistakes repeated by various tech guys is focusing on technology rather than customers requirement which results, they end up with solutions that fail to fulfill the minimal requirements for the company to be successful. It hard location this challenge Toward working with its benefits of the business counterparts will get it the “people” and “process” parts former to recommending technology results. An user-centric administration methodology will also help streamline the methodology on distil necessities down of the negligible feasible result.

The post Common Problems in DevOps | DevOps Adoption Challenges appeared first on scmGalaxy.

]]> https://www.scmgalaxy.com/tutorials/common-problems-in-devops/feed/ 1 List of 5 Common Problems in CVS – Troubleshooting Guide https://www.scmgalaxy.com/tutorials/common-problems-in-cvs/ https://www.scmgalaxy.com/tutorials/common-problems-in-cvs/#comments Fri, 30 Jan 2009 07:33:28 +0000 http://www.scmgalaxy.com/tutorials/2009/01/30/common-problems-in-cvs/ List of 5 Common Problems in CVS – Troubleshooting Guide Problem 1:- How will we modify our conflict occurred files […]

The post List of 5 Common Problems in CVS – Troubleshooting Guide appeared first on scmGalaxy.

]]> cvs-common-problems

List of 5 Common Problems in CVS – Troubleshooting Guide

  • Problem 1:- How will we modify our conflict occurred files ?

While updating if you will get message like bellow, then check,

This will list:

* “A filename” for files that you added
* “M filename” for files that you modified
* “C filename” for files that have conflicts

Conflicts are files that you modified and that were modified on the head revision as well.

@ If u ll get C or conflict then go to that file and remove that lines and duplicate line then it will recover, it because, if more than two developer working on same file and comming on same time then conflict occures,

Files with conflicts will have conflict markers in them. Conflict markers look like:

<<<<<<< filename
your lines
=======
other person’s lines
>>>>>>> current version

  • Problem 2:-

If you are using your colleague’s checked out code for some changes, after that If you made any changes in code and then if you will try to check-in the code in CVS from your machine,after that if  it will ask your colleague’s password for checking-in. So How will we resolve this one ?

Soln:-
Please fine the CVS dir on your present code directory, then go to CVS dirctory, there, you will find Entries, Root, Repository like files , So now open that Rot file and change that username then your problem will solve, else let me know.
Steps:
cd CVS
vim Root
edit present urername to your username
@cvs:
:wq   // save and quit
cd ..  // come to parent directory
then do your work ..
it will fine

  • Problem 3:-
    Is there any way to identify the information of deleted lines in a file through CVS annotate or any other means?

Soln:-

         You deleted from CVS or local server ? if u deleted from both server then i have to see, else if u deleted from      either local server or CVS server  then do “cvs -q up -Pd  “

else do “ cvs -q up -Pd -r  ” .

  •  Problem4:-

           When I view the “cvs log”, the log report is fetching the file but says

            “date: 2008/12/31 06:00:51;  author: amareshcd;  state: Exp;  lines: +0 -0”
But I have added with 130 lines. Why the log is not showing “+130 -0” in its report.   ?

Soln:-

Use ,“cvs log -d date1 logfile.log”

  •  Problem5:-

        I have files that went into the Attic.  How do I restore them back? Viewing  the files  revealed that they’re in DEAD State. Someone has ‘cvs remove’d the files. Just restore them with ‘cvs add’. How ?

Soln:-

Step1:-
cvs log
Step2:-
Find til newest non-dead version
step 3:-
cvs update -r
step4:-
mv foo
step 5:-
cvs update -A
step 6:-
mv foo
step 7:-
cvs add
step 8:-
cvs commit -m “bring out your dead”

The post List of 5 Common Problems in CVS – Troubleshooting Guide appeared first on scmGalaxy.

]]> https://www.scmgalaxy.com/tutorials/common-problems-in-cvs/feed/ 1