[jira] [Commented] (MINIFICPP-974) Ensure that non-docker tested processors are not included into the make packaged docker builds

2019-07-31 Thread Arpad Boda (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896914#comment-16896914
 ] 

Arpad Boda commented on MINIFICPP-974:
--

I'm in, too.

As a first step I would like to have a well defined criteria for "sufficiently 
tested" to leave no room for "why did you...?" discussions. :) 

> Ensure that non-docker tested processors are not included into the make 
> packaged docker builds
> --
>
> Key: MINIFICPP-974
> URL: https://issues.apache.org/jira/browse/MINIFICPP-974
> Project: Apache NiFi MiNiFi C++
>  Issue Type: New Feature
>Reporter: Mr TheSegfault
>Priority: Major
>
> This ensures that we don't trust and deploy artifacts that don't have some 
> type of regression test framework as it relates to our SITs. There may be 
> exceptions, so we can feel this desire out.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (MINIFICPP-974) Ensure that non-docker tested processors are not included into the make packaged docker builds

2019-07-30 Thread Aldrin Piri (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896222#comment-16896222
 ] 

Aldrin Piri commented on MINIFICPP-974:
---

[~phrocker] I am in favor for of it.  The complexity of libraries and 
functionality is large and has more inherent weight to inclusion to the 
codebase.  If we do not have a way of conducting an automated way to cover the 
rudimentary aspects of it in the codebase, it will leave the codebase in a hard 
to maintain state.

> Ensure that non-docker tested processors are not included into the make 
> packaged docker builds
> --
>
> Key: MINIFICPP-974
> URL: https://issues.apache.org/jira/browse/MINIFICPP-974
> Project: Apache NiFi MiNiFi C++
>  Issue Type: New Feature
>Reporter: Mr TheSegfault
>Priority: Major
>
> This ensures that we don't trust and deploy artifacts that don't have some 
> type of regression test framework as it relates to our SITs. There may be 
> exceptions, so we can feel this desire out.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (MINIFICPP-974) Ensure that non-docker tested processors are not included into the make packaged docker builds

2019-07-30 Thread Mr TheSegfault (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896146#comment-16896146
 ] 

Mr TheSegfault commented on MINIFICPP-974:
--

[~aboda] and [~aldrin] what do you think about this? I think we should draw a 
line in the sand that if something is contributed without sufficient tests in 
either unit and/or docker we don't release it with our Apache process. 
Obviously we can't pull the wool out from the processors and features we have, 
so this would have to be staged, but I'd like to set the stage for controlling 
what we release.

> Ensure that non-docker tested processors are not included into the make 
> packaged docker builds
> --
>
> Key: MINIFICPP-974
> URL: https://issues.apache.org/jira/browse/MINIFICPP-974
> Project: Apache NiFi MiNiFi C++
>  Issue Type: New Feature
>Reporter: Mr TheSegfault
>Priority: Major
>
> This ensures that we don't trust and deploy artifacts that don't have some 
> type of regression test framework as it relates to our SITs. There may be 
> exceptions, so we can feel this desire out.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)