Skip to content
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

Retrieve deploy result json in the pipe #9

Open
scolladon opened this issue Apr 9, 2017 · 2 comments
Open

Retrieve deploy result json in the pipe #9

scolladon opened this issue Apr 9, 2017 · 2 comments

Comments

@scolladon
Copy link

It would be great if we could retrieve the deploy result json object in the pipe when deployment is done.
I think it has more sense than the zip file (pretty useless to me).
In attachment what I did to return the res instead of the file
gulp-jsforce-deploy.js.txt
.
Not sure it is the best way with gulp.
Any idea ?

@scolladon
Copy link
Author

I think this version is more elegant and cleaner.
gulp-jsforce-deploy.js.txt

You can use it in gulpfile this way:
gulp.task('deploy', cb => { return gulp.src('./src/**') .pipe(zip('pkg.zip')) .pipe(forceDeploy(options)) .pipe(rename(DEPLOY_RESULT_FILE)) .pipe(gulp.dest('.')); });

@ahuggins-nhs
Copy link

ahuggins-nhs commented Jan 25, 2020

It would be great if we could retrieve the deploy result json object in the pipe when deployment is done.
[...]
Not sure it is the best way with gulp.
Any idea ?

@scolladon I've made a PR #11 that closely implements something like your suggestion, but I also added some additional functionality to more fully replace the Ant Migration Tool, and then to use that output in test pipelines. I've also published my PR under our org @nhs-llc/gulp-jsforce-deploy and made the deploy result reporter available at jsforce-deploy-reporter. I know it's been a few years since your comment and PR were submitted, but if you're still using this gulp plugin, let me know what you think of the changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants