Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Tyler Hughes
    @tylerbhughes
    so version 3 is that based on the Newman version? I assume it's not based on the the extension package since that has a 1:1 relation.
    Carlo Wahlstedt
    @carlowahlstedt
    no…If you look at any task that you have installed in TFS/VSTS there’s a version dropdown. We chose to increment the major version of the task to v3 because @sebcaps had added support for all command line options. However, we don’t have good testing setup for when we make changes. So instead of (potentially, accidentally) breaking everyone using the task, we chose to increment the major version of the task.
    Tyler Hughes
    @tylerbhughes
    ah ok. I remember seeing his PR now. Though, with something as small as changing the UI from a textbox to checkboxes I wouldn't think of that as beeing a breaking change seeing as you can still use the same options as before.
    Carlo Wahlstedt
    @carlowahlstedt
    yeah, I can’t say I’ve done the best job of branching to be able to release to multiple version at once. I honestly only first created this task for me and just put it out there. It’s picked up more traction than I expected.
    sebcaps
    @sebcaps
    @carlowahlstedt just release good tool at perfect moment ;-)
    I must admit I'm not very comfortable without tests (jsut refer to fix after release...), but assume after some research not very comfortable on 'how to' implement them
    not so many vsts extensions have tests that can be used as a basis...
    Carlo Wahlstedt
    @carlowahlstedt
    @sebcaps released the change you made for multi-select. Looks good, but I’m not using the task myself anywhere enough to test atm.
    Screen Shot 2018-02-21 at 9.29.56 AM.png
    Tyler Hughes
    @tylerbhughes
    I'll see if I can get one of our VSTS admins to update to the lastest version so I can try it out.
    sebcaps
    @sebcaps
    Hmmm, space after ',' makes me feel anguished. @tylerbhughes if you have chance to update and check, please let me know. In any case I'll give a try tomorrow.
    Carlo Wahlstedt
    @carlowahlstedt
    I thought VSTS should auto update the task. TFS would be what needs the manual update.
    Tyler Hughes
    @tylerbhughes
    I'll have to check and see.
    Ok yes, When I go to the build task and click the Version dropdown I see 3.x as an option now.
    That's cool. When I select the new version VSTS is smart enough to translate my cli,json to the correct checkboxes.
    Carlo Wahlstedt
    @carlowahlstedt
    Great! So it was successful?
    Tyler Hughes
    @tylerbhughes
    The build? not so much. I need to update my collection for a change that was made. But will let you know how it goes once I get that change checked in.
    Carlo Wahlstedt
    @carlowahlstedt
    Ok, I think I have a CI pipeline that will release to the marketplace. I will test on the next PR change that comes through.
    Tyler Hughes
    @tylerbhughes
    I know it's been over a year but that did work btw.
    Tyler Hughes
    @tylerbhughes
    I'm seeing a new issue now. I logged an issue for it. It's #55 but the gist of it is that I've been running Postman tests for over a year now in my release pipeline. Recently we decided to add them for each environment in our pipeline. The collection we're doing just hits a few endpoints to verify the services are all up and running. These tasks are running as deployment group. Because of that I'm not sure what users it's running under. I've installed Node and Newman on each server, added NPM to the path, rebooted the server and the task still can't find newman. With the addition of npx in NPM@5.2.0 we shouldn't have to install newman anymore. It should be as simple as running npx before the newman command and NPM will run the command for us even though it's not installed on the VM. How hard would it be to add support for this @carlowahlstedt?
    Carlo Wahlstedt
    @carlowahlstedt

    The user on the server would be the user the agent is running as. The agent was likely installed as some user on the machine.

    That said...I do see value in supporting npx (which I have no knowledge of) as you explain it. I’ll see if I can find some time to understand this and how to support it. Any assistance you can give is welcomed.

    Tyler Hughes
    @tylerbhughes
    Well when you add a server to a deployment group you have to run a PowerShell script, so I'm not sure what user it is using. I'll find that script and see if that provides any useful info.
    NPX is very useful, I have been using it for a few months now any time I start a new React project. Instead of installing create-react-app globally and having to keep that up to date I just run npx create-react-app my-app and it will run it as if it was installed on my machine.
    Tyler Hughes
    @tylerbhughes
    support for this should be fairly straightforward. Do a check to make sure npm version is at >= 5.2.0. If it's not then throw an error. If the server does have 5.2.0 installed then instead of checking for the path to newman just use npx newman <command>
    Carlo Wahlstedt
    @carlowahlstedt
    Thanks Tyler. Started looking into some of this and found that the task is uninstalled and locked…So trying to get that cleared up now...
    Carlo Wahlstedt
    @carlowahlstedt
    I did look into this a bit recently but didn’t get far. Seems that the standard pattern used is to install the tool. Not saying that’s what makes sense though.