Task :rpmBuild NO-SOURCE Skipping task ':uild' as it has no source files and no previous output files

Help/Discuss
1

Hi Team,

Getting below issue while doing gradle build with 8.x, same code works with gradle 7.x

Task :pmBuild NO-SOURCE
Skipping task ‘:rpmBuild’ as it has no source files and no previous output files.

2

You are missing various characters it seems.
In your title for example you have :rpmBuild and :uild, in your text :pmBuild an d:rpmBuild.
If that is really literally copied what you get, something is probably broken with your console.
If you just manually typed and mistyped, don’t ever do that, if you share code or errors to get help, it is always important to be precise.
Easiest and best is to share a build --scan URL.

Besides that, you shared no information about your build at all, so how should anyone be able to guess why it does not behave as you expect? The output tells you that the task has no input files and is skipped due to that. So you probably changed something more besides the Gradle version. rpmBuild is not something Gradle provides built-in.

If you really think you did not change more, you most probably should provide an MCVE so that someone might be able to help.

3

./gradlew --scan

To honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/8.10/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation.
Daemon will be stopped at the end of the build
Configuration on demand is an incubating feature.

> Configure project :
Cannot publish Ivy descriptor if ivyDescriptor not set in task ':artifactoryPublish' and task 'uploadArchives' does not exist.
Adding "apply plugin: 'java'" or any other plugin extending the 'base' pluginwill solve this issue.
Cannot publish pom for project ':' since it does not contain the Maven plugin install task and task ':artifactoryPublish' does not specify a custom pom path.

> Task :help

Welcome to Gradle 8.10.

To run a build, run gradlew <task> ...

To see a list of available tasks, run gradlew tasks

To see more detail about a task, run gradlew help --task <task>

To see a list of command-line options, run gradlew --help

For more detail on using Gradle, see https://docs.gradle.org/8.10/userguide/command_line_interface.html

For troubleshooting, visit https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.10/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD SUCCESSFUL in 1m 16s

we have defined

apply plugin: 'java'
apply plugin: 'maven-publish'
apply plugin: 'jacoco'
apply plugin: 'ivy-publish'
apply plugin: "com.jfrog.artifactory"
apply plugin: 'groovy'
4

That was pretty useless.

  1. you run with --scan but you did not provide the build can URL
  2. you did not execute the failing run with --scan added, but just a help task, that will not help in any way

we have define

Why are you telling this?
Besides that you should not use the legacy way to apply plugins via apply plugin, but the recommended plugins { ... } block.

And I can strongly recommend using Kotlin DSL instead of Groovy DSL. By now it is the default DSL, you immediately get type-safe build scripts, actually helpful error messages if you mess up the syntax, and amazingly better IDE support if you use a good IDE like IntelliJ IDEA or Android Studio.