|
We still use CC but are looking to move to Jenkins soon-ish.
You don't have to be mad to live here [UK], but it helps.
|
|
|
|
|
|
Question is worded so that you should be able to select more than one (and I use more than one*), but it's set up as a radio button not checkboxes.
- Jenkins (to AWS), azure dev ops (to Azure), and WT
![Elephant | [mastadon]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/elephant.gif) BitBucket offers (Android app).
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Agreed. I used Azure DevOps (to Azure) and TeamCity
|
|
|
|
|
Only need one option - "We don't use any..." 
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
I second that. We also use Azure DevOps and Jenkins
If you are not criticized, you may not be doing much.
|
|
|
|
|
We use for our Asp.net core web apps Teamcity for CI stuff and Octopus Deploy for the CD part. We're using it a few years now
P.S. Option was also missing. Might be better to have the option to check more than one tool..?
|
|
|
|
|
We use the same CI / CD stack 
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
What's that? 
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Azure DevOps (formerly Visual Studio Team Services, or VSTS, and before that Visual Studio Online, or VSO (not to be confused with the new Visual Studio Online which just offers Visual Studio, online)).
People may also be familiar with the on-premises version: Team Foundation Server, or TFS, which was re-branded as Azure DevOps Server.
I went for "other", but how could this be missed? 
Maybe it's on the list, but under yet another name? 
|
|
|
|
|
We use the features of GitHub & AppCenter.ms.
Basic stuff, but enought for us.
|
|
|
|
|
Simple, easy to integrate and enough as a tool.
Have not heard most of the other ones in the list.
|
|
|
|
|
I've used Jenkins and TravisCI. I like both personally 
|
|
|
|
|
Found Jenkins a drag for C# development.
Everything required a plug-in, nothing came out of the box, and for some reason half of the plug-ins didn't support their new (at the time) pipelines as code model 
It works a lot better for Java and JavaScript, which were the primary technologies the company I used Jenkins at did.
That was about four years ago though, so maybe it's better now.
|
|
|
|
|
Same here, but I would not call it "simple". Also, it is buggy and slow.
|
|
|
|
|
I use CircleCI after long research on what to replace Jenkins with. Oh, how relieved I am that we did it. Was happy to pull the plug on it.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson
Our heads are round so our thoughts can change direction - Francis Picabia
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
