I have installed Jenkins on a Linux Server and I am trying to connect Jenkins to a TFS server. I have the TFS plug-in (4.0.0) installed on my Jenkins and I have also installed the tf command line tool (from here) on my Linux server.
When I create a new job in Jenkins, I get the TFS options to specify the URL, path, user name etc. I was also expecting the "TF command line executable" option to specify the path of the tf tool in my "Manage Jenkins" options but I am not seeing it. Any pointers on why I am not seeing it?
This answers it!
From the plugin notes for TFS on Jenkins:
Ever since release 4.0.0, a TFS command-line client or tool is no
longer necessary as all the interaction with the TFS server is done
using the TFS SDK for Java. The native libraries needed by the SDK are
automatically copied to a sub-directory under the agent user's home
folder.
Related
I'm currently using vscode-tomcat extension within a RHEL7 container and developing over SSH using the vscode-remote extension. However, I am unable to launch the tomcat debugger due to this unresolved issue.
"TypeError: Cannot set property 'readableListening' of undefined"
The issue only occurs when trying to launch the Tomcat debugger while doing remote SSH development. I am making an attempt to debug the issue, but I'm not sure how to debug a VSCode extension within a remote container.
Any tips would be greatly appreciated. Let me know if I can provide any additional details.
There is now documentation for all of this. Read
https://code.visualstudio.com/api/advanced-topics/remote-extensions#debugging-using-ssh
and then keep reading because further down you will find this
https://code.visualstudio.com/api/advanced-topics/remote-extensions#debugging-using-ssh
in fact read all of it, there's a lot of stuff there that initially made me think "So?" but which is vital knowledge in specialised problems.
Here's the portion relating to the immediate problem.
Debugging using SSH
Follow steps:
After installing and configuring the Remote - SSH extension, select Remote-SSH: Connect to Host... from the Command Palette (F1) in VS Code to connect to a host.
Once connected, either use File > Open... / Open Folder... to select the remote folder with your extension source code in it or select Git: Clone from the Command Palette (F1) to clone it and open it on the remote host.
Install any required dependencies that might be missing (for example using yarn install or apt-get) in a new VS Code terminal window (Ctrl+Shift+` ).
Finally, press F5 or use the Run view to launch the extension inside on the remote host and attach the debugger.
Note: You will not be able to open the extension source code folder in the window that appears, but you can open a sub-folder or somewhere else on the SSH host.
The extension development host window that appears will include your extension running on the SSH host with the debugger attached to it.
Installing a development version of your extension
Anytime VS Code automatically installs an extension on an SSH host, inside a container or WSL, or through GitHub Codespaces, the Marketplace version is used (and not the version already installed on your local machine).
While this makes sense in most situations, you may want to use (or share) an unpublished version of your extension for testing without having to set up a debugging environment. To install an unpublished version of your extension, you can package the extension as a VSIX and manually install it into a VS Code window that is already connected to a running remote environment.
Follow these steps:
If this is a published extension, you may want to add "extensions.autoUpdate": false to settings.json to prevent it from auto-updating to the latest Marketplace version.
Next, use vsce package to package your extension as a VSIX.
Connect to a codespace, development container, SSH host, or WSL environment.
Use the Install from VSIX... command available in the Extensions view More Actions (...) menu to install the extension in this specific window (not a local one).
5.Reload when prompted.
Tip: Once installed, you can use the Developer: Show Running Extensions command to see whether VS Code is running the extension locally or remotely.
I have a Visual Studio for Linux project. As myself, I can build it fine using devenv from the command line. However, when I try to run the same command from a Jenkins build, I get the error:
There are not remote machines configured for remote builds. Please configure a
machine using Tools Options / Cross Platform / Linux.
This didn't really surprise me, because the Jenkins job is running as SYSTEM, and my remote host setting is defined under my user account.
I tried copying my AppData/Local/Microsoft/Linux directory (which contains the remote host setting) to the system local appdata directory, but the remote host configuration still isn't found. Any idea how to work around?
The only way I found that worked was to run the Jenkins node as an actual user, one for which I had logged in and opened the Solution using VS 2017, and configured the remote host. Then the Jenkins process picked up the configuration.
I have easily installed Node.js before on Macs and other PCs, but the PC I have now at work restricts the running of .msi files.
Is there a way to manually install and configure node.js and npm on Windows 7? I have access to Powershell.
Installing nodejs (and npm) on a Windows 7 machine does not require any "magic" if you have Admin access on the target machine and do not care about setting up the expected "uninstall", various Windows performance counters, event tracing or Start menu entries.
To manually install from an existing installation on one machine to another machine, simply
Copy the entire contents of your "\Program Files\nodejs" and "\Users\USERNAME\AppData\Roaming\npm" directories as well as the "\Users\USERNAME\.npmrc" file to the same directories on target machine. (Replace USERNAME with your own Windows login name.)
Edit the "\Users\USERNAME\.npmrc" file to replace the source username with the username on the target machine.
Add "C:\Program Files\nodejs" and "C:\Users\USERNAME\AppData\Roaming\npm" to your PATH.
If you'd like to manually install direct from the MSI (without an existing installation to work from), get Scott Willeke's excellent lessmsi program, which allows you to extract all the files from any msi archive and discover all the actions taken by the Windows Installer, such as required edits to the Register, etc. (Though for nodejs, you'll only need to edit the Registry to add the proper keys to uninstall it automagically.)
I have installed the VisualSVN server on our Windows Server 2008 plus i did connect it with Dreamweaver on other client PC.
so Dreamweaver is ready to go.
But i also want to setup the PHPStorm on other Client PC with that visualSVN.
But i want PHPStorm to use TortoiseSVN to connect to VisualSVN.
I can't find its settings page, i am new to PHPStorm, Especially to this Subversion Control thingy.
I also searched for this over web, but i cant find specific PHPStorm Setup procedure with TortoiseSVN or connecting to VisualSVN Server.
Can anyone Guide me to the Right Path?
The accepted answer is not entirely accurate. It is possible to use TortoiseSVN through PHPStorm's External Tools configurations. This does not integrate into the project navigation directly, but does allow direct file manipulation (and allows for 'blame' support - something PHPStorm's subversion lacks).
Similar functionality is used in eclipse.
Example, paths/macros's might need to be altered:
Name: SVN View Log
Program: C:\Program Files\TortoiseSVN\bin\TortoiseProc.exe
Parameters: /command:log /path:"$FileName$"
Working Directory: $FileDir$
It's impossible to connect PhpStorm to TortoiseSVN as they are doing the same thing.
Then you have two choices :
Connect PhpStorm to your SVN server with his built-in feature.
Or use TortoiseSVN
I'll recommande using PhpStorm feature as it is directly in the IDE.
You can find documentation here : https://www.jetbrains.com/phpstorm/webhelp/using-subversion-integration.html
You can actually do this very easily and it will work inside PHP Storm 8. Install Tortoise SVN and make sure to include "Command Line Tools" as part of the installation. Then you can enable External client and select the "svn.exe" as the executable. This will enable SVN 1.8 format and still work within the IDE.
My solution:
Install TortoiseSVN
Install CollabNet Subversion with command-line binaries (32 or 64-bit)
Open phpStorm
File > Settings > Version Control > Subversion
Set path for your SVN command line client
e.g.
C:\Program Files\CollabNet\Subversion Client\svn.exe
Tortoise can be used as a GUI tool, whereas CollabNet Subversion command line tool can be used with phpStorm. Enjoy!
Setup:
- Eclipse Juno running on Windows 7
- GNU toolchain located on a Linux build server
- ClearCase repository accessible from a Windows 7 machine and a Linux build server
I want to open a C++ project from Eclipse in Windows and be able to build the project on the remote Linux build server. What is the best way to accomplish this now in 2013 with the state of Eclipse development?
(There were some dated questions with partial solutions.)
You would need to make a snapshot view directly on a linux path, which is possible through samba: your Windows server would be used for the view_server.exe, but the root directory of your snapshot view would be on Linux.
That leaves you with the issue to execute the gnu toolset from Linux from your Windows session. It is discussed in this 2011 thread.
Basically add a new "Remote Builder" option for managed build projects.
Similar to the Internal Builder, but it would invoke the compile commands over SSH or
whatever protocol the user chose.
It would be a RMB (Remote Managed Build), as in "Remote building".