I have a project hosted on Sourceforge.net using Mercurial.
Are there any free continuous integration services that can interface with open source projects and start a build every time there is a push to upstream?
I have had a great experience with travic-ci.org (github) and drone.io (bitbucket) but now need something similar that integrates with sourceforge.
As a workaround I have set up a proxy-project bitbucket->drone.io that pulls the repository from sourceforge and builds it... but that is not really what I had in mind.
(I do not actually own the hosted project, so switching to github/bitbucket is not an option right now.)
That might be possible since March 11th, 2015.
See "How to use webhooks for Git, Mercurial, and SVN repositories": SourceForge has introduced webhooks!
It comes with webhook-management API.
Related
I am wanting to use VisualStudio.com to link work-items and user stories to source control check-ins for a current project of mine that is hosted on Codeplex.
The project is an open source project and has been hosted on Codeplex for several years. Now that I am doing a re-write, I am wanting to use an Agile process, creating user stories and building it in sprints, while I develop the app. The issue is that Codeplex's hosted TFS does not support this, while Visual Studio online does.
Visual Studio online is geared more towards closed-source projects with team members. It's offered for free, so I'm a bit bummed that they didn't open it up to support Open Source projects. Is there a way for me to have Visual Studio online host my source, and when I am ready to distribute a build, merge my branch in to Codeplex? I assume something along these lines is possible as the Prism team seems to do this with their releases. Since I don't have control over either TFS though, I'm not sure if external parties can do this or not.
If you use git on both projects (you can ask the Codeplex team to convert your project for you) then you can simply set up your git repo with two remotes.
Do you work locally and push to the main VSO git repo whenever you wish. When you've made enough changes that you want to push to Codeplex, just do a separate push to that remote and it'll be good to go.
If you're using TFVC on both then you're out of luck, unless you want to mess with the TFS Integration Platform (which I wouldn't recommend)
my team is working on a project but we figured out if we continue, committing the changes we're making will be different. The option we're considering is to share the project on an adhoc wireless connection and work on it together but I'm wondering if there's a better way of doing this, like one that will allow you see that a different user is working on a class when you open it (like Google Documents) etc.. Thanks.
ps: I'm looking into the Team Foundation Server, but it sounds a bit complex, though I'm downloading the trial now, I don't know if it's what I'm looking for...
If you have a MSDN account install Team Foundation Server in Basic configuration or do what KMoraz told you: use TFS Express (it's still a beta, but it's "go live" so don't be afraid to use it). You can install both version on any kind of computer (yours for instance but it will have to be started all the time your teammates are working).
I strongly encourage you to give a try to tfspreview.com (Team Foundation Services) which is the cloud version of TFS, it's free for now (as long as it's beta) but Microsoft always said that it won't cost a lot when going retail.
Team Foundation Services is really great, you know have continuous integration in the cloud, it's pretty nice. I can give you more info about it if you're interested.
GIT, GIT, GIT.
GIT is a simple free solution to this problem. It merges files modified by multiple users very well.
GIT with VS.NET
GIT
I'm totaly newbie to Source Control idea, so please be kind.
My situation is that we are a development team which contains 2 developers and 1 designer.
We use Visual Studio 2010 and we need to use a Git as a Source Control.
I've installed Git Source Control Provider and GitExtensions using Extensions Manager on all machines.
But there is only one thing I don't get it, how can I configure every Git on every machine to find a central repositry where we can Push and Update all work in one place?
Does that mean everyone will take a copy of a solution into his own machine (Locally) and configure Git to a repositry OR are we going to run on the same solution?
Honestly, I have not found articles regarding this issue and how teams on same project on Visual Studio 2010?
Git is distributed version control system means that whenever you clone a repository you can work on your copy and commit too. Once you done you can push the commits to remote repository.
My company is currently implementing a versioning system using Mercurial and BitBucket. We currently have respositories set up on bitbucket and are able to use them, but our work processes for doing so are a bit clunky. We use Visual Studio for web programming in .Net. Currently, we have set up a cloned repository locally and work from there. We can do this using Visual Studio with VisualHg.
In order to edit files we open them in Visual Studio from the local repository and make our edits. We then commit our changes to Hg, which updates the repository as it should. Then we need to FTP the files from our local system to the DEV server for testing and then FTP again to the Production server once QA is completed and approved.
It would help streamline things if we could have the BitBucket repository synced with our DEV server so that all that was required is to commit changes for testing in DEV, bypassing the otherwise necessary step of locating and FTP'ing all relevant files.
Does anyone know if this is possible? If so, can you point me to any documentation that would show me how to set this up? Our developers would be eternally grateful. Thanks for your time.
In my opinion, using Mercurial is not the correct solution for this problem.
The main reason for it not being the correct solution is that the files that are in Mercurial are not the files that you want on the production server and so aren't the files that you want to use on your development server (because you want the QA environment to be as close to the production environment as possible). There are no assembly files stored in Mercurial (or there shouldn't be) and those are the files that the server should be using to run the application.
There are deployment tools built into Visual Studio that you can use for this task. They can be configured to upload all the necessary files with one button click.
Scott Hanselman has a post on his blog about this.
Troy Hunt takes it one step further by introducing a build server with this excellent set of posts. It uses Subversion as the repository but it can be done using Mercurial too.
I prefer the build server method as, once you have it set up correctly, it makes it 100% reliable. It will do the same thing every time you ask it to do the deployment. If you use Visual Studio to do it the developer doing the publish could choose different options and get it wrong.
Our dev team is small (3 developers) and windows based.
I'm looking for a source control that can do the following:
Check out files for editing and warn others that file is used
Check in files and merge if they have changed
Split baselines for release versions and merge baselines if needed
Visual Studio integration
Can work over WAN
Thanks.
SW
Team Foundation Server fits all of those.
SVN would be great, as long as you use locking (normally the server has no idea what clients are doing by default)
Perforce might be a nice one to look at which does this more by default.
Both have VS integration, SVN especially.
SVN, provided that you explicitly lock the files. This is not by default, but you can easily lock the file via SVN commands or via TortoiseSVN.
VisualSVN provides the Visual Studio integration.
If you want good Visual Studio Integration, then check out Microsoft Team System. You didn't specify if you wanted free or commercial or how critical Visual Studio intergration was.
git will do almost all of it. Not sure about integrating it with Visual Studio though. there might be a plugin for that.
Reasons:
No central server needed. If you want one, you can have one, but it's not necessary
You can push/pull changes to the others at will.
Each of you can have your own local branches, and push only the ones you need to
each other. Branching/merging is easy enough to do branch-per-task. Then push just that task to a co-worker if needed.
Unlike SVN, only one directory is needed for git, in the top level of the directory structure.
git stash rocks for when you have changes in your current branch, and need to switch to another for a while. This is one of those things you don't miss until you don't have.
Merges are awesome.