Command line Archives - scmGalaxy https://www.scmgalaxy.com/tutorials/tag/command-line/ A Platform for Software Engineers Sat, 27 Feb 2021 09:55:54 +0000 en-US hourly 1 https://wordpress.org/?v=7.1 Perforce Command Line Global Options https://www.scmgalaxy.com/tutorials/perforce-command-line-global-options/ https://www.scmgalaxy.com/tutorials/perforce-command-line-global-options/#respond Tue, 09 Jan 2018 06:17:30 +0000 http://www.scmgalaxy.com/tutorials/?p=4572 <!– .style1 { font-size: 24px; font-weight: bold; } –> Perforce Command Line Global Options Global options for Perforce commands; these […]

The post Perforce Command Line Global Options appeared first on scmGalaxy.

]]> <!– .style1 { font-size: 24px; font-weight: bold; } –>

Perforce Command Line Global Options

Global options for Perforce commands; these options can be supplied on the command line before any Perforce command.

Syntax
p4 [-cclient -ddir -Hhost -pport -Ppass -uuser -xfile -Ccharset -Qcharset -Llanguage] [-G] [-s] [-z tag] cmd [args …]
p4 -V
p4 -h

 

Options
 
-c client
Overrides any P4CLIENT setting with the specified client name.
-d dir
Overrides any PWD setting (i.e. current working directory) and replaces it with the specified directory.
-G
Causes all output (and batch input for form commands with -i) to be formatted as marshalled Python dictionary objects. This is most often used when scripting.
-H host
Overrides any P4HOST setting and replaces it with the specified hostname.
-p port
Overrides any P4PORT setting with the specified port number.
-P pass
Overrides any P4PASSWD setting with the specified password.
-s
Prepends a descriptive field (for example, text:, info:, error:, exit:) to each line of output produced by a Perforce command. This is most often used when scripting.
-u user
Overrides any P4USER, USER, or USERNAME setting with the specified user name.
-x file
Instructs Perforce to read arguments, one per line, from the specified file. If file is a single hyphen (-), then standard input is read.
-C charset
Overrides any P4CHARSET setting with the specified character set.
-Q charset
Overrides any P4COMMANDCHARSET setting with the specified character set.
-L language
This feature is reserved for system integrators.
-z tag
Causes output of many reporting commands to be in the same tagged format as that generated by p4 fstat.
-V
Displays the version of the p4 client program and exits.
-h
Displays basic usage information and exits.

 

Usage Notes
•
Be aware that the global options must be specified on the command line before the Perforce command. Options specified after the Perforce command will not be interpreted as global options, but as options for the command being invoked. It is therefore possible to have the same command line option appearing twice in the same command, being interpreted differently each time.
For example, the command p4 -c anotherclient edit -c 140 file.c will open file file.c for edit in pending changelist 140 under client workspace anotherclient.
•
The -x option is useful for automating tedious tasks; a user adding several files at once could create a text file with the names of these files and invoke p4 -x textfile add to add them all at once.
The -x option can be extremely powerful – as powerful as whatever generates its input. For example, a UNIX developer wishing to edit any file referring to an included file.h file, for instance, could grep -l file.h *.c | cut -f1 -d: | p4 -x – edit.
In this example, the grep command lists occurrences of file.h in the *.c files, the -l option tells grep to list each file only once, and the cut command splits off the filename from grep’s output before passing it to the p4 -x command.
•
The -s option can be useful in automated scripts.
For example, a script could be written as part of an in-house build process which executes p4 -s commands, discards any output lines beginning with “info:”, and alerts the user if any output lines begin with “error:”.
•
Python developers will find the -G option extremely useful for scripting. For instance, to get a dictionary of all fields of a job whose ID is known, use the following:
job_dict = marshal.load(os.popen(‘p4 -G job -o ‘ + job_id, ‘rb’))
In some cases, it may not be intuitively obvious what keys are used by the client program. If you pipe the output of any p4 -G invocation to the following script, you will see every record printed out in key/value pairs:

The post Perforce Command Line Global Options appeared first on scmGalaxy.

]]> https://www.scmgalaxy.com/tutorials/perforce-command-line-global-options/feed/ 0 Perforce Command Line https://www.scmgalaxy.com/tutorials/perforce-command-line/ https://www.scmgalaxy.com/tutorials/perforce-command-line/#respond Tue, 09 Jan 2018 06:13:04 +0000 http://www.scmgalaxy.com/tutorials/?p=4570 Command Description p4 add Open file(s) in a client workspace for addition to the depot. p4 admin Perform administrative operations […]

The post Perforce Command Line appeared first on scmGalaxy.

]]>

Command

Description

p4 add
Open file(s) in a client workspace for addition to the depot.
p4 admin
Perform administrative operations on the server.
p4 branch
Create or edit a branch specification and its view.
p4 change
Create or edit a changelist specification.
p4 changelists
List submitted and pending changelists.
p4 changelist
Create or edit a changelist specification.
p4 client
Create or edit a client workspace specification and its view.
p4 clients
List all client workspaces currently known to the system.
p4 delete
Open file(s) in a client workspace for deletion from the depot.
p4 depot
Create or edit a depot specification.
p4 depots
Display a list of depots known to the Perforce server.
p4 describe
Provides information about changelists and the changelists’ files.
p4 groups
List groups of users.
p4 group
Add or delete users from a group, or set the maxresults, maxscanrows, and timeout limits for the members of a group.
p4 have
List files and revisions that have been synced to the client workspace
p4 info
Display information about the current client and server.
p4 integrate
Open files for branching or merging.
p4 integrated
Show integrations that have been submitted.
p4 job
Create or edit a defect, enhancement request, or other job specification.
p4 jobs
List jobs known to the Perforce server.
p4 label
Create or edit a label specification and its view.
p4 labels
Display list of defined labels.
p4 lock
Lock an opened file against changelist submission.
p4 login
Log in to a Perforce server by obtaining a ticket.
p4 logout
Log out of a Perforce server by removing or invalidating a ticket.
p4 passwd
Change a user’s Perforce password on the server.
p4 rename
Renaming files under Perforce.
p4 resolve
Resolve conflicts between file revisions.
p4 revert
Discard changes made to open files.
p4 set
Set Perforce variables in the Windows registry.
p4 submit
Send changes made to open files to the depot.
p4 sync
Copy files from the depot into the workspace.
p4 tag
Tag files with a label.
p4 triggers
Edit a list of scripts to be run conditionally whenever changelists are submitted, forms are updated, or when integrating Perforce with external authentication mechanisms.
p4 user
Create or edit Perforce user specifications and preferences.
p4 users
Print a list of all known users of the current server.
p4 verify
Verify that the server archives are intact.
p4 workspace
Create or edit a client workspace specification and its view.

The post Perforce Command Line appeared first on scmGalaxy.

]]> https://www.scmgalaxy.com/tutorials/perforce-command-line/feed/ 0 Java Command Line Options https://www.scmgalaxy.com/tutorials/java-command-line-options/ https://www.scmgalaxy.com/tutorials/java-command-line-options/#respond Mon, 08 Jan 2018 12:29:29 +0000 http://www.scmgalaxy.com/tutorials/?p=4553 -client       to select the “client” VM -server       to select the “server” VM -hotspot      is a synonym for the “client” VM  […]

The post Java Command Line Options appeared first on scmGalaxy.

]]> -client       to select the “client” VM
-server       to select the “server” VM
-hotspot      is a synonym for the “client” VM  [deprecated]
The default VM is client.

-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D<name>=<value>
set a system property
-verbose[:class|gc|jni]
enable verbose output
-version      print product version and exit
-version:<value>
require the specified version to run
-showversion  print product version and continue
-jre-restrict-search | -jre-no-restrict-search
include/exclude user private JREs in the version search
-? -help      print this help message
-X            print help on non-standard options
-ea[:<packagename>…|:<classname>]
-enableassertions[:<packagename>…|:<classname>]
enable assertions
-da[:<packagename>…|:<classname>]
-disableassertions[:<packagename>…|:<classname>]
disable assertions
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
-agentlib:<libname>[=<options>]
load native agent library <libname>, e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:<pathname>[=<options>]
load native agent library by full pathname
-javaagent:<jarpath>[=<options>]
load Java programming language agent, see java.lang.instrument
-splash:<imagepath>
show splash screen with specified image

The post Java Command Line Options appeared first on scmGalaxy.

]]> https://www.scmgalaxy.com/tutorials/java-command-line-options/feed/ 0 Complete guide to use Jenkins CLI / Command line | Jenkins Tutorials https://www.scmgalaxy.com/tutorials/complete-guide-to-use-jenkins-cli-command-line/ https://www.scmgalaxy.com/tutorials/complete-guide-to-use-jenkins-cli-command-line/#comments Sun, 08 Jan 2017 08:37:19 +0000 http://www.scmgalaxy.com/tutorials/2017/01/08/complete-guide-to-use-jenkins-cli-command-line/ Complete guide to use Jenkins CLI / Command line? Run Jenkins build from command is very simple in Linux system. […]

