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

Add custom build arguments in jib artifacts #1609

Merged
merged 2 commits into from Feb 14, 2019

Conversation

corneliusweig
Copy link
Contributor

Before, there was no way to pass custom arguments to the jib artifacts.
Now, there is the mavenArgs and gradleArgs field which expect a list of strings which is forwarded to the maven and gradle builder, respectively.

Fixes #1565

@codecov-io
Copy link

codecov-io commented Feb 5, 2019

Codecov Report

Merging #1609 into master will increase coverage by 0.02%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1609      +/-   ##
==========================================
+ Coverage   46.95%   46.97%   +0.02%     
==========================================
  Files         119      119              
  Lines        5143     5145       +2     
==========================================
+ Hits         2415     2417       +2     
  Misses       2480     2480              
  Partials      248      248
Impacted Files Coverage Δ
pkg/skaffold/jib/jib_maven.go 100% <100%> (ø) ⬆️
pkg/skaffold/jib/jib_gradle.go 100% <100%> (ø) ⬆️

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 9c13adb...78bd619. Read the comment docs.

@balopat balopat added the kokoro:run runs the kokoro jobs on a PR label Feb 6, 2019
@kokoro-team kokoro-team removed the kokoro:run runs the kokoro jobs on a PR label Feb 6, 2019
Copy link
Contributor

@dgageot dgageot left a comment

Choose a reason for hiding this comment

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

@corneliusweig Can you rename mavenArgs and gradleArgs to args?

@balopat balopat added the kokoro:run runs the kokoro jobs on a PR label Feb 8, 2019
@kokoro-team kokoro-team removed the kokoro:run runs the kokoro jobs on a PR label Feb 8, 2019
Cornelius Weig added 2 commits February 12, 2019 13:36
Before, there was no way to pass custom arguments to the jib artifacts.
Now, there is the `mavenArgs` and `gradleArgs` field which expect a list of strings which is forwarded to the maven and gradle builder, respectively.

Signed-off-by: Cornelius Weig <cornelius.weig@tngtech.com>
Signed-off-by: Cornelius Weig <cornelius.weig@tngtech.com>
@balopat balopat added the kokoro:run runs the kokoro jobs on a PR label Feb 14, 2019
@kokoro-team kokoro-team removed the kokoro:run runs the kokoro jobs on a PR label Feb 14, 2019
@dgageot dgageot merged commit b9c979d into GoogleContainerTools:master Feb 14, 2019
@corneliusweig corneliusweig deleted the jib-args branch February 14, 2019 22:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants