Comments (4)
If you build from the command-line, you will execute ./gradlew build
. This requires the executable bit to be set on the script.
If you are only building from the IDE, then you may never notice this being broken.
I've pushed a fix for this issue, so with the next release you'll just see a warning in your workflow run, not an error.
from actions.
When I clone your repository, the gradlew
script isn't executable, as mentioned in the error. This means that either:
- The IDE you used to generate the project didn't make this file executable, OR
- The executable bit wasn't retained when you committed the project to GitHub
I think the error message is pretty clear, but the I think the action could be improved to handle a non-executable gradlew
script, even if it makes no sense to have a project like that.
from actions.
When I clone your repository, the
gradlew
script isn't executable, as mentioned in the error. This means that either:* The IDE you used to generate the project didn't make this file executable, OR * The executable bit wasn't retained when you committed the project to GitHub
I think the error message is pretty clear, but the I think the action could be improved to handle a non-executable
gradlew
script, even if it makes no sense to have a project like that.
Thanks.
from actions.
When I clone your repository, the
gradlew
script isn't executable, as mentioned in the error. This means that either:* The IDE you used to generate the project didn't make this file executable, OR * The executable bit wasn't retained when you committed the project to GitHub
I think the error message is pretty clear, but the I think the action could be improved to handle a non-executable
gradlew
script, even if it makes no sense to have a project like that.
I don't know about that, however, somehow changing my workflow file to this fixed the problem. Modern Android apps need JDK 17 but I don't know why we need to grant permission for the gradlew
file explicitly.
name: Dependency Submission
on: [ push ]
permissions:
contents: write
jobs:
dependency-submission:
runs-on: ubuntu-latest
steps:
- name: Checkout sources
uses: actions/checkout@v4
- name: Set up JDK 17
uses: actions/setup-java@v4
with:
java-version: '17'
distribution: 'temurin'
cache: gradle
- name: Grant execute permission for gradlew
run: chmod +x gradlew
- name: Generate and submit dependency graph
uses: gradle/actions/dependency-submission@v3
from actions.
Related Issues (20)
- Dependency submission fails with HttpError HOT 14
- Provide input parameters for key environment variable supported by GitHub Dependency Graph plugin HOT 5
- The setup-gradle action should make the Gradle wrapper executable HOT 5
- Provide assistance to users attempting to resolve vulnerable dependencies
- Artifact downloaded but 'No dependency graph files found to submit' when using `download-and-submit` HOT 4
- How to configure this action to ignore plugin dependencies? HOT 4
- [Question] Inconsistent gradle configuration exclusion results HOT 12
- The `setup-gradle` action with `dependency-graph` option fails with Gradle Project Isolation HOT 13
- Cache cleanup should use the same Gradle executable as the build HOT 2
- Dependency graph are generated for all Gradle jobs following a `dependnecy-submission` step
- dependency-submissoin fails job even with upgraded dependencies HOT 4
- Dependency-submission setup recursively. HOT 2
- class cast from DependencyExtractorBuildService to DependencyExtractor failed on self-hosted runner HOT 4
- Failing to restore Gradle Cache because of "Error: Content-Length not found on blob response" HOT 5
- Does the build scan will reveal the secret key? HOT 1
- Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read HOT 4
- gradle/actions/dependency-submission needs to work on tag builds HOT 3
- Indicate why cache is read-only in Job Summary
- Provide guidance on dependency-verification config when enabling build-scan publishing
- Develocity build scan publishing fails with v3.4.0 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from actions.