gocd / go-plugins

These are some test plugins used to test how GoCD behaves for different plugins, and to check if we've broken any API.

Contributing

We encourage you to contribute to Go. For information on contributing to this project, please see our contributor's guide. A lot of useful information like links to user documentation, design documentation, mailing lists etc. can be found in the resources section.

License

Copyright 2021 Thoughtworks, Inc.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

go-plugins's Issues

Yum repo poller which supports json message based plugin api

Missing com.thoughtworks.go:go-plugin-api:15.1.0 article

I'm unable to build this project due to missing articles.
It looks like they are not in Maven Central.
Can you either upload to Maven Central or give us access to your repo?

Yum Repo Poller doesn't accept self signed SSL certificates

Hey,

The repoquery command used by the yum plugin doesn't allow you to query repos over a self signed SSL connection. I'm wondering if this was intentional behaviour or not? It would be nice if you could turn this feature on and off.

Command being run: https://github.com/gocd/go-plugins/blob/master/yum-plugin/src/com/tw/go/plugin/material/artifactrepository/yum/exec/command/RepoQueryCommand.java#L47
Best,
Gareth

NIST NVD dependency checker

Is is possible to create a plugin for gocd like Dependency-Check from OWASP?

Dependency-Check is a utility that identifies project dependencies and checks if there are any known, publicly disclosed, vulnerabilities.
https://www.owasp.org/index.php/OWASP_Dependency_Check
https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Dependency-Check+Plugin
Dependency-check has a command line interface, a Maven plugin, an Ant task, and a Jenkins plugin. The core engine contains a series of analyzers that inspect the project dependencies, collect pieces of information about the dependencies (referred to as evidence within the tool). The evidence is then used to identify the Common Platform Enumeration (CPE) for the given dependency. If a CPE is identified, a listing of associated Common Vulnerability and Exposure (CVE) entries are listed in a report.
Dependency-check automatically updates itself using the NVD Data Feeds hosted by NIST.

Sample authentication plugin is broken in latest 15.3

The sample authentication plugin works as intended when run against the 15.2.0 tag in the gocd repository, but updating to the latest commit to master (pre-release 15.3) causes a 404 to occur anytime the plugin icon is clicked, breaking the authentication flow, as demonstrated below.

15.2:

15.3:

The developer documentation hasn't been updated to indicate what change is required to the authentication plugins to make them work in 15.3 and there are no bugs related to the authentication flow on the main gocd project, but I can't determine whether this is API breaking change, a bug in Go, or a bug in the plugin.

Plugin reports 500 when there is no package in the repo

We have the plugin check for new packages, however becuase we tend to move final packages away from the initial repo, and we have a cleanup policy for those applications that we rarely release, the repo that we're polling is often empty.

The plugin returns 500 error and our Go server has the tray always with 7-9 errors from such applications.

Is there a workaround? Or it requires a fix in the code?

Multiple repos produces yum pid lock errors

Go 15.2.0-2248 and Yum plugin 2.0.0

Go is setup with 20 yum repos. When polling for changes in the repos, Go or the Yum Plugin is attempting to do so with multiple threads. The repoquery tool (and yum in general) does not support multiple threads and errors like the following are produced consistently and constantly against every repo.

Interaction with plugin with id 'yum' implementing 'package-repository' extension failed while requesting     
for 'latest-revision-since'. Reason: [Unsuccessful response from plugin. Plugin returned with code '500' 
and the following response: 'Error while querying repository with path 'https://*****' and package spec
'****'. Error Message: Existing lock /var/tmp/yum-go-_4vX3k/x86_64/7/yum.pid: another copy is running 
as pid 33677

The result is some updated materials will not register with Go for 2 hours or more because of the lock contention.