I am unable to run GitVersion Task , after I updated the version to v4.0.0-beta.12 followed the guidelines and updated the Gitversion task
any help is appreciated. what did i miss here ?
gitversion Task:
output looks like this:
Take a look at this thread: Nuget Packager - how to specify GitVersion variables
This won't work on TFS2015 on prem as mentioned by
#chrisrpatterson due to limitation in the agent. There was a note
in the GitVersion documentation about this, which was removed since
this is implemented now in VSO, but might be a good idea to add it
back for the On-Prem case.
Not sure if it works well with new released build agent, try to update it.
As a workaround environment variables can be used in custom scripts. You could try to directly call GitVersion.exe command. Detail steps about how to handle this please refer this tutorial: Integrating GitVersion and Gitflow in your vNext Build
Related
In my project we are using QC to execute our test cases(QTP), moving forward we would be eliminating QC (for cost reasons).
As far as I explored MSBuild & Jenkins, they would be suitable.
But MSBuild will trigger the execution when a new build pushed to the repository. Also it will automatically test on the latest build.
Is there any other CI tool available to execute test cases through QTP?
I will be executing automation once in a release. Also we install our application by manual since it requires lots of configuration.
Take a look at HP Application Automation Tools.
This plugin basically replaces the need for QC, and is developed by HP.
Create a Jenkins job using this plugin on the same Jenkins installation used to build your code, then you can configure your job to run your tests as soon the code is available (e.g. on a nightly basis).
See here for a helpful guide on how to implement a simple Jenkins job using this plugin.
They also host the code on Github, which is very useful if you need to change the behavior of the plugin to suit your needs.
I'm currently setting up continuous integration using TFS/Visual Studio Team Services (was VS Online), and I'm using the Team Foundation Build 2015 tasks. So not the XAML builds.
I'm using it to build a Xamarin Android project, but that's pretty irreverent I guess,
The process should be like this:
After a check-in:
TFS should download the sources
TFS should increment the version number within AndroidManifest.xml
I've managed to do this by making a PowerShell script for this.
After the AndroidManifest.xml file is modified, it should be committed back into the TFS repository
Then the rest, build deploy into hockeyapp etc
The first steps are all configured, but I'm struggling with the commit part. How do I get TFS to commit the file? I don't really see any task suitable for it. I've tried using the Copy and Publish Build Artifacts Utility - But that did not seem to work, and I'm not even sure if that's the right utility
I'm using the default hosted build agent btw. Any help would be appreciated
Warning
I do want to point out that checking in changes as part of the build can lead to some features of VSTS/TFS not working. Association of work items to the checkin, sources and symbol generation, tractability from changes to build to release and integration with Test Manager, remote debugging, will likely not yield the expected results because the Changeset/commit recorded in te build may not match the actual sources. This may lead to unexpected funny behavior.
Also, if any new changes have already been committed/checked-in after the build has started, the version number may be updated in Source Control for code that was not actually released under that version.
So: First of all, it's considered a bad practice to change the sources from the build process.
Alternatives
There are better ways of doing it, one is to use the build version (Build_BuildNumber or Build_BuildID variables). Alternatively you an use a task like GitVersion to generate the semantic version based on the branch and tag in your git repository. That way your build will generate the correct version number and will increment the revision in case the same sources are built multiple times.
I understand, but I still want to check in my code as part of the build
If these things don't work for you and you still want to check in the changes as part of the build, you can either use the TFVC Build Tasks if you're using TFVC or use the Git Build Tools to add the remote to the local repository and then use the git commandline tools to commit and push the changes back to the repository.
These extensions require TFS Update 2 to install. But you can push the individual build tasks using the tfx commandlien tool. For the TFVC tasks the process is explained here.
On mac
On the mac it's going to be harder since you're using TFVC. My TFVC tasks leverage the TFS Client Object Model and Powershell to communicate to the TFS Server. The tf.exe tool doesn't even work on windows when you're in the context of a build, which is why I need to call into the VersionControlServer object directly. Given I'm dependent on these technologies, the tasks won't run on a Mac or Linux agent.
You could try to see whether the Team explorer Everywhere X-platform commandline works from the build agent (using a shell script). I have no way to test this on an actual Mac.
Given the cross platform nature of your project I'd recommend to move to Git, it integrates into XCode and Android Studio, making it easier to do a native UI or build on top of native libraries.
Alternative 2
You could setup a build which does the required changes to the code and then checks in the modified code. Then have a (CI) build run the Android and the Mac builds using the modified code.
I'm recently working with TFS 2015. I've realized that Microsoft has introduced a new way to configure TFS build pipelines which I think it is very intuitive.
Anyone knows if there is a mechanism to export or save these build configuration?
I think that it would be very useful to have the configuration into the versión control.
Thus, a user could review the history about how the pipeline has been changed. Also it would be possible to clone the build pipeline into another TFS continuous integration server.
Thanks!
Into source control? No. But go look at the "History" view on any build definition, it will show you exactly what you want: A full revision history of the build definition.
I'm attempting to set up a Xamarin iOS build on an internally hosted TFS 2015 build server. We have been working with this for a few months now and have used many of the contributed build tasks on GitHub and written a couple of our own.
So far we have only used tasks written using NodeJs and PowerShell. The Xamarin.iOS task is written using TypeScript and it seems our build agents don't have the required handler for this. We get this error when trying to run a build.
The definition for the task does not have a handler that matches any supported by this agent. Supported handlers: AzurePowerShell, AzurePowerShellHandler, PowerShell, PowerShellHandler, PowerShellExe, PowerShellExeHandler, Process, ProcessHandler
I'm not sure how to add this capability to the agents. Can anyone help?
Xamarin.iOS build task requires a Mac OS build agent, refer to this link for the configuration: Xplat build agents
Another reference may help: http://developer.xamarin.com/guides/cross-platform/ci/configuring_tfs/
I'm getting extremely frustrated. I've been trying to learn semantic web programming for the entire weekend and I've gotten no where. Nothing seems to build or work.
I'm new to using maven and gradle but I've followed all the steps.
Trying to build the stardog-example code
https://github.com/clarkparsia/stardog-examples
But when I run the gradle command, it says
"Url to Stardog repository is not defined, Set up the property 'stardogRepo' in gradle.properties.
I can't even find gradle.properties. Looked everyhere =/ It's not in the gradle folder either.
Any help will be appreciated
Sorry, those examples are in flux as we get ready for the Stardog 3 release.
Your best bet is to go back and check out the 2.2.x version of the examples.
We'll have it finalized for the release or shortly thereafter.