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

added skip config for ui build-check #3030

Merged
merged 9 commits into from Mar 2, 2022
Merged

added skip config for ui build-check #3030

merged 9 commits into from Mar 2, 2022

Conversation

parthp2107
Copy link
Contributor

Describe your changes :

Fix #3016

Type of change :

  • Bug fix
  • Improvement

Checklist:

  • I have read the CONTRIBUTING document.
  • I have performed a self-review of my own.
  • I have tagged my reviewers below.
  • I have commented on my code, particularly in hard-to-understand areas.
  • My changes generate no new warnings.
  • I have added tests that prove my fix is effective or that my feature works.
  • All new and existing tests passed.

@parthp2107 parthp2107 marked this pull request as draft March 1, 2022 08:41
@sonarcloud
Copy link

sonarcloud bot commented Mar 1, 2022

[catalog] Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 19 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@parthp2107 parthp2107 marked this pull request as ready for review March 1, 2022 13:54
<!-- optional: the default phase is "generate-resources" -->
<phase>test</phase>
<configuration>
<!-- optional: if not specified, it will run gulp's default task
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we remove these comments?

They seem outdated

For reference on what these parameters are, one can always look at maven documentation

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Addressed in the latest commit.

@@ -83,7 +83,8 @@
"lint": "eslint \"./src/**/*.{js,jsx,ts,tsx}\"",
"lint:fix": "eslint './src/**/*.{js,jsx,ts,tsx}' --fix",
"pretty": "prettier . --config './.prettierrc' --write",
"build-check": "yarn run lint && yarn run test",
"build-check": "yarn run lint",
"build-test": "yarn run test",
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this included in the GitHub CI to detect frontend unit test failures?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes unit tests will run for mvn clean package, and same runs in CI

@shahsank3t shahsank3t merged commit bf25787 into main Mar 2, 2022
@shahsank3t shahsank3t deleted the skip-uiTests branch March 2, 2022 07:29
@mithmatt
Copy link
Collaborator

mithmatt commented Mar 2, 2022

#3072 (comment)

Does jest get installed on CI ?

Got this failure on a recent PR for 'yarn run build-test'

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.

mvn -DskipTests should skip UI tests
6 participants