Downloads:

2,348

Downloads of v 0.2.0:

15

Last Update:

18 Feb 2021

Published Date:

18 Feb 2021

Package Maintainer(s):

Software Author(s):

  • Erik Veld
  • Nic Jackson

Tags:

shipyard docker

Shipyard

(Waiting for Maintainer to take corrective action)

0.2.0 | Updated: 18 Feb 2021

Downloads:

2,348

Downloads of v 0.2.0:

15

Published:

18 Feb 2021

Maintainer(s):

Software Author(s):

  • Erik Veld
  • Nic Jackson

Shipyard 0.2.0

(Waiting for Maintainer to take corrective action)

Some Checks Have Failed or Are Not Yet Complete

1 Test Failing and 1 Pending Test


Validation Testing Failed


Verification Testing Pending

This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.

  • Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
  • This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
  • You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
  • There are also no guarantees that it will be approved.

There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.

shipyard (maintainer) on 18 Feb 2021 14:40:37 +00:00:

User 'shipyard' (maintainer) submitted package.

chocolatey-ops (reviewer) on 18 Feb 2021 15:12:22 +00:00:

shipyard has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 18 Feb 2021 16:02:57 +00:00:

shipyard has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 18 Feb 2021 16:08:00 +00:00:

shipyard has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 18 Feb 2021 16:14:02 +00:00:

shipyard has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • The DocsUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectUrl element in the nuspec file should be a valid Url. Please correct this More...
Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
Description

Shipyard is tool for managing cloud native development environments. It can be used as a replacement for Docker Compose
for creating containers with complex dependencies or Shipyard can also be used for creating development versions of Kuberentes or Nomad.
Shipyard allows you to define the configuration of your application as code, you can create clusters and containers, install software,
create ingress' and much more.


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'; # stop on all errors
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url = 'https://github.com/shipyard-run/shipyard/releases/download/v0.2.0/shipyard_0.2.0_Windows_x86_64.zip' # download url, HTTPS preferred
$checkSum = "D28EAAE41C0A5CA96FB6CEA0494F47D866B642B3CCBA7461B6A425CB17829A23"

Install-ChocolateyZipPackage -PackageName 'shipyard' -Url $url -UnzipLocation $toolsDir -ChecksumType "sha256" -Checksum $checkSum
Install-BinFile -Name shipyard -Path "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)\shipyard"
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop'; # stop on all errors

Uninstall-BinFile -Name shipyard -Path "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)\shipyard"

No results available for this package. We are building up results for older packages over time so expect to see results. If this is a new package, it should have results within a day or two.

Version Downloads Last Updated Status
Shipyard 0.3.3 9 Monday, March 29, 2021 Approved
Shipyard 0.3.2 41 Monday, March 22, 2021 Approved
Shipyard 0.3.1 39 Wednesday, March 17, 2021 Approved
Shipyard 0.2.16 28 Wednesday, March 17, 2021 Approved
Shipyard 0.2.15 36 Friday, March 12, 2021 Approved
Shipyard 0.2.13 27 Monday, March 8, 2021 Approved
Shipyard 0.2.12 24 Monday, March 8, 2021 Approved
Shipyard 0.2.11 22 Thursday, February 25, 2021 Approved
Shipyard 0.2.10 22 Wednesday, February 24, 2021 Approved

This package has no dependencies.

Discussion for the Shipyard Package

Ground Rules:

  • This discussion is only about Shipyard and the Shipyard package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Shipyard, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus