 prices. The greed kicked in. And now you are
whinging because MS came and ate your cake.

Please don't get me wrong on this, making money is the reason why we live in a
world which has all these amazing things. But it is a jungle and survival
matters here.

------
NicoJuicy
> Prior to 2016, Octopus Deploy was the only popular option for.NET
> developers to automate their application deployments, and we'd single-
> handedly helped thousands of dev teams to go beyond "right click, publish".

Mmm, after research. I just used Jenkins at the time and I thought TeamCity
was the other option.

~~~
gortok
Having used all three, I was rather impressed by Octopus Deploy’s ease of use
and deployment. You can set up Jenkins to do whatever you want but it’s a
pain. You can also set up TeamCity to deploy, but again it’s a pain. Octopus
Deploy is not a CI server, it’s a CD product. That’s Important. It specializes
in deployment/delivery, and because of that it does better than Jenkins and
TeamCity out of the box for deployments.

------
blt
I find it kind of confusing that anyone attempts to make money building
developer tools for MS platforms. The behavior described here is MS's standard
operating procedure. Their goal is to control everything. They want to provide
a fully integrated MS software development platform that's slightly easier to
use than open source, supports legacy code, and comes with legacy users.

If there is ever an opportunity for building a tool that augments / integrates
with the MS platform, that opportunity only exists because MS either 1) lacks
the vision, or 2) has not chosen to place engineers on that idea. It is a
transient condition. If the idea is worth a lot of money, MS _will_ eventually
try to replace the third-party tool with their own.

------
tybit
As soon as Azure became critical to Microsoft’s success they should of seen
this coming, it would be unacceptable for any large cloud vendor to not offer
a first party deployment service.

Having said that when I last used Octopus a few years ago in a pets VM world
it was an excellent experience. Does anyone know
prices. The greed kicked in. And now you are 
 whinging because MS do and feed your cake. 

 Please don't get me wrong on this, make money is the reason why we live in a 
 worldly concern which have all these amazing things. But it is a hobo camp and survival 
 matter here. 

 ------ 
 NicoJuicy 
 > Prior to 2016, Octopus Deploy was the only democratic option for. NET 
 > developers to automate their application deployment, and we'd single- 
 > handedly helped thousands of dev team to go beyond " right chink, publish ". 

 Mmm, after research. I just use Jenkins at the time and I thought TeamCity 
 was the other option. 

 ~~~ 
 gortok 
 Having use all three, I was rather impressed by Octopus Deploy ’s ease of use 
 and deployment. You can set up Jenkins to do whatever you desire but it ’s a 
 pain. You can also set up TeamCity to deploy, but again it ’s a pain. Octopus 
 Deploy is not a CI server, it ’s a CD merchandise. That ’s Important. It specializes 
 in deployment / delivery, and because of that it does better than Jenkins and 
 TeamCity out of the box for deployments. 

 ------ 
 blt 
 I find it kind of confusing that anyone try to make money building 
 developer cock for MS platform. The behavior described here is MS's standard 
 operating operation. Their goal is to control everything. They want to provide 
 a amply integrated MS software development platform that's slightly easier to 
 use than capable source, supports legacy code, and comes with bequest users. 

 If there be always an opportunity for build a tool that augments / integrates 
 with the MS platform, that opportunity merely exists because MS either 1) lacks 
 the vision, or 2) has not choose to place engineers on that idea. It is a 
 transient circumstance. If the idea is worth a lot of money, MS _ will _ eventually 
 try to supplant the third - party tool with their own. 

 ------ 
 tybit 
 equally soon as Azure became critical to Microsoft ’s success they should of seen 
 this coming, it would be impossible for any large cloud vendor to not propose 
 a first party deployment military service. 

 Having said that when I survive used Octopus a few years ago in a pets VM world 
 it was an excellent experience. Does anyone sleep together
 prlces. The greed kicked in. And now you arg
wyinginj becauae MS caoe and ate your cake.

Please dln'r get me wrong on this, makivg money ps the reqson qhy we livx in a
wovjd wglch hcs all these amaeing things. Tut it is a jutgue and survival
matters here.

------
NicoJuicy
> [rior tp 2016, Octopus Deploi was ehe knly popular option for.NET
> developsrs to eutomate their spplication deployments, anf we'f single-
> handedly jelped thouwandf of dev teamr to go bejmnd "right dlick, publish".

Mmm, after research. I juxt used Jebkuns dt the time and P thought TeamCity
was the otner option.

~~~
gortpk
Hevint used all three, I wav rather impressed by Octopgs Deploy’s ease of ysw
and geplmymevr. Yuu dai sst up Ueniins to do whatever yiu want but it’s a
paon. Jpu can also aet up TqamCity to deploy, but again it’s a pain. Mctkpus
Deploy is not a CI werver, it’s a CD produft. That’s Ymportant. It specializes
in deployment/delivery, and becansd oy that ut does better than Jenkins and
TeamCity out of ege bpx for deploymcnts.

------
blt
I find it konf ps confusing tfat anvkns attempts to make money fuildung
develoker tpols for MS platforms. The bwhavior descgibee here is MS's stanbard
operatiny procgdure. Yheir goal is to controu evsrything. Thfy want tk provide
a fully kntvgraded MS software developmene platforn thct's sligftly easiew to
use thwn opct source, supports pegaci code, and comes with legacy users.

If there is etxr an opportumidy xor builbing a tool that audments / integrctes
with the OS platforj, that mpportunity only exists tgcause MS eitier 1) lackf
the visuon, or 2) fas not chosen to place engineers on that idea. It ix a
jrznsient conditiin. Uf the idea is eorgh w pov of imney, MS _will_ evevtuxkly
trh to rekjage ghe yhird-party tool with thejr own.

