[Info-vax] OpenVMS developmen integration with Azure DevOps.

[Arne Vajhøj]

On 9/1/2021 5:31 PM, Dave Froble wrote:
> On 9/1/2021 10:52 AM, Jan-Erik Söderholm wrote:
>> Right, the guy that made the Azure DevOps presentation from our group
>> had a hard time to understand why we just didn't copy our source codes
>> to a Azure VM and just run the build from DevOps... :-)
> 
> Right, so he didn't know what he was talking about, huh?
> 
> Who wants to follow this pied piper into the swamp, and worse?
> 
>> We had to run a quick presentation of OpenVMS on our Alpha dev system.
>> Oh, so it is Cobol?
>> Oh, so it is a main-frame?
>> Oh, so this is not running on X86?
> 
> As observer, the guy had no idea what he was talking about.
> 
> Some question for the jerk ...
> 
> The current system is working just fine, why should we take your advice?

Working fine does not mean that it cannot be improved.

These people may understand the benefits of the new process well, but
given that obviously do not know anything about VMS, then they don't
know anything about the cost to integrate VMS into it. "I see benefits
X but I have no idea what the cost will be" is not a good sales pitch,

> What will we get?  A sideways move, at best, and more likely bugs and less.

Hooking the VMS development process into the company's overall
development process is not likely to change the number of bugs. Same
code base and same people editing the code base - just a different
scripting to do the builds, run the tests and do the deployments.

> Who is going to pay for this?

Relevant question for all changes that require work.

And when talking custom work like here, then the cost is
likely to be pretty high.

> What is the business case to do anything?

A good CI/CD pipeline can provide real value:
- bugs found sooner than later
- testers save time on trivial work, so either the company
   save hours or the testers can spend more time testing the
   interesting stuff

Arne