I need assistance on OpenTest for below scenario:
My code is in Aws-Code-Commit repository and my Jenkins is installed in one of the ec2 instance. Now I want to run all my OpenTest test-cases in a Jenkins job and publish the results. I have seen the Jenkins integration tutorial but still getting stuck in Opentest integration with remote Linux Jenkins instance.
I have no clue on how to start the server and actor in my Linux Jenkins instance and how can I execute my test-cases.
Can you help me out here?
You'll likely want to trigger a bash script file which will then execute the node and opentest commands to run your tests. If this answer seems obvious but you still have questions, can you clarify how far along in the process you are stuck?
Related
Every nice developer!
I use a Drone as my team CI/CD tool.
And my server is running two Drone container, one for Gogs , the other one for Github.
I need to finish my Pipelines in exec runner mode now. But I wonder how can I connect two Git servers? Just be Gogs and Github.
This is exec runner installation tutorial. And the config file can only fill one DRONE_RPC_HOST. But I have two hosts.
DRONE_RPC_PROTO=https
DRONE_RPC_HOST=drone.company.com
DRONE_RPC_SECRET=super-duper-secret
How can I solve my problem? I am glad to get your answer.
Thank you for your read.
I am working on a project. I need to create a workflow to run integration tests on an iOS device.
Scenario:
I've to run a local server at some port and in parallel I've run integration tests.
Query:
Can I achieve this in Github Actions?
If yes then how?
I'll be thankful for the help.
There's no built in solution for parallel steps at the moment.
Workaround:
Run your server in the background (server &). Or as a daemon if it has it built in.
If you would like to have this feature you can try voting on this feedback thing: https://github.com/github-community/community/discussions/14484
I have a bunch of marathon docker tasks that are run on our test deployment machines.
There is a Jenkins CI job, that triggers the deployment a whole bunch of docker containers that are run on marathon-mesos cluster. (3 mesos-slaves, 1 master and 1 marathon.)
There is another downstream jenkins job (a automated test suite) that is triggered after above job. Presently, we wait for sufficient time, so that deployment gets completed then only we proceed with this automation testsuite. I want to change this behavior. I know marathon exposes rest APIs using which I can determine if I am good to go - after all the containers are deployed and all health checks are passing - for running the automation test suite.
Question is: Is there any library already out there for marathon, that I can reuse to accomplish above task ? I do not want to reinvent the wheel.
When I posted this question, I had java library actually in mind, but forgot to mention that. I find #michael 's libraries are also very good. But this is what I settled upon. Marathon-client. I think I saw this, while browsing through mesosphere repositories but somehow missed it.
This is the library: marathon-client
I've successfully been using the two following libs:
Go: gambol99/go-marathon
Python: thefactory/marathon-python
I have a project that need to works on windows\linux with those databases : oracle\sqlserver.
Our project is built by Maven.
I have installed Jenkins with master\slave set-up.
master: windows + sqlserver
slave : linux + oracle
for our testing.
Jenkins - Promoting a build to different environments
but its really not helping that much for me.
I have also read Jenkins wiki : https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds
but i still cannot figure out how should i do it.
Since compiling our code takes a lot of time i would like to do it just once than use the final result and test it on those environments master and slave.
build succes only if he runs on both environments.
I have also noticed that i cannot invoke on "post steps" at jenkins to do it. i didn't find any plugin that can really help with deploying and testing on the slave.
I have read somewhere that maybe i should split it to 3 jobs and not to use one job.
first job compiles, and then other jobs are running integration test.
you can look at : http://zeroturnaround.com/rebellabs/the-correct-way-to-use-integration-tests-in-your-build-process/
I hope you could advise to me how should i do it.
Thanks
I would split the build up as follows:
Job 1 compiles the code, runs unit tests and builds your deployable artifact (since you're using Maven, I assume you have a JAR or WAR file)
Job 2 deploys and runs the artifact - you could use build parameters to specify environment-specific criteria.
Job 3 runs the integration test and reports results.
I have a job configured to automatically deploy an application to a running server. I would like to know if Jenkins provides a way to verify if this application was deployed successfully. Ideally, the build should fail when the deployment fails.
Jenkins has a rundeck plugin which might perhaps be useful.
Rundeck deploys the application, and can be setup to trigger a post-deployment build on Jenkins to perform tasks like running integration tests.
Jenkins could be used to report the status of the deployment, however it might make more sense to use rundeck's dashboard instead.