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

JENKINS-43671# Test coverage investigation #1013

Merged
merged 2 commits into from
May 3, 2017

Conversation

vivek
Copy link
Collaborator

@vivek vivek commented Apr 28, 2017

haltOnFailure is false, that is building blueocean modules will not fail
build if coverage criteria is not met.

At present to enable this propert use -Djacoco.haltOnFailure=true with
mvn.

Description

See JENKINS-43671.

Submitter checklist

  • Link to JIRA ticket in description, if appropriate.
  • Change is code complete and matches issue description
  • Appropriate unit or acceptance tests or explanation to why this change has no tests
  • Reviewer's manual test instructions provided in PR description. See Reviewer's first task below.
  • Ran Acceptance Test Harness against PR changes.

Reviewer checklist

  • Run the changes and verified the change matches the issue description
  • Reviewed the code
  • Verified that the appropriate tests have been written or valid explanation given

haltOnFailure is false, that is building blueocean modules will not fail
build if coverage criteria is not met.

At present to enable this propert use -Djacoco.haltOnFailure=true with
mvn.
@michaelneale
Copy link
Member

nice

@vivek
Copy link
Collaborator Author

vivek commented May 1, 2017

@michaelneale I think we should let it merge. This will give warning but will be handy to determine if newly added code has good coverage or not. When we have all in good standing, we can turn on to fail if specific coverage threshold is not met.

@michaelneale
Copy link
Member

SGTM 🐝 in that case, s long as all tests happy etc.

@vivek
Copy link
Collaborator Author

vivek commented May 2, 2017

@michaelneale For some reason ATH is failing. There has only test coverage related changes in pom, any idea what could this be? https://ci.blueocean.io/blue/organizations/jenkins/ATH-Jenkinsfile/detail/master/2337/pipeline

@michaelneale
Copy link
Member

@vivek update it to master - as there was a recent change on tables that affect ATH validation, and then it should be ok. If not, I will take a look later.

@vivek
Copy link
Collaborator Author

vivek commented May 2, 2017

@michaelneale done. Lets see if it goes thru.

@michaelneale
Copy link
Member

@vivek ATH passes if you are happy then 🐝 from me as I think @i386 is happy

@vivek vivek merged commit 2490327 into master May 3, 2017
@vivek vivek deleted the task/JENKINS-43671-test-coverage branch May 3, 2017 01:36
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.

2 participants