Another approach would be to have a time-based build, say no more
frequently than once/day. You would lose granularity to a specific commit,
but reduce compute cycles required by reducing the number of builds being
executed.
Just a thought.
On Mon, Apr 19, 2021 at 2:34 PM David Handermann
Chris,,
Thanks for the description of the modular approach. Here is one GitHub
action that supports conditional execution based on Git changes:
https://github.com/dorny/paths-filter
It would take some effort to implement an approach that covers all the
bases, but using the Maven also-make and
Our approach is the use a `git diff` between source and destination
branches when a branch is merged (and the same for on dev branch builds).
Each component within the repo then checks for whether any files within its
directories were changed (bearing in mind a dev branch may consist of
multiple
Chris,
Yeah that would be very helpful. But do you have any idea how that
might be achieved in this environment?
Thanks
On Mon, Apr 19, 2021 at 10:33 AM Chris Sampson
wrote:
>
> Could an approach of building only the updated parts of the repo help to
> reduce build times?
>
> For example,
Could an approach of building only the updated parts of the repo help to
reduce build times?
For example, changes to the classes under the AWS bundle (and only that
bundle) would only need those classes to be built and tested.
Where such an approach gets a bit more complex is interdependence
This background is very helpful to keep in mind when evaluating new and
updated unit tests. There are definitely some expensive tests that could
be streamlined, but introducing a separate version lifecycle for framework
and extensions seems like it is becoming more necessary. Moving to a Java
11
Thanks for bringing this up. The most clear next step I can envision
at this point is that we break up our core framework from our
extensions. Not obvious how best to break this up but we need to.
The build times are insane.
Joe
On Mon, Apr 19, 2021 at 7:57 AM Otto Fowler wrote:
>
> As you can
As you can probably imagine, it takes a lot of resources in order to CI for all
the Apache projects. Periodically this becomes an issue, as the donated
resources from cloud CI providers ( Travis and now GitHub Actions ) end up
queuing and delaying builds across Apache projects because of
I have a few listed here
https://github.com/tspannhw/EverythingApacheNiFi
On Sun, Apr 18, 2021 at 10:22 AM Pinnamareddy, Gopal <
gopal.pinnamare...@alionscience.com> wrote:
> I’m looking to implement the NiFi Project scratch onwards, I was
> installed the server ec2 NiFi and business cases .
There are tons of tutorials on YouTube that are free, accessible and
decent quality. Start there if you're looking for that sort of
introduction.
On Sun, Apr 18, 2021 at 10:22 AM Pinnamareddy, Gopal
wrote:
>
> I’m looking to implement the NiFi Project scratch onwards, I was installed
> the
I’m looking to implement the NiFi Project scratch onwards, I was installed the
server ec2 NiFi and business cases . Please let me know any webnair or sessions
available fo r the project implementations. Looking forward to hear from you
Thank you
-Gopal
Sent from
11 matches
Mail list logo