The post Complete guide to use Jenkins CLI / Command line | Jenkins Tutorials appeared first on scmGalaxy.

]]> jenkins-cli-command-line
Complete guide to use Jenkins CLI / Command line?
Run Jenkins build from command is very simple in Linux system. If you are using using windows, gitbash is a recommended which has bash shell in built. You can use windows command line as well. Jenkins has support to command line client that allows you to access Jenkins from command line.
To Trigger Jenkins build from command line some prerequisite are there
Jenkins service is running.
Enable security option under “Configure Global Security”
Go to jenkins dashboard in Home page ( e.g http://localhost:8080/ ) -> Manage Jenkins
-> Configure Global Security -> Click on “Enable security” checkbox

You can also configure “Access Control” and “Authorization” option in Global Security page.

Download Jenkins-cli.jar
Download Jenkins-cli.jar from http://<your_jenkins_server_url>/jnlpJars/jenkins-cli.jar. (Here <your_jenkins_server_url> is your respective Jenkins server URL (development or staging))
Go to http://<your_jenkins_server_url>/cli and build your command by following the instructions there.
How to login to Jenkins using commands
If your Jenkins requires authentication, use –username and –password or –password-file options to specify the credentials. To avoid doing this for every command, you can also use the login CLI command once (with the same credentials parameters), and after that you may use other commands without specifying credentials.
Whenever the CLI tries to to connect to the Jenkins server, it offers the before mentioned SSH keys. When the user has those keys but don’t want use them to authenticate, preventing being prompted by the key’s password, it’s possible to use the -noKeyAuth argument. This way the CLI will never try to use the SSH keys available. failure to authenticate by itself does not constitute a fatal error. It will instead try to execute the command anyway, as the anonymous user.
Login Jenkins using username and Password
Jenkins allow us to trigger Jenkins build with any specific user, For that we have to pass username and password in command line.
$ java -jar “/tmp/kitchen/cache/jenkins-cli.jar” -s http://localhost:8080 who-am-i –username jenkins –password foobar
$ java -jar jenkins-cli.jar -s http://myjenkins help –username me –password mypassword
Login Jenkins using public keys
Starting 1.419 (which will be out July 4th), Jenkins CLI supports authentication based on the SSH key pair. Just like CloudBees DEV@cloud (or GitHub, or other similar sites), you interactively login from the web UI, then associate your public keys with your user account. Then CLI will silently authenticates itself using your ~/.ssh/id_rsa, ~/.ssh/id_dsa, or ~/.ssh/identity.
https://help.github.com/articles/generating-an-ssh-key/
Login Jenkins using private keys
You can also pass the priate key as follows
To use the -i option the syntax is as follows:
$ java -jar jenkins-cli.jar -s http://myjenkins help -i ~/.ssh/id_rsa
$ java -jar jenkins-cli.jar [-s JENKINS_URL] [-i PRIVATE_KEY] command [options…] [arguments…]
For compatibility reasons, unless you use the -i option,
Login Jenkins using initialAdminPassword
try user “admin” and password from “Jenkins\secrets\initialAdminPassword”
java -jar jenkins-cli.jar -s http://localhost:8080 who-am-i –username admin –password fe3f1e1624ea4be8873b7a35e28b24be
Login Jenkins using passphrase
Go to http://jenkins-serer:8085/user/admin/configure and set the passphrase in “SSH Public Keys” and use the same passphrase with jenkins commands.
E.g 1 – Getting help
The list of the available commands depends on the server you are talking to. Visit https://jenkins.example.com/cli or use ‘help’ command to list them all:
> java -jar jenkins-cli.jar -s https://jenkins.example.com help [command]
E.g 2 – Run Jenkins Build From Command Line
> java -jar jenkins-cli.jar -s http://<jenkins server>/ build build-name [-c] [-f] [-p] [-r N] [-s] [-v] [-w]
build-name : Name of the job to build
-c  : Check for SCM changes before starting the build, and if there’s no change, exit without doing a build
-f  : Follow the build progress. Like -s only interrupts are not passed through to the build.
-p  : Specify the build parameters in the key=value format.
-s  : Wait until the completion/abortion of the command. Interrupts are passed through to the build.
-v  : Prints out the console output of the build. Use with -s
-w  : Wait until the start of the command
Example  – java -jar jenkins-cli.jar -s http://localhost:8080/ build ‘my-project-build’ –username roop –password roop
E.g 3 – List all jobs under the view: tools
$ java -jar jenkins-cli.jar -s http://jenkins/ list-jobs tools
E.g 4 – Get the configuration of the job: template
$ java -jar jenkins-cli.jar -s http://jenkins/ get-job template > template.xml
E.g 5 – Create a new job based on the configuration
$ java -jar jenkins-cli.jar -s http://jenkins/ create-job new_job_name < new_job_name.xml
E.g 6 – Run groovy script
$ java -jar jenkins-cli.jar -s http://jenkins/ groovy scripts/add_job_to_view.groovy
If there are any parameters in the script, just as:
import jenkins.model.*
if (args.length != 2 ) {
  println “Error on arguments!”
}
def jobName  = args[0] ?: ‘a_job’
def viewName = args[1] ?: ‘a_view’
println jobName + ‘ ‘ + viewName
def v = Jenkins.instance.getView(viewName)
def i = Jenkins.instance.getItemByFullName(jobName)
if (v && i) {
  v.add(i)
}
pass the parameters as:
$ java -jar jenkins-cli.jar -s http://jenkins/ groovy scripts/add_job_to_view.groovy JOB_NAME VIEM_NAME
E.g 7 – Build a job
$ java -jar jenkins-cli.jar -s http://jenkins/ build new_job_name
E.g 8 – Diable a job
$ java -jar jenkins-cli.jar -s http://jenkins/ disable-job new_job_name
E.g 8 – Passing parameters when triggering a job build
Job parameters are a very handy concept. Perhaps you’ve only ever used Jenkins or another CI system to automatically run builds when a remote SCM/git repo changes. You can also trigger builds manually from within Jenkins. And whilst you’re doing that, your job can prompt for parameters to the build.
For example, we have a job named similar to “Deploy XYZ App”. It has the git repo hardcoded in the job like a normal build, but when you press “Build”, it shows a list of options: string fields, drop-down lists, etc.
When the job runs, you can use these values anywhere within your job’s configuration. Its very cool.
But how to pass those same parameters via the CLI? You use the -p key=value flag for each parameter you want to pass.
So our finished product might look like:
$ java -jar jenkins-cli.jar -s http://myjenkins build ‘Deploy XYZ App’ -i ~/.ssh/id_rsa -s -v -p target_env=api.cloudfoundry.com -p branch=master
Commons problems
Operation timed out
$ java -jar jenkins-cli.jar -s YOUR_SERVER_URL help
Exception in thread “main” java.net.ConnectException: Operation timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at java.net.Socket.<init>(Socket.java:375)
at java.net.Socket.<init>(Socket.java:189)
at hudson.cli.CLI.<init>(CLI.java:97)
at hudson.cli.CLI.<init>(CLI.java:82)
at hudson.cli.CLI._main(CLI.java:250)
at hudson.cli.CLI.main(CLI.java:199)
Check that the JNLP port is opened if you are using a firewall on your server. You can configure its value in Jenkins configuration. By default it is set to use a random port.
java.io.IOException: No X-Jenkins-CLI2-Port
java.io.IOException: No X-Jenkins-CLI2-Port among [X-Jenkins, null, Server, X-Content-Type-Options, Connection, X-You-Are-In-Group, X-Hudson, X-Permission-Implied-By, Date, X-Jenkins-Session, X-You-Are-Authenticated-As, X-Required-Permission, Set-Cookie, Expires, Content-Length, Content-Type]
at hudson.cli.CLI.getCliTcpPort(CLI.java:284)
at hudson.cli.CLI.<init>(CLI.java:128)
at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72)
at hudson.cli.CLI._main(CLI.java:473)
at hudson.cli.CLI.main(CLI.java:384)
Suppressed: java.io.IOException: Server returned HTTP response code: 403 for URL: http://citest.gce.px/cli
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1840)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
at hudson.cli.FullDuplexHttpStream.<init>(FullDuplexHttpStream.java:78)
at hudson.cli.CLI.connectViaHttp(CLI.java:152)
at hudson.cli.CLI.<init>(CLI.java:132)
… 3 more
Solution: Go to Manage Jenkins -> Configure Global Security -> “TCP port for JNLP agents”: choose fixed or random
Reference

The post Complete guide to use Jenkins CLI / Command line | Jenkins Tutorials appeared first on scmGalaxy.

]]> https://www.scmgalaxy.com/tutorials/complete-guide-to-use-jenkins-cli-command-line/feed/ 1 Docker Command line Reference | Docker Tutorial | Docker Guide https://www.scmgalaxy.com/tutorials/docker-commands-line-reference/ https://www.scmgalaxy.com/tutorials/docker-commands-line-reference/#comments Fri, 15 Jul 2016 17:50:41 +0000 http://www.scmgalaxy.com/tutorials/2016/07/15/docker-commands-line-reference/ One liner to stop all of Docker containers: > docker stop $(docker ps -a -q) One liner to remove all […]

The post Docker Command line Reference | Docker Tutorial | Docker Guide appeared first on scmGalaxy.

]]>
One liner to stop all of Docker containers:
> docker stop $(docker ps -a -q)
One liner to remove all of Docker containers:
> docker rm $(docker ps -a -q)
OR
> docker rm $(docker images -q)
OR
> docker rmi $(docker images -q)
In case of error message Get http:///var/run/docker.sock/v1.14/containers/json?all=1: dial unix /var/run/docker.sock: permission denied
> sudo docker rm $(sudo docker ps -a -q)
To only stop exited containers and delete only non-tagged images.:
> docker ps –filter ‘status=Exited’ -a | xargs docker stop
> docker images –filter “dangling=true” -q | xargs docker rmi
Remove all containers that aren’t currently running:
> docker rm $(docker ps -a -q -f “status=exited*”)
if not the volumes will not be delete !!! (like if you are using a mysql docker image) and all the volumes will be orphans !
> sudo docker rm -f -v $(sudo docker ps -a -q)

The post Docker Command line Reference | Docker Tutorial | Docker Guide appeared first on scmGalaxy.

]]> https://www.scmgalaxy.com/tutorials/docker-commands-line-reference/feed/ 1 Chef Commands Line Reference | Chef Commands Line Guide | Cheatsheet https://www.scmgalaxy.com/tutorials/chef-commands-line-reference/ https://www.scmgalaxy.com/tutorials/chef-commands-line-reference/#respond Sun, 20 Sep 2015 09:17:05 +0000 http://www.scmgalaxy.com/tutorials/2015/09/20/chef-commands-line-reference/ To run single recipe using chef-solo > chef-solo -c /opt/chef/repo/config/solo.rb -o my_cookbook::recipe To run the single reciepe in same machine […]

The post Chef Commands Line Reference | Chef Commands Line Guide | Cheatsheet appeared first on scmGalaxy.

]]> chef-commands-line-reference

To run single recipe using chef-solo

> chef-solo -c /opt/chef/repo/config/solo.rb -o my_cookbook::recipe

To run the single reciepe in same machine

> chef-apply hello.rb

To generate the cookbook standard structure

> chef generate cookbook learn_chef_httpd
> knife cookbook create smartmontools -r md

To generate the template file in cookbook

> chef generate template learn_chef_httpd index.html

To run the cookbook in local mode

> sudo chef-client --local-mode --runlist ‘recipe[learn_chef_httpd]’


To download the cookbooks from market place


> knife cookbook site download learn_chef_httpd


> knife cookbook site install learn_chef_httpd




To Upload the cookbooks to chef server


> knife cookbook upload learn_chef_httpd


> knife cookbook upload -a


To bootstrap a nodes


> knife bootstrap {{address}} --ssh-user {{user}} --ssh-password '{{password}}' --sudo --use-sudo-password --node-name node1 --run-list 'recipe[learn_chef_apache2]'


> knife bootstrap uvo1t75faaktzc532w6.vm.cld.sr -x root -P Br356YS0iy –sudo –node-name firefox


> knife bootstrap 123.45.6.789 -x username -P password –sudo




To see the list of nodes


>knife node list


To edit the node run list


> knife node edit name_of_node


To see the info about each nodes


> knife node show node1


Run the cooksbooks on nodes


> knife ssh {{address}} 'sudo chef-client' --manual-list --ssh-user {{user}} --ssh-password '{{password}}'


> ssh username@ipadddress -i mycredentials.pem sudo chef-client


To add the run list to the nodes.


knife node run_list add C2445575914.domain 'recipe[hptrain]'


knife node run_list set test-node '''recipe[iptables]''' [Windows - Powershell]


knife node run_list set test-node 'recipe[iptables]' [Windows - Command]


The post Chef Commands Line Reference | Chef Commands Line Guide | Cheatsheet appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/chef-commands-line-reference/feed/
			0
		
		
			
		
		Jenkins Command line Reference for login and trigger a job
		https://www.scmgalaxy.com/tutorials/jenkins-command-line-reference-for-login-and-trigger-a-job/
					https://www.scmgalaxy.com/tutorials/jenkins-command-line-reference-for-login-and-trigger-a-job/#comments
		
		
		Thu, 05 Feb 2015 00:00:00 +0000
				
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2015/02/05/jenkins-command-line-reference-for-login-and-trigger-a-job/

					Grep will return 0 while the build is running: $ curl http://myjenkins/job/myjob/lastBuild/api/json | grep –color result\”:null $ echo $? Trigger […]


The post Jenkins Command line Reference for login and trigger a job appeared first on scmGalaxy.

]]>
										jenkins-command-line-reference


Grep will return 0 while the build is running:


$ curl http://myjenkins/job/myjob/lastBuild/api/json | grep –color result\”:null


$ echo $?


Trigger a Jenkins Job from command line


$ wget http://yourserver/job/MyJobname/build?delay=0sec


$ wget -O – $HUDSON_URL/job/JOBNAME/build


Trigger a Jenkins Job without authentication


$ curl http://jenkins:8080/job/my%20job/build


Trigger a Jenkins Job with authentication


$ curl –user dbacher:$MY_API_TOKEN http://jenkins:8080/job/my%20job/build


$ curl –user <your_jenkins_username>:<your_jenkins_API_key> http://<jenkins_server_url>/job/<your_jenkins_job_name>/build


Running commands against a secure Jenkins (basic auth or ssh keys)


$ java -jar jenkins-cli.jar -s http://myjenkins help –username me –password mypassword


$ java -jar jenkins-cli.jar -s http://myjenkins help -i ~/.ssh/id_rsa


Triggering a job build against a secure Jenkins (avoiding a 1.5 year old open bug!)


$ java -jar jenkins-cli.jar -s http://myjenkins build ‘My Awesome Jenkins Job’ -i ~/.ssh/id_rsa


$ java -jar jenkins-cli.jar -s http://myjenkins build ‘My Awesome Jenkins Job’ -i ~/.ssh/id_rsa -s -v


Passing parameters when triggering a job build


$ java -jar jenkins-cli.jar -s http://myjenkins build ‘Deploy XYZ App’ -i ~/.ssh/id_rsa -s -v -p target_env=api.cloudfoundry.com -p branch=master


Reference


http://starkandwayne.com/articles/2013/04/12/jenkins-builds-from-cli/


http://www.scmgalaxy.com/index.php?option=com_k2&view=item&id=890:ways-to-login-jenkins-using-command-line&Itemid=120


Appendix


1. How to get your_jenkins_API_key?


    

  • Login to your Jenkins.
    • 

  • Click on the username in the top right.
    • 

  • Click on Configure.
    • 

  • Click on ‘Show API Token’ button.
    • 

  • You got it.
    • 



The post Jenkins Command line Reference for login and trigger a job appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/jenkins-command-line-reference-for-login-and-trigger-a-job/feed/
			2
		
		
			
		
		What are the ways to Login Jenkins using Command line ?
		https://www.scmgalaxy.com/tutorials/ways-to-login-jenkins-using-command-line/
					https://www.scmgalaxy.com/tutorials/ways-to-login-jenkins-using-command-line/#comments
		
		
		Tue, 27 May 2014 00:00:00 +0000
				
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2014/05/27/ways-to-login-jenkins-using-command-line/

					Ways to Login Jenkins using Command line & Way to trigger Jenkins job using Command line or script Wget Note: […]


The post What are the ways to Login Jenkins using Command line ? appeared first on scmGalaxy.

]]>
										login-jenkins-using-command-line


Ways to Login Jenkins using Command line


&


Way to trigger Jenkins job using Command line or script


Wget


Note: If you are using wget 1.11, you might need to use the following options:






 wget --auth-no-challenge --http-user=user --http-password=apiToken http://jenkins.yourcompany.com/job/your_job/build?token=TOKEN






With wget 1.10.x the following is enough (but will not work with 1.11.x) :






 wget http://user:apiToken@jenkins.yourcompany.com/job/your_job/build?token=TOKEN



ex – wget http://yourserver/job/MyJobname/build?delay=0sec


CURL


Without authentication:


$ curl http://jenkins:8080/job/my%20job/build [ HTML page saying "Authentication required" ] 


With authentication:


$ curl --user dbacher:$MY_API_TOKEN http://jenkins:8080/job/my%20job/build [ returns nothing and the build starts ] 


curl -X POST http://server/view/name/job/jobname/build?delay=0sec --user 1019352:61bb8531292794315f5dda8113548630






Login Jenkins using groovy script or Perl Script or Java, please refer the reference page…


Reference:

https://wiki.jenkins-ci.org/display/JENKINS/Authenticating+scripted+clients


https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API


The post What are the ways to Login Jenkins using Command line ? appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/ways-to-login-jenkins-using-command-line/feed/
			2
		
		
			
		
		Know About Jenkins CLI | Jenkins CLI Guide
		https://www.scmgalaxy.com/tutorials/know-about-jenkins-cli/
					https://www.scmgalaxy.com/tutorials/know-about-jenkins-cli/#respond
		
		
		Mon, 10 Feb 2014 04:16:10 +0000
				
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2014/02/10/know-about-jenkins-cli/

					Running CLI java -jar jenkins-cli.jar [-s JENKINS_URL] command [options…] [arguments…] Getting help java -jar jenkins-cli.jar -s yourserver.com help [command] How […]


The post Know About Jenkins CLI | Jenkins CLI Guide appeared first on scmGalaxy.

]]>
										jenkins-cli


Running CLI

java -jar jenkins-cli.jar [-s JENKINS_URL] command [options…] [arguments…]


Getting help

java -jar jenkins-cli.jar -s yourserver.com help [command]


How to download jenkins-cli.jar?

The best place to download the Jenkins CLI jar is from your own Jenkins server. This means you’ll have the matching CLI version. Visit the /cli endpoint, such as http://yourserver.com/cli, and it will give you a link to download the jar (the /jnlpJars/jenkins-cli.jar endpoint). Download that jar.


Running commands against a secure Jenkins (basic auth or ssh keys)


If your Jenkins is secured, and it probably is so that you control who can create jobs, run jobs, view results, then the command above may fail and ask for credentials.

You have two options: provide –username & –password options to every command or provide -i option and provide the path to the ssh private key that matches the public key you provided to your user account.

For example:


$ java -jar jenkins-cli.jar -s http://myjenkins help –username me –password mypassword

$ java -jar jenkins-cli.jar -s http://myjenkins help -i ~/.ssh/id_rsa


Passing parameters when triggering a job build

To pass those same parameters via the CLI? You use the -p key=value flag for each parameter you want to pass.


So our finished product might look like:


$ java -jar jenkins-cli.jar -s http://myjenkins build ‘Deploy XYZ App’ -i ~/.ssh/id_rsa -s -v -p target_env=api.cloudfoundry.com -p branch=master


How to get all commands for Jenkins CLI-

Run > http://yourserver.com/cli


java -jar jenkins-cli.jar -s http://fmsscm.corp.intuit.net/qbo-qa/ help


Available Commands


    

  • build: Builds a job, and optionally waits until its completion.
    • 

  • cancel-quiet-down: Cancel the effect of the “quiet-down” command.
    • 

  • clear-queue: Clears the build queue
    • 

  • connect-node: Reconnect to a node
    • 

  • console: Retrieves console output of a build
    • 

  • copy-job: Copies a job.
    • 

  • create-job: Creates a new job by reading stdin as a configuration XML file.
    • 

  • create-node: Creates a new node by reading stdin as a XML configuration.
    • 

  • delete-builds: Deletes build record(s).
    • 

  • delete-job: Deletes a job
    • 

  • delete-node: Deletes a node
    • 

  • disable-job: Disables a job
    • 

  • disconnect-node: Disconnects from a node
    • 

  • enable-job: Enables a job
    • 

  • get-job: Dumps the job definition XML to stdout
    • 

  • get-node: Dumps the node definition XML to stdout
    • 

  • groovy: Executes the specified Groovy script.
    • 

  • groovysh: Runs an interactive groovy shell.
    • 

  • help: Lists all the available commands.
    • 

  • install-plugin: Installs a plugin either from a file, an URL, or from update center.
    • 

  • install-tool: Performs automatic tool installation, and print its location to stdout. Can be only called from inside a build.
    • 

  • keep-build: Mark the build to keep the build forever.
    • 

  • list-changes: Dumps the changelog for the specified build(s).
    • 

  • list-jobs: Lists all jobs in a specific view or item group.
    • 

  • list-plugins: Outputs a list of installed plugins.
    • 

  • login: Saves the current credential to allow future commands to run without explicit credential information.
    • 

  • logout: Deletes the credential stored with the login command.
    • 

  • mail: Reads stdin and sends that out as an e-mail.
    • 

  • offline-node: Stop using a node for performing builds temporarily, until the next “online-node” command.
    • 

  • online-node: Resume using a node for performing builds, to cancel out the earlier “offline-node” command.
    • 

  • quiet-down: Quiet down Jenkins, in preparation for a restart. Don’t start any builds.
    • 

  • reload-configuration: Discard all the loaded data in memory and reload everything from file system. Useful when you modified config files directly on disk.
    • 

  • restart: Restart Jenkins
    • 

  • safe-restart: Safely restart Jenkins
    • 

  • safe-shutdown: Puts Jenkins into the quiet mode, wait for existing builds to be completed, and then shut down Jenkins.
    • 

  • session-id: Outputs the session ID, which changes every time Jenkins restarts
    • 

  • set-build-description: Sets the description of a build.
    • 

  • set-build-display-name: Sets the displayName of a build
    • 

  • set-build-parameter: Update/set the build parameter of the current build in progress
    • 

  • set-build-result: Sets the result of the current build. Works only if invoked from within a build.
    • 

  • set-external-build-result: Set external monitor job result.
    • 

  • set-next-build-number: Set build number to be used for next build.
    • 

  • shutdown: Immediately shuts down Jenkins server
    • 

  • update-job: Updates the job definition XML from stdin. The opposite of the get-job command
    • 

  • update-node: Updates the node definition XML from stdin. The opposite of the get-node command
    • 

  • version: Outputs the current version.
    • 

  • wait-node-offline: Wait for a node to become offline
    • 

  • wait-node-online: Wait for a node to become online
    • 

  • who-am-i: Reports your credential and permissions
    • 



Reference –

https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI

http://stackoverflow.com/questions/18199355/jenkins-cli-authentication

http://stackoverflow.com/questions/16617232/jenkins-cli-public-key-authentication-where-to-put-my-public-key-in-jenkins


The post Know About Jenkins CLI | Jenkins CLI Guide appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/know-about-jenkins-cli/feed/
			0
		
		
			
		
		Understand Jenkins CLI | Jenkins CLI Reference
		https://www.scmgalaxy.com/tutorials/know-about-jenkins-cli-2/
					https://www.scmgalaxy.com/tutorials/know-about-jenkins-cli-2/#respond
		
		
		Mon, 10 Feb 2014 04:16:10 +0000
				
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2014/02/10/know-about-jenkins-cli-2/

					Running CLI java -jar jenkins-cli.jar [-s JENKINS_URL] command [options…] [arguments…] Getting help java -jar jenkins-cli.jar -s yourserver.com help [command] How […]


The post Understand Jenkins CLI | Jenkins CLI Reference appeared first on scmGalaxy.

]]>
										jenkins-cli


Running CLI

java -jar jenkins-cli.jar [-s JENKINS_URL] command [options…] [arguments…]


Getting help

java -jar jenkins-cli.jar -s yourserver.com help [command]


How to download jenkins-cli.jar?

The best place to download the Jenkins CLI jar is from your own Jenkins server. This means you’ll have the matching CLI version. Visit the /cli endpoint, such as http://yourserver.com/cli, and it will give you a link to download the jar (the /jnlpJars/jenkins-cli.jar endpoint). Download that jar.


Running commands against a secure Jenkins (basic auth or ssh keys)


If your Jenkins is secured, and it probably is so that you control who can create jobs, run jobs, view results, then the command above may fail and ask for credentials.

You have two options: provide –username & –password options to every command or provide -i option and provide the path to the ssh private key that matches the public key you provided to your user account.

For example:


$ java -jar jenkins-cli.jar -s http://myjenkins help –username me –password mypassword

$ java -jar jenkins-cli.jar -s http://myjenkins help -i ~/.ssh/id_rsa


Passing parameters when triggering a job build

To pass those same parameters via the CLI? You use the -p key=value flag for each parameter you want to pass.


So our finished product might look like:


$ java -jar jenkins-cli.jar -s http://myjenkins build ‘Deploy XYZ App’ -i ~/.ssh/id_rsa -s -v -p target_env=api.cloudfoundry.com -p branch=master


How to get all commands for Jenkins CLI-

Run > http://yourserver.com/cli


java -jar jenkins-cli.jar -s http://fmsscm.corp.intuit.net/qbo-qa/ help


Available Commands


    

  • build: Builds a job, and optionally waits until its completion.
    • 

  • cancel-quiet-down: Cancel the effect of the “quiet-down” command.
    • 

  • clear-queue: Clears the build queue
    • 

  • connect-node: Reconnect to a node
    • 

  • console: Retrieves console output of a build
    • 

  • copy-job: Copies a job.
    • 

  • create-job: Creates a new job by reading stdin as a configuration XML file.
    • 

  • create-node: Creates a new node by reading stdin as a XML configuration.
    • 

  • delete-builds: Deletes build record(s).
    • 

  • delete-job: Deletes a job
    • 

  • delete-node: Deletes a node
    • 

  • disable-job: Disables a job
    • 

  • disconnect-node: Disconnects from a node
    • 

  • enable-job: Enables a job
    • 

  • get-job: Dumps the job definition XML to stdout
    • 

  • get-node: Dumps the node definition XML to stdout
    • 

  • groovy: Executes the specified Groovy script.
    • 

  • groovysh: Runs an interactive groovy shell.
    • 

  • help: Lists all the available commands.
    • 

  • install-plugin: Installs a plugin either from a file, an URL, or from update center.
    • 

  • install-tool: Performs automatic tool installation, and print its location to stdout. Can be only called from inside a build.
    • 

  • keep-build: Mark the build to keep the build forever.
    • 

  • list-changes: Dumps the changelog for the specified build(s).
    • 

  • list-jobs: Lists all jobs in a specific view or item group.
    • 

  • list-plugins: Outputs a list of installed plugins.
    • 

  • login: Saves the current credential to allow future commands to run without explicit credential information.
    • 

  • logout: Deletes the credential stored with the login command.
    • 

  • mail: Reads stdin and sends that out as an e-mail.
    • 

  • offline-node: Stop using a node for performing builds temporarily, until the next “online-node” command.
    • 

  • online-node: Resume using a node for performing builds, to cancel out the earlier “offline-node” command.
    • 

  • quiet-down: Quiet down Jenkins, in preparation for a restart. Don’t start any builds.
    • 

  • reload-configuration: Discard all the loaded data in memory and reload everything from file system. Useful when you modified config files directly on disk.
    • 

  • restart: Restart Jenkins
    • 

  • safe-restart: Safely restart Jenkins
    • 

  • safe-shutdown: Puts Jenkins into the quiet mode, wait for existing builds to be completed, and then shut down Jenkins.
    • 

  • session-id: Outputs the session ID, which changes every time Jenkins restarts
    • 

  • set-build-description: Sets the description of a build.
    • 

  • set-build-display-name: Sets the displayName of a build
    • 

  • set-build-parameter: Update/set the build parameter of the current build in progress
    • 

  • set-build-result: Sets the result of the current build. Works only if invoked from within a build.
    • 

  • set-external-build-result: Set external monitor job result.
    • 

  • set-next-build-number: Set build number to be used for next build.
    • 

  • shutdown: Immediately shuts down Jenkins server
    • 

  • update-job: Updates the job definition XML from stdin. The opposite of the get-job command
    • 

  • update-node: Updates the node definition XML from stdin. The opposite of the get-node command
    • 

  • version: Outputs the current version.
    • 

  • wait-node-offline: Wait for a node to become offline
    • 

  • wait-node-online: Wait for a node to become online
    • 

  • who-am-i: Reports your credential and permissions
    • 



Reference –

https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI

http://stackoverflow.com/questions/18199355/jenkins-cli-authentication

http://stackoverflow.com/questions/16617232/jenkins-cli-public-key-authentication-where-to-put-my-public-key-in-jenkins


The post Understand Jenkins CLI | Jenkins CLI Reference appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/know-about-jenkins-cli-2/feed/
			0
		
		
			
		
		Maven CLI Options Reference – Command Line | Maven Command Line Cheatsheet
		https://www.scmgalaxy.com/tutorials/maven-cli-options-reference-command-line/
					https://www.scmgalaxy.com/tutorials/maven-cli-options-reference-command-line/#respond
		
		
		Thu, 12 Sep 2013 10:06:42 +0000
				
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2013/09/12/maven-cli-options-reference-command-line/

					Maven CLI Options Reference Options Description -am,--also-make If project list is specified, also build projects required by the list -amd,--also-make-dependents […]


The post Maven CLI Options Reference – Command Line | Maven Command Line Cheatsheet appeared first on scmGalaxy.

]]>
										maven-cli-options-reference

Maven CLI Options Reference






Options
Description




-am,--also-make
If project list is specified, also build projects required by the list




-amd,--also-make-dependents
If project list is specified, also build projects that depend on projects on the list




–B,–batch-mode
Run in non-interactive (batch) mode




-C,--strict-checksums
Fail the build if checksums don’t match




-c,--lax-checksums
Warn if checksums don’t match




-cpu,--check-plugin-updates
Ineffective, only kept for backward compatibility




-D,--define <arg>
Define a system property




-e,--errors
Produce execution error messages




-emp,--encrypt-master-password <arg>
Encrypt master security password




-ep,--encrypt-password <arg>
Encrypt server password




-f,--file <arg>
Force the use of an alternate POM file (or directory with pom.xml).




-fae,--fail-at-end
Only fail the build afterwards; allow all non-impacted builds to continue




-ff,--fail-fast
Stop at first failure in reactorized builds




-fn,--fail-never
NEVER fail the build, regardless of project result




-gs,--global-settings <arg>
Alternate path for the global settings file




-h,--help
Display help information




-l,--log-file <arg>
Log file to where all build output will go.




-llr,--legacy-local-repository
Use Maven 2 Legacy Local Repository behaviour, ie no use of _maven.repositories. Can also be activated by using -Dmaven.legacyLocalRepo=true




-N,--non-recursive
Do not recurse into sub-projects




-npr,--no-plugin-registry
Ineffective, only kept for backward compatibility




-npu,--no-plugin-updates
Ineffective, only kept for backward compatibility




-nsu,--no-snapshot-updates
Suppress SNAPSHOT updates




-o,--offline
Work offline




-P,--activate-profiles <arg>
Comma-delimited list of profiles to activate




-pl,--projects <arg>
Comma-delimited list of specified reactor projects to build instead of all projects. A project can be specified by [groupId]:artifactId or by its relative path.




-q,--quiet
Quiet output – only show errors




-rf,--resume-from <arg>
Resume reactor from specified project




-s,--settings <arg>
Alternate path for the user settings file




-T,--threads <arg>
Thread count, for instance 2.0C where C is core multiplied




-t,--toolchains <arg>
Alternate path for the user toolchains file




-U,--update-snapshots
Forces a check for updated releases and snapshots on remote repositories




-up,--update-plugins
Ineffective, only kept for backward compatibility




-V,--show-version
Display version information WITHOUT stopping build




-v,--version
Display version information




-X,--debug
Produce execution debug output






The post Maven CLI Options Reference – Command Line | Maven Command Line Cheatsheet appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/maven-cli-options-reference-command-line/feed/
			0
		
		
			
		
		Understand Ant command line arguments with Examples
		https://www.scmgalaxy.com/tutorials/ant-command-line-arguments-2/
					https://www.scmgalaxy.com/tutorials/ant-command-line-arguments-2/#respond
		
		
		Tue, 06 Oct 2009 11:36:10 +0000
				
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2009/10/06/ant-command-line-arguments-2/

					Several tasks take arguments that will be passed to another process on the command line. To make it easier to […]


The post Understand Ant command line arguments with Examples appeared first on scmGalaxy.

]]>
										ant-command-line-arguments


Several tasks take arguments that will be passed to another process on the command line. To make it easier to specify arguments that contain space characters, nested arg elements can be used.


value – a single command-line argument; can contain space characters.


file – The name of a file as a single command-line argument; will be replaced with the absolute filename of the file.


path – A string that will be treated as a path-like string as a single command-line argument; you can use ; or : as path separators and Ant will convert it to the platform’s local conventions.


pathref – Reference to a path defined elsewhere. Ant will convert it to the platform’s local conventions.


line – a space-delimited list of command-line arguments.


It is highly recommended to avoid the line version when possible. Ant will try to split the command line in a way similar to what a (Unix) shell would do, but may create something that is very different from what you expect under some circumstances.


Examples


<arg value=”-l -a”/>


is a single command-line argument containing a space character.


<arg line=”-l -a”/>


represents two separate command-line arguments.


<arg path=”/dir;/dir2:\dir3″/>


is a single command-line argument with the value \dir;\dir2;\dir3 on DOS-based systems and /dir:/dir2:/dir3 on Unix-like systems.


Command-line Options Summary

ant [options] [target [target2 [target3] …]]









Options:





-help, -h
Displays help information describing the Ant command and its options




-projecthelp, -p
Print project help information




-version
Print the version information and exit




-diagnostics
Print information that might be helpful to diagnose or report problems.




-quiet, -q
Suppresses most messages not originated by an echo task in the buildfile




-verbose, -v
Displays detailed messages for every operation during a build.




-debug, -d
Print debugging information




-emacs, -e
Produce logging information without adornments




-lib <path>
Specifies a path to search for jars and classes




-logfile <file>
Use given file for log




-l <file>
Use given file for log




-logger <classname>
Specifies a class to handle Ant logging.




-listener <classname>
Add an instance of class as a project listener




-noinput
Do not allow interactive input




-buildfile <file>
Use given buildfile




-file <file>
Use given buildfile




-f <file>
Use given buildfile




-D<property>=<value>
Defines a property name-value pair on the command line.




-keep-going, -k
execute all targets that do not depend on failed target(s)




-propertyfile <name>
load all properties from file with -D properties taking precedence




-inputhandler <class>
the class which will handle input requests




-find <file>
Search for buildfile towards the root of the filesystem and use it






The post Understand Ant command line arguments with Examples appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/ant-command-line-arguments-2/feed/
			0
		
		
			
		
		WinZip Command Line | WinZip Command line CheatSheet – Reference
		https://www.scmgalaxy.com/tutorials/winzip-command-line/
					https://www.scmgalaxy.com/tutorials/winzip-command-line/#respond
		
		
		Sat, 20 Jun 2009 05:12:41 +0000
				
		
		
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2009/06/20/winzip-command-line/

					The default action is to add or replace zipfile entries from list, which can include the special name – to […]


The post WinZip Command Line | WinZip Command line CheatSheet – Reference appeared first on scmGalaxy.

]]>
										  


winzip-command-line


The default action is to add or replace zipfile entries from list, which can include the special name – to compress standard input. If zipfile and list are omitted, zip compresses stdin to stdout.




 -f   freshen: only changed files                   -u   update: only changed or new files


 -d   delete entries in zipfile                         -m   move into zipfile (delete files)


 -k   force MSDOS (8+3) file names           -g   allow growing existing zipfile


 -r   recurse into directories                          -j   junk (don’t record) directory names


 -0   store only                                                   -l   convert LF to CR LF (-ll CR LF to LF)


 -1   compress faster                                       -9   compress better


 -q   quiet operation                                        -v   verbose operation/print version info


 -c   add one-line comments                        -z   add zipfile comment


 -b   use “path” for temp file                        -t   only do files after “mmddyy”


 -@   read names from stdin                        -o   make zipfile as old as latest entry


 -x   exclude the following names              -i   include only the following names


 -F   fix zipfile (-FF try harder)                      -D   do not add directory entries


 -A   adjust self-extracting exe                    -J   junk zip file prefix (unzipsfx)


 -T   test zipfile integrity                                 -X   eXclude eXtra file attributes


 -$   include volume label                              -S   include system and hidden files


 -h   show this help                                          -n   don’t compress these suffixes


