i will click changeset Details
and can i use sdk to popup this window???
You can do it via command line as follows: tf changeset 13684I am not aware of a direct way to get the same kind of thing via SDK, but, if you have to do with code, you can always wrap the console-call.
Related
I have created multiple applications from boilerplate templates and for some reason, it is no longer possible to download the Starter Code. I open the application panel, select Start Coding in the left pane, then select Eclipse Tools for Bluemix. Further down, as expected, there is a "Download Starter Code" button, but it links back to bluemix.net instead of to a code archive file. Has anyone seen this? I have deleted / re-created the apps many times, but it never produces an archive. I have seen several posts here on Starter Code, but none specifically with this issue.
In some cases this behaviour is related to the browser language setting. Try setting it to English (if you use another language) and check if the download button url now points to the correct zip.
Another possible workaround is to instantiate one of the boilerplates and then click on the Add Git button at the top right hand of the screen when viewing the overview of the running app. Using the Add Git button on a boilerplate (or runtime) instantiated app you can see the sample code in DevOps Service. You can download it from there or you could git clone the repository and get the code that way.
Alternatively please take a look at the IBM Bluemix repo on GitHub.
you can do same by three ways you can also clone git repository of starter code or you can download commandline interface and fallow instruction
for me while developing node application download eclipse archive worked fine
Is there any recommendable solution to integrate SVN with TFS 2013 in a sense that SVN is being used for source control and TFS for work item tracking?
For example, it should be possible to link commits in SVN to work items in TFS.
You can use Integration with Bug Tracking Systems / Issue Trackers: http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-bugtracker.html
It is very common in Software Development for changes to be related to
a specific bug or issue ID. Users of bug tracking systems (issue
trackers) would like to associate the changes they make in Subversion
with a specific ID in their issue tracker. Most issue trackers
therefore provide a pre-commit hook script which parses the log
message to find the bug ID with which the commit is associated. This
is somewhat error prone since it relies on the user to write the log
message properly so that the pre-commit hook script can parse it
correctly.
TortoiseSVN can help the user in two ways:
When the user enters a log message, a well defined line including the
issue number associated with the commit can be added automatically.
This reduces the risk that the user enters the issue number in a way
the bug tracking tools can't parse correctly.
Or TortoiseSVN can highlight the part of the entered log message which
is recognized by the issue tracker. That way the user knows that the
log message can be parsed correctly.
When the user browses the log messages, TortoiseSVN creates a link out
of each bug ID in the log message which fires up the browser to the
issue mentioned.
Go through mentioned URL for detailed description.
https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-bugtracker.html describes how to configure folders in TortoiseSVN to do a one-way integration between file versions committed in TortoiseSVN, and work items in TFS. When a developer commits the file version, he/she is prompted for the TFS work item number (which works fine if the developer knows the number). It even creates a link to the TFS work item in the Revision Log of the file in TortoiseSVN. However, it does not display a list of work items for the developer to choose from, nor is there any link in the TFS work item going back to the committed file version in TortoiseSVN. (It is possible to write an issue tracker plug-in for TFS to do this, but all the plug-ins I have found on the internet seem to be for older versions of TFS.)
This integration will insert the bug number into the Revision Log of committed source files, and will add a link from the log to the selected bug in TFS. Although you make this change inside your working copy, it will apply to the same folder in other working copies once those working copies have been updated.
To associate a folder tree in TortoiseSVN to TFS:
1. Right-click on the folder in your working copy. This should be at the apex of the folder tree you want to associate with a project in TFS. Select TortoiseSVN > Properties.
2. On the Properties - TortoiseSVN window, check to see whether there are any bugtraq properties for this folder. If not, click New > Bugtraq (issue tracking integration).
3. The Edit Bugtraq Properties - TortoiseSVN window opens.
a. For Issue tracker URL, specify the URL to your work items:
http://tfs_server_name:8080/tfs/DefaultCollection/TFS_Project_Name/_workitems?id=%BUGID%&_a=edit
b. Next, place a check in the "Remind me to enter a bug-ID" checkbox.
c. For Message Pattern, specify something like:
TFS Work Item: %BUGID%
d. For Message Label, specify something like:
TFS Work Item:
e. For "Bug-id is", specify Numeric.
f. At the bottom of the window, place a check next to "Apply property recursively". Click OK.
4. Back on the Properties - TortoiseSVN window, verify that the bugtraq properties have been added and click OK.
5. Remember to perform an SVN Update and SVN Commit on the folder after changing its bugtraq properties.
The bugtraq properties that implement this one-way integration between SVN and TFS are built into Apache Subversion and so should work for SVN even if you are not using the TortoiseSVN user interface.
I need to migrate my Xcode Bot to another repository and I wish to keep build history. In the edit bot interface (both browser and Xcode) repository field is not editable. How can I migrate?
OS X Server version 3.1.2
This is an old question but i suspect people will find this and look for an answer as it is the top result in google. This is how you do it:
change the repo you point to in git
open your Xcode project, select the bot and hit edit bot
in the repositories tab, uncheck the one that you want to update
hit done
go back to edit bot
you should now see the new repo instead of the old one
I know the ID of a changeset that im interested in seeing the details of. Is there anywhere i can enter the ID of a changeset in order to see what changes were included in the commit without having to know what branch the change was made in?
Im using VS2010 / TFS2010.
Set the focus on SourceControlExplorer in VS and press CTRL+G
In the Source Control Explorer in VS2010, click the "Find Changeset" icon on the toolbar.
From the command line you can use 'tf.exe changeset ID'.
Be aware that your current directory needs to be a mapped workspace on the server you're trying to look up the changeset on. Otherwise you need to specify /s:servername (e.g. /s:http://tfsserver:8080/tfs
Extension to Rassi's answer to get everything on command prompt
From the command line you can use tf.exe changeset <<changeset ID>> /noprompt
Microsoft link
When I get latest from TFS source control, I don't see the changes made to my workspace.
I know I can go to the Output window and see the changes, but this is just a text list with no context actions.
What I really want is to see a list of changes, with the ability to right-click a file and see differences straight away.
Is there a better, alternative way to see changes like this after getting latest?
Sounds like using the command line tool tf.exe with folderdiff command would achieve what you need.
Use the folderdiff command to display
and compare a visual representation of
the differences between files in two
server folders, in a server folder and
a local folder, or in two local
folders.
From the header toolbar click the "Find Chengsets" option (it is between History and Branch options), it will open a dialog box, on that fill your required attributes and click Find button on that dialog box.