Re: [VOTE] Release Apache NiFi 0.7.2
+1 (non-binding) Built from src on OSX Sierra 10.12.3 (16D32), all tests pass Verified sigs and hashes. Ran sample flow. On Mon, Feb 20, 2017 at 5:13 AM, Bryan Rosanderwrote: > +1 (non-binding) > > Verified signature, hashes > Contrib-check build against fresh local repo > Simple flow on 3 node cluster > > On Sat, Feb 18, 2017 at 3:45 PM, Joe Witt wrote: > >> James >> >> It is simply enough that someone volunteered to RM the release. If time is >> available to help review/vote then great. Same with the 1.x release. >> >> Thanks >> Joe >> >> On Feb 18, 2017 2:59 PM, "James Wing" wrote: >> >> > The unifying theme of 0.7.2 and 1.1.2 appears to be NIFI-3487 "Refactor >> > user formatting". Is this urgent? >> > >> > https://issues.apache.org/jira/browse/NIFI-3487 >> > https://github.com/apache/nifi/commit/bd88e4335ad151592f1310996e9a05 >> > 13b7f0829a >> > >> > >> > Thanks, >> > >> > James >> > >> > >> > On Fri, Feb 17, 2017 at 9:55 AM, Joe Witt wrote: >> > >> > > Mike, >> > > >> > > You're absolutely right that there are some good fixes to be included >> > > in an upcoming release. There is no reason someone couldn't put >> > > together an 0.7.3. >> > > >> > > This is just something that we're wanting resolved and have the energy >> > > to push forward and doesn't require additional testing as inclusion of >> > > other items would. >> > > >> > > Please by no means see this as a deterrent to progression on an 0.7.3. >> > > >> > > Thanks >> > > Joe >> > > >> > > On Fri, Feb 17, 2017 at 12:38 PM, Michael Moser >> > > wrote: >> > > > I'm sad that 0.7.2 does not contain some of the other bug fixes >> > currently >> > > > on the 0.x branch. It doesn't seem like it would have cost very much >> > to >> > > > just include them. >> > > > >> > > > +0 (non binding) >> > > > >> > > > -- Mike >> > > > >> > > > >> > > > On Thu, Feb 16, 2017 at 11:42 PM, Andy LoPresto < >> alopre...@apache.org> >> > > > wrote: >> > > > >> > > >> Hello, >> > > >> >> > > >> I am pleased to be calling this vote for the source release of >> Apache >> > > NiFi >> > > >> nifi-0.7.2. >> > > >> >> > > >> The source zip, including signatures, digests, etc. can be found at: >> > > >> https://repository.apache.org/content/repositories/ >> orgapachenifi-1099 >> > > >> >> > > >> The Git tag is nifi-0.7.2-RC1 >> > > >> The Git commit ID is 831ac6939df7d418cadb336eedb4e09fb97541a1 >> > > >> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= >> > > >> 831ac6939df7d418cadb336eedb4e09fb97541a1 >> > > >> >> > > >> Checksums of nifi-0.7.2-source-release.zip: >> > > >> MD5: efe9ea1cf0698a57a6829fe3829fc136 >> > > >> SHA1: aee51164af34394c7017dae491b239a88b614865 >> > > >> SHA256: 8cd02675003fca837ea0092b622560 >> 0a4700b905e5214a751ae7ff833263 >> > > 193b >> > > >> >> > > >> Release artifacts are signed with the following key: >> > > >> https://people.apache.org/keys/committer/alopresto.asc >> > > >> >> > > >> KEYS file available here: >> > > >> https://dist.apache.org/repos/dist/release/nifi/KEYS >> > > >> >> > > >> 2 issues were closed/resolved for this release: >> > > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa? >> > > >> version=12339601=12316020 >> > > >> >> > > >> Release note highlights can be found here: >> > > >> https://cwiki.apache.org/confluence/display/NIFI/ >> > > >> Release+Notes#ReleaseNotes-Version0.7.2 >> > > >> >> > > >> The vote will be open for 96 hours (over holiday weekend). >> > > >> Please download the release candidate and evaluate the necessary >> items >> > > >> including checking hashes, signatures, build >> > > >> from source, and test. The please vote: >> > > >> >> > > >> [ ] +1 Release this package as nifi-0.7.2 >> > > >> [ ] +0 no opinion >> > > >> [ ] -1 Do not release this package because becauseā¦ >> > > >> >> > > >> Andy LoPresto >> > > >> alopre...@apache.org >> > > >> *alopresto.apa...@gmail.com * >> > > >> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 >> > > >> >> > > >> >> > > >> > >>
Re: [VOTE] Release Apache NiFi 1.1.2
+1 (non-binding) Verified signature, checksums Contrib check build with Oracle jdk 1.8.0_111 on macOS Sierra. Tested Site-to-Site connectivity (RAW and HTTP) among following NiFi environments: A. Standalone Non-secured B. Standalone Secured C. Cluster Non-secured D. Cluster Secured On Mon, Feb 20, 2017 at 4:40 AM, Bryan Rosanderwrote: > +1 (non-binding) > > Verified signature, checksums > Contrib check build with Oracle jdk 1.8.0_121 on Ubuntu, fresh local repo > Tested non-secured cluster with simple flow > Tested secured cluster with simple flow, command line site to site client > > On Sun, Feb 19, 2017 at 9:01 AM, Tony Kurc wrote: > >> +1 (binding) >> >> Rebuilt successfully with jdk 1.8.0_121. Ran some simple flows without >> issue. >> >> On Feb 18, 2017 8:09 PM, "Aldrin Piri" wrote: >> >> > On a hunch, but I feel like there have been reported issues and/or I have >> > personally experienced them with u45. Is it possible to get something a >> > bit newer? >> > >> > On Sat, Feb 18, 2017 at 8:02 PM, Tony Kurc wrote: >> > >> > > Something went terribly wrong when I was pasting my maven angrygrams. >> Do >> > > these look like environment problems? >> > > >> > > ($ mvn --version >> > > Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; >> > > 2015-04-22T07:57:37-04:00) >> > > Maven home: /opt/maven/apache-maven-3.3.3 >> > > Java version: 1.8.0_45, vendor: Oracle Corporation >> > > Java home: /opt/java/jdk1.8.0_45/jre >> > > Default locale: en_US, platform encoding: UTF-8 >> > > OS name: "linux", version: "3.13.0-108-generic", arch: "amd64", family: >> > > "unix" >> > > ): >> > > >> > > testReadFlowFileContentAndStoreInFlowFileAttribute(org. >> > > apache.nifi.processors.script.TestInvokeJavascript) >> > > Time elapsed: 1.35 sec <<< FAILURE! >> > > java.lang.AssertionError: Processor has 1 validation failures: >> > > 'Validation' validated against >> > > 'target/test/resources/javascript/test_reader.js' is invalid because >> An >> > > error occurred calling validate in the configured script Processor. >> > > >> > > at org.junit.Assert.fail(Assert.java:88) >> > > at >> > > org.apache.nifi.util.MockProcessContext.assertValid( >> > > MockProcessContext.java:251) >> > > at >> > > org.apache.nifi.util.StandardProcessorTestRunner.assertValid( >> > > StandardProcessorTestRunner.java:334) >> > > at >> > > org.apache.nifi.processors.script.TestInvokeJavascript. >> > > testReadFlowFileContentAndStoreInFlowFileAttribute( >> > > TestInvokeJavascript.java:59) >> > > >> > > testScriptDefinedRelationship(org.apache.nifi.processors. >> > > script.TestInvokeJavascript) >> > > Time elapsed: 0.266 sec <<< FAILURE! >> > > java.lang.AssertionError: null >> > > at org.junit.Assert.fail(Assert.java:86) >> > > at org.junit.Assert.assertTrue(Assert.java:41) >> > > at org.junit.Assert.assertTrue(Assert.java:52) >> > > at >> > > org.apache.nifi.processors.script.TestInvokeJavascript. >> > > testScriptDefinedRelationship(TestInvokeJavascript.java:128) >> > > >> > > testScriptRoutesToFailure(org.apache.nifi.processors.script. >> > > TestInvokeJavascript) >> > > Time elapsed: 0.116 sec <<< FAILURE! >> > > java.lang.AssertionError: Processor has 1 validation failures: >> > > 'Validation' is invalid because An error occurred calling validate in >> the >> > > configured script Processor. >> > > >> > > at org.junit.Assert.fail(Assert.java:88) >> > > at >> > > org.apache.nifi.util.MockProcessContext.assertValid( >> > > MockProcessContext.java:251) >> > > at >> > > org.apache.nifi.util.StandardProcessorTestRunner.assertValid( >> > > StandardProcessorTestRunner.java:334) >> > > at >> > > org.apache.nifi.processors.script.TestInvokeJavascript. >> > > testScriptRoutesToFailure(TestInvokeJavascript.java:171) >> > > >> > > >> > > >> > > On Sat, Feb 18, 2017 at 7:59 PM, Tony Kurc wrote: >> > > >> > > > I've verified the signatures and hashes, but I can't build 1.1.2 >> > > > >> > > > >> > > > On Sat, Feb 18, 2017 at 7:11 PM, James Wing >> wrote: >> > > > >> > > >> +1 (non-binding) - went through release helper. >> > > >> >> > > >> On Thu, Feb 16, 2017 at 7:37 PM, Andy LoPresto < >> alopre...@apache.org> >> > > >> wrote: >> > > >> >> > > >> > Hello, >> > > >> > >> > > >> > I am pleased to be calling this vote for the source release of >> > Apache >> > > >> NiFi >> > > >> > nifi-1.1.2. >> > > >> > >> > > >> > The source zip, including signatures, digests, etc. can be found >> at: >> > > >> > https://repository.apache.org/content/repositories/orgapache >> > nifi-1098 >> > > >> > >> > > >> > The Git tag is nifi-1.1.2-RC1 >> > > >> > The Git commit ID is 51fad01f5daf33716b8b5379c32ee932d91c8c63 >> > > >> > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= >> > > >> > 51fad01f5daf33716b8b5379c32ee932d91c8c63
Re: [VOTE] Release Apache NiFi 0.7.2
+1 (non-binding) Verified signature, hashes Contrib-check build against fresh local repo Simple flow on 3 node cluster On Sat, Feb 18, 2017 at 3:45 PM, Joe Wittwrote: > James > > It is simply enough that someone volunteered to RM the release. If time is > available to help review/vote then great. Same with the 1.x release. > > Thanks > Joe > > On Feb 18, 2017 2:59 PM, "James Wing" wrote: > > > The unifying theme of 0.7.2 and 1.1.2 appears to be NIFI-3487 "Refactor > > user formatting". Is this urgent? > > > > https://issues.apache.org/jira/browse/NIFI-3487 > > https://github.com/apache/nifi/commit/bd88e4335ad151592f1310996e9a05 > > 13b7f0829a > > > > > > Thanks, > > > > James > > > > > > On Fri, Feb 17, 2017 at 9:55 AM, Joe Witt wrote: > > > > > Mike, > > > > > > You're absolutely right that there are some good fixes to be included > > > in an upcoming release. There is no reason someone couldn't put > > > together an 0.7.3. > > > > > > This is just something that we're wanting resolved and have the energy > > > to push forward and doesn't require additional testing as inclusion of > > > other items would. > > > > > > Please by no means see this as a deterrent to progression on an 0.7.3. > > > > > > Thanks > > > Joe > > > > > > On Fri, Feb 17, 2017 at 12:38 PM, Michael Moser > > > wrote: > > > > I'm sad that 0.7.2 does not contain some of the other bug fixes > > currently > > > > on the 0.x branch. It doesn't seem like it would have cost very much > > to > > > > just include them. > > > > > > > > +0 (non binding) > > > > > > > > -- Mike > > > > > > > > > > > > On Thu, Feb 16, 2017 at 11:42 PM, Andy LoPresto < > alopre...@apache.org> > > > > wrote: > > > > > > > >> Hello, > > > >> > > > >> I am pleased to be calling this vote for the source release of > Apache > > > NiFi > > > >> nifi-0.7.2. > > > >> > > > >> The source zip, including signatures, digests, etc. can be found at: > > > >> https://repository.apache.org/content/repositories/ > orgapachenifi-1099 > > > >> > > > >> The Git tag is nifi-0.7.2-RC1 > > > >> The Git commit ID is 831ac6939df7d418cadb336eedb4e09fb97541a1 > > > >> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= > > > >> 831ac6939df7d418cadb336eedb4e09fb97541a1 > > > >> > > > >> Checksums of nifi-0.7.2-source-release.zip: > > > >> MD5: efe9ea1cf0698a57a6829fe3829fc136 > > > >> SHA1: aee51164af34394c7017dae491b239a88b614865 > > > >> SHA256: 8cd02675003fca837ea0092b622560 > 0a4700b905e5214a751ae7ff833263 > > > 193b > > > >> > > > >> Release artifacts are signed with the following key: > > > >> https://people.apache.org/keys/committer/alopresto.asc > > > >> > > > >> KEYS file available here: > > > >> https://dist.apache.org/repos/dist/release/nifi/KEYS > > > >> > > > >> 2 issues were closed/resolved for this release: > > > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > > >> version=12339601=12316020 > > > >> > > > >> Release note highlights can be found here: > > > >> https://cwiki.apache.org/confluence/display/NIFI/ > > > >> Release+Notes#ReleaseNotes-Version0.7.2 > > > >> > > > >> The vote will be open for 96 hours (over holiday weekend). > > > >> Please download the release candidate and evaluate the necessary > items > > > >> including checking hashes, signatures, build > > > >> from source, and test. The please vote: > > > >> > > > >> [ ] +1 Release this package as nifi-0.7.2 > > > >> [ ] +0 no opinion > > > >> [ ] -1 Do not release this package because becauseā¦ > > > >> > > > >> Andy LoPresto > > > >> alopre...@apache.org > > > >> *alopresto.apa...@gmail.com * > > > >> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > > >> > > > >> > > > > > >
Re: [VOTE] Release Apache NiFi 1.1.2
+1 (non-binding) Verified signature, checksums Contrib check build with Oracle jdk 1.8.0_121 on Ubuntu, fresh local repo Tested non-secured cluster with simple flow Tested secured cluster with simple flow, command line site to site client On Sun, Feb 19, 2017 at 9:01 AM, Tony Kurcwrote: > +1 (binding) > > Rebuilt successfully with jdk 1.8.0_121. Ran some simple flows without > issue. > > On Feb 18, 2017 8:09 PM, "Aldrin Piri" wrote: > > > On a hunch, but I feel like there have been reported issues and/or I have > > personally experienced them with u45. Is it possible to get something a > > bit newer? > > > > On Sat, Feb 18, 2017 at 8:02 PM, Tony Kurc wrote: > > > > > Something went terribly wrong when I was pasting my maven angrygrams. > Do > > > these look like environment problems? > > > > > > ($ mvn --version > > > Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; > > > 2015-04-22T07:57:37-04:00) > > > Maven home: /opt/maven/apache-maven-3.3.3 > > > Java version: 1.8.0_45, vendor: Oracle Corporation > > > Java home: /opt/java/jdk1.8.0_45/jre > > > Default locale: en_US, platform encoding: UTF-8 > > > OS name: "linux", version: "3.13.0-108-generic", arch: "amd64", family: > > > "unix" > > > ): > > > > > > testReadFlowFileContentAndStoreInFlowFileAttribute(org. > > > apache.nifi.processors.script.TestInvokeJavascript) > > > Time elapsed: 1.35 sec <<< FAILURE! > > > java.lang.AssertionError: Processor has 1 validation failures: > > > 'Validation' validated against > > > 'target/test/resources/javascript/test_reader.js' is invalid because > An > > > error occurred calling validate in the configured script Processor. > > > > > > at org.junit.Assert.fail(Assert.java:88) > > > at > > > org.apache.nifi.util.MockProcessContext.assertValid( > > > MockProcessContext.java:251) > > > at > > > org.apache.nifi.util.StandardProcessorTestRunner.assertValid( > > > StandardProcessorTestRunner.java:334) > > > at > > > org.apache.nifi.processors.script.TestInvokeJavascript. > > > testReadFlowFileContentAndStoreInFlowFileAttribute( > > > TestInvokeJavascript.java:59) > > > > > > testScriptDefinedRelationship(org.apache.nifi.processors. > > > script.TestInvokeJavascript) > > > Time elapsed: 0.266 sec <<< FAILURE! > > > java.lang.AssertionError: null > > > at org.junit.Assert.fail(Assert.java:86) > > > at org.junit.Assert.assertTrue(Assert.java:41) > > > at org.junit.Assert.assertTrue(Assert.java:52) > > > at > > > org.apache.nifi.processors.script.TestInvokeJavascript. > > > testScriptDefinedRelationship(TestInvokeJavascript.java:128) > > > > > > testScriptRoutesToFailure(org.apache.nifi.processors.script. > > > TestInvokeJavascript) > > > Time elapsed: 0.116 sec <<< FAILURE! > > > java.lang.AssertionError: Processor has 1 validation failures: > > > 'Validation' is invalid because An error occurred calling validate in > the > > > configured script Processor. > > > > > > at org.junit.Assert.fail(Assert.java:88) > > > at > > > org.apache.nifi.util.MockProcessContext.assertValid( > > > MockProcessContext.java:251) > > > at > > > org.apache.nifi.util.StandardProcessorTestRunner.assertValid( > > > StandardProcessorTestRunner.java:334) > > > at > > > org.apache.nifi.processors.script.TestInvokeJavascript. > > > testScriptRoutesToFailure(TestInvokeJavascript.java:171) > > > > > > > > > > > > On Sat, Feb 18, 2017 at 7:59 PM, Tony Kurc wrote: > > > > > > > I've verified the signatures and hashes, but I can't build 1.1.2 > > > > > > > > > > > > On Sat, Feb 18, 2017 at 7:11 PM, James Wing > wrote: > > > > > > > >> +1 (non-binding) - went through release helper. > > > >> > > > >> On Thu, Feb 16, 2017 at 7:37 PM, Andy LoPresto < > alopre...@apache.org> > > > >> wrote: > > > >> > > > >> > Hello, > > > >> > > > > >> > I am pleased to be calling this vote for the source release of > > Apache > > > >> NiFi > > > >> > nifi-1.1.2. > > > >> > > > > >> > The source zip, including signatures, digests, etc. can be found > at: > > > >> > https://repository.apache.org/content/repositories/orgapache > > nifi-1098 > > > >> > > > > >> > The Git tag is nifi-1.1.2-RC1 > > > >> > The Git commit ID is 51fad01f5daf33716b8b5379c32ee932d91c8c63 > > > >> > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= > > > >> > 51fad01f5daf33716b8b5379c32ee932d91c8c63 > > > >> > > > > >> > Checksums of nifi-1.1.2-source-release.zip: > > > >> > MD5: 31d20a09955fac32d5b4147c497deede > > > >> > SHA1: 9f8f2ce00397d990dfb0890f9b1ede70dca4f25e > > > >> > SHA256: 0f57b5ae7f5e1d7f1289d779df39f2 > > 0d70af0ffd92cb01b265beb90b309b > > > >> 747e > > > >> > > > > >> > Release artifacts are signed with the following key: > > > >> > https://people.apache.org/keys/committer/alopresto.asc > > > >> > > > > >> > KEYS file available here: > > > >> >
Re: [VOTE] Release Apache NiFi 1.1.2
+1 (binding) Rebuilt successfully with jdk 1.8.0_121. Ran some simple flows without issue. On Feb 18, 2017 8:09 PM, "Aldrin Piri"wrote: > On a hunch, but I feel like there have been reported issues and/or I have > personally experienced them with u45. Is it possible to get something a > bit newer? > > On Sat, Feb 18, 2017 at 8:02 PM, Tony Kurc wrote: > > > Something went terribly wrong when I was pasting my maven angrygrams. Do > > these look like environment problems? > > > > ($ mvn --version > > Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; > > 2015-04-22T07:57:37-04:00) > > Maven home: /opt/maven/apache-maven-3.3.3 > > Java version: 1.8.0_45, vendor: Oracle Corporation > > Java home: /opt/java/jdk1.8.0_45/jre > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "linux", version: "3.13.0-108-generic", arch: "amd64", family: > > "unix" > > ): > > > > testReadFlowFileContentAndStoreInFlowFileAttribute(org. > > apache.nifi.processors.script.TestInvokeJavascript) > > Time elapsed: 1.35 sec <<< FAILURE! > > java.lang.AssertionError: Processor has 1 validation failures: > > 'Validation' validated against > > 'target/test/resources/javascript/test_reader.js' is invalid because An > > error occurred calling validate in the configured script Processor. > > > > at org.junit.Assert.fail(Assert.java:88) > > at > > org.apache.nifi.util.MockProcessContext.assertValid( > > MockProcessContext.java:251) > > at > > org.apache.nifi.util.StandardProcessorTestRunner.assertValid( > > StandardProcessorTestRunner.java:334) > > at > > org.apache.nifi.processors.script.TestInvokeJavascript. > > testReadFlowFileContentAndStoreInFlowFileAttribute( > > TestInvokeJavascript.java:59) > > > > testScriptDefinedRelationship(org.apache.nifi.processors. > > script.TestInvokeJavascript) > > Time elapsed: 0.266 sec <<< FAILURE! > > java.lang.AssertionError: null > > at org.junit.Assert.fail(Assert.java:86) > > at org.junit.Assert.assertTrue(Assert.java:41) > > at org.junit.Assert.assertTrue(Assert.java:52) > > at > > org.apache.nifi.processors.script.TestInvokeJavascript. > > testScriptDefinedRelationship(TestInvokeJavascript.java:128) > > > > testScriptRoutesToFailure(org.apache.nifi.processors.script. > > TestInvokeJavascript) > > Time elapsed: 0.116 sec <<< FAILURE! > > java.lang.AssertionError: Processor has 1 validation failures: > > 'Validation' is invalid because An error occurred calling validate in the > > configured script Processor. > > > > at org.junit.Assert.fail(Assert.java:88) > > at > > org.apache.nifi.util.MockProcessContext.assertValid( > > MockProcessContext.java:251) > > at > > org.apache.nifi.util.StandardProcessorTestRunner.assertValid( > > StandardProcessorTestRunner.java:334) > > at > > org.apache.nifi.processors.script.TestInvokeJavascript. > > testScriptRoutesToFailure(TestInvokeJavascript.java:171) > > > > > > > > On Sat, Feb 18, 2017 at 7:59 PM, Tony Kurc wrote: > > > > > I've verified the signatures and hashes, but I can't build 1.1.2 > > > > > > > > > On Sat, Feb 18, 2017 at 7:11 PM, James Wing wrote: > > > > > >> +1 (non-binding) - went through release helper. > > >> > > >> On Thu, Feb 16, 2017 at 7:37 PM, Andy LoPresto > > >> wrote: > > >> > > >> > Hello, > > >> > > > >> > I am pleased to be calling this vote for the source release of > Apache > > >> NiFi > > >> > nifi-1.1.2. > > >> > > > >> > The source zip, including signatures, digests, etc. can be found at: > > >> > https://repository.apache.org/content/repositories/orgapache > nifi-1098 > > >> > > > >> > The Git tag is nifi-1.1.2-RC1 > > >> > The Git commit ID is 51fad01f5daf33716b8b5379c32ee932d91c8c63 > > >> > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= > > >> > 51fad01f5daf33716b8b5379c32ee932d91c8c63 > > >> > > > >> > Checksums of nifi-1.1.2-source-release.zip: > > >> > MD5: 31d20a09955fac32d5b4147c497deede > > >> > SHA1: 9f8f2ce00397d990dfb0890f9b1ede70dca4f25e > > >> > SHA256: 0f57b5ae7f5e1d7f1289d779df39f2 > 0d70af0ffd92cb01b265beb90b309b > > >> 747e > > >> > > > >> > Release artifacts are signed with the following key: > > >> > https://people.apache.org/keys/committer/alopresto.asc > > >> > > > >> > KEYS file available here: > > >> > https://dist.apache.org/repos/dist/release/nifi/KEYS > > >> > > > >> > 2 issues were closed/resolved for this release: > > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > >> > version=12339600=12316020 > > >> > > > >> > Release note highlights can be found here: > > >> > https://cwiki.apache.org/confluence/display/NIFI/ > > >> > Release+Notes#ReleaseNotes-Version1.1.2 > > >> > > > >> > The vote will be open for 96 hours (over holiday weekend). > > >> > Please download the release candidate and evaluate the necessary > items > > >> > including checking
Re: travis-ci auto cancellation
Aldrin, The feature is enabled and seems to be working greatly. The only thing I am keeping an eye on are overly extensive delays due to resource allocation. I suspect once a job gets cancelled, the next one gets shoved to the end of the queue. Depending on my findings I may feed the travis folks with some suggestions. Let me know if you have issues. On Sun, Feb 19, 2017 at 12:15 PM, Aldrin Piriwrote: > Sounds like a superb feature to enable. Anything we can do to be more > effective with our Travis cycles is most welcomed. > > On Fri, Feb 17, 2017 at 8:22 AM, Andre wrote: > > > dev, > > > > Would you mind if I configured the NiFi, MiNiFi and MiNiFI-CPP travis-ci > > integration to perform auto-cancellation when new commits are pushed to > the > > same branch or PR? > > > > This should significantly reduce the number of builds we do per busy days > > and offer benefits to the whole community. > > > > Cheers > > >