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.

Sign up for GitHub

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

Jump to bottom

Build order strategy #592

Closed
lburgazzoli opened this issue Apr 8, 2019 · 5 comments · Fixed by #4523
Closed

Build order strategy #592

lburgazzoli opened this issue Apr 8, 2019 · 5 comments · Fixed by #4523
Assignees
@christophd
Labels
area/build-operator Related to the internal image build operator kind/feature New feature or request status/never-stale
Milestone
2.0.0

Comments

@lburgazzoli
Copy link
Contributor

The builder state machine does not define an order in which queue build are executed so we can provide a number of strategies like:

  • fifo: execute the requests in the order they have been submitted
  • dependencies: try to maximize base image re-use so build order should depend on dependencies required by the build
@lburgazzoli lburgazzoli added the kind/feature New feature or request label Apr 8, 2019
@lburgazzoli lburgazzoli changed the title build order strategy Build order strategy Apr 8, 2019
@lburgazzoli lburgazzoli added this to the 1.0.0 milestone May 22, 2019
@nicolaferraro nicolaferraro added area/core Core features of the integration platform area/build-operator Related to the internal image build operator and removed area/core Core features of the integration platform labels May 28, 2019
@nicolaferraro nicolaferraro modified the milestones: 1.0.0, post 1.0.0 Apr 28, 2020
@lburgazzoli lburgazzoli mentioned this issue Nov 2, 2020
Closed
@nicolaferraro nicolaferraro modified the milestones: 1.3.0, 1.4.0 Dec 22, 2020
@astefanutti astefanutti mentioned this issue Feb 19, 2021
Merged
2 tasks
@nicolaferraro nicolaferraro modified the milestones: 1.4.0, 1.5.0 Mar 16, 2021
@nicolaferraro nicolaferraro modified the milestones: 1.5.0, 1.6.0 Jul 5, 2021
@nicolaferraro nicolaferraro modified the milestones: 1.6.0, 1.7.0 Sep 7, 2021
@nicolaferraro nicolaferraro modified the milestones: 1.7.0, 1.8.0 Nov 15, 2021
@oscerd oscerd modified the milestones: 1.8.0, 1.9.0 Jan 19, 2022
@oscerd oscerd modified the milestones: 1.9.0, 1.9.1 Apr 26, 2022
@oscerd oscerd modified the milestones: 1.9.1, 1.9.2 May 13, 2022
@oscerd oscerd modified the milestones: 1.9.2, 2.0.0 May 23, 2022
christophd added a commit to christophd/camel-k that referenced this issue Jun 28, 2023
@christophd
fix(apache#592): Introduce build order strategy
5d9c834 
- Run builds on same operator namespace with user defined strategy
- Default strategy is "sequential" running only one single build at a time
- Also support "fifo" strategy where builds are run/queued based on their creation timestamp. This strategy allows parallel builds as long as individual build dependency lists are not colliding
- Users may adjust/overwrite the build order strategy via install command option, in the (local) integration platform settings or via the builder trait option
- Max number of running builds limitation is not affected by the build order strategy (ensure to always obey the limitation)
christophd added a commit to christophd/camel-k that referenced this issue Jun 28, 2023
@christophd
fix(apache#592): Introduce build order strategy
d08503a 
- Run builds on same operator namespace with user defined strategy
- Default strategy is "sequential" running only one single build at a time
- Also support "fifo" strategy where builds are run/queued based on their creation timestamp. This strategy allows parallel builds as long as individual build dependency lists are not colliding
- Users may adjust/overwrite the build order strategy via install command option, in the (local) integration platform settings or via the builder trait option
- Max number of running builds limitation is not affected by the build order strategy (ensure to always obey the limitation)
christophd added a commit to christophd/camel-k that referenced this issue Jun 28, 2023
@christophd
fix(apache#592): Introduce build order strategy
bda1d26 
- Run builds on same operator namespace with user defined strategy
- Default strategy is "sequential" running only one single build at a time
- Also support "fifo" strategy where builds are run/queued based on their creation timestamp. This strategy allows parallel builds as long as individual build dependency lists are not colliding
- Users may adjust/overwrite the build order strategy via install command option, in the (local) integration platform settings or via the builder trait option
- Max number of running builds limitation is not affected by the build order strategy (ensure to always obey the limitation)
christophd added a commit to christophd/camel-k that referenced this issue Jun 29, 2023
@christophd
fix(apache#592): Introduce build order strategy
91b1695 
- Run builds on same operator namespace with user defined strategy
- Default strategy is "sequential" running only one single build at a time
- Also support "fifo" strategy where builds are run/queued based on their creation timestamp. This strategy allows parallel builds as long as individual build dependency lists are not colliding
- Users may adjust/overwrite the build order strategy via install command option, in the (local) integration platform settings or via the builder trait option
- Max number of running builds limitation is not affected by the build order strategy (ensure to always obey the limitation)
christophd added a commit to christophd/camel-k that referenced this issue Jun 29, 2023
@christophd
fix(apache#592): Introduce build order strategy
bfa8dc6 
- Run builds on same operator namespace with user defined strategy
- Default strategy is "sequential" running only one single build at a time
- Also support "fifo" strategy where builds are run/queued based on their creation timestamp. This strategy allows parallel builds as long as individual build dependency lists are not colliding
- Users may adjust/overwrite the build order strategy via install command option, in the (local) integration platform settings or via the builder trait option
- Max number of running builds limitation is not affected by the build order strategy (ensure to always obey the limitation)
christophd added a commit to christophd/camel-k that referenced this issue Jun 29, 2023
@christophd
fix(apache#592): Introduce build order strategy
b06bea2 
- Run builds on same operator namespace with user defined strategy
- Default strategy is "sequential" running only one single build at a time
- Also support "fifo" strategy where builds are run/queued based on their creation timestamp. This strategy allows parallel builds as long as individual build dependency lists are not colliding
- Users may adjust/overwrite the build order strategy via install command option, in the (local) integration platform settings or via the builder trait option
- Max number of running builds limitation is not affected by the build order strategy (ensure to always obey the limitation)
christophd added a commit to christophd/camel-k that referenced this issue Jun 30, 2023
@christophd
fix(apache#592): Introduce build order strategy
2e05e48 
- Run builds on same operator namespace with user defined strategy
- Default strategy is "sequential" running only one single build at a time
- Also support "fifo" strategy where builds are run/queued based on their creation timestamp. This strategy allows parallel builds as long as individual build dependency lists are not colliding
- Users may adjust/overwrite the build order strategy via install command option, in the (local) integration platform settings or via the builder trait option
- Max number of running builds limitation is not affected by the build order strategy (ensure to always obey the limitation)
christophd added a commit to christophd/camel-k that referenced this issue Jul 3, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
72dd42c 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 4, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
8a5e171 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 4, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
db00884 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 4, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
5ab1065 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 4, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
a9f25b1 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
@squakez squakez linked a pull request Jul 4, 2023 that will close this issue
fix(#592): Introduce build order strategy #4523
Merged
christophd added a commit to christophd/camel-k that referenced this issue Jul 4, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
f4a2584 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 4, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
76658aa 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 4, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
332e29a 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 5, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
ef6bbca 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 5, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
b851342 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 5, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
f157033 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 5, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
cde5daa 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 5, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
fb15b3b 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 6, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
67706ef 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 6, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
15a7e4f 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 6, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
6d54955 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit to christophd/camel-k that referenced this issue Jul 6, 2023
@christophd
fix(apache#592): Introduce build order strategy
262868e 
- Run builds on same operator namespace with user defined strategy
- Default strategy is "sequential" running only one single build at a time
- Also support "fifo" strategy where builds are run/queued based on their creation timestamp. This strategy allows parallel builds as long as individual build dependency lists are not colliding
- Users may adjust/overwrite the build order strategy via install command option, in the (local) integration platform settings or via the builder trait option
- Max number of running builds limitation is not affected by the build order strategy (ensure to always obey the limitation)
christophd added a commit to christophd/camel-k that referenced this issue Jul 6, 2023
@christophd
fix(apache#592): Introduce "dependencies" build order strategy
1973825 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
christophd added a commit that referenced this issue Jul 6, 2023
@christophd
fix(#592): Introduce build order strategy
ffa5313 
- Run builds on same operator namespace with user defined strategy
- Default strategy is "sequential" running only one single build at a time
- Also support "fifo" strategy where builds are run/queued based on their creation timestamp. This strategy allows parallel builds as long as individual build dependency lists are not colliding
- Users may adjust/overwrite the build order strategy via install command option, in the (local) integration platform settings or via the builder trait option
- Max number of running builds limitation is not affected by the build order strategy (ensure to always obey the limitation)
christophd added a commit that referenced this issue Jul 6, 2023
@christophd
fix(#592): Introduce "dependencies" build order strategy
21b9689 
- Introduce new build order strategy "dependencies"
- Strategy looks at the list of dependencies required by an Integration and queues builds that may reuse base images produced by other scheduled builds in order to leverage the incremental build option
- The strategy allows non-matching builds to run in parallel to each other
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@christophd christophd

Labels
area/build-operator Related to the internal image build operator kind/feature New feature or request status/never-stale
Projects
None yet
Milestone
2.0.0
Development

Successfully merging a pull request may close this issue.

fix(#592): Introduce build order strategy christophd/camel-k
6 participants
@christophd @astefanutti @lburgazzoli @nicolaferraro @oscerd @squakez