I have a Hudson server on one PC, and I need to move it to another PC.
I want to do this right the first time without messing up a bunch of things. I've found in my Googling a Stack Overflow question and answer for moving Jenkins here.
I am wary to follow those instructions for Hudson because:
There might be a subtle but significant difference between Hudson and Jenkins since the time that they forked from each other that causes complications;
I'm dealing with Windows 7, not Linux;
I want to know if I can just move Hudson directly from one PC to another, without having to install and reconfigure Hudson on the target PC first (as per the Jenkins instructions).
So my question is, can I move my Hudson installation directly without installing a fresh Hudson on the target PC first? If so, what are the steps?
Related
I'm having an issue with the Live Server extension for VS Code (https://marketplace.visualstudio.com/items?itemName=ritwickdey.LiveServer). I'm using WSL 2 for my programming and I have my GitHub repos saved in the Linux filesystems:
\wsl$\Ubuntu\home\myName\Files\GitHub\CSS-My-Site
The issue is that when I make any changes in my project and save, the web page does not automatically reload the way it's supposed to. Now, when I initially run Live Server it does indeed open up my browser and display my page. It just doesn't update after that, I have to refresh manually.
I'm guessing it has something to do with WSL2 because if I move my project folder to my Windows desktop, Live Server works perfectly. I've tried 3 different projects from within the Linux filesystems and none of them update automatically. I've moved all 3 to my desktop, and they auto-refresh just fine. I've also uninstalled and reinstalled the extension, and reinstalled VS Code as well.
I've gone through a couple of posts but none of them seem to have my specific issue. The 2 most relevant were:
https://learn.microsoft.com/en-us/windows/wsl/troubleshooting
https://github.com/ritwickdey/vscode-live-server/issues/452
I am running Mullvad VPN and also tried turning it off and the issue persisted. My system information is below:
Edition Windows 10 Home
Version 20H2
Installed on 11/13/2020
OS build 19042.630
Experience Windows Feature Experience Pack 120.2212.31.0
It seems WSL doesn't support live reload if the file is in another OS. Please refer the GitHub issue.
The solution is to keep the source and execution in the same place.
I solved my problem just by changing the extension, now I use "Five Server"
I solved it by looking for the local ip of my machine using ifconfig in the terminal, copy the ip, paste it in my browser and then :5500
In this tutorial you can see how to extract the VHD image file of the Windows XP contained in the "Windows XP Mode".
The tutorial also explains how to run it on VirtualBox and it works nicely (no special parameter, you just add the disk).
But I want to run it on QEmu and there I get a blue screen.
This is the command I'm using:
qemu-system-i386 -m 1G --enable-kvm -drive file=VirtualXP.vhd
I tried to convert the image to qcow2, raw, ... same issue.
I tried x86_64... same issue.
I tried without --enable-kvm... same issue but the blue screen is covered partly by a black rectangle.
After the blue screen it restarts and allows me to choose safe mode. But all options give this identical blue screen.
When I boot the image with VirtualBox I noticed that the VM has already a driver installed to allow the use of the host's mouse cursor. I suspect that this image has VM guest drivers installed that are not compatible with QEmu and maybe make it crashes.
Important note: I don't have a Windows XP CD-ROM to help me.
Here is a screen shot of the blue screen (I suppose it will be the exact same error on all machines):
This might have to do with the drivers windows expects, there are various results using search engines to fix/repair this issue I found but they mostly boil down to:
Install standard IDE drivers
Registery edit to add these IDE drivers
If BSOD 0xCE
Remove Intelppm driver
Edit registery to reflect the removal of this CPU driver
I like the idea of a Windows XP image converted to another, for qemu. And it sounded awesome if this was a legal way. And I now know how they solved this. There is a 30 days trail period and after this, our downloaded image will nolonger boot. (unless you redo all your steps on a fresh copy that never has been started).
Sources to help you (and I ) anyway: https://learn.microsoft.com/en-us/windows/client-management/troubleshoot-inaccessible-boot-device
wich was to me very cryptic and what to do?
But it was also reverenced by the following more helpfull article, and i was almost capable of making a bootable harddisk image for qemu because of this: http://0x0badc0de.blogspot.com/2013/05/converting-windows-virtual-machine-from.html
But after some hours back and forth, I wasnt fully successful and even the author mentions the 30day trial. legal, maybe, but still troublesome.
There is however a key included and if you where to acquire a XP install disk, maybe able to obtain a successful install of windows XP with the same 30 days trial. Hope this answer helps you or any traveler to decide their own story.
I downloaded MySQL installer. I chose the Developer Default Setup Type. Now it's downloading the various components of MySQL. There is an issue here: the downloading seems to be stalled. As you can see, some components have already completed downloaded, but others are still downloading. It had been downloading for over an hour now and the percentages have not changed. There has been no visible progress so far after this state. What could be the cause of this? How can I make sure that the installer is really working instead of stalling? It seems that the installer downloaded some components and ... stopped working? I have a wireless internet connection. I don't know whether this could be the issue.
So basically I got bored waiting and I just canceled the install. It turned out that the installer was stalled. Then I started the installer again. I selected the Developer Default Setup Type again, and I repeated everything as I did it the first time. The second time the installer ran much faster. Now when it came to the Installation step, all the products or components of MySQL which had been already downloaded did not need to be downloaded again. They just were installed. The products which were incompletely downloaded the first time had to be downloaded again the second time, but the downloading was much faster.
If MySQL installer shows no progress during this step, it is better to just cancel it, and then restart it again. The next time it should work as expected.
I have a PC with a dual boot: Win 8.1 and Ubuntu 14.04 and I have some project in PHP & mySql and sometimes I need to develop under ubuntu (but I usually prefer Windows) but I need to share the files and db's between the two os.
In share I mean if I change some php files or rows in the database that must be visible in both OS. Is it possible?
Extra thing: The most beautiful thing would be if I could get the mercurial in this thing.
Liquibase for proper versioning of DB-changes in both OS
Mercurial in both OS
External Mercurial hosting (Bitbucket?) for intermediate repository and backup
Good editor or IDE, in which you can configure EOL-style (in order to have same EOL in Windows and Linux, different by default)
Code in active OS, commit changes to local Mercurial, push to remote.
Before starting work in another OS - pull collected changes from remote
We are in the process of upgrading from Windows XP x86 to Windows 7 x64, and I'm testing for compatibility problems with our current workflow.
Currently, we store central Mercurial repositories on a network share, clone copies to our workstations, and push our changes back to the network-based repositories. This works perfectly in WinXP, but in Win7 I consistently get an error message when pushing back to the network share:
pushing to t:\datamgt\automat\Kevin\SampleRepo
searching for changes
[Error 32] The process cannot access the file because it is being used by another process: 'T:\datamgt\automat\Kevin\SampleRepo\.hg\journal.dirstate'
I'm using TortoiseHG 1.1.1 and Mercurial 1.6.1023.
I've been able to push to repositories stored on the same workstation, but not to the network share repo. If possible, we'd prefer not to go to a webserver-based repository - it's an up-hill fight to get new software added to our servers.
Pushing to a network share is possible, but not recommended by the Mercurial team.
See the "shared disk" part in Publishing Repositories in the Mercurial wiki:
generally restricted to intranets, not
generally recommended due to general
issues with network filesystem
reliability
At my workplace, we are keeping our HG repositories on a network share (on a Windows 2003 server) as well because it was the easiest to set up. We're doing this for about one and a half year now, and we never had problems like yours.
But at home, I have a network share on a NAS (it's accessible from Windows and it looks and feels like a Windows share, but the NAS actually runs on Linux). I had no problems for a long time, but since a few weeks I'm having similar errors like you (with a different error message though).
I posted this on the Mercurial bug tracker, and I was told that my problem is probably caused by the fact that my NAS runs on Linux, because they don't know of any problems with real Windows shares:
On real Windows shares (served by
Windows) there doesn't seem to be a
problem (never heard of others having
problems doing that).
So maybe your problem is caused by something similar as well.
What kind of Windows share is it that you try to push to? Is it really on a Windows machine?