actions / actions/starter-workflows
Default Maven workflow fails with 'Resource not accessible by integration' error (2)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.1k
- Forks
- 7.3k
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce
Create a Java with Maven workflow.
Run the workflow out-of-the-box.
Result
Execution ends up with deprecation warnings, and the Resource not accessible by integration error.
To be precise, it is the Update dependency graph step that fails (not the first action one would want to run when starting to work with GitHub Actions).
Expected
At least, the Update dependency graph step should be commented out.
At best, it should contain all required properties, with placeholders for values users have to input.
Possibly, a configuration guide should be provided for this specific functionality.
Example
https://github.com/FreekVanDooren/ccwc/actions/runs/14510205378/job/40707019248
Duplicate
Issue already reported here: https://github.com/actions/starter-workflows/issues/2310 but was automatically closed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the default Java with Maven workflow and inspect its Update dependency graph step. Reproduce the out-of-the-box run to confirm the Resource not accessible by integration failure, then align the workflow with the issue's expected behavior and verify that a new run no longer fails at that step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100