Closed wg102 closed 2 years ago
Trying to figure out the steps to get the 1.7 version running locally.
git clone https://github.com/kubeflow/pipelines.git
git reset --hard 1d53de9
I am not positive if we will need to test both the frontend and the backend or if
npm run mock:api
will suffice.
Node version: apparently, node v 12
cd
to the frontend
folder
npm ci
npm start
port 3000
Do the npm run mock:api in a different cmd line. And it will open http://localhost:3000
TODO: Should we try a more recent version than indicated?
It needs Node Version 12, would that conflict with the other code that needs other version??
Note: will need to fix:
found 121 vulnerabilities (4 low, 19 moderate, 86 high, 12 critical)
Missing content:
const compilePipelineDocs = (
<div className={padding(10, 'b')}>
{t('expectedFileFormat')}{' '}
<ExternalLink href='https://www.kubeflow.org/docs/pipelines/sdk/build-component/#compile-the-pipeline'>
{t('compilePipelineDoc')}
</ExternalLink>
.
</div>
);
Notes on how to build the test: 1) Ensure you are running on node v12, I used nvm 2) cd to /frontend 3) npm test a dialog prompt will come up just press 'a' to do all of them
Relates to the epic of Kubeflow 1.4 Upgrade
In the 1.4.1 Release documentation it says that the recommended version of pipelines is 1.7.0. Therefore this issue is to do all the work of upgrading our kubeflow-pipelines repo to match said 1.7.0 version.
In our current release of pipelines seems to be 1.2. Recommended version with Kubeflow 1.4 is Pipelines 1.7
There were previous issues creating for upgrading pipelines, and upstreaming. This might be a good ocasion to update those issues as well with more appropriate content.
The only concern about pipelines is i18n since we did not add any new features.
Steps of rebasing: