-
Notifications
You must be signed in to change notification settings - Fork 845
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
scp (write-only) resource #141
Comments
Hi there! We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created. The current status is as follows:
This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes. |
[finishes #127219723] Submodule src/github.com/concourse/atc 1ee1c48..a3023dd: > ginkgo blur reoreded everything > return all public pipelines on GetAllPipelines endpoint > only check for basic auth on get token endpoint > do not default team name to main if not provided > do not default team name to main in api Submodule src/github.com/concourse/fly cb98e4c..3269297: > make --team-name required > retrieves token if there is no auth method set Submodule src/github.com/concourse/testflight fdd0c3f..abd306e: > do not default team name to 'main' Submodule src/github.com/onsi/ginkgo e43390e..74c678d: > Make JUnit reporter include failure location in message. (#262) > remove 1.4 from travis.yml > Add gcflags option (#276) > Revert "Use the go1.5 build tag to handle vendor exceptions" (#274) > Merge pull request #272 from fsouza/fix-vendor > Add flaky test mitigation (#261) > Allow units and precision in benchmark (#266) > Add Solaris support (#264) > Merge pull request #259 from kwadrat/master > Merge branch 'apvail-spell-fix' > Fix go16 vendor > Merge pull request #250 from james-lawrence/master > Merge pull request #228 from jayunit100/RegexFileNameFiltering > Fix test flakiness > Merge pull request #235 from mboersma/fix-travis > fix compilation on older versions of go > fix issue where packages that reference vendored dependencies weren't compiling > Merge pull request #216 from sha1sum/master > Merge pull request #209 from luxas/build_on_arm64 > Merge pull request #212 from cfmobile/master > Merge pull request #210 from cfmobile/master Submodule src/github.com/onsi/gomega 2152b45..9ed8da1: > Merge pull request #166 from trayo/patch-2 > Merge pull request #164 from wendorf/assert_typo > Merge remote-tracking branch 'origin/pr/163' > Merge pull request #160 from tinygrasshopper/fix_failing_close_ghttp > Merge pull request #150 from tinygrasshopper/build-fix > Merge pull request #159 from WesleyJeanette/patch-1 > Merge pull request #157 from kwadrat/master > Merge pull request #141 from mariantalla/gomega-yaml-matcher > Reset tmpDir in gexec.CleanupBuildArtifacts > Update test description for match json tests. > Make the error message for expected JSON values having the wrong type accurate > Merge pull request #133 from tjarratt/be-identical-to-matcher > Merge pull request #132 from tjarratt/improve-match-json-error-message > Merge pull request #128 from tinygrasshopper/have-cap > drop 1.4 from travis > ghttp tests should now pass in 1.6 > CloseClientConnections test uses http.Post instead of http.Get to avoid retries > add tip to .travis.yml > Merge pull request #125 from cfmobile/master > Merge pull request #122 from cfmobile/master > Merge pull request #119 from jim-slattery-rs/gitignore_idea > Merge pull request #118 from jim-slattery-rs/fix_up_succeed Signed-off-by: Yucheng Tu <ytu@pivotal.io>
Closing this for now. Seems like someone else might have done this. https://hub.docker.com/r/mookas/concourse-scp-resource |
@joshzarrabi there's zero documentation provided on the link :-/ |
For some of my more low-tech deploy stagess, I find myself scp-ing files across from the worker to the target VM. Currently i'm achieving that with the
scp
command inside a task, but it feels more 'concoursey' to have this as a resource.I'm happy to create this - just want to get some thoughts before I embark.
In case it's not clear from the title - I anticipate this being an
out
only resource, to avoid any aspects of versioning.The text was updated successfully, but these errors were encountered: