-
Notifications
You must be signed in to change notification settings - Fork 659
NO-JIRA: Remove yarn-generate from post-install script #15373
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
base: main
Are you sure you want to change the base?
NO-JIRA: Remove yarn-generate from post-install script #15373
Conversation
@TheRealJon: This pull request explicitly references no jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
/retest |
1 similar comment
/retest |
5eecf6b
to
f054214
Compare
f054214
to
182e488
Compare
/retest |
2 similar comments
/retest |
/retest |
/retest cluster install failed |
/retest |
/test okd-scos-e2e-aws-ovn |
Should we update the |
@Mylanos That one does not need an update, since it skips the "build demo plugin" part in favor of reusing the existing files. |
/test okd-scos-e2e-aws-ovn |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Mylanos, TheRealJon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@TheRealJon: The following test failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
/label px-approved internal tech-debt |
/assign @yapei |
QE Approver |
@@ -9,11 +9,10 @@ RUN mkdir -p /src/console | |||
COPY . /src/console | |||
|
|||
WORKDIR /src/console/frontend | |||
RUN yarn install | |||
RUN yarn install && yarn generate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, why do we need yarn generate
here?
building demo plugin image without yarn generate
also works well
This is a build task and is repetitive when installing then immediately building, which is a very common use case.