AWS Code Commit Trigger SQS Plugin section does not appear in Configure System

[epmccormick]

After installing the aws-codecommit-trigger-plugin there is no configuration options that appear under Configure System, where I would expect to enter the Queue anme, Access key ID and Secret Key information.

My environment:

AWS EC2 t2.micro instance built from us-west-2 ami-6e1a0117 ubuntu
Linux jenkins 4.4.0-1022-aws #31-Ubuntu SMP Tue Jun 27 11:27:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Fresh first-time jenkins 2.76 installed with "apt-get install jenkins"
Only plug-in added after fresh install: aws-codecommit-trigger-plugin version 1.15

I tried several things to get it to work:

• Upgraded jenkins package to 2.77 with "apt-get install jenkins" tonight
• Installed additional Plug-ins:
  o Amazon S3 Bucket Credentials Plugin | 0.1.1 |
  o CloudBees Amazon Web Services Credentials Plugin | 1.22 |
  o CloudBees Credentials Plugin | 3.3 |

None of those steps enabled me to see the SQS Queue config options in Configure System. Just to make sure I wasn't having a general Jenkins plug-ins problem, I also installed the older AWS SQS Build Trigger Plugin version 1.005, and I WAS indeed able to see its similar configuration options now appearing in the Configure System screen under a section called "Configuration of Amazon SQS queues". So I seem to have proven that my installation is valid and other plug-ins are able to present their configuration sections under Configure System.

Please let me know if I can take any additional configuration or troubleshooting steps to assist you, I am happy to do so. This was all set up in an automated fashion using packer and terraform so I can easily re-create the environment. I will end my post with my packer configuration used to build my ami. Thank you very much for your assistance.

{
    "builders": [{
        "type": "amazon-ebs",
        "access_key": "",
        "secret_key": "",
        "region": "us-west-2",
        "source_ami": "ami-6e1a0117",
        "instance_type": "t2.micro",
        "ssh_username": "ubuntu",
        "ami_name": "packer-jenkins {{timestamp}}"
    }],
    "provisioners": [{
        "type": "shell",
        "inline": [
            "sudo apt-get update",
            "sudo apt-get install -y openjdk-8-jdk",
            "wget -q -O - http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -",
            "sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'",
            "sudo apt-get update",
            "sudo apt-get install -y jenkins"
        ]
    }]
}

[epmccormick]

I continued to troubleshoot and I found a path that allowed me to see and successfully configure the plug-in. I reinstalled Jenkins and this time I did the installation of the plug-ins recommended by the community (the option on the left). And I also created a user as opposed to just using the Admin account. I have many more plug-ins than I anticipated installing, but at least I can use your plug-in now. So there must be some hidden dependency then among the myriad of plug-ins that got installed.

You may be able to reproduce my first issue by installing neither the community-recommended plugins nor configuring your own on that initial screen, and instead hitting the X to close that whole window and go straight to the Jenkins main page as the Admin user, creating no additional users.

[ronaldtse]

@epmccormick thanks for reporting this. I don't think the "Admin account" made the difference but the plugin dependencies probably did?

@phuonghuynh could you have a look and see how we can make the process smoother for a non-interactive installation? Thanks!

[epmccormick]

@ronaldtse you're very welcome. And thank you and the team for such a great plug-in. It is very much appreciated.

[phuonghuynh]

Thanks @epmccormick

[phuonghuynh]

@epmccormick v2.0.1 released, could you verify if this version fixed your issue?

[epmccormick]

@phuonghuynh I tried v2.0.1 against Jenkins 2.76 and it worked great. I entered my AWS creds and was able to see my Queue. I did the same set-up where I didn't add any plug-ins at start (Hitting X in the upper right on that screen) and then went straight to Manage Jenkins/Plugins and added your plug-in, then Configure System to add my creds and queue.

Thank you!

[phuonghuynh]

👍

[duysdc]

Hi phuonghuynh, I encounter the same problem as @epmccormick . I look into jenkins.err.log and I found this error
WARNING h.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate Key[type=io.relution.jenkins.awssqs.SQSTriggerQueue$DescriptorImpl, annotation=[none]]; skipping this component
java.lang.ClassNotFoundException: com.amazonaws.services.sqs.AmazonSQS