How QA2 copies haldata

From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Tuesday, April 24, 2012 10:20 AM
To: Bojja, Sridhar (HAL Contractor); Thompson, Sonya (HAL); Phatak, Sheetal (HAL)
Cc: Ruckman, Maurice (HAL); Fillman, Eric (HAL)
Subject: qa2

I created a new /wbi/haldata/webqa2 folder. The Apache document root for qa2 is now /wbi/haldata/webqa2/halwebsite (it was /wbi/haldata/webtst/halwebsite before). I also added a line in the Hudson job that deploys to qa2 so that it copies ${WORKSPACE}/halwebsite onto /wbi/haldata/webqa2/halwebsite at the end of the job.

Install new version of Eclipse

Still a work in progress but here are the results so far:

The Maven project with our base JBoss install has lots-o-errors, and seems to run slowly.  I’ve installed the newest version of Eclipse.  It still shows many JSP errors but some of them are worth fixing and it seems like it cannot find tag library through our proxy perhaps.  It also seems to run a bit snappier and it does not have that JSF problem that occurs when viewing JSP pages.

Still probably will need to install a few more times, here’s what’s been tried so far.

Eclipse Version
eclipse-jee-indigo-SR2-linux-gtk-x86_64.tar.gz

For Maven Integration with Eclipse
http://download.eclipse.org/technology/m2e/releases/

Subclipse
http://subclipse.tigris.org/update_1.6.x (works)
http://subclipse.tigris.org/update_1.8.x (failed)

From: Fillman, Eric (HAL)
Sent: Sunday, June 16, 2013 9:27 PM
To: Klein, Brian (HAL)
Cc: Ruckman, Maurice (HAL)
Subject: I think I got Eclipse working on the Linux VM

Can you try this on your machine and see if it fixes the problem?

On your Linux VM, go in to where your main eclipse directory is located.

On my VM, it’s in /home/jboss1/programs/eclipse.

Within this directory, there should be a file called eclipse.ini.  It contains a bunch of arguments and parameters that get passed to Eclipse when it starts.

Make a copy of eclipse.ini, and call it eclipse.ini.bak or something like that.

Open eclipse.ini in text editor, and add the following to the bottom of the list of arguments.

-Dorg.eclipse.swt.browser.XULRunnerPath=/home/jboss1/programs/jbdevstudio/studio/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.1.2a/xulrunner

-Dorg.eclipse.swt.browser.UseWebKitGTK=false

What this does is tells Eclipse to use XULRunner that is part of the JBoss Dev Studio rather than the XULRunner that was patched on Wednesday.  Eclipse needs to run with XULRunner 1.9.2 or earlier.  The patch on Wednesday upgraded the version used by Firefox to version 17 or something like that, and that’s what Eclipse is trying to use.  It don’t work.

JBoss Dev Studio works because it’s using that 1.9.1.2a version of XULRunner.

Save the changes to eclipse.ini, and try to start Eclipse.

Let me know how it goes.

Thanks.

Eric

 

Copying static content to VM’s

First you need to copy static content from here:
cp -R /wbi/haldata/webdev/* /home/jboss1/HAL/

And then supplement it from your workspace:

On developer VM, to copy static content from the checked out halwebsite folder to the apache document root and compile at the same time, you can run the following command from the root of your checked out project:

cp -R halwebsite/* /home/jboss1/HAL/halwebsite/ && mvn install

The && shell operator is a logic AND, it means that the 'mvn install' command only runs if the left part of the commands succeeds.

Deploy static content and deploy in JBoss (using hot deploy):

mvn install && cp hal-ear/target/hal-*.ear /home/jboss1/programs/jboss-eap-5.1/jbossas/server/haldev-vm-template/deploy/ && cp -R halwebsite/* /home/jboss1/HAL/halwebsite/

Adding subversion to LDAP

-----Original Message-----
From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Friday, April 27, 2012 12:13 PM
To: Tripp, Donald (HAL)
Cc: Hofsetz, Therron (HAL); Thompson, Sonya (HAL); Fillman, Eric (HAL); Doan, Thomas (HAL Contractor); Phatak, Sheetal (HAL); Bojja, Sridhar (HAL Contractor); Augustine, Anila (HAL); Ruckman, Maurice (HAL); HAL DistList: IS UNIX
Subject: Re: Noticen of Intent: Restart halsvn01

Thanks for taking care of that Don. Also, on the long term it might be a good idea to have the subversion server use LDAP for authentication so that new accounts get automatically created.

The subversion server relies on Apache for authentication (developers access subversion through http:// protocol). So the steps to do so would be the following:

1) Edit the file /etc/httpd/conf.d/svn.conf and replace "AuthUserFile /etc/httpd/conf/.htaccess" with equivalent LDAP authentication section

2) In the /etc/httpd/conf/svn_acl, replace the name of user with their equivalent LDAP login

That should be it...

Guillaume

Merging from a revision

Example that wants just what was done in revision 2723 in trunk:

svn merge -c [good_revision] [repository_url]
svn merge -c 2723 http://halsvn01/svn/hal/trunk

This will rollback revision 2723 in trunk, pay attention to the negative sign in front of the revision number:

svn merge -c -[bad_revision] [repository_url]
svn merge -c -2723 http://halsvn01/svn/hal/trunk

Older methods as show by Guillaume below, the one above are now supported and recommended by me.

svn merge ~/branches/features/your-feature-t0-merge-no-ending-slash -r 995:999

Where 995 represent the first revision and 999 represents the last revision to merge

$ svn merge -c 614 https://secreturl/trunk or $ svn merge -r 613:614 https://secreturl/trunk.

The first means apply changes in revision 614 only, while the second form means take all changes required to go from r613 to r614 and apply them here.

Looking at Linux history

Hit [Ctrl]+[R] and then start type and it will find history that matches that string

Hit [Ctrl]+[R] again to cycle through your subset to find an entry

Subversion Maintenance – Adding Users

1. SSH to the subversion server
Putty to halsvn01.hq.halw.com

sudo to root:
The Unix team added sudoers file for mlr, ezf, and sst to be able to do the following, additional users would needed added by Unix team:

sudo /usr/bin/htpasswd -m /etc/httpd/conf/.htaccess
sudo /bin/vi /etc/httpd/conf/svn_acl
sudo /usr/bin/vim /etc/httpd/conf/svn_acl

originally Guillaume used:
sudo su -

2. Edit the configuration files

The following will allow you to enter the user's password:

cd /etc/httpd/conf
ls -la
htpasswd -m /etc/httpd/conf/.htaccess user-account

The following will allow defines access control in subversion:
vim svn_acl

vim command
[Esc] [:] [q] to quit without saving
[Esc] [:] "wq" to write (save) and quit

[i] - Insert

You will change users in groups which propagate down through the rest of the script, here's the start of the script:

[groups]

## For HAL
#developers
dev = aja, szb, ezf, sst, mlr, sxp, kxs, wgh, mad, mwm, c-rgong, c-rsmith, jeff, c-rradhakrishnan, jay, guillaume, c-mhartman, c-fcastro, c-dgreca, @rm, @rev, @qa

Searching for files

Use the attached Perl script in conjunction with the following example bash command:

for i in `perl findfiles.pl /home/jboss1/workspace_maven/hal-parent/hal-web/ .jsp`; do grep -il 'look for something'  $i; done

findfiles.pl (txt)