[GRADLE-2069] Build announcements cause build failure with jenkins CI Created: 25/Jan/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-6
Fix Version/s: None

Type: Bug
Reporter: Tino Nitze Assignee: Adam Murdoch
Resolution: Won't Fix Votes: 0

Comment by Tino Nitze [ 25/Jan/12 ]

Ok, I got it again, this time when using gradle (m6/7) with Jenkins (as user jenkins) which most likely lacks some system linux requirements and causes the build to succeed with a failure, which is quite inconvenient as jenkins will recognize this as failed built....
fyi: notify-send is installed

16:14:14.892 [DEBUG] [org.gradle.process.internal.ProcessBuilderFactory] creating process builder for command '/usr/bin/notify-send'
16:14:14.892 [DEBUG] [org.gradle.process.internal.ProcessBuilderFactory] in directory /var/lib/jenkins/workspace/mopay20
16:14:14.893 [DEBUG] [org.gradle.process.internal.ProcessBuilderFactory] with argument#0 = Build successful
16:14:14.893 [DEBUG] [org.gradle.process.internal.ProcessBuilderFactory] with argument#1 = 12 tasks executed
16:14:14.926 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Started command '/usr/bin/notify-send'.
16:14:14.975 [ERROR] [system.err]
16:14:14.976 [ERROR] [system.err] GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
16:14:14.976 [ERROR] [system.err] aborting...
16:14:14.976 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Process finished for command '/usr/bin/notify-send'.
16:14:14.982 [ERROR] [org.gradle.BuildExceptionReporter]
16:14:14.982 [ERROR] [org.gradle.BuildExceptionReporter] FAILURE: Build failed with an exception.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:11:58 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.