Skip to content

Conversation

@vojtechszocs
Copy link
Contributor

This PR adds new console-scripts package containing common scripts available to all packages.

This is conceptually similar to fabric8-ui scripts package. Reusing scripts across packages allows for aligning common workflows such as testing, linting, etc. and therefore improve monorepo cohesiveness.

"scripts": {
-  "test": "yarn --cwd ../.. run test packages/console-shared"
+  "test": "console-test"
}

Here's what happens when you run the console-test script:

  • check if the script was called from within the Console monorepo
  • execute yarn test packages/<caller-pkg> in the monorepo root directory

Note: Jest testRegex option was modified to allow future test co-location.

I've tested this by adding a temporary packages/console-shared/src/index.test.js file and running yarn test in the monorepo root and then in the packages/console-shared directory. Both global and package-specific test workflow works as expected.

@openshift-ci-robot openshift-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Apr 10, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vojtechszocs
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: bparees

If they are not already assigned, you can assign the PR to them by writing /assign @bparees in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@vojtechszocs
Copy link
Contributor Author

@openshift-ci-robot
Copy link
Contributor

@vojtechszocs: GitHub didn't allow me to request PR reviews from the following users: mareklibra, rawagner, jelkosz.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc @spadgett @jhadvig @christianvogt @priley86 @mareklibra @rawagner @jelkosz

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@vojtechszocs
Copy link
Contributor Author

vojtechszocs commented Apr 10, 2019

vojtechszocs wants to merge 20 commits

Edit: forgot to switch to master-next branch 🤦‍♂️ 😆

@vojtechszocs vojtechszocs changed the base branch from master to master-next April 10, 2019 16:56
@openshift-ci-robot openshift-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Apr 10, 2019
@@ -0,0 +1,5 @@
{
"extends": [
"../../integration-tests/.eslintrc"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Normally I'd create named ESLint configs, e.g. .eslintrc.node and .eslintrc.browser, but wanted to minimize my changes so just reusing an existing one for now.

@vojtechszocs
Copy link
Contributor Author

/retest

@christianvogt
Copy link
Contributor

@vojtechszocs often we add an argument to run a specific test, or extra jest options. Looks like this will not work with this approach when running the console-test within a package. What should a dev do in this case?

@vojtechszocs
Copy link
Contributor Author

@vojtechszocs often we add an argument to run a specific test, or extra jest options. Looks like this will not work with this approach when running the console-test within a package. What should a dev do in this case?

That's a good point, I missed that 😐

I'll update the console-test script to pass additional command line arguments (process.argv.slice(2)) to the yarn test execution.

@christianvogt
Copy link
Contributor

I don't think you can simply pass all the args because you're also adding the dir as an arg to run tests for the package. If the user wants to run tests for a specific file, they can't do so as all tests in the package will still be picked up.

@spadgett spadgett added this to the v4.2 milestone Apr 16, 2019
@openshift-ci-robot
Copy link
Contributor

@vojtechszocs: PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 24, 2019
@spadgett spadgett changed the base branch from master-next to master May 13, 2019 22:44
@vojtechszocs
Copy link
Contributor Author

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 26, 2019
@spadgett spadgett removed this from the v4.2 milestone Jul 29, 2019
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 20, 2020
@openshift-ci-robot
Copy link
Contributor

@vojtechszocs: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws 3797390 link /test e2e-aws
ci/prow/e2e-aws-console-olm 3797390 link /test e2e-aws-console-olm
ci/prow/e2e-aws-console 3797390 link /test e2e-aws-console
ci/prow/images 3797390 link /test images
ci/prow/frontend 3797390 link /test frontend
ci/prow/e2e-gcp 3797390 link /test e2e-gcp
ci/prow/e2e-gcp-console 3797390 link /test e2e-gcp-console
ci/prow/analyze 3797390 link /test analyze
ci/prow/kubevirt-plugin 3797390 link /test kubevirt-plugin

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 6, 2020
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci-robot
Copy link
Contributor

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants