search

UTNAK / kepler16b-using-imce-vocabulary

Forked from a demo project for the openCAESAR platform
http://opencaesar.github.io/kepler16b-example/
0 stars 0 forks source link

Execute Simulation Code on a CICD Pipeline #7

Closed pogi7 closed 4 weeks ago

pogi7 commented 1 month ago

Checklist before submitting a feature request

Is your feature request related to a problem? If yes, describe the problem

I would like to execute the simulation code in #6 on a CICD Pipeline. I want the CICD pipeline to have at least 3 stages

  1. Build / Simulation
  2. Test
  3. Deploy

Describe the desired feature

I would like to execute the simulation code in #6 on a CICD Pipeline in order to see how simulations affect OML descriptions

Additional context

[Any additional context]

pogi7 commented 1 month ago

@UTNAK How to run CICD pipeline in GitHub Actions

  1. Config CICD pipeline to follow requirements in Dev Container
  2. Run on command line quarto render src/analysis/analysisShell.qmd
  3. Deploy to Github Pages using a bot
UTNAK commented 1 month ago

When I use r2u as an image for R, following errors happened.

> library(devtools); install_github('UTNAK/tansakusuR')
Loading required package: usethis
Using bundled GitHub PAT. Please add your own PAT using `gitcreds::gitcreds_set()`
Error: Failed to install 'unknown package' from GitHub:
  HTTP error 401.
  Bad credentials
  Rate limit remaining: 59/60
  Rate limit reset at: 2024-05-24 20:22:30 UTC

This might be related to the error in here

Now i am trying to use https://github.com/r-lib/pak in this branch

https://github.com/UTNAK/kepler16b-using-imce-vocabulary/tree/testing-r2u

The build task has been completed now! In the analysis task, 'quarto render' can't run with error below.

 quarto: command not found
UTNAK commented 4 weeks ago

I found the quarto -V command works when the command run in the build job.

Same thing happened for python -m nbconvert --output="analysis" --output-dir='.' --execute --to html src/analysis/analysisShell.ipynb --no-input.

In the current analysis.yml file, separating the job of building the environment from the job of executing commands results in an error that the command does not exist.

image