Slide 1
Most trusted JOB oriented professional program
DevOps Certified Professional (DCP)

Take your first step into the world of DevOps with this course, which will help you to learn about the methodologies and tools used to develop, deploy, and operate high-quality software.

Slide 2
DevOps to DevSecOps – Learn the evolution
DevSecOps Certified Professional (DSOCP)

Learn to automate security into a fast-paced DevOps environment using various open-source tools and scripts.

Slide 2
Get certified in the new tech skill to rule the industry
Site Reliability Engineering (SRE) Certified Professional

A method of measuring and achieving reliability through engineering and operations work – developed by Google to manage services.

Slide 2
Master the art of DevOps
Master in DevOps Engineering (MDE)

Get enrolled for the most advanced and only course in the WORLD which can make you an expert and proficient Architect in DevOps, DevSecOps and Site Reliability Engineering (SRE) principles together.

Slide 2
Gain expertise and certified yourself
Azure DevOps Solutions Expert

Learn about the DevOps services available on Azure and how you can use them to make your workflow more efficient.

Slide 3
Learn and get certified
AWS Certified DevOps Professional

Learn about the DevOps services offered by AWS and how you can use them to make your workflow more efficient.

previous arrow
next arrow

Find perforce Label info from Workspace

Spread the Knowledge

scmuser created the topic: Find perforce Label info from Workspace
Hi,

I have perforce workspace which is synced with p4 label specification. i want to know which label has been sync here in my workspace.

Could you please let me know the command for this?

mnanjala replied the topic: Re:Find perforce Label info from Workspace
It’s not easy, especially when you consider that the workspace might be only partly synced to that label. i.e, the label was used with a more restrictive path than that in the label itself.

One rather crude method is to take each label that might apply to the workspace (you can determine this by the view in the labels, or if you use a meaningful naming convention) and do a test sync (p4 sync -n) of each one in the workspace. With luck, only one of them will show zero actions. However, it’s possible that more than one will seem correct, or that none of them will.Essentially, you’re trying to access label information backwards.
They are aliases for a particular state of the repository, but are not a state in and of themselves. (I.e., “synced to which label” isn’t really meaningful in Perforce.)

If you need to duplicate the state of a workspace into another workspace, are you aware that workspace names are also labels?
You can sync one workspace to the same state as another by using the other workspace’s name. (Assuming the views are compatible.)

Rajesh Kumar