The Go CD Pipeline Builder is designed to have the same function in the Go CD ecology, as the Jenkins Job Builder has in the Jenkins ecology. Given a (git) repository and appropriate configuration, it should be able to add a suitable pipeline to a Go-server. The current version does not trigger on git events. It is simply a command line driven tool.
Metadata
Release files for gocdpb 4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gocdpb-4.tar.gz | 8.5 kB | Without provenance | Details for gocdpb-4.tar.gz |
Release files / gocdpb-4.tar.gz
| Download URL | gocdpb-4.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3eed230ed9c0bbc273b7e471cc1687bfd080cbfae237fa6d5bfe964a9c6a0ee1
|
|
BLAKE2b-256 checksum How to use checksums |
67fa418ecdc10d23b61d892fc80e3e99ce38fbef1aaff07cc52e336f881be678
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gocdpb 4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.