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

[Craig A. Berry]

On 9/1/21 10:16 AM, Arne Vajhøj wrote:
> On 9/1/2021 10:52 AM, Jan-Erik Söderholm wrote:
>> Den 2021-09-01 kl. 14:35, skrev Arne Vajhøj:
>>> On 9/1/2021 5:47 AM, Jan-Erik Söderholm wrote:
>>>> There are talks around our OpenVMS environment and project work
>>>> where it is looked at to add Azure DevOps to our work environment.
>>>>
>>>> They are talkning about "pipelines" within Azure DevOps where
>>>> the build procedures are setup and the build is run from within
>>>> the Azure Devops environment.
>>>>
>>>> Does anyone have any comments around this? Have anyone looked at
>>>> using Azure DevOps for their OpenVMS development/test/deploy?
>>>>
>>>> Has anyone looked at other tools (DECset?) to do anything in
>>>> this direction?
>>>
>>> I suspect that typical VMS processes are a few decades behind
>>> modern cloud devops processes.
>>>
>>> But most things are possible with some effort.
>>>
>>> I know that:
>>> - John Malmberg & vms-ports use Jenkins for builds
>>> - Jenkins integrate with Azure devops
>>>
>>> https://sourceforge.net/p/vms-ports/wiki/UsingJenkinsCi/
>>>
>>> https://medium.com/@bbenz/azure-devops-and-jenkins-in-perfect-harmony-8c92ff980723 
>>>
>>>
>>> Maybe some of that stuff can be utilized.
>>
>> 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... :-)
>>
>> 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?
> 
> :-)
> 
> But if they want to proceed then there may be some ways to integrate.

I couldn't find anything quickly about the Azure DevOps test runner.  I
know the GitHub CI test runner is a .NET Core application so it would
have to be either ported (requiring .NET Core to be ported) or
completely reimplemented to report test results from VMS.  It's possible
Azure DevOps has a published API and writing a client for it wouldn't be
too horrible.  But more work than on other platforms where all the
pieces are already there.