Jenkins doesn't complete Ant task

Question

I am creating Jenkins for the first time and run into a problem when Jenkins doesn't seem to even try to complete the Ant task that I specified.

I defined the JDK and Ant installations in the Jenkins Management section.

I set my task to call Ant using the "Goals - All" command

I can force the assembly or wait for its natural execution after the next commit, nothing happens in the console assembly output about trying to complete the Ant task.

Here is an example of console output:

Any ideas as to why this might not be fulfilled would be appreciated. Also, tips on how I can find more logging from Jenkins that can give clues as to why it is not running would be helpful. I'm not sure if I can specify Logger, or even when the registration information is written to the file system.

Answer 1

The problem was that I chose the "Build multi-configuration project" as the type of my work. When I select "Create a free style project" as my job type, after completing the SVN update, the Ant task will be executed.

Answer 2

It looks like your svn does not see any changes and therefore does not restore the module.

Try deleting the workspace and restarting the assembly or changing the statement strategy for Always Check New Copy.

Answer 3

I encountered the same problem when upgrading to 1.417 from 1.413.

The Ant version match has disappeared from the Invoke ant build phase. He must be here.

I just dropped to 1.413 and continue to work.

So, the answer: you must specify "Ant version" in the project settings. But you cannot do it in 1.417.

Answer 4

Jenkins doesn't seem to like it when you create a task before setting up the JDK. If this happens, the work will not work properly. So for me the solution was:

• Delete task.
• Configure JDK
• Restore the task.

Probably the same problem may occur when deleting a JDK job.

Answer 5

In my case, the default ant value was not selected from build.xml, so I had to explicitly specify the target in the jenkins option. I solved this by changing jdk to the default value, and then switched back to what was installed earlier. This is a workaround, but not sure how this is allowed.