This repository has been archived by the owner on May 7, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 18
Linking annotations from build pipeline to bayesian npm #264
Comments
arunkumars08
added a commit
to arunkumars08/fabric8-runtime-console
that referenced
this issue
Apr 11, 2017
…he build pipeline to pass as input to npm. Changes: 1. Moves the position of the Bayesian stack reports button to inside the pipelines stages - build-stage-view.component.html 2. Removes the existing bayesian includes from list.pipeline.component.html 3. Removes the hardcoded information from list.pipeline.component.ts 4. Made a version change in package.json as both fabric8-stack-analysis-ui and this change have to go in sync. Fixes fabric8-ui#264.
arunkumars08
added a commit
to arunkumars08/fabric8-runtime-console
that referenced
this issue
Apr 11, 2017
…he build pipeline to pass as input to npm. Changes: 1. Moves the position of the Bayesian stack reports button to inside the pipelines stages - build-stage-view.component.html 2. Removes the existing bayesian includes from list.pipeline.component.html 3. Removes the hardcoded information from list.pipeline.component.ts 4. Made a version change in package.json as both fabric8-stack-analysis-ui and this change have to go in sync. 5. Include the package module in various test cases to make it run without failing. Fixes fabric8-ui#264.
joshuawilson
pushed a commit
that referenced
this issue
Apr 11, 2017
…he build pipeline to pass as input to npm. Changes: 1. Moves the position of the Bayesian stack reports button to inside the pipelines stages - build-stage-view.component.html 2. Removes the existing bayesian includes from list.pipeline.component.html 3. Removes the hardcoded information from list.pipeline.component.ts 4. Made a version change in package.json as both fabric8-stack-analysis-ui and this change have to go in sync. 5. Include the package module in various test cases to make it run without failing. Fixes #264.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
No description provided.
The text was updated successfully, but these errors were encountered: