I am trying to do a build system with advanced commands.
My build command needed project specific settings, so as I didn't found how to load a project setting in a build command, I wrote a plugin to generate my command, but for now I am only able to access such command through the command palette or using a custom menu field.
Is there a way to use a plugin command in a build system action ?
Related
I am trying to make a VS Code extension where the launch.json would have launch configurations that link to the command palette.
Specifically, I have registered commands using vscode.commands.registerCommand("CommandA"). Is there a way to make it so that the launch.json would direct to "CommandA"?
EDIT: I basically want to run a command from package.json
You can use have a launch configuration run a registered command from the command palette using command variables.
I created a solution based of the different csproj files using solution maker tool. This tool creates a master solution but does not add configurations to the projects or the solution, the way Visual Studio adds configuration settings to the solution file when it builds it. I tried to build it using MSbuild new.sln command from the Developer Command prompt for VS2013. I even tried using the command by giving configuration options but it still doesn't work. The solution builds without actually building any output when triggered by MSbuild unless built in Visual Studio first. Is there a way for MSbuild or another way to add the configuration settings to the solution file so it can actually build it?
I used devenv to build the solution instead and it worked.
I really love Sublime Text 2 and I want to use it for Software programming.
The problem is that our source files are stored on a Linux server and we all work using PuTTy to connect and Vim to edit the code. We can compile the source by executing a command in PuTTy.
I want to use Sublime Text 2 for coding (the folders in Linux are mounted on our Windows system so the files can be opened in Windows). But whenever I want to compile, I have to open PuTTy and compile manually which asks a lot of time. Can I automate this somehow? Like if I push a button (F8 for example) then PuTTy opens, connects to the Linux server with SSH goes to the correct folder and compiles the source file. Is this possible?
Thanks for any help!
Sublime Build Systems can be used to launch a process like this.
I'm not sure if you can automate anything using putty. But the fork named ExtraPutty allows this: it is scriptable using Lua, an you can launch a script from command line.
If you arefamiliar with Javascript, another alternative would be to use Grunt + a module like SSH2 to automate you compilation process, then launch it from a Sublime build system. The ssh module does not allow interactive commands to be scripted, so I recommend you to use SSH2.
There are many other options; pick the one with which you're the more confortable, then use Sublime Build system to launch it.
I am currently writing a simple plugin for Sublime Text 2 to make a shortcut, running pdflatex program with my opened file as an option.
So there is a question: is there any way to run linux command from sublime? I haven't found appropriate function in Plugin API Reference.
How can i access jenkins build status at runtime without email-ext plugin?
i want to access build_status using environment variable of jenkins. Or Any other way to access build status variable of jenkins?
The default Jenkins environment variables don't include the build result.
However, you can use the Groovy Postbuild Plugin, which is run under the Jenkins JVM and have access to the current instance of the build.
Then from groovy you can access the build result via manager.build.result. See my answer here for the example usage.
You can use currentBuild.currentResult which is a global variable inside jenkins server to access the current build status. These variables are accessible inside pipelines.
Further you can check all the available global variables inside the server using below url
http://<server>/pipeline-syntax/globals