Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

new builder #223

Merged
merged 1 commit into from
Nov 15, 2018
Merged

new builder #223

merged 1 commit into from
Nov 15, 2018

Conversation

lburgazzoli
Copy link
Contributor

This PR is aimed to introduce a flexible builder to accommodate different build needs without having to introduces conditional paths in the current build manager.

Next step are:

  • let the traits inject specific build step
  • split the build in different go routines according to the building phase

@lburgazzoli lburgazzoli added the status/wip Work in progress label Nov 15, 2018
Copy link
Member

@nicolaferraro nicolaferraro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds really good. Just a note about the Camel version..

//TODO: camel version should be retrieved from an external request or provided as static version
GroupID: "org.apache.camel",
ArtifactID: "camel-bom",
Version: "2.22.1",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we switched to "2.22.2"

return request.Steps[i].Phase() < request.Steps[j].Phase()
})

for _, step := range request.Steps {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this means that the phases are no more interleaved, so a full build needs to be completed before a new one is started.
It solves also the problem of the initial contexts not being based one on another sometimes (e.g. randomly the Groovy context is not based on the JVM one)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see you've added this to the next things to do, but I'm not sure if it helps using the old strategy...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes a full build is needed now, it is much simpler and it avoid clashes as you said. About parallel build, yeah, I'm not sure they are needed, so let's keep it simple for the moment.

@lburgazzoli lburgazzoli changed the title DO NOT MERGE - new builder poc new builder Nov 15, 2018
@lburgazzoli lburgazzoli removed the status/wip Work in progress label Nov 15, 2018
@lburgazzoli
Copy link
Contributor Author

@nicolaferraro fixed, should bre ready to merge

@nicolaferraro nicolaferraro merged commit 84985a9 into apache:master Nov 15, 2018
@lburgazzoli lburgazzoli deleted the build-manager branch November 15, 2018 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants