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: Print formatted message instead of throwing NPE #1295

Merged
merged 1 commit into from
Nov 4, 2020

Conversation

pawelpasterz
Copy link
Contributor

Fixes #1294

Test Plan

How do we know the code works?

  1. Prepare config, for instance:
    gcloud:
      app: [any app]
    flank:
      legacy-junit-result:
    
    (notice no value for legacy-junit-result)
  2. Run flank with created config
  3. Flank run should terminate with a message Invalid value for [legacy-junit-result]: no argument value found and without any stack trace
  4. Run again but with --legacy-junit-result flag
  5. Flank should proceed normally and legacy-junit-result should be equal true

Checklist

  • Unit tested

@pawelpasterz pawelpasterz force-pushed the 1294-fix-NPE-with-incorrect-config branch from a71e767 to ca0077f Compare November 4, 2020 07:03
@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2020

Timestamp: 2020-11-04 07:08:33
Buildscan url for ubuntu-workflow run 345020073
https://gradle.com/s/3b3xkc6mpg7tq

Copy link
Contributor

@Sloox Sloox left a comment

Choose a reason for hiding this comment

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

Nice change!

@mergify mergify bot merged commit 5547625 into master Nov 4, 2020
@mergify mergify bot deleted the 1294-fix-NPE-with-incorrect-config branch November 4, 2020 16:35
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.

Flank throws NPE when invalid config yml used
3 participants