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

fix: Build strategy picked up from XML configuration and properties #335

Merged
merged 1 commit into from
Aug 3, 2020

Conversation

manusa
Copy link
Member

@manusa manusa commented Aug 3, 2020

Description

fix #334: Build strategy picked up from XML configuration and properties

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change
  • Chore (non-breaking change which doesn't affect codebase;
    test, version modification, documentation, etc.)

Checklist

@rohanKanojia
Copy link
Member

strange, Does setting parameter in maven XML config doesn't set property too?

@manusa manusa force-pushed the fix/#334-build-strategy-config branch from 35e9753 to 3d92246 Compare August 3, 2020 10:42
@manusa
Copy link
Member Author

manusa commented Aug 3, 2020

strange, Does setting parameter in maven XML config doesn't set property too?

Nope, it's the other way around. Setting a property (XML, command-line) will set the parameter given it's properly annotated `@Parameter(property="whatever")

@manusa
Copy link
Member Author

manusa commented Aug 3, 2020

There are probably a few more cases left around the code that weren't addressed in #248. It's really hard to tack down all of the properties that should be "shared" in a configuration since they are scattered all around and used in the most creative possible ways.

@codecov
Copy link

codecov bot commented Aug 3, 2020

Codecov Report

Merging #335 into master will not change coverage.
The diff coverage is 50.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #335   +/-   ##
=========================================
  Coverage     33.76%   33.76%           
  Complexity     2174     2174           
=========================================
  Files           364      364           
  Lines         18567    18567           
  Branches       2741     2740    -1     
=========================================
  Hits           6270     6270           
- Misses        11547    11548    +1     
+ Partials        750      749    -1     
Impacted Files Coverage Δ Complexity Δ
...be/maven/plugin/mojo/build/AbstractDockerMojo.java 0.00% <0.00%> (ø) 0.00 <0.00> (ø)
...ipse/jkube/kit/config/service/JKubeServiceHub.java 84.44% <100.00%> (+1.83%) 16.00 <3.00> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 90136e0...76f7281. Read the comment docs.

@manusa manusa force-pushed the fix/#334-build-strategy-config branch from 3d92246 to 76f7281 Compare August 3, 2020 12:15
@sonarqubecloud
Copy link

sonarqubecloud bot commented Aug 3, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

75.0% 75.0% Coverage
0.0% 0.0% Duplication

warning The version of Java (1.8.0_131) you have used to run this analysis is deprecated and we will stop accepting it from October 2020. Please update to at least Java 11.
Read more here

@manusa manusa merged commit f9e415f into eclipse-jkube:master Aug 3, 2020
@manusa manusa deleted the fix/#334-build-strategy-config branch August 3, 2020 12:52
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.

BuildStrategy jib produces exception "Service hub created without a docker access to a docker daemon"
2 participants