-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Node execution in GitVersionTfsTask #909
Comments
@RyanMelenaNoesis I have no idea what this request is for, but do I understand the implementation correctly in that all we have to do is add this: "Node": {
"target": "nugetinstaller.js",
"argumentFormat": ""
} to the |
@asbjornu The example I provided was for the NugetInstaller VSTS task. For the GitVersion VSTS task it would be adding something like: "Node": {
"target": "$(currentDirectory)\\GitVersion.js",
"argumentFormat": ""
} to the Basically, Nix/OSX don't know how to run the GitVersion.ps1 because they don't support Powershell. |
@RyanMelenaNoesis Ah, that makes sense. Do you have any idea how to translate |
@asbjornu I could take a stab at it. I believe the Powershell Additionally, I'd probably need an OSX compatible version of the GitVersion.exe command line app in order to test which sounds like it is currently an issue (#854). |
@RyanMelenaNoesis Excellent! As soon as we've worked out the kinks in #890, I'll merge that and we should have a working |
@RyanMelenaNoesis I wish I could move #890 forward, but I don't have the time to help that with much else than code review. Currently, it seems to be halting on @JakeGinnivan providing some information on how the build providers work and @eatdrinksleepcode implementing a Travis build provider. If you're able to contribute to anything, then please fork that pull request and submit your own. 😃 |
Just quickly regarding the PS implementation: Implementing in a x-plat compatible fashion is definitely the way to go. This was already discussed in the original PR, but we decided to go with the PS implementation until someone has the time to provide the x-plat implementation. We should rewrite the task in TypeScript and make use of the VSTS Task SDK. |
Is this still planned? It would be great to be able to use the GitVersion VSTS build step on a Mac build agent. |
@Ivan-L Rewriting the VSTS task to Node and the new VSTS Task SDK still makes sense. But I don't think anybody is currently working on it. But I would be happy to accept a PR for this :) |
We've been struggling with this for monthes with @galo, so I've started the work on this. In addition to updating the execution engine I have a few proposals :
What do you think? WIP is visible here : https://github.com/sandorfr/GitVersion/tree/feature/node-tfs-task-and-tooling |
@sandorfr Thanks for your work on this. Can you create a PR for this so that we can discuss it there? One point. We're already using Cake for our build, and we should keep to a single build system for building everything. Of course it's possible to call a node or gulp script from the Cake script if this makes sense. Also I'm not really happy with adding a submodule and therefore add a dependency to an outside repository. If these are general purpose build scripts they should be published as npm modules IMHO. |
Ditto on the submodules, don't want to use them if at all possible. Lets either take a fork and just check them in or publish them as an NPM module as @pascalberger said. A pull request would be great, I have some comments on things but really like the direction. The comments are along the lines of, list typescript in devDependencies, lets use v2 and Side note, I would like to build on this node/typescript foundation and actually publish GitVersion to NPM. |
I'll see how we can publish our scripts as an npm module, it might actually help make our scripts easier to use. Regarding the typing I agree with the vision, but as a first step I would recommand staying on typings as a first step as it works today. I'm interested in the new typing approach but I'm pretty sure it won't be as straightforward as promised. I usually state typescript as a dev dependency to be sure that we do not require a user to install an extensive list of global dependencies to actually build the extension. The philosophy behind what we do for our extensions is clone, npm install and start contributing. That said, let me take as much of the feedback into account and I'll open a PR in a few days. |
Hi @pascalberger, I can't make it work on OSX. It seems to be smilar to this issue #1097. It seems that it may have been addressed by Execution log:
|
@asbjornu Any idea about this? |
@pascalberger: No, sorry. I think someone with deep LibGit2Sharp knowledge needs to help us out with this one. |
Hi, LibGit2Sharp has released the final 0.24.0. This should fix the problem on OSX, and make everything work fine. |
After upgrading to LibGit2Sharp 0.26 in #1713, I hope this problem is now fixed. Can you please try the latest build of GitVersion and report back whether it fixes this problem or not? Please reopen this issue if the problem persists. |
Please consider adding a Node execution property to GitVersionTfsTask/task.json. (example)
I believe this would allow for running the GitVersion VSO/VSTS custom task on Nix/OSX VSTS build agents. This feature would likely also depend on #854.
The text was updated successfully, but these errors were encountered: