[JIRA] (JENKINS-56002) Upgrading Git Plugin to :latest causes Issues with SQS Plugin

[justinseiser@gmail.com (JIRA)]

Justin Seiser created an issue

Jenkins / JENKINS-56002 Upgrading Git Plugin to :latest causes Issues with SQS Plugin Issue Type: Bug Assignee: Mark Waite Attachments: Error.txt, Jenkins.png, noidea.png Components: git-plugin Created: 2019-02-06 20:30 Environment: Jenkins Version 2.150.2 jenkins/jenkins:lts All plugins set to latest Priority: Minor Reporter: Justin Seiser Upgraded Docker container, and it with the plugins.     Started getting the attached error, and the UI for the SQS plugin broke.  Reverting the git plugin, brought the UI for the SQS plugin back, and everything started flowing again. Error.txt Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[batmat@batmat.net (JIRA)]

Baptiste Mathus commented on JENKINS-56002

Re: Upgrading Git Plugin to :latest causes Issues with SQS Plugin Can you please be more specific about the plugin versions you have, the ones that caused the issue, etc. Thanks

Add Comment

[justinseiser@gmail.com (JIRA)]

Justin Seiser commented on JENKINS-56002

Re: Upgrading Git Plugin to :latest causes Issues with SQS Plugin

We were trying git plugin 3.9.1-3.9.3, all of which failed to clone on the latest release of jenkins.  So we would move to the 4.0 rc plugin, which would cause the SQS plugin to fail.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite updated an issue

Jenkins / JENKINS-56002

Upgrading Git Plugin to :latest causes Issues with SQS Plugin

Change By: Mark Waite Component/s: sqs-notification-plugin Component/s: git-plugin

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite assigned an issue to Unassigned

Jenkins / JENKINS-56002 Upgrading Git Plugin to :latest causes Issues with SQS Plugin

Change By: Mark Waite Assignee: Mark Waite

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-56002

Re: Upgrading Git Plugin to :latest causes Issues with SQS Plugin I see nothing git related in the SQS plugin stack trace that was provided with this bug report. The information in the bug report is insufficient for me to duplicate the problem since it provides no configuration details of the environment which was showing the failure. I see an optional dependency in the SQS plugin on the git plugin and a reference to that dependency in the EventTriggerMatcherImpl. The dependency appears to be correctly implemented for an optional dependency and uses minimal functionality from the git plugin. I'm reassigning this bug report to the sqs plugin. If the sqs plugin maintainer is willing to perform a "smoke test" with git client plugin 3.0.0-rc and git plugin 4.0.0-rc, I'd be very grateful. I don't have an SQS configuration available and won't test this further. Alternately, the original submitter can provide a numbered set of steps which will allow someone else to duplicate the failure.

Add Comment

[mstuart2@dxc.com (JIRA)]

Michele Stuart updated an issue

Jenkins / JENKINS-56002

Upgrading Git Plugin to :latest causes Issues with SQS Plugin

Change By: Michele Stuart Attachment: sqsError.txt

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[mstuart2@dxc.com (JIRA)]

[mstuart2@dxc.com (JIRA)]

Michele Stuart commented on JENKINS-56002

Re: Upgrading Git Plugin to :latest causes Issues with SQS Plugin I realize this is several months old, but as it's still open, perhaps I can provide more info. I just ran into the problem and posted about it at https://github.com/jenkinsci/aws-sqs-plugin/issues/29#issuecomment-558347125.   Versions: Jenkins: 2.190.3 Java OpenJDK: 11.0.4 AWS SQS plugin: 2.0.1 Git plugin: 3.10.0 / 4.0.0 OS: Ubuntu 18.04 LTS   To reproduce: With a valid Jenkins SQS configuration in place under Configure System => Configuration of Amazon SQS queues, i.e. with a queue configured and appropriate IAM credentials to connect to it.   Upgrade the Git plugin to version 4.0.0. Restart Jenkins If you are tailing the Jenkins log, you will immediately start seeing the attached errors spewing into the log. In the Jenkins web interface, go to Configure System => Configuration of Amazon SQS queues and click "Test Access" on one of your queues. You will see the result "Error." If you click on the Error link, you'll see the Java error, as in the server log.       5. Downgrade the Git plugin to 3.10.0       6. Restart Jenkins        7. If you are tailing the server log, the errors will now stop.        8. In the web interface queue configuration, clicking "Test Access" will now result in success (assuming you have good credentials).   sqsError.txt

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite assigned an issue to Chris Contolini

Jenkins / JENKINS-56002

Upgrading Git Plugin to :latest causes Issues with SQS Plugin

Change By: Mark Waite Assignee: Chris Contolini

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-56002

Re: Upgrading Git Plugin to :latest causes Issues with SQS Plugin I don't know why the upgrade of the git plugin would break with: Could not initialize class com.amazonaws.auth.internal.AWS4SignerUtils I've taken the liberty of assigning the bug to the "Automatic Assignee" as though the bug had been originally submitted to the sqs-notification-plugin.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite edited a comment on JENKINS-56002

Re: Upgrading Git Plugin to :latest causes Issues with SQS Plugin

I don't know why the upgrade of the git plugin would break the SQS notifier notification plugin with:

{{Could not initialize class com.amazonaws.auth.internal.AWS4SignerUtils}} I've taken the liberty of assigning the bug to the "Automatic Assignee" as though the bug had been originally submitted to the sqs-notification-plugin.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite edited a comment on JENKINS-56002

Re: Upgrading Git Plugin to :latest causes Issues with SQS Plugin

I don't know why the upgrade of the git plugin would break the SQS notifier plugin with:

{{Could not initialize class com.amazonaws.auth.internal.AWS4SignerUtils}} I've taken the liberty of assigning the bug to the "Automatic Assignee" as though the bug had been originally submitted to the sqs-notification-plugin.

Add Comment