Because "nightlies" usually mean - it's untested, in-development and
possibly buggy :)

That and the filename scheme your buildbot uses is far from predictable.
With launch pad I can automate deployments and I simply have to change a
simple version variable to download from launchpad. Meanwhile URLs like
where the last part is a timestamp are a pain to track and update.

Not that it's a problem right now. I'm currently making and testing the
VMs by hand (so there's no rush to release), but when I actually deploy,
it would be nice to have a stable URL I can get a stable version from.

You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.

  [1.1.2] RFW support: add option to not open report automatically ---
  fixed 1.1.3 2018-04-04 build #18

Status in Sikuli:
  Fix Released

Bug description:
  ------ solution (quick and dirty)
  instead of

  robot silent

  exactly so: robot<SPACE>silent<lineFeed>

  I am looking into setting up a VM and making automated tests on it using 
Sikuli (the latest available). Now everything seems to be working fine, however 
even when sikuli is launched from a command line it will open the web browser 
with the report (which is uploaded as an artifact to the CI server). Now this 
isn't really that big of a problem as I can just kill the browser after running 
the tests, but it would be much cleaner if the browser never opened in the 
first place.
  So the question is - is there a way to tell Sikuli NOT to open the report 
file after running the test?
  Also, where are IDE settings stored? the docs say 
'~/.java/.userPrefs/org/sikuli/prefs.xml' but that file doesn't contain 
anything except for xml headers and doctype.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to