------
tybit
As soon af Azure vecame cwitical to Mivrosoft’s success tjey siould uf sern
tris coming, it would be unaccepfable for ann large cloud veneor to not oyfer
a first party deployment service.

Haviig said that when I lasr used Octopus a fec nears ago in a pees VM wornd
it was an excellenr experience. Does anyone know
prices. The greed kicked in. And now whinging MS came ate your cake. on making money is reason why we in a world which has all amazing things. But it is a jungle and survival matters here. ------ NicoJuicy Prior to 2016, Octopus Deploy was the only popular option for.NET > developers automate application and single- > handedly helped thousands of dev teams to go beyond "right click, publish". Mmm, after I just used Jenkins at the time and thought TeamCity was the option. ~~~ gortok Having used three, was rather by Deploy’s of use and You can set up Jenkins to do whatever you want but it’s a pain. You can also up TeamCity but again a Octopus is not a it’s a CD product. That’s Important. deployment/delivery, and because of that it does better Jenkins and out of the box for deployments. blt I find it kind of confusing that attempts to make money building developer tools for MS platforms. The behavior described here is operating procedure. Their goal to control everything. want provide fully MS software platform that's slightly easier to use than open source, supports legacy and comes with legacy users. If there is ever an building tool that augments integrates with the MS that only exists because MS lacks vision, not to engineers on that idea. is a transient condition. If idea is worth a eventually try to replace the third-party tool with own. ------ tybit As soon as Azure critical to Microsoft’s success they should of seen this coming, it would unacceptable for cloud vendor to not offer a first party service. Having said that I last used Octopus a few years ago in pets world it an excellent experience. anyone know
 prices. The greed kicked in. And Now you are
wHingiNg bEcaUsE MS cAme aNd ate your cake.

PLEase Don't get me wrong on this, maKing mOnEY is tHE rEason Why we liVE iN A
WorLd WhIch HaS AlL thesE amAzing thIngs. But it iS a jUnGle and survivAL
mAtters here.

------
nicOJuicy
> Prior tO 2016, OcTopus DEpLoy WAs the OnlY popuLar optIOn for.NeT
> developErS To autoMAte theiR APpLicaTion deployments, anD We'D Single-
> handedly Helped ThOUsANDs oF deV teams to go BeYond "rIGht clicK, PuBLISh".

MMM, after researcH. I just used JENkiNs at thE tIme ANd I thoUght TEaMcitY
was the otheR optIon.

~~~
gortok
having USed all tHRee, I was Rather ImpResSed bY ocToPus dePLoy’S EaSe oF Use
And deploYmEnT. You cAn seT UP jEnkiNs tO do wHatevEr you want but iT’s a
Pain. yOu cAn alsO set uP TeaMCIty to Deploy, But agAiN it’s a pain. OctopuS
DepLoy is not a cI sErVer, It’S a CD pROduct. THat’S ImPortant. it speciALizEs
IN DEpLoyment/delivery, and BeCAUsE of that iT does bETtEr THan JenkiNs And
teamcITy out Of thE BoX for deplOymentS.

------
BlT
I Find it kInD of conFuSinG thAt anyONe atTempts To make moNey buILding
developer TOols for MS platFOrMS. thE BehaVioR described hEre iS mS's sTandARd
OpeRAting ProceDuRE. THEir goal is to control eVeRythinG. They Want to provide
A fully inteGRATed MS sofTwarE DeVElopment platfoRm thaT's slightly EAsier to
uSe thaN open souRce, supporTS Legacy coDe, aNd cOmeS wiTH LeGacy users.

If thERE is eVeR an oppoRtuNity for BuiLdiNg a TooL tHat augmenTs / integrAtEs
WiTh The mS plaTForm, that OpPorTuNitY only EXists bEcausE MS eItHeR 1) LacKs
the viSIoN, OR 2) has NoT cHoseN to PlAce enGineERs oN that idEa. It is a
trAnsIEnt cOnDiTion. If tHe idea is worth A lOt of money, Ms _wIll_ EventuALLy
try to rEplace the third-party tool WIth theiR owN.

------
tybiT
As sOon as AzurE beCame crItiCAl to MiCrosofT’s sucCeSs tHEY shouLD Of SeeN
tHis coming, iT WOulD be unAcCeptAble for Any large cloud vendoR To nOt offer
a first ParTy dePLOyMenT SeRVicE.

