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

[Feature] Handle Pipeline Error #500

Closed
2 tasks done
BenjaminKlatt opened this issue May 25, 2022 · 1 comment
Closed
2 tasks done

[Feature] Handle Pipeline Error #500

BenjaminKlatt opened this issue May 25, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@BenjaminKlatt
Copy link

Is this feature missing in the latest version?

  • I'm using the latest release

Is your feature request related to a problem? Please describe.

We use the action to identify changes in a specific module and trigger subsequent deployments only if need.
Now, in case of an error in the subsequent process, there is no chance to rerun the pipeline as the file change filter does not detect any files changed.

Example

    steps:
      - uses: actions/checkout@v2
        with:
          fetch-depth: 2
      - name: Get changed files
        id: changed-files
        uses: tj-actions/changed-files@v20.2
        with:
          files: |
            submodule/**
      - name: Setup Node
        if: steps.changed-files.outputs.any_changed == 'true'
        uses: actions/setup-node@v2
        with:
          node-version: '14'
          cache: 'npm'

Describe the solution you'd like?

Maybe just a matter of an existing configuration we could not figure out:
How to setup the pipeline, to not filter subsequent processes wich were not successful before?

Describe alternatives you've considered?

No response

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@BenjaminKlatt BenjaminKlatt added the enhancement New feature or request label May 25, 2022
@jackton1
Copy link
Member

jackton1 commented May 25, 2022

@BenjaminKlatt sounds like you might want to take a look at nrwl/last-successful-commit-action other than that you’ll need to provide a more elaborate description of the problem and the solution you want with logs and pictures of the exact issue and if it can be solved by an action.

...
      - name: Get branch name
        id: branch-name
        uses: tj-actions/branch-names@v5
        if: github.event_name == 'pull_request'

      - uses: nrwl/last-successful-commit-action@v1
        id: last_successful_commit
        if: github.event_name == 'pull_request'
        with:
          branch: ${{ steps.branch-name.outputs.base_ref_branch }} # Get the last successful commit on master or main branch 
          workflow_id: 'test.yml'
          github_token: ${{ secrets.GITHUB_TOKEN }}

      - name: Run changed-files with a custom base sha
        if: github.event_name == 'pull_request'
        id: changed-files-custom-base-sha
        uses: tj-actions/changed-files@v20.2
        with:
          base_sha: ${{ steps.last_successful_commit.outputs.commit_hash }}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants