Remove obsolete CI provider "shippable" from CI example list #5145
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
👷 Deploy request for cypress-docs pending review.Visit the deploys page to approve it
|
This was referenced Mar 27, 2023
jaffrepaul
approved these changes
Mar 28, 2023
This was referenced Mar 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes the obsolete CI provider "Shippable" from CI Provider Examples. The CI provider "Shippable" is no longer operating and the link to https://github.com/cypress-io/cypress-example-kitchensink/blob/master/shippable.yml is therefore obsolete.
Background
The former CI provider "Shippable" no longer provides a service.
https://app.shippable.com/github/cypress-io/cypress-example-kitchensink is no longer reachable.
http://docs.shippable.com/ is no longer reachable.
Shippable's GitHub repositories under https://github.com/Shippable have not been updated since September 2021.
See We’ve Acquired Shippable to Complete DevOps Pipeline Automation From Code to Production February 21, 2019. JFrog stated they would replace shippable with JFrog Pipelines however it seems there is no simple migration from a
Shippableworkflow to aJFrog Pipelinesworkflow.JFrog Pipelineswould have to be treated like a completely new CI provider.Related PR