Bug 766257 - skynet client: push with specified server and apikey does not work
Summary: skynet client: push with specified server and apikey does not work
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lee Newson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-11 11:03 UTC by Joshua Wulf
Modified: 2014-10-19 22:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-20 01:44:32 UTC


Attachments (Terms of Use)

Description Joshua Wulf 2011-12-11 11:03:07 UTC
[jwulf@gaura csprocessor-data.sql]$ skynet push -s skynet.bne.redhat.com:8180 -a 108108 -cn ~/Work/EDS/EDS\ GSG-spec

Error: Invalid argument!

java -jar skynet.jar push [OPTIONS] [FILENAME]
  OPTIONS:
    --contentspec, -c
    --edit, -e
    --exec-time
    --new, -n
    --permissive, -p
    --tagsmap, -T

  FILENAME - The name/location of the file to be uploaded.
--------------------------------------------------------------------------
That should work.

Current Workaround:

Put the server and apikey information into ~/.config/skynet-ws/skynet.ini and use:

skynet push --config ~/.config/skynet-ws ~/Work/EDS/EDS\ GSG-spec

Comment 1 Lee Newson 2012-01-05 23:21:10 UTC
Tested with build 0.16.0 of the client. The parameter -s is for snapshots, to specify the server path you need to use a capital S. I may have forgotten to change the symbol in older versions of the client help file, however I'm unable to check since I no longer have access to the older versions. The symbol used to be -s however it was changed to a capital when snapshots were added.


Note You need to log in before you can comment on or make changes to this bug.