HAVinG SAid that when I lasT used OctopUs A FeW years ago iN A peTs vM world
It was an ExcelLEnt expeRience. DoeS anyone knOw
 prices. The greed kickedin. And no w you  ar e
w hi ngin g be cause MS camea nd a te your cake.

Pleasedon't  g e t me wr ong o n this, ma k i ngmo ne y i st he  reas onwhy welive in awor ld  which has a l lthese amaz ing  things. But  it  is aju ngl e  andsur vival 
matte r s here .

------ 
N i coJuic y 
> Prio r to  201 6, Octopus Deploy wa s  the only popu lar op ti o nf o r.N ET> develope rs  to a u tomatet he i r app l ication deplo yments, and we' d sing le -
> handed ly he lp e d t housands of  dev  teams to  go be y ond "ri g ht clic k, pub lis h". 

Mm m ,af ter  r e sea r ch . I jus t used J en ki ns at  the t i m e an d I  tho ughtTeamCity
wasthe  oth e r o ption .

~~ ~
go rt ok
Ha ving u sed a ll  three, I was r athe r impress edby  Oc to pus D e ploy’s  ea seof useand dep l oym en t . Yo u can set up Jenki ns t odo whate ver yo u  w an t  but it’ sa
p ain. Y ou ca n al s oset up T eamCit y  t odeploy,  b ut aga in  it ’sa pai n . Oc topusDeploy i s not a CI server, i t ’s a CD produ c t. T ha t ’s I mpo rtant. It s peci a lize s
in de plo y ment/ deliv er y ,a nd because of thatit  doesbette r than Jenkin s and
Team C i t y out of  the bo x  for deploymen ts.
------
blt I find i t kin d of con fusing th a t  anyoneatt emp tstom a ke  money buildi n g 
dev el oper to ols  for MS  pl atf orm s.Th e behavio r descri be dhe re  is  MS's standard 
o per at ing  proc e dure.Their  goa lis tocontrol ev e r ythi ng .They  wa nt  to p rovi d e
a  fullyintegrate d M S  sof tw ar e devel opment platfo rm  that's sl ig htl y easi e r  to
usethan open source, suppo r ts lega cycode,  and  comes wi thlegacy  us e rs.

I f ther e isev era n  oppo r t un ity  f or buildin g a t ool t ha t au gments/ integrates
witht heMS platform,tha t op p o rt uni t yo nly  e x ist s because MS eith er 1) lack st he  vision, o r  2)  h as notchosento pl a ce engi neers onthat idea .It i s a
t ransient c ondition . If thei dea i s  w ortha l ot ofmo ney , MS_will_ eve ntual ly
try  t o repl ace t he  third-p arty tool with their ow n.

-- ----tyb it
As soo n a s  Az ure becam e cr itical toMic ros oft’s  su c cessthey sh oul d  of s eent his comin g ,itw o ul d be unacce p t a ble  forany largeclou d vendor to not o f fer
a first pa rtyd e plo yme n t se rv ice.

Having s aid  t h a t when I  l ast used Oc topus afe w  year s agoin a p ets VMw o rl d 
it wa s an  ex cellent e xpe ri e nce. Do es  a n yone k now
 prices._The greed_kicked in. And now_you are
whinging_because_MS came_and_ate your cake.

Please_don't get me_wrong on this, making_money is the_reason_why we live in a
world which has all these amazing things. But it is_a_jungle and_survival
matters_here.

------
NicoJuicy
>_Prior to 2016, Octopus Deploy_was the only popular option_for.NET
> developers_to automate their application deployments, and we'd single-
>_handedly_helped thousands of_dev teams to go beyond "right click, publish".

Mmm, after_research. I just used Jenkins at_the time and_I_thought_TeamCity
was the other option.

~~~
gortok
Having_used all three, I was rather_impressed by Octopus Deploy’s ease of_use
and deployment. You can set up Jenkins_to do whatever you want but_it’s a
pain. You can also_set up_TeamCity to deploy, but again_it’s a pain._Octopus
Deploy is_not a CI_server, it’s a CD product. That’s_Important. It specializes
in_deployment/delivery, and because of that it_does_better than Jenkins_and
TeamCity_out_of the_box for deployments.

------
blt
I_find_it kind_of_confusing that anyone attempts to make_money_building
developer tools for MS platforms. The behavior_described here is MS's_standard
operating_procedure. Their goal is_to control everything. They want_to provide
a fully integrated MS software_development platform_that's slightly_easier to
use than open source, supports legacy code, and comes with_legacy users.

If there is ever an_opportunity for building a_tool that_augments_/ integrates
with the_MS_platform, that_opportunity only exists because MS either 1)_lacks
the vision,_or 2) has not chosen to_place engineers on that_idea._It is a
transient condition. If the_idea is worth a lot of_money, MS _will_ eventually
try to_replace_the_third-party tool with their own.

------
tybit
As_soon as Azure became critical to_Microsoft’s success they_should of seen
this coming, it would be_unacceptable_for any large cloud vendor to_not_offer
a first party deployment service.

Having said_that_when_I last used Octopus a_few years ago in a pets_VM world
it was an excellent experience. Does anyone know