|
Excuse me, but exactly what makefiles and pre-compile, pre-build and post-build operations do differently? And why would someone build the entire freaking system any time? We're way past statically included libraries and objects so unless using crap-loaded and monkey-designed frameworks there should be no real need to build every component every time.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
I've never even heard of it and I'm a much better developer than you are.
|
|
|
|
|
La la la la la, I can't hear you.
|
|
|
|
|
N_tro_P wrote: Builds are extremely complicated.
Perhaps yours are. Our main app is an ASP.Net application. The build takes a few minutes even though we have a massive web app. We wrote a sql script that generates a sql script to create all our objects. It takes about 10 minutes to run but is fully automated.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
You're so sure I need this, but can't tell me what I build and in what language. Seriously, a holier-than-thou attitude causes me to discount the rest of your lecture as ranting by someone who needs to be right. You'll catch more flies with honey than vinegar.
|
|
|
|
|
I am a mathematician that uses Fortran to build predictive models. 80% of my work is programming. For front ends I use Win forms built in C#. Myself and another are the sole programmers of the system used here. My builds take a few minutes and I can repeat any of them. The users are analysts within the company. If one has a problem, they call me and I walk down to their desk. The entirety of the project is so close to me and familiar that I don't need such formal techniques. My boss has no idea how I do what I do and my actions require little justification.
I have the luxury of living in the old world of programming before trendy techniques with special names. It's quite pleasant. That stuff just would just slow me down.
So, I think my situation is relevant. I don't know of the technique you espouse, nor do I need to. I have been highly successful so far and don't see that changing.
Thanks for looking out for all of us though.
|
|
|
|
|
N_tro_P wrote: spending days on a build
I've never used CI nor have I ever seen a build even take a day to do or anywhere close to that. You're experience seems quite strange to me.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I think a clear example upfront would have gone a long way against all the confusion.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Don't forget some extras:
- indirect check of source code integrity ("works on my machine" - but forgot to check-in some files...)
- automatic execution of unit tests
- test coverage reports
- automatic code analysis
- reporting over time
- automatic emails for failures
You may also add automated integration / system tests.
And perhaps many more things depending on your choice.
CI helps to keep our code base clean and reliable.
I hope more people will now be able to see the advantages of CI.
|
|
|
|
|
That few agree should be a clue. There are many programming realities.
|
|
|
|
|
Thanks for the responses.
|
|
|
|
|
I don't think it's important that I know so move along.
|
|
|
|
|
Agreed until proven otherwise!
|
|
|
|
|
It's a fancy word for 'applications that replace build scripts'.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