The post WinZip Command Line | WinZip Command line CheatSheet – Reference appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/winzip-command-line/feed/
			0
		
		
			
		
		“Cheat Sheet” of Perforce command-line | Perforce command-line Guide
		https://www.scmgalaxy.com/tutorials/cheat-sheet-of-perforce-command-line/
					https://www.scmgalaxy.com/tutorials/cheat-sheet-of-perforce-command-line/#respond
		
		
		Sat, 20 Jun 2009 04:59:12 +0000
				
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2009/06/20/cheat-sheet-of-perforce-command-line/

					A way to remember data-mining commands The following is a set of questions that will be used during the Perforce […]


The post “Cheat Sheet” of Perforce command-line | Perforce command-line Guide appeared first on scmGalaxy.

]]>
										perforce-command-line-cheatsheet






A way to remember data-mining commands




The following is a set of questions that will be used during the Perforce training to remind students which “data-mining” commands to use for specific situations. Perforce is a terrific tool, but it’s easy to get lost in the choices between “p4 files” and “p4 changes” and “p4 filelog” and so on. This list can help a great deal.








the question starts with…




the answer starts with…






Examples






“What are the filenames that…?”
“p4 files….”
p4 files //depot/…#have

p4 have

p4 files //depot/…

(which is the same as)

p4 files //depot/…#head

p4 files //depot/…@label

p4 files //depot/…@client

p4 files //depot/…@2001/02/12

p4 files //depot/…@1541		




“What are the differences between the

workspace copy of XXX and the depot

copy of XXX?”		
“p4 diff …”
• p4 diff file.c

• p4 diff file.c#2

• p4 diff file.c#head

• p4 diff //… or “p4 diff”

• p4 diff –se		




“What are the differences the depot copy

of ______ and the depot copy of ______?”		
“p4 diff2 ….”
• p4 diff2 file1.c file2.c

• p4 diff2 file1.c#1 file.c#2

• p4 diff2 dir1/… dir2/…

• p4 diff2 dir1/…@now dir1/…@2000/01/02		




“Tell me everything about changelist #___.”
“p4 describe”
• p4 describe 1231




“What’s a list of changelists that….?”
“p4 changes….”
• p4 changes

(which is the same as)

p4 changes //…

• p4 changes file.c

• p4 changes –i file.c | grep 1255

• p4 changes //depot/…@label1,@label2		






 





“Cheat Sheet” of Perforce command-line




The following list is a set of helpful commands that anyone can run, but that the person administering the Perforce codelines will

be using a lot. They’re included here for quick reference.








Function




Commands






Create a new workspace…

1. That’s modeled after the

“1.0dev” workspace – same

mappings

2. That’s the Perforce defaults,		
Set the workspace name using “p4 set” or in the environment. Then run:

1. p4 client –t 1.0dev

2. p4 client		




Retrieve a file as of

1. Now (head revision)

2. April 15, 2000

3. Label “xyz”

4. Changelist 123456

5. the revision that client

“jab.work” has retrieved

6. The revision you had before

accidently bashing your disk		
Use “p4 sync” as follows:

1. p4 sync file.java

p4 sync file.java#head

p4 sync file.java@now

2. p4 sync file.java@2000/04/15

3. p4 sync file.java@xyz

4. p4 sync file.java@123456

5. p4 sync file.java@jab.work

6. p4 sync –f file.java#have

See “p4 help revisions” for more examples. Note that anywhere that “file.java” is used in these

examples, a full pathname (“c:\work\projects\file.java”) or depot name

(“//depot/rel_218/base/projects/file.java”) could be used.		




Open a file for:

1. add

2. edit

3. delete

And then publish the change to others

.		
Use “p4” with the appropriate verb:

• p4 add file.java

• p4 edit file.java

• p4 delete file.java

Then “p4 submit” to publish it		




What have I changed in the files I

have opened for edit?		
• p4 diff (for all opened files)

• p4 diff file1 file2 (for specific files)		




Undo a checkout.
If the file hasn’t been submitted yet:

• Use “p4 revert –a” to find all opened files that have no modifications – it’ll revert those.

• Use “p4 revert file.java” to revert an individual file.

• Use “p4 revert //…” to revert all files.

Remember that “p4 revert” is irreversible.

If the file has been submitted, you’ll need to open the file for edit and check in a prior revision.

Use very good change descriptions to say what you did and why.		




Interrupt your work to edit a single

file and check it in, without any other

disruptions. (You’re hacking Java and

someone needs a “relnotes.txt”

updated ASAP to issue a release.)		
Two ways:

1. Edit the file and submit only that file.

• p4 edit relnotes.txt

• do the modifications

• p4 submit relnotes.txt

2. Make a new changelist to manage just that change.

• p4 change

remove all the files in this change from the Files: section, it’ll create an empty

change.

• p4 edit –c XXX relnotes.txt

where XXX is the change number in the previous step

• p4 submit –c XXX		




Publish your work to others
“p4 submit”




Compress the data on the net

because you have a slow modem line

between your workspace and the

server.		
Run “p4 client” for your workspace, and change the options from “nocompress” to “compress”.

(Read “p4 help client” for details.)		




Get the list of…

1. All changelists applied to the

base codeline

2. … to the prodxyz codeline

3. … to the prodxyz codeline,

including those applied

originally to another codeline

and integrated into prodxyz

4. All revisions of file.java		
Use “p4 changes” or “p4 filelog” as follows:

1. p4 changes //depot/eng/…

2. p4 changes //depot/eng/prodxyz/…

3. p4 changes –i //depot/eng/prodxyz/…

4. p4 filelog file.java		




Push … from the base codeline

(“prodxyz”) to the 1.0.1 codeline

(“prodxyz-1.0.1”):

1. Push change #1232

2. From change #129 to #134

3. all changes in the base

codeline		
Use “p4 integrate –b prodxyz-1.0.1” as the place to start, in each case:

1. p4 integ –b prodxyz-1.0.1 //…@=1232

2. p4 integ –b prodxyz-1.0.1 //…@129,@134

3. p4 integ –b prodxyz-1.0.1 (no additional args)

Note that this assumes that the named branch specification “prodxyz-1.0.1” has been created

by your project lead or administrator using “p4 branch”.		




Push … from the prodxyz-1.0.1

codeline to the base (“prodxyz”)

codeline:

1. Push change #1235

2. From change #127 to #128

3. all changes in the base		
Use “p4 integrate –b prodxyz-1.0.1” as the place to start, in each case:

1. p4 integ –b prodxyz-1.0.1 –r @=1235

2. p4 integ –b prodxyz-1.0.1 –r //…@127,@128

3. p4 integ –b prodxyz-1.0.1 –r (no additional args)

The “-r” reverses the order of source/target in that named branch specification.

Note that for the ‘selective integration’ cases, you’ll want to be VERY CAUTIOUS of ‘accept

theirs’.		




Show the ‘diff’ between the

prodxyz-1.0.1 codeline and its

parent		
“p4 diff2 –b prodxyz-1.0.1” (This works because “prodxyz” is the name of the branch

specification, not because “prodxyz” is part of “//depot/prodxyz/…”)		




What branches do I have?
If you use “p4 branch” to create branch specifications and use them consistently, then “p4

branches” provides this info.		




How do I make a new codeline

named prodxyz-2.0?		
There are several steps:

1. Make a named branch specification. Save it.

• “p4 prodxyz-2.0”

• if you want to exactly imitate another branch (e.g. prodxyz), use

“p4 branch –o prodxyz-1.0.1 > tmp” to capture the output, edit this temporary file

and replace the “1.0.1” references with “2.0”, then run “p4 branch –i < tmp”.

2. Run the “p4 integrate” command to populate this new codeline. Submit the change.

• p4 integrate –b prodxyz-2.0

or, if you want to push content as of a certain label (e.g. “xyz”) from the parent,

p4 integrate –b prodxyz-2.0 //…@xyz

• p4 submit

3. Send e-mail telling everyone about this codeline and what it’s used for.		




Put everything onto a laptop, you’re

going to the beach and want to hack.

(This assumes that you won’t be

connected to a net while away.)		
There are several steps:

1. Connect the laptop to the net.

2. Run “p4 sync” to populate the source onto the laptop.

3. Leave for the beach.

4. While editing, use “chmod” or “attrib” to make the files writeable. Make your changes.

5. Get back to work, reconnect to the net.

6. Run the following commands to tell you what’s updated and open them for

add/edit/delete:

• p4 diff –se | p4 –x – edit

• p4 diff –sd | p4 –x – delete

• find . –type f –print | p4 –x – add

Then inspect what’s opened (“p4 opened”) and what you’ve changed (“p4 diff”). Submit or

revert as appropriate.		




Run a checkpoint
“p4 admin checkpoint” – only an administrator can run this. (An administrator has “super”

permissions in the “p4 protect” data.)

Be sure to back up the checkpoint, the current journal, and each of the “depot” directories on

the server machine!		




Change the security/permissions
“p4 protect” – only an administrator can run this.

Also…

“p4 protects” – used in 2006.1 and later to TELL you your permissions .		




Make a label
It’s a two-step process:

1. Make the label using “p4 label xxx”

2. Populate it using “p4 labelsync –l xxx”

or if you have a specific list of files,

“p4 labelsync –l xxx file1 file2 …”.		




Copy a label’s contents to another

label. Assume that the existing label

is “xxx” and the new label is to be

“abc”.		
Again, a two-step process:

1. Make the label using “p4 label –t xxx abc”

2. Populate it using

“p4 labelsync –l abc //…@xxx”

Note that the second step is really identical to the second step in the previous question – we’re

just specifying a very specific list of revisions [of files] to include in the new label.

(Also…

In 2005.1 and later, “p4 tag” will make the label and apply it to a set of files.)		












 







The post “Cheat Sheet” of Perforce command-line | Perforce command-line Guide appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/cheat-sheet-of-perforce-command-line/feed/
			0
		
		
			
		
		Windows XP/2000 Commands & Tools | Windows XP Command-line Reference
		https://www.scmgalaxy.com/tutorials/windows-xp-2000-commands-tools/
					https://www.scmgalaxy.com/tutorials/windows-xp-2000-commands-tools/#respond
		
		
		Sat, 20 Jun 2009 04:35:19 +0000
				
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2009/06/20/windows-xp-2000-commands-tools/

					Here’s the ultimate Windows XP/2000 command list that will make any Linux user feel at home at the command prompt. […]


The post Windows XP/2000 Commands & Tools | Windows XP Command-line Reference appeared first on scmGalaxy.

]]>
										windows-xp-2000-commands-tools


