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.

Sign up for GitHub

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

Jump to bottom

"Not a Paragon Project" #3

Open
glaidler opened this issue Jun 12, 2024 · 10 comments · May be fixed by #4
Open

"Not a Paragon Project" #3

glaidler opened this issue Jun 12, 2024 · 10 comments · May be fixed by #4

Comments

@glaidler
Copy link

How do I specify this to run the para build within a project folder?

Without this, the action always errors with "Not a Paragon Project"
@ethanlee16
Copy link
Member

Hey @glaidler - do you mind sharing the usage of this GitHub Action in your workflow file so that we can better debug?

One thing to consider using is working-directory, which would look like this in your workflow file:

jobs:
  push_to_paragon:
    name: Push to Paragon
    runs-on: ubuntu-latest
      
    steps:
      - uses: actions/checkout@v4
      - id: push
+       working-directory: [DIRECTORY HERE]
        uses: useparagon/paragraph-push@v1
        with:
          paragonKey: ${{ secrets.PARAGON_CLI_KEY }}
          paragonZeusUrl: ${{ secrets.ZEUS_URL }}
          paragonDashboardUrl: ${{ secrets.DASHBOARD_URL }}

@glaidler
Copy link
Author

I have tried this, but get vscode syntax errors.

image

All docs suggest that the working-directory only works with a "run", not with "uses"?
https://stackoverflow.com/questions/58139175/running-actions-in-another-directory

@ethanlee16
Copy link
Member

ethanlee16 commented Jun 13, 2024 •
edited
Loading

I see - can we try using it in the defaults for this job instead?

jobs:
  push_to_paragon:
    name: Push to Paragon
    runs-on: ubuntu-latest
+   defaults:
+     run:
+      working-directory: ./harbour-assist
      
    steps:
      - uses: actions/checkout@v4
      - id: push
        uses: useparagon/paragraph-push@v1
        with:
          paragonKey: ${{ secrets.PARAGON_CLI_KEY }}
          paragonZeusUrl: ${{ secrets.ZEUS_URL }}
          paragonDashboardUrl: ${{ secrets.DASHBOARD_URL }}

edit: this may not work due to the checkout also using that same working directory though - looking into this further

@ethanlee16 ethanlee16 linked a pull request Jun 13, 2024 that will close this issue
Open
@ethanlee16
Copy link
Member

ethanlee16 commented Jun 13, 2024 •
edited
Loading

@glaidler I just added support for an optional path input in the linked PR, can you try referencing this version?

jobs:
  push_to_paragon:
    name: Push to Paragon
    runs-on: ubuntu-latest
      
    steps:
      - uses: actions/checkout@v4
      - id: push
-       uses: useparagon/paragraph-push@v1
+       uses: useparagon/paragraph-push@b62d66b21d84f767c716c5cbee1e646d3fbf0db8
        with:
          paragonKey: ${{ secrets.PARAGON_CLI_KEY }}
          paragonZeusUrl: ${{ secrets.ZEUS_URL }}
          paragonDashboardUrl: ${{ secrets.DASHBOARD_URL }}
+         path: ./harbour-assist

@glaidler
Copy link
Author

got further! unfortunately there are missing dependencies in that folder.

image

@ethanlee16
Copy link
Member

@glaidler What step is that erroring on?

@glaidler
Copy link
Author

image

@ethanlee16
Copy link
Member

@glaidler I just updated the action to use a different strategy to check for a locally-specified CLI version, which should avoid this error. Can you try with this version: @ce0dbba611105ed62e8446e7b401e3e2ce119e43

@glaidler
Copy link
Author

Hi - it looks like it's got further, but it's failing still I'm afraid:

image

@ethanlee16
Copy link
Member

@glaidler almost there, thanks for your patience! I reverted a pending change that we have to the locally-specified CLI feature so you can test with just the subfolder support we discussed, let's try: f72d541c58d4b9c9a900a7ec69fc397cb5ef2a45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for path parameter and use local CLI version if available useparagon/paragraph-push
2 participants
@glaidler @ethanlee16