Access to aws EC2 instance using password in linux

Here’s what I did on a Ubuntu EC2

A) Login as root using the keypairs

B) Setup the necessary users and their passwords with

# adduser
C) Edit /etc/ssh/sshd_config setting

PasswordAuthentication yes
D) Restart the sshd with

# sudo service sshd restart

Credit Illy
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Access to aws EC2 instance using password in linux appeared first on scmGalaxy.

Problem Area:
There is one clientSpec called “ClientSpec1” and two user has opened a file in same clientspec “user1” and “user2”. Now we want to delete “user2” without deleted workspace. Also we can
not impersonate user2 login e.g p4 -p PORT -u user2 -c ClientSpec1 -H host1 revert //…
and then revert the files as user access has been disabled.

Please suggest what should be done in this case to revert the files and delete the users.

Solution:
There are a few ways in which you could do this.

Firstly, an admin should be able to log in as another user – so ‘p4 -u admin login user2’ would create the ticket without needing the password for ‘user2’.
Once logged in, you should be able to impersonate this user and run ‘p4 revert -k’ for the files in question.
This is covered in the following KB article.
kb.perforce.com/article/38/reverting-another-users-files

Alternatively, another user could take ownership of the files. Here’s an example:

Users ‘rajesh’ and ‘kumar’ have each opened a file in workspace ‘temporary’.
>p4 opened -a //depot/test…
//depot/test.js#3 – edit default change (xtext) by rajesh@temporary
//depot/test2.js#2 – edit default change (text) by kumar@temporary

I use the ‘reopen’ command to change the user:
>p4 -u adam -c temporary reopen //depot/test…
//depot/test.js#3 – reopened; user adam
//depot/test2.js#2 – reopened; user adam

As these changes are now ‘mine’, I can revert them (noting the ‘-k’ flag here):
>p4 -u adam -c temporary revert -k //depot/test…
//depot/test.js#3 – was edit, cleared
//depot/test2.js#2 – was edit, cleared
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Revert the files of user access has been disabled appeared first on scmGalaxy.

if [ -n "$job_status" ] then     # Run your script commands here else   echo "BUILD FAILURE: Other build is unsuccessful or status could not be obtained."   exit 1 fi

The post Jenkins Remote access API Example | Jenkins Tutorial appeared first on scmGalaxy.

Step 1- Generate a public/private key using puttygen

• Download a puttygen from  and generate a public key and private key by following below image.
• Click on Conversions à Export OpenSSH Key à  and save it to % USERPROFILE %\.ssh with file name “id_rsa”
• Copy the public key from puttygen window and save into gitlab.

Step 2-  Add .ssh folder to your command line path
By following command..

     set HOME=%USERPROFILE%

or
add into user system variable.
HOME=%USERPROFILE%

And you are good to go. Comment if you face any issues?

The post Access gitlab Password Less in Windows appeared first on scmGalaxy.

You could access all Java system properties directly via ${name}, e.g.

${user.name}, ${user.dir}, ${user.home}, …

You could read environment properties and use them

  <properties environment=”env”/>

  ${env.ENVIRONMENT_VARIABLE}

e.g.

  ${env.USERPROFILE}, ${env.USERNAME}, ${env.PATH}

You could pass properties during Ants start

  ant -Dname=value -Danothername=anothervalue

Also you Ant could ask for input

  <input addproperty=”foo”/>

  ${foo}

The post How to access all Java system properties directly? appeared first on scmGalaxy.

The Subversion client can go through a proxy, if you configure it to do so.

First, edit your “servers” configuration file to indicate which proxy to use. The files location depends on your operating system.

On Linux or Unix it is located in the directory “~/.subversion”.

On Windows it is in “%APPDATA%\Subversion”. (Try “echo %APPDATA%”, note this is a hidden directory.)

The post How to Access SVN when client is under proxy ? appeared first on scmGalaxy.

Write a script to list the clients in descending access date order (for deleting obsolete clients).

#!/usr/bin/ruby
require “P4”
p4 = P4.new
p4.tagged
p4.connect
clients = p4.run_clients.sort {|a,b| a[ “Access”].to_i <=> b[“Access”].to_i }
clients[0…10].each do
|c|
stamp = Time.at( c[ “Access” ].to_i )
printf( “%-20s %s\n”, c[ “client” ], stamp )
end

OR

#!/usr/bin/perl
use P4;
my $p4 = new P4;
$p4->Tag();
$p4->Init() or die( “Failed to connect to Perforce” );
my @clients = $p4->Clients();
@clients = sort { $a->{ “Access” } <=> $b->{ “Access” } } @clients;
@clients = @clients[ 0..9 ];
foreach my $client ( @clients )
{
last unless defined( $client );
my $stamp = localtime( $client->{ “Access” } );
printf( “%-20s %s\n”, $client->{ “client” }, $stamp );
}

The post Script to list the clients in descending access date order appeared first on scmGalaxy.