I have just begun using TFS command line version. I love it. However, I need to know how to find an App Release that is associated/assigned to a given Branch (A) and (B) how to retrieve that App Release using TFS Command Line.
Is there a way to do this?
Thank you!!
I am lost on this one, after having spent a fair amount of time search the TFS Help files (tf vc help, etc.), Google, DuckDuckgo, etc.
tf vc help
I would like to see the App Release using TFS Command Line.
Just as Daniel suggested in the comment.
We recommend to use Rest API to fetch such kind of information.
You could either use some 3rd-party extension to Auto App Version.
Or you could link work items to a release or use Rest API to query release info in an 3rd-party/powershell task.
Kindly refer this blog-- Auto-generating release notes in Azure DevOps pipelines
tf.exe command which is used to run version control commands. Also have some limitations, it only work with TFVC not work with git.
Is there any trick to just get a specific version of just a solution? I have a large number of solutions and support libraries in the source code tree. I would prefer not to have to bring all of them down when I build a sandbox of a specific labelled version. In VS2015, I can open a specific solution, but is there a way to specify the label when I do this?
It is not possible to choose the version of the solution when opening it.
You can however choose to get a specific version of the solution and its projects when getting the source code locally. You can do this by right clicking the solution folder in the Source Control Explorer and selecting Get Specific Version. Here you can select a specific version either by specifying a changeset, label or date.
I think I have a solution with the suggestion from Tore. You can use the File/Source Control/Advanced/Open From Server... to load the latest version of a solution into your sandbox. Once you have the latest, you can use Tore's suggestion of Right Clicking on the solution then Source Control/Get Specific Version... to pull down the labelled version you want to work on. This appears to limit the file structure of the sandbox to just the files you need to build the solution.
Seems to work with the limited number of labelled version I have. Will update this post if I have trouble with more history in the vault.
We are constantly doing changes to the ETL program (IBM Datastage 8.5) and mostly in the same project folder.
There are so many versions of code which confuses the developer at the point of implementation.
What I am looking for is a GitHub thingy for datastage codes..
Can the experts please assist me...
Thanks!
Datastage is pretty terrible when it comes to version control.
Different organizations use different tools to try and get some amount of version control in place.
for example
1. they would store the latest dsx of the code in a server.
2. and from there on use SVN to check in and check out the code.
3. So if you need to work on a code you would first check if anyone has checked it out if not then proceed to extract the latest version of the dsx from SVN ; check out the dsx in SVN ;
4. import and make the changes ;
5. take the export of the changed code ;
6. check it back in at SVN
I know its not a solution really but probably your best bet in large developer environment.
We have InfoSphere Information Server Manager and its available with DataStage installation .
Use InfoSphere Information Server Manager to create deployment packages for
DataStage Components .
and get any good version control Tool to maintain versions .
Example - you can use eclipse SVN Version utility
To start this process , always get latest code from LIVE Env and make the changes in Test Env Or other Env.
before deployment -
use InfoSphere Information Server Manager to create backup package of related DataStage component in Prod and get the version number for that from SVN
create the package for modified jobs and send it to Live Env with out replacing the existing or running code .
get version number for this package from SVN .
Deployment -
Use InfoSphere Information Server Manager replace the existing code with new one .
Rollback the code to previous version if any problem with new deplyment
Currently I'm using the option to export jobs as dsx files do versionate them.
So, when I need to rollback to an previous version, just use the import objects option and select the exported dsx file.
Those following this thread might be interested to know that my organisation's solution for implementing DevOps approaches with DataStage development (called 'MettleCI') has now been announced on the Atlassian Marketplace:
https://marketplace.atlassian.com/plugins/com.datamigrators.atlassian.bitbucket.mettleci/
MettleCI Website
Example of DataStage job in Git
Does TFS have a way to indicate that I have gotten an old version of a file?
I have previously used Accurev which will put the old version in your default group. So I'm wondering if TFS shows this information somewhere?
If you look in Source Control Explorer, there is a column called "Latest". It would show Yes, if you have the latest file and No" if you don't have the latest version.
Please be mindful it doesn't scan your file contents to see if you have the latest. For example, if you have manually updated the file in your local drive without using TFS, the latest column will still show the status it was in before.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
What is a version control system? How is Git useful?
I am new to Ruby on Rails platform, and so this may sound a little naive.
Why and when do we store our work in a version control system like git?
I mean what is the advantage of it ! Can't we just keep it in our local machine ?
Advantages for using git/source control:
For yourself
Remembering what you have coded and when you did it
Being able to compare what you did to previous work
Allow you to work on something experimental, and if it doesn't work switch it back to where it was before
Working with a team
It makes working with others easier - you can work on the same file at the same time and really easily combine your changes.
It will allow you to work in multiple locations and easily have the most recent code
It will help in deploying your code to a server
Git workflow for teams
Git branching model
When to store or commit your work:
You want to do this each time you finish on a particular "idea" or piece of work you are working on. This means you can have a useful commit message and can go back im time to that feature you just wrote or that bug that you just fixed.
How often and when to commit
Reasons for using Git over other source control
Its fast (switching branches is really fast and you have a local copy, so you dont have to communicate to a server for a lot of things unless you want to push or pull changes to the server)
Yes, this seems quite naive, but every question is worth asking!
First of all, using a SCM (software configuration manager) will greatly help you in a number of scenarios:
trying out experimental features without touching the main code
developing several independent ideas at the same time
recovering from failed changes, whenever they are complex and include changes in multiple files.
tracking the exact code used in a specific release, to fix a reported bug.
This doesn't even start to touch the infinite amount of work you'd have if working in a team without SCM.
And using a SCM doesn't involve network, git and any other distributed SCM is equally valid for local development, as the repository is all in your computer. You just don't pull and push.
The choice is not whether to store code in version control versus storing it on your local machine. In fact, unlike other version control systems (like Subversion, known also as svn), Git does not need a server to run.
Version control makes it easy to understand what changes were made, view and restore older versions of files, and even import changes from one version to another.
RETRIEVAL: Imagine you are working on a project on your own. You delete an old file you don't think you need anymore. A week later, you realize that the file was very important. If you use version control, you can see what the file looked like just before you deleted it, and restore it as if it were never deleted. Also, most changes committed to version control contain messages; if you join a team and the previous developer used version control (with good commit messages) you can get an easier context for when changes were made and why.
MULTIPLE RELEASES (BRANCHES): Now imagine that your software is version 1.0. You're busy working on version 2.0, but someone files a bug. What can you do? With version control, you can zoom back to version 1.0, make some changes, and then create version 1.0.1. Most version control platforms even let you apply the changes made in version 1.0.1 onto the work you're doing in version 2.0.
MULTIPLE FEATURES: Your software is so successful, you start releasing it weekly. However, not every feature is ready for release. First you start working on the widget feature, than you start working on the doodad feature. If you work on both of these at the same time, you may have two half-coded features in development at the same time, and nothing is working well enough to release. With version control, once one of the features is done, you can merge it into the "main" release as if you wrote it in one day.
COLLABORATION: Finally, now imagine that you're in a team of five or six developers all working on the same code. Naturally, you don't want to email zip files of code back and forth, especially when every developer is working on a separate feature. With version control, you can have a single history, to which all of your developers write and read.
Naturally, some of the above can be done by keeping multiple copies of the same files in different adjacent directories. The benefit of version control software is that it can handle much of the work for you while avoiding duplicating the same file over and over on your disk.
Long winded--sorry--but hope that helps!
Advantages of using git:
Code will be safe in remote repo, even if the local project crashes
You can try out new things without worrying about previous works as they can retrieved
The code can accessed from anywhere in the world
When working in team, all the work will be stored in a single place so that it will be accessible to everybody in your team
Each and every change can be tracked easily, who did it and when they did it
Deployment of application will more easier
You can have multiple versions/branches so that it will be easy for you to identify the new features added to the application in every version
you see #arulmr, #kieran-andrews, #Jeff and #rewritten that post many advantages but still if you want learn more in details you can see below links
1) http://git-scm.com/book/ch8-1.html
2) http://www-oss.fnal.gov/~mengel/git_vs_subversion.html.bak
3) https://git.wiki.kernel.org/index.php/GitSvnComparison
4) http://www.wikivs.com/wiki/Git_vs_Subversion #History, Architecture, Licensing, Performance, Features of git and svn
now the difference between git and subversion
1) http://boxysystems.com/index.php/5-fundamental-differences-between-git-svn/