<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: How would you compare Nifi with Jenkins in-terms of Scheduling in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-would-you-compare-Nifi-with-Jenkins-in-terms-of/m-p/172326#M45925</link>
    <description>&lt;P&gt;Nifi's provenance UI provides very low level information. If operations team is interested in high level information then other option is publish provenance information to ElasticSearch and create a Kibana dashboard on top of it customized for operations team.&lt;/P&gt;</description>
    <pubDate>Mon, 14 Nov 2016 23:48:47 GMT</pubDate>
    <dc:creator>ninad_patkhedka</dc:creator>
    <dc:date>2016-11-14T23:48:47Z</dc:date>
    <item>
      <title>How would you compare Nifi with Jenkins in-terms of Scheduling</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-would-you-compare-Nifi-with-Jenkins-in-terms-of/m-p/172324#M45923</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;We have been using Jenkins for scheduling jobs, hence it is easy to schedule a job (or jobs, define dependencies etc) and keep track of each job run i.e if a job fails you get an alert etc. Hence for Operation teams, Jenkins is an easy platform to manage/keep track of jobs.&lt;/P&gt;&lt;P&gt;&lt;U&gt;I have following questions:&lt;/U&gt;&lt;/P&gt;&lt;P&gt;1. For scheduling jobs, what is the best tool: Jenkins or Nifi? &lt;/P&gt;&lt;P&gt;2. How could you operationalize a dataflow like you can in Jenkins? Meaning, if any individual dataflow fails, Operation team gets an alert, so they have complete visibility on each job run? &lt;/P&gt;&lt;P&gt;3. Can I (or should I, meaning does it sound reasonable) use Jenkins to launch DataFlows on Nifi? Just to let Operation team have a single UI to keep track of all jobs !&lt;/P&gt;&lt;P&gt;4. How can we track the status of each DataFlow run on Nifi? &lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Obaid&lt;/P&gt;</description>
      <pubDate>Fri, 11 Nov 2016 08:24:59 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-would-you-compare-Nifi-with-Jenkins-in-terms-of/m-p/172324#M45923</guid>
      <dc:creator>obaid_salikeen</dc:creator>
      <dc:date>2016-11-11T08:24:59Z</dc:date>
    </item>
    <item>
      <title>Re: How would you compare Nifi with Jenkins in-terms of Scheduling</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-would-you-compare-Nifi-with-Jenkins-in-terms-of/m-p/172325#M45924</link>
      <description>&lt;P&gt;I will try to answer your questions at a high level, and I (or others) can add detail as you need.&lt;/P&gt;&lt;P&gt;1. Jenkins and NiFi can both use CRON scheduling to start processing.&lt;/P&gt;&lt;P&gt;2. For any failure of a processor in a NiFi flow, you can route to a processor such as PutEmail to notify operation team members.&lt;/P&gt;&lt;P&gt;3. NiFi offers Data Provenance through which you can track how data flows through NiFi.  Data Provenance provides a way to search the Data Provenance repositories for flowfile names, component IDs, and other attributes to determine what happened during the data flow.  Jenkins has a more specific status display for jobs, but NiFi's Data Provenance UI may also serve your purpose, though it is more oriented towards data flow.&lt;/P&gt;&lt;P&gt;4. Data Provenance, described above, allows you to track the status of data flow in NiFi.&lt;/P&gt;&lt;P&gt;Do these answers help you, and are they detailed enough?&lt;/P&gt;</description>
      <pubDate>Fri, 11 Nov 2016 09:57:09 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-would-you-compare-Nifi-with-Jenkins-in-terms-of/m-p/172325#M45924</guid>
      <dc:creator>jts</dc:creator>
      <dc:date>2016-11-11T09:57:09Z</dc:date>
    </item>
    <item>
      <title>Re: How would you compare Nifi with Jenkins in-terms of Scheduling</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-would-you-compare-Nifi-with-Jenkins-in-terms-of/m-p/172326#M45925</link>
      <description>&lt;P&gt;Nifi's provenance UI provides very low level information. If operations team is interested in high level information then other option is publish provenance information to ElasticSearch and create a Kibana dashboard on top of it customized for operations team.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Nov 2016 23:48:47 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-would-you-compare-Nifi-with-Jenkins-in-terms-of/m-p/172326#M45925</guid>
      <dc:creator>ninad_patkhedka</dc:creator>
      <dc:date>2016-11-14T23:48:47Z</dc:date>
    </item>
  </channel>
</rss>