Here’s the ultimate Windows XP/2000 command list that will make any Linux user feel at home at the command prompt. A lot of these commands are intended for administrating a network, but they are great for savvy home users as well.  We even listed which OS you need for these commands.


Many thanks to the digg users who ‘dugg’ our site and care to leave comments of helpful commands that we have left out!


    

  • at (windows XP/2000)
    
    Scheduling utility. 
    • 

  • bootcfg (XP only)
    
This utility allows you to set up your boot options, such as your default OS and other loading options. 
    • 

  • cacls (XP, 2000, & NT4.0)
    
Changes the ACLs (security Settings) of files and folders. Very similar to chmod in Linux.  
    • 

  • comp (XP & 2000)
    
This utility is very similar to diff in Linux.  Use the /? switch to get examples of command usage. 
    • 

  • contig (works with NT4.0 and newer)
    
A great defrag utility for NTFS partitions. 
    • 

  • control (XP only) – unpublished!
    
Allows you to launch control panel applets from the command line.      control userpasswords2, for example will launch a helpful local user admin utility. 
    • 

  • defrag (XP only – NT4.0 and Win2k use contig)
    
Yes, XP comes with a command line disk defrag utility. If you are running Win2k or NT4.0 there is still hope. Contig is a free defrag program that I describe on the defrag page. 
    • 

  • diskpart (XP only)
    
Use this command to manage your disk partitions.  This is the text version for the GUI Disk Manager. 
    • 

  • driverquery (XP only)
    
Produces a list of drivers, their properties, and their versions. Great for computer documentation. 
    • 

  • eudcedit (XP only) – unpublished!
    
Private Character editor.  Yes with this program built into Windows XP you can create your own font! 
    • 

  • fsutil (XP only) – unpublished!
    
This is a utility with a lot of capability.  Come back soon for great examples. 
    • 

  • getmac (XP & 2000)
    
This command gets the Media Access Control (MAC) address of your network cards. 
    • 

  • gpresult (XP & 2000)
    
This generates a summary of the user settings and computer group policy settings. 
    • 

  • gpupdate (XP only)
    
Use this utility to manually apply computer and user policy from your windows 2000 (or newer) domain. 
    • 

  • ipconfig (XP, 2000 & NT4.0)
    
This handy tool displays IP settings of the current computer and much more. 
    • 

  • MMC (XP, 2000 & NT4.0) – Microsoft Management Console
    
This is the master tool for Windows, it is the main interface in which all other tools use starting primarily in Windows 2000 and newer systems. 
    • 

  • more
    
    Utility used to display text output one screen at a time. Ex. more c:\windows\win.ini 
    • 

  • msconfig (XP only)
    
The ultimate tool to change the services and utilities that start when your Windows machine boots up. You can also copy the executable from XP and use it in Win2k. 
    • 

  • msinfo32 (XP &smp; 2000)
    
An awesome diagnostic tool. With it you can get a list of running processes, including the residing path of the executable (great for manually removing malware) and get detailed information about hardware and system diagnostics. 
    • 

  • narrator (XP only)
    
Turns on the system narrator (can also be found in accessibility options in control panel).  Will will allow your computer to dictate text to you. 
    • 

  • netsh (XP & 2000)
    
A network configuration tool console.  At the ‘netsh>’ prompt, use the ‘?’ to list the available commands and type “exit” to get back to a command prompt. 
    • 

  • nslookup (all)
    
A DNS name resolution tool. 
    • 

  • openfiles (XP Only)
    
Allows an administrator to display or disconnect open files in XP professional. Type “openfiles /?” for a list of possible parameters. 
    • 

  • Pathping (XP & 2000)
    
A cross between the ping and traceroute utilities. Who needs Neotrace when you can use this? Type “pathping <ip address>” and watch it go. 
    • 

  • recover (XP & 2000)
    
This command can recover readable information from a damaged disk and is very easy to use. 
    • 

  • reg (XP & 2000)
    
A console registry tool, great for scripting Registry edits. 
    • 

  • sc (XP & 2000)
    
A command line utility called the Service Controller.  A power tool to make service changes via a logon/logoff or startup/shutdown script. 
    • 

  • schtasks (XP only)
    
A newer version of the AT command.  This allows an administrator to schedule and manage scheduled tasks on a local and remote machines. 
    • 

  • secedit (XP & 2000)
    
Use this utility to manually apply computer and user policy from your windows 2000 (or newer) domain.  Example to update the machine policy: secedit /refreshpolicy machine_policy /enforce
    
To view help on this, just type secedit.
    
NOTE: In Windows XP SP1 and news, this command is superceded by: gpupdate /force 
    • 

  • sfc (XP & 2000)
    
The system file checker scans important system files and replaces the ones you (or your applications) hacked beyond repair with the real, official Microsoft versions. 
    • 

  • shutdown (XP & 2000)
    
With this tool, You can shut down or restart your own computer, or an administrator can shut down or restart a remote computer. 
    • 

  • sigverif (XP only)
    
Microsoft has created driver signatures. A signed driver is Microsoft tested and approved. With the sigverif tool you can have all driver files analyzed to verify that they are digitally signed. Just type ‘sigverif’ at the command prompt. 
    • 

  • systeminfo (XP only)
    
Basic system configuration information, such as the system type, the processor type, time zone, virtual memory settings, system uptime, and much more.  This program is great for creating an inventory of computers on your network. 
    • 

  • sysedit (XP/2000)
    
System Configuration File Editor.  An old tool that was very handy for the Windows 9X days.  msconfig is what you want to use now. 
    • 

  • tasklist (XP pro only)
    
Tasklist is the command console equivalent to the task manager in windows. It is a must have when fighting scumware and viruses. Try the command:
    
tasklist /svc
    
to view the memory resources your services take up. 
    • 

  • taskkill (XP only)
    
Taskkill contains the rest of the task manager functionality.  It allows you to kill those unneeded or locked up applications. 
    • 

  • tree (XP & 2000)
    
An amazing experience everyone should try!  This command will provide a ‘family tree’ style display of the drive/folder you specify. 
    • 

  • WMIC (XP & 2000)
    
Windows Management Instrumentation Command tool.  This allows you to pull an amazing amount of low-level system information from a command line scripting interface. 
    • 



The post Windows XP/2000 Commands & Tools | Windows XP Command-line Reference appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/windows-xp-2000-commands-tools/feed/
			0
		
		
			
		
		Command line switches of devenv.exe | Devenv command line switches Guide
		https://www.scmgalaxy.com/tutorials/command-line-switches-of-devenvexe/
					https://www.scmgalaxy.com/tutorials/command-line-switches-of-devenvexe/#respond
		
		
		Sat, 20 Jun 2009 04:34:43 +0000
				
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2009/06/20/command-line-switches-of-devenvexe/

					To see this list, type devenv /? on command prompt /build – build the specified solution configuration   /project – […]


The post Command line switches of devenv.exe | Devenv command line switches Guide appeared first on scmGalaxy.

]]>
										devenvexe-command-line-switches


