Continuous Integration in Visual Studio Online

[Eric_S_2]

I have code hosted in VSO and would like to use the continuous integration. Is there any way to get our IVF license working with VSO's continuous integration feature? 

[Steven_L_Intel1]

Not that I know of. That is a Microsoft-hosted service and I am not aware that there is a facility for adding non-Microsoft integration.

[Eric_S_2]

Thanks Steve. Does the Intel team recommend any particular CI solution (officially or unofficially)?

[Steven_L_Intel1]

Not that I know of, but to be honest I'm really not familiar with this other than having browsed Microsoft's web page about it.

[P__Robert]

Greetings Steve, Can we expect interoperation between Intel and Microsoft to accomplish this requirement?

I have noticed a massive improvement of Github Services integration into Visual Studio Online.
The support of Intel Stack on Visual Studio Online enables greater benchmark functionality.
To be honest, our requirement would be satisfied with Intel Stack support on Travis, Appveyor, or Visual Studio Online.
Additionally, open-source projects for k1om require some sort of free CI support.
However, I would prefer KNC CI support on Visual Studio Online because I like to use their reports.

What are your thoughts?

Thanks,
Rob

[Kevin_D_Intel]

Steve is away at the moment, so I’ll try to help. I’m not clear about what you are asking, can you elaborate further?

The discussion seems related to https://www.visualstudio.com/vso/.

[P__Robert]

Greetings Kevin,

Thanks for continuing the discussion regarding this requirement.

Let us focus on https://www.visualstudio.com/vso/ Continuous Integration using Intel Compiler.

Now consider GPL adoption of x100 KNC Co-processors Platform.

Specifically, the Mandelbulber project benefits from x100 KNC Co-processors Continuous Integration.

https://github.com/buddhi1980/mandelbulber2/issues/179

I request Intel interoperation with Microsoft to enable new features of Visual Studio Team Services Agent:

https://github.com/Microsoft/vsts-agent/issues/719

What are your thoughts, Kevin?

Thanks,

Rob

[Kevin_D_Intel]

Thank you for clarifying/sharing those references. I'll inquire w/those more knowledgeable in this area and share what I learn.

[Kevin_D_Intel]

Hi Rob,

Our IDE integration developer reviewed this post and the references you cited in your last reply.

As far he understands the response from Microsoft (i.e. https://github.com/Microsoft/vsts-agent/issues/719), the customer can always install the VSO CI agent to their own system (including cloud hosted, like Azure VM), which has any required tools including Intel Fortran, and then use this system as a VSO CI agent.

Given that he was uncertain what else you may need or be requesting and asked if you could clarify the exact scenario you want enabled?  Or does that help resolve your interests/inquiry?

[P__Robert]

Greetings Kevin,

I will get together a word document with all the details and screenshots for our Xeon Phi KNC Continuous Integration needs within the Mandelbulber2 project.  I imagine that other GPL projects that support 1st-gen KNC would also benefit from similar accommodations.

Thanks,

Rob

[Kevin_D_Intel]

Ok, thank you. That will be helpful.

[P__Robert]

Greetings,

I have found some useful details for travis CI that would add massive value to Visual Studio CI.

Please review this repo: https://github.com/nemequ/icc-travis

However, in order to fully compile for KNC we also require MPSS on the CI server.

What are your thoughts?

Thanks,

coast

[P__Robert]

Greetings Kevin, The process requirements for use on Visual Studio Online and Appveyor are listed below:

1.) To bridge the gap, we require you to support a "chocolatey package" to quickly perform silent install of the Intel Stack in Windows CI Server.

2.) We need to be able to specify the Intel Stack Registration Information using a secured environment variable.

3.) The build minutes for Continuous Integration Services are limited, so we require minimum install time of the Intel Stack in Windows CI Server.

Thanks,

Rob