Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - QNX continuous integration with Team Foundation Server: (4 Items)
   
QNX continuous integration with Team Foundation Server  
We use Microsoft Team Foundation Server to run continuous integration for application development (Windows/iOS).    Now 
evaluating QNX and wish to sound the forum out for experiences with this setup.   I realise that it may not be ideal, 
but we wish to leverage existing infrastructure and technical know-how as much as it is practical to do so.    

As a minimum, this is what we want to achieve:
1. Develop with Momentics using an Eclipse plugin for TFS to access Git repos hosted in TFS.
2. Create an automated build task in TFS to trigger a build on commit.   TFS is compatible with CMAKE with VisualGDB.   
When triggered, build agents wake up to build the project and hand off to the next step.   Our QNX targets are likely 
going to be x86.
3. Unit tests kick in automatically.    Doxygen kicks in to update documentation.
4. New executable gets deployed to a test VM.
5. Error reports get emailed to devs.
This is generally the process we use for application development and would love to know how well or poorly QNX dev fits 
in this process.

Thank you.
Re: QNX continuous integration with Team Foundation Server  
All of this sounds reasonable. At first glance, MS ships an Eclipse
plug-in that seems well featured, and CMAKE does have QNX support. At the
worst, it looks like TFS supports command line calls for their build &
release tasks. Looks like TFS has an SSH deploy task, so you could use
that to deploy the built binaries to the test VM, trigger tests and copy
back results. Unfortunately it doesn¹t look like TFS supports gcov for
code coverage results.

However, as far as I¹m aware, it is not something anyone has done. I¹d
recommend trying it out as part of your evaluation. If you have questions
along the way, please let us know.

On 2017-11-22, 5:10 PM, "Froilan Yap" <community-noreply@qnx.com> wrote:

>We use Microsoft Team Foundation Server to run continuous integration for
>application development (Windows/iOS).    Now evaluating QNX and wish to
>sound the forum out for experiences with this setup.   I realise that it
>may not be ideal, but we wish to leverage existing infrastructure and
>technical know-how as much as it is practical to do so.
>
>As a minimum, this is what we want to achieve:
>1. Develop with Momentics using an Eclipse plugin for TFS to access Git
>repos hosted in TFS.
>2. Create an automated build task in TFS to trigger a build on commit.
>TFS is compatible with CMAKE with VisualGDB.   When triggered, build
>agents wake up to build the project and hand off to the next step.   Our
>QNX targets are likely going to be x86.
>3. Unit tests kick in automatically.    Doxygen kicks in to update
>documentation.
>4. New executable gets deployed to a test VM.
>5. Error reports get emailed to devs.
>This is generally the process we use for application development and
>would love to know how well or poorly QNX dev fits in this process.
>
>Thank you.
>
>
>
>_______________________________________________
>
>QNX Momentics Getting Started
>http://community.qnx.com/sf/go/post118233
>To cancel your subscription to this discussion, please e-mail
>momenticsgs-community-unsubscribe@community.qnx.com

Re: QNX continuous integration with Team Foundation Server  
BTW if you go down the cmake road, you can get the updated toolchain file
from https://cdtdoug.ca/qnx-cmake-toolchain-file/

On 2017-11-22, 5:10 PM, "Froilan Yap" <community-noreply@qnx.com> wrote:

>We use Microsoft Team Foundation Server to run continuous integration for
>application development (Windows/iOS).    Now evaluating QNX and wish to
>sound the forum out for experiences with this setup.   I realise that it
>may not be ideal, but we wish to leverage existing infrastructure and
>technical know-how as much as it is practical to do so.
>
>As a minimum, this is what we want to achieve:
>1. Develop with Momentics using an Eclipse plugin for TFS to access Git
>repos hosted in TFS.
>2. Create an automated build task in TFS to trigger a build on commit.
>TFS is compatible with CMAKE with VisualGDB.   When triggered, build
>agents wake up to build the project and hand off to the next step.   Our
>QNX targets are likely going to be x86.
>3. Unit tests kick in automatically.    Doxygen kicks in to update
>documentation.
>4. New executable gets deployed to a test VM.
>5. Error reports get emailed to devs.
>This is generally the process we use for application development and
>would love to know how well or poorly QNX dev fits in this process.
>
>Thank you.
>
>
>
>_______________________________________________
>
>QNX Momentics Getting Started
>http://community.qnx.com/sf/go/post118233
>To cancel your subscription to this discussion, please e-mail
>momenticsgs-community-unsubscribe@community.qnx.com

Re: QNX continuous integration with Team Foundation Server  
Thanks - I subscribed to CDT Doug.   Great blog.



> BTW if you go down the cmake road, you can get the updated toolchain file
> from https://cdtdoug.ca/qnx-cmake-toolchain-file/
> 
> On 2017-11-22, 5:10 PM, "Froilan Yap" <community-noreply@qnx.com> wrote:
> 
> >We use Microsoft Team Foundation Server to run continuous integration for
> >application development (Windows/iOS).    Now evaluating QNX and wish to
> >sound the forum out for experiences with this setup.   I realise that it
> >may not be ideal, but we wish to leverage existing infrastructure and
> >technical know-how as much as it is practical to do so.
> >
> >As a minimum, this is what we want to achieve:
> >1. Develop with Momentics using an Eclipse plugin for TFS to access Git
> >repos hosted in TFS.
> >2. Create an automated build task in TFS to trigger a build on commit.
> >TFS is compatible with CMAKE with VisualGDB.   When triggered, build
> >agents wake up to build the project and hand off to the next step.   Our
> >QNX targets are likely going to be x86.
> >3. Unit tests kick in automatically.    Doxygen kicks in to update
> >documentation.
> >4. New executable gets deployed to a test VM.
> >5. Error reports get emailed to devs.
> >This is generally the process we use for application development and
> >would love to know how well or poorly QNX dev fits in this process.
> >
> >Thank you.
> >
> >
> >
> >_______________________________________________
> >
> >QNX Momentics Getting Started
> >http://community.qnx.com/sf/go/post118233
> >To cancel your subscription to this discussion, please e-mail
> >momenticsgs-community-unsubscribe@community.qnx.com
>