Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ci build fails for xblock #411

Closed
Talha-Rizwan opened this issue Nov 28, 2023 · 2 comments
Closed

Ci build fails for xblock #411

Talha-Rizwan opened this issue Nov 28, 2023 · 2 comments
Assignees

Comments

@Talha-Rizwan
Copy link

Hi,
I recently created an openedx xblock using the edx-cookiecutter template but turns out the github actions ci.yml is failing at this stage

- name: Create Build
      run: |
        rm -rf /tmp/myxblock-xblock
        XBLOCK=$(pwd) && cd /tmp/ && echo -e '\n\n\n\n\n' | cookiecutter $XBLOCK
        cd /tmp/myxblock-xblock && make help && pip install -e .
        cd /tmp/myxblock-xblock && make dev.build

Error:

-> Run rm -rf /tmp/myxblock-xblock
/home/runner/work/_temp/54fcbeee-2c42-4109-b7e4-76c22b1b61fa.sh: line 2: cookiecutter: command not found
Error: Process completed with exit code 127.

I also installed the cookiecutter in the ci but the build still failed with the following error:

A valid repository for "/home/runner/work/openedx-cmi5-xblock/openedx-cmi5-xblock" could not be found in the following locations:
/home/runner/work/openedx-cmi5-xblock/openedx-cmi5-xblock
/home/runner/work/openedx-cmi5-xblock/openedx-cmi5-xblock
Error: Process completed with exit code 1.

This is happening from the very first commit since the template xblock got created and make upgrade didn’t help either.

Once you eliminate this Build step and perform certain necessary linting corrections in the template xblock, the workflow passes all the checks.

You can also discuss this issue here

@timmc-edx timmc-edx moved this to Prioritized in Arch-BOM Nov 28, 2023
@rgraber
Copy link
Contributor

rgraber commented Nov 29, 2023

Acceptance Criteria:

@rgraber rgraber moved this from Prioritized to Groomed in Arch-BOM Nov 29, 2023
@rgraber rgraber moved this from Groomed to In Progress in Arch-BOM Dec 4, 2023
@rgraber rgraber self-assigned this Dec 4, 2023
@rgraber rgraber moved this from In Progress to In Code Review in Arch-BOM Dec 5, 2023
@rgraber
Copy link
Contributor

rgraber commented Dec 18, 2023

The acceptance criteria have been updated to fixing the CI issues. Ended up closing the initial PR and splitting the work into multiple new ones:
#423
#424
#425
#426
#428

@rgraber rgraber closed this as completed Dec 21, 2023
@github-project-automation github-project-automation bot moved this from In Code Review to Done in Arch-BOM Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants