|
Is a rodent's drawing a mouseterpiece?
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
A very Auguste Rodin.t!
Got my site back up after my time in the woods!
JaxCoder.com
|
|
|
|
|
are you taking the mickey?
Message Signature
(Click to edit ->)
|
|
|
|
|
At the rat were going, I gnaw we'll discuss squirreling them away until they litter-aly increase in value.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
It might be a nutria bomb.
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
Lemming think about it.....no.
|
|
|
|
|
Let me know if it would be better to create a survey....
background: I handle building a multi-part application that crosses multiple development tools, custom processing, etc. Basing my "automation" work off of some work by another developer, I essentially have a dozen MS-DOS scripts that build each part and then assemble the whole. Now, IMHO, MS-DOS scripting just blows, and I'm being generous. Sure, it gets the job done, but calling it archaic is too generous. So, I'm looking to implement something a bit more modern that will work effectively with a nightly build process.
So, what do you use? MS-DOS script users need not reply 
I'm looking at SCons now, but thought I'd get some feedback from CP.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
I used to work on similar projects and used make and makefiles. They are exceedingly flexible, customisable and work with just about any directory structure. The learning process (as with all) can be a little steep but time spent learning it does pay dividends. I have done something similar on Windows with Visual Studio projects, but on a much smaller scale.
|
|
|
|
|
I perceive you are an old fart (no offense, I am too). I used to use MMS (DEC) - very similar to make. I'm headed in that direction, but I'm looking to put a little more intelligence in it.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
charlieg wrote: I perceive you are an old fart
More like a very old fart ... I first started programming in machine code on Leo Computers Society. Leo 3 photos[^] (first four pictures in the second row) in 1966.
|
|
|
|
|
charlieg wrote: but I'm looking to put a little more intelligence in it.
Not sure what that means but you can add conditional build semantics to make files if that is what you are referring to.
|
|
|
|
|
We're using Jenkins[^] where I work.
Latest Article - Slack-Chatting with you rPi
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
A daily build script for your project[^] 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Touche'  I'll review it.
Thank you
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
It has been a while since that, and I heard some good things about FogBugz. You may want to browse around a bit, after reading the tip on how to do it yourself.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Our build process used to be exactly as you describe: a mish-mash of batch files, VBscript's, and a few odds-and-ends executables thrown in for fun. I looked at a few of the existing build tools before writing a Windows service written in C#. Most of the public tools were preferentially biased toward a specific tool-chain or target operating system. The other problem was customization - you had to learn their "paradigm" in order to adjust the process to your requirements, and you could spend a lot of effort getting around paradigm features that weren't needed or appropriate.
My service handles everything: get source from source control, compile, move files as needed to compile installers, create install images, and finally generate .ISO's to archive the build. The service communicates with our in-house network tracing tool to display progress and to let users cancel or pause builds. Builds for specific products are implemented as classes deriving from a base 'build' class. Product build classes can override steps in the build process as needed. New products and branches can usually be added in minutes, rather than the days it used to require. The whole thing is vastly easier to debug and maintain than the original wretched hive of scum and villainy  .
Software Zen: delete this;
|
|
|
|
|
Automated builds
To me that means getting F5 pressed without having to explicitly do it myself.
You mean there's more to it?
|
|
|
|
|
lol, yeah, I wish. Our release process can become something like "We need to ship something to test tonight." This might occur at 9am or 5pm. Manually performing all the steps is a recipe for disaster. The entire point of post is I just in fact did this - screwed the build up.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
It turns out writing software is easy.
It's the build systems that are downright horrifying.
|
|
|
|
|
PowerShell is the modern way to write scripts, according to Microsoft. That might be an acceptable option. There are also tools for developing PowerShell things in VS2017. I would take that route before resorting to writing custom tools.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I've looked at powershell briefly. Maybe it's just me but it reminds me of someone on crack cocaine trying to write a "scripting" language.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
As per Marc - Jenkins
We're a c++, c#, Ruby shop - Jenkins calls wrapper scripts and/or nmake, MSBUILD, Rake etc etc - its quick to get up and started
One of the things you may need to consider is build/test pipelines and whether parts of the pipeline need to be run on different servers (we typically run build server(s) and test server(s), Jenkins works well for this, the test server(s) are 'pooled' where we need to, dedicated for other builds)
|
|
|
|
|
Based on your comments you are going to need more than just a normal 'build' system.
A build system creates the artifacts. But you are also looking for automated deployment.
And I suspect you might have distinct and perhaps different deployment targets (QA and prod) for example.
That complicates the process.
And it my experience doing that will require a mix of tools.
From your post I suspect you haven't even scoped out the actual use cases. Which should be your first step.
Let me provide some use case scenarios
- Allow a way to run unit tests (not on the developer machine.)
- Allow a way for a developer to run the full deployment on their machine, so they can test the full process.
- Allow a deployment to a QA box.
- Allow a deployment to a QA stack. Different than the above since it might include a cloud target.
- Allow a deployment to create (important) and deploy to a production clone target.
- Allow a full build, versioning to specified target. So a release candidate for QA or production.
- Allow a deployment to the Sales Demo box.
- Allow a deployment to a Professional Services box.
- Allow a hotfix build (start with a versioned build and apply a branch)
Your use cases presumably would be different and you might not want to build all of those now but you need to understand all of them now so you don't make any decisions that complicate or even preclude the scenarios you need.
|
|
|
|
|
baby steps dude, baby steps 
I live in an embedded world, so there is no cloud- it's a lump of hardware sitting on a desk. It may or may not be production hardware.
I just want to know if everything built correctly. For example, I just did a full build, hardware A is at 9.346, hardware b is 9.344.
bad
Right now I build with ms-dos scripts and it's as painful as an in-grown toe nail.... but your point is valid. There just isn't the resources to support all of that....
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
https://www.nytimes.com/2019/02/01/nyregion/standardized-testing-teachers-students.html[^]
How do you test a teacher's performance? Not by seeing if his students have learned anything, obviously.
So our suffering at finding that highly-qualified programmers don't know how to code will be shared among other professions.
Contrary to the popular old saying, I don't think that will halve it.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
