Open katilp opened 3 years ago
katilp
commented
3 years ago Make sure you actually run the GitHub workflow in your own fork. There are no run workflows visible in https://github.com/roaatamimi/AOD2NanoAODOutreachTool/actions and no pull request which would have triggered that workflow in https://github.com/roaatamimi/AOD2NanoAODOutreachTool/pulls
Enable the github workflows and start the test as explained above. Thanks!
roaatamimi
commented
3 years ago Hi kati ,
I Think i need your help in doing this , can we have a zoom meeting when you have a time that works for you .
best regards , roua Tamimi
[image: image.png]
On Fri, Apr 16, 2021 at 1:58 PM Kati Lassila-Perini < @.***> wrote:
Make sure you actually run the GitHub workflow in your own fork. There are no run workflows visible in https://github.com/roaatamimi/AOD2NanoAODOutreachTool/actions and no pull request which would have triggered that workflow in https://github.com/roaatamimi/AOD2NanoAODOutreachTool/pulls
Enable the github workflows and start the test as explained above. Thanks!
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/cms-dpoa/cms-dpoa-getting-started/issues/64#issuecomment-821095219, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASZLUI6K3XNV6KSH2WAIKYLTJAJ4DANCNFSM42OTMSLQ .
katilp
commented
3 years ago OK, would today at 14 CEST do? Or on Monday?
roaatamimi
commented
3 years ago Sure, that works for me.
On Fri, 16 Apr 2021 at 2:14 PM Kati Lassila-Perini @.***> wrote:
OK, would today at 14 CEST do? Or on Monday?
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/cms-dpoa/cms-dpoa-getting-started/issues/64#issuecomment-821103648, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASZLUI4RW2UFAO6ORQGSZYLTJAL2LANCNFSM42OTMSLQ .
The exercise in https://cms-opendata-workshop.github.io/workshop-lesson-docker-preexercises/05-validation/index.html was a very simple one-step workflow, i.e. a collection of commands.
Have a look at how a similar one-step process is implemented as an automated test in
This code is an example code for the CMS open data, available also through http://opendata.cern.ch/record/12340
Make a "fork" of the repository (top right of the github page).
Enable the github workflows in your fork from Settings -> Actions from the github web interface of your forked repository.
Start the test workflow by editing a file (whatever edit is OK, in this case, it is needed just to start a pull request which triggers the workflow) and doing a pull request (to your own fork, not to the original).
In this case, the job does not run on your own computer, but on "runners" that GitHub makes available for testing.
You can follow the progress of the workflows in the "Actions" tab.