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

Jib builder strategy enhancements #4703

Open
1 of 2 tasks
squakez opened this issue Aug 30, 2023 · 6 comments
Open
1 of 2 tasks

Jib builder strategy enhancements #4703

squakez opened this issue Aug 30, 2023 · 6 comments
Assignees
@gansheer
Labels
area/builder status/never-stale

Comments

@squakez
Copy link
Contributor

squakez commented Aug 30, 2023 •
edited
Loading

  • extract plugin version in camel-k-runtime
  • refactor the way we interact with maven to be able to reuse the code to generate a complete maven command in the publish task instead of using a temp file "MAVEN_CONTEXT"

Ref #4680
@squakez
Copy link
Contributor Author

squakez commented Aug 30, 2023

cc @gansheer

@gansheer
Copy link
Contributor

@squakez I will work on it.

@gansheer gansheer mentioned this issue Oct 5, 2023
Merged
gansheer added a commit to gansheer/camel-k-runtime that referenced this issue Oct 5, 2023
@gansheer
feat: Add jib plugins versions to catalog runtime metadata
ae50542 
Ref apache/camel-k#4703
gansheer added a commit to gansheer/camel-k that referenced this issue Oct 6, 2023
@gansheer
feat(core): Move jib plugins versions to camelcatalog
e9bf525 
Ref apache#4703

Extracted jib plugin versions to camel-k-runtime:
* use .spec.runtime.metadata values
* set default values for catalog backward compatibility
@gansheer gansheer mentioned this issue Oct 6, 2023
Merged
gansheer added a commit to gansheer/camel-k that referenced this issue Oct 6, 2023
@gansheer
feat(core): Move jib plugins versions to camelcatalog
97ceccd 
Ref apache#4703

Extracted jib plugin versions to camel-k-runtime:
* use .spec.runtime.metadata values
* set default values for catalog backward compatibility
gansheer added a commit to gansheer/camel-k that referenced this issue Oct 6, 2023
@gansheer
feat(core): Move jib plugins versions to camelcatalog
82ba67d 
Ref apache#4703

Extracted jib plugin versions to camel-k-runtime:
* use .spec.runtime.metadata values
* set default values for catalog backward compatibility
gansheer added a commit to gansheer/camel-k that referenced this issue Oct 6, 2023
@gansheer
feat(core): Move jib plugins versions to camelcatalog
2dabb6d 
Ref apache#4703

Extracted jib plugin versions to camel-k-runtime:
* use .spec.runtime.metadata values
* set default values for catalog backward compatibility
gansheer added a commit to gansheer/camel-k that referenced this issue Oct 6, 2023
@gansheer
feat(core): Move jib plugins versions to camelcatalog
375ada6 
Ref apache#4703

Extracted jib plugin versions to camel-k-runtime:
* use .spec.runtime.metadata values
* set default values for catalog backward compatibility
squakez pushed a commit to apache/camel-k-runtime that referenced this issue Oct 9, 2023
@gansheer @squakez
feat: Add jib plugins versions to catalog runtime metadata
3b36cdb 
Ref apache/camel-k#4703
squakez pushed a commit that referenced this issue Oct 9, 2023
@gansheer @squakez
feat(core): Move jib plugins versions to camelcatalog
e3e947f 
Ref #4703

Extracted jib plugin versions to camel-k-runtime:
* use .spec.runtime.metadata values
* set default values for catalog backward compatibility
@squakez
Copy link
Contributor Author

squakez commented Oct 17, 2023

I think this can be closed, right @gansheer ?

@squakez squakez added this to the 2.1.0 milestone Oct 17, 2023
@gansheer
Copy link
Contributor

The first point was done but not the second. I can create another issue with the refactoring and then we can close this one.

@squakez
Copy link
Contributor Author

squakez commented Oct 17, 2023

No. I'm updating this and leaving open for next milestone.

@squakez squakez modified the milestones: 2.1.0, 2.2.0 Oct 17, 2023
@squakez squakez modified the milestones: 2.2.0, 2.3.0 Jan 8, 2024
@squakez squakez removed this from the 2.3.0 milestone Apr 2, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Jul 2, 2024

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gansheer gansheer

Labels
area/builder status/never-stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gansheer @squakez