trecnoc / nexus-resource Goto Github PK

Is your feature request related to a problem? Please describe.
Add the Go Report Badge

Is your feature request related to a problem? Please describe.
Integration tests are currently not running in the CI workflow since we don't have access to a Nexus repository.

Describe the solution you'd like
We need to add the ENV variable in the CI workflow so that Integration are run. For this work we will need an account on Nexus and a Raw Repository we can use for tests.

Is your feature request related to a problem? Please describe.
When a Release is created it needs to be built with Docker and the image needs to be pushed to DockerHub

Describe the solution you'd like
Github Action when draft release is created:

• Run the docker build with the integration tests args
• Push the image to DockerHub
• Remove draft status on the release on success

Is your feature request related to a problem? Please describe.
Add the Build status badge

Describe the bug
Resource doesn't pull artifacts with this provided source:

  source:
    url: ((nexus.url))
    username: ((nexus-username))
    password: ((nexus-password))
    repository: ((nexus.repository))
    group: ((nexus.buildpack.group))
    regexp: ((nexus.buildpack.regex))
    debug: ((nexus.debug))

Looking at the debug log in the container the group field is always an empty string.

Expected behavior
Resource finds new versions of the artifact

Describe the bug
Running a Buildpack pipeline to create a Bosh release, it failed when running the put of the bosh release.

error running command: Post "http://192.168.50.10:8081/service/rest/v1/components?repository=software": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Concourse(please complete the following information):

• OS: Ubuntu
• Deployment Type: Docker
• Version: 6.0.0

Describe the bug
Nexus search returns data paginated. If this is the case the current client will only return data from the first page.

To Reproduce
Steps to reproduce the behavior:

1. Run a Check against a repository/group which contains a large number of items
2. Return the latest from the first page

Expected behavior
Returns the latest version from the repository/group

Is your feature request related to a problem? Please describe.
We need to implement a way to build and deploy the resource automaticly.

Describe the solution you'd like
Using Concourse we can build and test PR and implement a release process.

Describe alternatives you've considered
None

Additional context
None

Is your feature request related to a problem? Please describe.
Trying to diagnose why this is not pulling from Nexus. Adding debug would be usefull.

Describe the solution you'd like

• Add a debug flag in the source to enable debugging information logged in the container.
• Debug information could be added in the /tmp directory of the container (note that this should be kept to a mininum since we don't want to fill up the container)
• Then using fly -t your-target hijack --check=your-pipeline/your-resource-name to view the debug information.

Describe the bug
Report Card