To see this list, type devenv /? on command prompt


    

  • 

      

    • /build – build the specified solution configuration
      • 

    

    • 



 


    

  • 

      

    • /project – specifies the project to build instead of solution, must specify /build to use /project
      • 

    

    • 



 


    

  • 

      

    • /projectconfig – specifies project configuration to build, must specify /project to use /projectconfig
      • 

    

    • 



 


    

  • 

      

    • /out – write build output to specified file
      • 

    

    • 



 


    

  • 

      

    • /rebuild – like /build, but forces a clean first
      • 

    

    • 



 


    

  • 

      

    • /clean – clean up build outputs
      • 

    

    • 



 


    

  • 

      

    • /deploy – build the specified solution configuration and then deploy it
      • 

    

    • 



 


    

  • 

      

    • /run – run the specified solution configuration
      • 

    

    • 



 


    

  • 

      

    • /runexit – run the specified solution configuration and then terminate
      • 

    

    • 



 


    

  • 

      

    • /command – executes the specified internal command line after startup
      • 

    

    • 



 


    

  • 

      

    • /mditabs – use tabbed documents interface
      • 

    

    • 



 


    

  • 

      

    • /mdi – use MDI interface
      • 

    

    • 



 


    

  • 

      

    • /fn – use specified font name
      • 

    

    • 



 


    

  • 

      

    • /fs – use specified font size
      • 

    

    • 



 


    

  • 

      

    • /LCID – use specified language ID
      • 

    

    • 



 


    

  • 

      

    • /noVSIP – disables VSIP developers license key for VSIP testing
      • 

    

    • 



 


    

  • 

      

    • /safemode – only default environment and services load for stability
      • 

    

    • 



 


    

  • /resetskippkgs – allow VSPackages once flagged for loading failures to load again
    • 



The post Command line switches of devenv.exe | Devenv command line switches Guide appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/command-line-switches-of-devenvexe/feed/
			0
		
		
			
		
		How to run Remote Desktop Console by using command line?
		https://www.scmgalaxy.com/tutorials/how-to-run-remote-desktop-console-using-command-line/
					https://www.scmgalaxy.com/tutorials/how-to-run-remote-desktop-console-using-command-line/#respond
		
		
		Sat, 20 Jun 2009 04:24:04 +0000
				
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2009/06/20/how-to-run-remote-desktop-console-using-command-line/

					How to run Remote Desktop Console using command line If you may want to run Desktop Console from a batch […]


The post How to run Remote Desktop Console by using command line? appeared first on scmGalaxy.

]]>
										






How to run Remote Desktop Console using command line




If you may want to run Desktop Console from a batch file, for example RDC over VPN, you can use mstsc /v:servername /console command.


Mstsc


Creates connections to terminal servers or other remote computers, edits an existing Remote Desktop Connection (.rdp) configuration file, and migrates legacy connection files that were created with Client Connection Manager to new .rdp connection files.


Syntax


mstsc.exe {ConnectionFile | /v:ServerName[:Port]} [/console] [/f] [/w:Width /h:Height]

mstsc.exe /edit”ConnectionFile”

mstsc.exe /migrate

Parameters


ConnectionFile


Specifies the name of an .rdp file for the connection.

/v:ServerName[:Port]

Specifies the remote computer and, optionally, the port number to which you want to connect.


/console

Connects to the console session of the specified Windows Server 2003 family operating system.


/f

Starts Remote Desktop connection in full-screen mode.


/w:Width /h:Height

Specifies the dimensions of the Remote Desktop screen.


/edit”ConnectionFile”

Opens the specified .rdp file for editing.


/migrate

Migrates legacy connection files that were created with Client Connection Manager to new .rdp connection files.


Remarks

* You must be an administrator on the server to which you are connecting to create a remote console connection.

* default.rdp is stored for each user as a hidden file in My Documents. User created .rdp files are stored by default in My Documents but can be moved anywhere.

Examples


To connect to the console session of a server, type:

mstsc /console


To open a file called filename.rdp for editing, type:

mstsc /edit filename.rdp







The post How to run Remote Desktop Console by using command line? appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/how-to-run-remote-desktop-console-using-command-line/feed/
			0
		
		
			
		
		Ant command line arguments – Examples – Summary
		https://www.scmgalaxy.com/tutorials/ant-command-line-arguments/
					https://www.scmgalaxy.com/tutorials/ant-command-line-arguments/#comments
		
		
		Sat, 20 Jun 2009 04:04:31 +0000
				
		
		
		
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2009/06/20/ant-command-line-arguments/

					Ant command line arguments Several tasks take arguments that will be passed to another process on the command line. To […]


The post Ant command line arguments – Examples – Summary appeared first on scmGalaxy.

]]>
										ant-command-line-arguments






Ant command line arguments




Several tasks take arguments that will be passed to another process on the command line. To make it easier to specify arguments that contain space characters, nested arg elements can be used.


value – a single command-line argument; can contain space characters.

file – The name of a file as a single command-line argument; will be replaced with the absolute filename of the file.

path – A string that will be treated as a path-like string as a single command-line argument; you can use ; or : as path separators and Ant will convert it to the platform’s local conventions.

pathref – Reference to a path defined elsewhere. Ant will convert it to the platform’s local conventions.

line – a space-delimited list of command-line arguments.


It is highly recommended to avoid the line version when possible. Ant will try to split the command line in a way similar to what a (Unix) shell would do, but may create something that is very different from what you expect under some circumstances.





Examples




<arg value=”-l -a”/>

is a single command-line argument containing a space character.

<arg line=”-l -a”/>

represents two separate command-line arguments.

<arg path=”/dir;/dir2:\dir3″/>

is a single command-line argument with the value \dir;\dir2;\dir3 on DOS-based systems and /dir:/dir2:/dir3 on Unix-like systems.		




Command-line Options Summary




ant [options] [target [target2 [target3] …]]


Options:






-help, -h
Displays help information describing the Ant command and its options




-projecthelp, -p
Print project help information




-version
Print the version information and exit




-diagnostics
Print information that might be helpful to diagnose or report problems.




-quiet, -q
Suppresses most messages not originated by an echo task in the buildfile




-verbose, -v
Displays detailed messages for every operation during a build.




-debug, -d
Print debugging information




-emacs, -e
Produce logging information without adornments




-lib <path>
Specifies a path to search for jars and classes




-logfile <file>
Use given file for log




-l <file>
Use given file for log




-logger <classname>
Specifies a class to handle Ant logging.




-listener <classname>
Add an instance of class as a project listener




-noinput
Do not allow interactive input




-buildfile <file>
Use given buildfile




-file <file>
Use given buildfile




-f <file>
Use given buildfile




-D<property>=<value>
Defines a property name-value pair on the command line.




-keep-going, -k
execute all targets that do not depend on failed target(s)




-propertyfile <name>
load all properties from file with -D properties taking precedence




-inputhandler <class>
the class which will handle input requests




-find <file>
Search for buildfile towards the root of the filesystem and use it

















The post Ant command line arguments – Examples – Summary appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/ant-command-line-arguments/feed/
			1
		
		
			
		
		Command Line to find a Change list properties in perforce server
		https://www.scmgalaxy.com/tutorials/command-line-to-find-a-change-list-properties-in-perforce-server/
					https://www.scmgalaxy.com/tutorials/command-line-to-find-a-change-list-properties-in-perforce-server/#respond
		
		
		Mon, 12 Jan 2009 12:04:18 +0000
				
		
		
		
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2009/01/12/command-line-to-find-a-change-list-properties-in-perforce-server/

					Command Line to find a Change list properties and associated path of the file in perforce server view: Examples of […]


The post Command Line to find a Change list properties in perforce server appeared first on scmGalaxy.

]]>
										command-line-to-find-a-change-list-properties-in-perforce-server


Command Line to find a Change list properties and associated path of the file in perforce server view:


Examples of the command you want:

p4 describe 1231928

p4 describe -s 1231928

p4 files @=1231928


Where 1231928 is the change list number.


The post Command Line to find a Change list properties in perforce server appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/command-line-to-find-a-change-list-properties-in-perforce-server/feed/
			0
		
		
			
		
		Batch Script to Login and sync the files from perforce | Step by step guide
		https://www.scmgalaxy.com/tutorials/batch-script-to-login-and-sync-the-files-from-perforce/
					https://www.scmgalaxy.com/tutorials/batch-script-to-login-and-sync-the-files-from-perforce/#respond
		
		
		Mon, 12 Jan 2009 11:43:29 +0000
				
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		http://www.scmgalaxy.com/tutorials/2009/01/12/batch-script-to-login-and-sync-the-files-from-perforce/

					Batch Script to Login Perforce server using command line Step 1: Create a new text file Step2: Copy following command […]


The post Batch Script to Login and sync the files from perforce | Step by step guide appeared first on scmGalaxy.

]]>
										batch-script-to-login-and-sync-the-files-from-perforce


Batch Script to Login Perforce server using command line


Step 1: Create a new text file

Step2: Copy following command

%path%

@echo on

p4 -p172.28.16.2:1666 -uUserName -P”Password” -c”Client_Name” client –o


Where

UserName is User name of perforce server

Password is Password of the perforce server.

Client_Name is the existing perforce client


Step3: Save with .bat extension


Step4: Run the batch file


Batch Script to Login and sync the files from perforce view


Step 1: Create a new text file

Step2: Copy following command

@echo off

p4 -c Client_Name -p 172.28.16.2:1666 -u UserName-P Password sync -f //SEABU/LiveStateDelivery/LSDMaintenance/Components/Webadmin/… //SYSTEMBUILDSTAR/LiveStateDelivery/LSDMaintenance/Components/Webadmin/…


Where

UserName is User name of perforce server

Password is Password of the perforce server.

Client_Name is the existing perforce client


Step3: Save with .bat extension


Step4: Run the batch file


The post Batch Script to Login and sync the files from perforce | Step by step guide appeared first on scmGalaxy.

]]>
					
					https://www.scmgalaxy.com/tutorials/batch-script-to-login-and-sync-the-files-from-perforce/feed/
			0