Can we automate Weblogic deployment process? - weblogic

I want to automate the deployment process of weblogic as everytime I have to first stop,delete,upload and start the war.

You can automate the deployment process using WLST where you need to execute jython script.
The script will be executed under WLST environment, which you may find at below location
<obiee_home>/u01/app/obiee/oracle_common/common/bin
You can refer good article for complete deployment process.

Related

Integrate Ranorex to Jenkins

I'd like to Integrate Ranorex to Jenkins and i have 2 staff i'd like to check
- First should only on the slave where the Ranorex automation should be triggered that Jenkins is not started as a service or on both master and slave
- Second i'm working with JenkinsFile pipline and i'd like execute Renorex test from this script (jenkinsfile) but i couldn't found any solution any ideas
Thanks a lot :P
I can help you with the first question you have:
The Jenkins service must be executed only on the machine where the automated tests are to be executed. You must also have Ranorex installed on that machine with a runtime license available. Jenkins can be configured to provide continuous integration, so each time you update the source code from Ranorex Jenkins will be able to automatically compile the solution and run the automated test.
Ranorex has an add-on that you can install in Jenkins to integrate the run configurations in order to be launched.

VeriFIX test automation in Jenkins

We are working with a client that uses VeriFIX to test their FIX message flow. Whilst they have built up lots of tests in many suites, it is a manual process to run them and to collate the results.
On the VeriFIX website it says
Incorporate tests into nightly builds using VeriFIX’s command-line script player.
but I cannot find any details on how to to it. Does anyone have any experience in running VeriFIX tests in a continuous integration server (ideally a Jenkins pipeline).
Many thanks.
You can run VeriFIX playlists in batch mode from the command line:
"%VERIFIX_HOME%\verifixbatch\verifixbatch.exe" -version "FIX (x.y)" -playlist "myplaylist" -disablelogging "false"
If you have received the user manual with your installation of veriFIX, the details of how to integrate with CI are in there.
To integrate veriFIX with Jenkins you will create batch files containing tests and run the batch files as jobs in Jenkins.
The placement of your veriFIX installation is important. If your veriFIX is on a users machine, as is often the case, separate from the environment machine Jenkins resides on, there can be difficulties getting the tests to run.
If you have a centralised install of veriFIX things are much easier.

Jenkins - Trigger Selenium test after deployment

I'm new to Jenkins, so please go easy!
I have a web application which we are developing, and we've started automating our release using Jenkins.
I also have a standalone Selenium WebDriver script which will perform a Smoke test on our web app. We usually run this manually each time there's a new deployment.
I heard Jenkins can automatically trigger Selenium tests. So what I did was to create a batch file, which will in turn call the Selenium script. I added a Build Step which will call this batch file.
What's happening now is Jenkins first Builds the WAR file, executes the batch (for selenium) and then deploys it to the target Tomcat.
But I was wondering if I could change the order to Build WAR --> Deploy to Tomcat --> Call the Batch file that executes Selenium Test. I want to do this as Jenkins Tests before deploying, which means my Selenium test still runs on the old build. This makes little sense, as I would rather run the Selenium test on the new build.
In short, is there a way I can execute the Batch file as part of a Post Build Step rather than a Build Step?
Thank you Würgspaß !!
I solved my problem by creating a separate Selenium Job which gets triggered automatically if my Build is successful. This way, I can create any number of downstream jobs to be triggered for a successful build.

Selenium - Jenkins - CI

I'm trying to integrate my selenium automation project with Jenkins using ANT build tool.
I've successfully configured a job and I'm able to BUILD too, but my scripts didn't launch the application and perform the test steps as expected. But still I could see the console output as 'BUILD SUCCESS'...!
When I tried to execute the ANT build through command prompt, it got executed appropriately by launching the application and performing required test steps. So expected the same to happen in Jenkins job as well, but it's not happening so.
Please help me in fixing this issue....!
Note: I have followed the steps given in the post below for integrating Jenkins & Selenium-
http://www.ontestautomation.com/running-selenium-webdriver-tests-in-jenkins-using-ant/
Make sure of two things
Configure Ant: Jenkins > Manage Jenkins > Configure System > Ant installations
Invoke Ant: Jenkins > Job > configure > Build > invoke ant targets
Followed the steps below to overcome the issue I logged/faced:
1) Upgraded the Chrome to latest version
2) Ensured 'Allow service to interact with deskop' is checked - refer to the post below for more information:
Jenkins windows slave service does not interact with desktop
3) Initiated the Jenkins through command prompt (Jenkins should be stopped in services.msc when we do this) in traditional way....

Triggering Jenkins after TFS build

I was wondering if it is possible for Jenkins to be notified after TFS finishes a build.
I'm trying to make a system where, after the TFS build, Jenkins is used to run automated selenium tests.
Thanks in advance!
You have a few options:
You could use a GenericTest to trigger Jenkins and include as part of the Build Definition. This also allows your script to communicate pass/fail information back to the build.
You could just include an InvokeProcess workflow activity to trigger Jenkins. The process would be similar to this or this.
Or you could use a tool that would trigger after a Team Build has finished. Normally people would use tools that then deploy stuff. Most of these tools trigger a Powershell script at some point, which would allow you to trigger the test run:
Octopus Deploy
TFS Deployer