I am using Hudson tool to automate tests for our project. I want to use FSTrigger plugin to trigger the build whenever there will a change in SVN.
As i set Folder path to "http://192.16.17.121/test/test1/config/". It gives error that folder should exist, but it exists at specified location.I can view it directly from browser too.
Can anybody tell me whats the problem?Your help will be appreciated.
Thanks...
You have to specify an absolute path to a directory on your filesystem. What you have shown there is a URL.
An absolute path would look like this:
/var/www/html/test/test1/config
Related
I am new to typescript and I am trying to do something that seems like it should be easy but no one on my team has got it to work and I can't find an answer online.
I have a common folder with shared components that I package with gulp, I then have an application folder that uses this package.
So the structure is something like
root
AppName
node_modules
CommonUi (with javascript)
src
..files..
CommonUi
node_modules
src
..files..
What I would like to do is run AppName and be able to put breakpoints in the typescript in CommonUi, if I debug CommonUi (point at the AppName url) the breakponits are disabled.
I assume I need a configuration setting to point at the CommonUi\src folder but I don't know where to put it.
Can anyone tell me what I need to do?
Thanks, Vincent
I have a Nightwatch + BrowserStack configuration on my project and I'm trying to add custom commands to my project to compare 2 screenshots using resemble.js .
I configure my nightwatch.json file with this :
"custom_commands_path": "./node_modules/nightwatch/commands",
"custom_assertions_path": "./node_modules/nightwatch/assertions"
I put the commands file in the folder and I tried to run my test in every directory possible to see if it was a path problem. I've also tried with different commands, some of them I get online and even the default example one. Whatever I run it returns nameOfTheCommand is not a function. So I guess it does not even find the path to the customs commands in the nightwatch.json file.
Is there anything I'm missing here? I'm quite new so the answer could be very simple but I tried every .json file of my project in case there was a special configuration linked to BrowserStack.
Path to the custom commands should be analogous to the path to custom commands. You should point a folder where you added them.
I've found that if I put them in the suite configuration file, it picks them up:
nightwatch_config = {
src_folders: ["tests/suite/product/"],
page_objects_path: "pages/product",
custom_commands_path: "./custom_commands"
}
I don't want PhpStorm to create an .idea folder. Is this possible?
I'm working in a new environment where I pretty much MUST figure out a way to remove them or I have to change IDE, which I really don't want to do.
Can't PhpStorm store the project files and settings in its own directory?
I don't want PhpStorm to create an .idea folder. Is this possible?
No, but workaround is very simple and described in the actual ticket body: http://youtrack.jetbrains.com/issue/WI-343 :
WORKAROUND: Actually you can do it for a long time - but only manually. Just create a new project anywhere where you want to store your project data, then go to "Settings | Directories" and detach its dir and attach your project root folder.
Just remember to open this folder instead of actual one next time.
Maybe, as an alternative, if you use a VCS, you can add .idea to your VCS ignore list? For example, for Mercurial it is called .hgignore and for Git - .gitignore.
I am writing a WIX installer and I have a following requirement:
During installation, I need to pass an absolute path to a file (lets call it A) included in my installer to a COM component, which already exists on the hard drive and is a part of another program. I have already written an appropriate Custom Action which expects a path to the file A. I don't want to include A as a file installed in the Program Files folder and removed during the uninstallation process. Instead, I would like to put A only temporary on the hard drive, call my Custom Action which will cause the COM component to use the content of A, and then remove A from disk. Is there an easy way to accomplish this goal?
I have tried to utilize the Binary Table and store A there, however I don't know how to reference A using absolute path. I know I could put A outside of MSI file but I would like to keep every file installer needs in a single MSI.
Any help would be appreciated.
Deleting a file that MSI installed means that MSI will consider it "broken" and try to auto-repair it if called on to do so. That happens automatically in several cases (e.g., advertised shortcuts and COM registration) so I'd recommend against it. Leave the file there instead -- it's done its job and there's no harm in leaving it there.
I would take this approach.
Install the file "A" into any directory. Run your custom action needed to update the COM component. Then run another custom action or modify the currently written one to remove the file after it is no longer in use. This would leave no trace of the file "A" and if you schedule the custom action to only run during the install you won't have to worry about it on uninstall.
Say I'm cloning a repository that I always clone to C:\working_copies\<customer-name>\<customer-project>\ and that the project has variables in it's build.properties that get filled in with <customer-name> <customer-project> (by me) everytime I clone the repo.
Is there a way that I can fill in these values in the file automatically by placing some special value in the file (in ant it's something like ${base-dir} or something like that) that would fill in these build.property values for me?
option 1: make sure build process only relies on relative paths, and dont change name/project variable
option2: write a hook, specifically a post-clone hook, try the book for a hook tutorial
No, Mercurial is completely unaware of what is outside of it's repository folder.
You should be able to rig this up using the Keyword Extension. Just set up a HGRC that populates the working directory with the values you want upon update.