[JIRA] (JENKINS-32121) Jenkins is skipping Build section intermittently
Title: Message Title Adam L commented on JENKINS-32121 Re: Jenkins is skipping Build section intermittently Has any work been done to address this issue, or any similar? I, too, am getting builds that are breaking because of the plugin. The only information I get in my log is: Build step 'Audit job info to Database' marked build as failure The side effects are maven not being installed on a slave, any of my build steps executing, and the job fails immediately after checking out source code. If I remove the audit step, everything works fine. if I add it back in, reverts to failure. I've checked my connection from the main config page, and it works fine. I have jobs that are successfully logging to the audit db, and others that are randomly failing. What's odd is the order in which the failures are listed: > /usr/bin/git rev-list 12345678 # timeout=10 No emails were triggered. Skipping sonar analysis due to bad build status FAILURE [BFA] Scanning build for known causes... [BFA] No failure causes found [BFA] Done. 0s Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Sending email to: x Build step 'Audit job info to Database' marked build as failure Finished: FAILURE any thoughts? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42237) Add a label per indicator
Title: Message Title Adam L created an issue Jenkins / JENKINS-42237 Add a label per indicator Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2017/Feb/21 9:41 PM Environment: jenkins 1.658 BFA 1.17.2 Priority: Minor Reporter: Adam L When reporting the build failure reasons, currently all that is shown is the cause group name, and "Indication 1". It would be useful to have a label for each indication added to a cause and display that instead. This would provide a much more useful analysis to the end user. Thank you. Add Comment
[JIRA] (JENKINS-23284) Get value of all parameters in the database
Title: Message Title Adam L commented on JENKINS-23284 Re: Get value of all parameters in the database This request was made almost 3 yrs ago. Check out: https://wiki.jenkins-ci.org/display/JENKINS/Audit+To+Database+Plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42229) Add link to job
Title: Message Title Adam L updated an issue Jenkins / JENKINS-42229 Add link to job Change By: Adam L Environment: Jenkins 1.6x audit db plugin v0.5 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42229) Add link to job
Title: Message Title Adam L created an issue Jenkins / JENKINS-42229 Add link to job Issue Type: New Feature Assignee: Unassigned Components: audit2db-plugin Created: 2017/Feb/21 5:37 PM Environment: Jenkins 1.6x Priority: Minor Reporter: Adam L It would be nice if the audit reports provided an HREF back to the job. Currently only the short name of the job is displayed, so "buildIt" as a job name is generic and doesn't allow to see the particular job in question without going directly to the DB, which is not useful. Adding HREF to the shortname would be a great solution. Add Comment
[JIRA] (JENKINS-41549) API incompatibility error
Title: Message Title Adam L reopened an issue nope.. subsequent runs produced the same error. Please let me know what I can set/provide to help figure out what's wrong.. It could very well be user error again. The one time it did run successfully, after i moved the plugin to the proper location, there were no changes in the artifacts. The pom versions were still the same as before i ran the promotion process. Jenkins / JENKINS-41549 API incompatibility error Change By: Adam L Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41549) API incompatibility error
Title: Message Title Adam L closed an issue as Not A Defect had the plugin in the pom in pluginmanagement, not plugins. sorry, pebcak Jenkins / JENKINS-41549 API incompatibility error Change By: Adam L Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-41549) API incompatibility error
Title: Message Title Adam L created an issue Jenkins / JENKINS-41549 API incompatibility error Issue Type: Bug Assignee: Stanley Hillner Components: unleash-plugin Created: 2017/Jan/30 4:26 AM Environment: Jenkins 1.630 Jenkins unleash plugin 2.1.1 pom:com.itemis.maven.plugins unleash-maven-plugin 2.2.3 com.itemis.maven.plugins unleash-scm-provider-git 2.0.2 Priority: Blocker Reporter: Adam L Created a simple maven project, ticked Unleash, left the defaults as is, triggered the plugin, left the defaults as is: [ERROR] Failed to execute goal com.itemis.maven.plugins:unleash-maven-plugin:2.2.3:perform (default-cli) on project promotion-parent: Execution default-cli of goal com.itemis.maven.plugins:unleash-maven-plugin:2.2.3:perform failed: An API incompatibility was encountered while executing com.itemis.maven.plugins:unleash-maven-plugin:2.2.3:perform: java.lang.LinkageError: loader constraint violation: when resolving overridden method "org.jboss.weld.AbstractCDI.select(Ljavax/enterprise/util/TypeLiteral;[Ljava/lang/annotation/Annotation;)Ljavax/enterprise/inject/Instance;" the class loader (instance of org/codehaus/plexus/classworlds/realm/ClassRealm) of the current class, org/jboss/weld/AbstractCDI, and its superclass loader (instance of org/codehaus/plexus/classworlds/realm/ClassRealm), have different Class objects for the type /annotation/Annotation;)Ljavax/enterprise/inject/Instance; used in the signature [ERROR] - [ERROR] realm = plugin>com.itemis.maven.plugins:unleash-maven-plugin:2.2.3 [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy [ERROR] urls[0] =
