Open AlexHedley opened 6 years ago
Thanks for bringing this our notice, we shall update the status of our roadmap when we plan this into it 😄
@AlexHedley - Thanks for the bringing this up. Currently we have integrations with Github and Gitlab. We have Bitbucket Cloud on our roadmap. We do not have TFS (VSTS) on our roadmap yet.
However we do support an integration with Microsoft Flow which has a connector to VSTS. Here is a blog post on how you can create a sync between Postman Collections and Microsoft Flow.
You can also achieve this manually by exporting the Postman Collection and checking it into your source code on TFS and build on VSTS.
We will update the status on our roadmap when we include support for TFS (VSTS).
Thanks for the links @ratpik, I'll look into the MS Flow for now. I'm hoping to automate it instead of a manual process but at least that's an option.
Any news on this feature? Should I rename it Azure DevOps now :p
When to expect an Integration for TFS? We're not using any of the supported integrations, but would very much like to sync our postman collections to TFS and integrate them in the CI pipeline.
yes, this would be a great feature to have.
Hi,
Is there an update on this? We're looking to include our postman collections in our CI pipeline. We're currently planning to export a Backup.postman_dump.json
from the app (which includes all collections in the workspace), and add it to the repo. This would then be run using newman
. If there is a way to integrate Postman with TFS or Azure Pipelines, that would be absolutely awesome.
Apologies if there is a good way to do this, just haven't come across it!
I'm not completely following what you are trying to do. I am curious if you have looked at using the Postman APIs to do this for you.
As an example, I use the Postman APIs to pull my Postman environments and collections versus having to export them. I pull them down in a VSTS Release step, so that I do not have to download them every time they change. I then use those in another step in my release using newman to run the tests as my Post Deployment tests in the release. I use a C# cmdlet to do pull them down to the local machine, then use PowerShell to execute the test using the json files retrieved from Postman. Sounds complicated, but it is not.
This may not be exactly what you are trying to do, but it seems like you could accomplish what you are trying to do in a similar way.
Hi, no. I'm just trying to continue using Postman the way I did on Thursday last week before the update.
Warm regards
Randell 082 741 6360
On Fri, May 24, 2019 at 4:18 PM jrothlander notifications@github.com wrote:
I'm not completely following what you are trying to do. I am curious if you have looked at using the Postman APIs to do this for you.
As an example, I use the Postman APIs to pull my Postman environments and collections versus having to export them. I pull them down in a VSTS Release step, so that I do not have to download them every time they change. I then use those in another step in my release using newman to run the tests as my Post Deployment tests in the release. I use a C# cmdlet to do pull them down to the local machine, then use PowerShell to execute the test using the json files retrieved from Postman. Sounds complicated, but it is not.
This may not be exactly what you are trying to do, but it seems like you could accomplish what you are trying to do in a similar way.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/postmanlabs/postman-app-support/issues/3796?email_source=notifications&email_token=AJEFADZXWBWR5CZXMFBBB7LPW72MZA5CNFSM4EDUD7U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWFQHZY#issuecomment-495649767, or mute the thread https://github.com/notifications/unsubscribe-auth/AJEFAD4NEJW4FIGBWXCCPSDPW72MZANCNFSM4EDUD7UQ .
Thanks @jrothlander, we haven't actually looked into using the Postman API to get the collections. That's a good idea - we currently simply export the collections we want to run as part of our CI/CD, push to our repo and the collections become part of our build artifact. Thise various collections are then run individually by Newman as a post deployment step.
I guess what I was looking for was some sort of way to point to a collection on postman that can be run by Newman, hence ommiting the manual step of exporting the collection. But then again, your suggestion might work nicely anyway. I'll look into it on Tuesday.
Thanks!
@Apostolos-Daniel That was the same issue I was trying to resolve, as it was annoying to have to export them and check then into TFS again and again, every time I wanted to make any change. Using the API allows you to pull them from Postman as a step in the release process before you execute the newman step.
If you get a little farther along and would like to see what I am doing, just let me know. I'd be happy to share what I have working and see if others have some ideas to improve on it.
@jrothlander that sounds like exactly what I want to do, don’t think I saw a way to do it a year ago, I’ll give that a try Was just hoping to have a better inbuilt/ automated way like they provided with GitHub
Hi All, we have launched a repository integration with Azure DevOps in App version 9.6.0. Please refer to the blog post for ideal flow and learning center docs to know how to configure Azure integration. The Azure DevOps Service (TFS/ on-prem) will follow soon.
Is there a Roadmap feature to create more Sync options for Postman Collections?
I'd like to sync to TFS (VSTS)
Backup and Sync your Postman Collections on GitHub http://blog.getpostman.com/2017/03/10/backup-and-sync-your-postman-collections-on-github/
Integrate API tests with Postman, Newman, and Travis CI http://blog.getpostman.com/2017/08/23/integrate-api-tests-with-postman-newman-and-travis-ci/
(or other source control systems)