CI/CD

[durandom]

not sure if this is the right repo.
How can we test the notebooks? Can we execute all cells before a build?

[harshad16]

not sure if this is the right repo.

@durandom for time being this repository feels the best place for discussion.

How can we test the notebooks? Can we execute all cells before a build?

Like a pre-test, if the notebook is in running condition?

[goern]

Like a pre-test, if the notebook is in running condition?

Ja, its a functional test before merge, before tag-release

[goern]

@crobby @vpavlin

[4n4nd]

@harshad16 maybe we can just run ipython my_notebook.ipynb inside the s2i tests and check if the command fails

[tumido]

Hi, we have something in plan and already in place in the openshift sme automation. Let's coordinate that with you. 🙂

• We use nbconvert to execute the notebooks in automation, can be reused as a CI.
• We plan on using nbtoolbelt to verify the formal side of notebooks as a CI pipeline.

Sources and config on that are internal for now, can be viewed here: https://gitlab.cee.redhat.com/mcliffor/openshift-sme-topic-modeling

[harshad16]

Hi, we have something in plan and already in place in the openshift sme automation. Let's coordinate that with you.

• We use nbconvert to execute the notebooks in automation, can be reused as a CI.
• We plan on using nbtoolbelt to verify the formal side of notebooks as a CI pipeline.

Sources and config on that are internal for now, can be viewed here: https://gitlab.cee.redhat.com/mcliffor/openshift-sme-topic-modeling

Surely, let coordinate, we will go over the following libraries and sync up with you.

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

/lifecycle stale

[harshad16]

/remove-lifecycle stale