I have a locust script with multiple steps as below..
#task(1)
step 1 - Setup step 1
step 2 - Setup step 2
step 3 - Setup step 3
step 4 - Do a post **self.client.get(...)**
step 5 - Do some additional setup
step 6 - Do a patch **self.client.patch(...)**
step 7 - Do some additional setup
step 8 - Do a get **self.client.get(...)**
When I run the above step using multiple users, steps 1 to 4 are run multiple times before continuing to the next steps. I would like each user to complete all the steps before restarting the task by another user. Please help
Related
Is there a way to run set of rundeck steps in a workflow in parallel?
Example:
==> means sequential
|| means parallel
Ex: Step 1 ==> Step 2.A || Step 2.B ==> Step 3
The feature of Ruleset Workflow Strategy is a plugin that is only available in the Rundeck Enterprise Version. Here you can find the official documentation
In the Rundeck community version, you can set the parallel strategy to run all steps at the same time.
I want to create a chain process. When a parent's job ends, a child (or multiple children) job starts. The main problem is that I want to have only the current job pods deployed.
Something like: job1 starts --> job 1 finish --> job 2 starts --> job 2 finish --> job 3 starts --> job 3 finish.
How can I do this? I thought that I could create in disabled mode job 1, job 2, and job 3 at the same time and enable them when the respective parent job ends (maybe with a service?).
I recently read about a tool called argo-workflow but I am not sure if it will do the chain effect that I am searching for.
Yes. CI/CD solution like Argo workflow is the way to go. You can check this example on how to execute different task one by one using steps here.
I am facing issue with preserving the outcome from my last test execution.
e.g.
I have a Test Plan 'Relase2.0' and the assigned configuration is 'Win 10'
Now I run this test plan and I could see how many have passed, failed, blocked, not run.
Now I go and create a new configuration and assign this Test plan to the newly added configuration.
Now I switch back to my previous configuration from step 1
When I check the outcome from the step 2 execution, I see that I have lost those and I see all those in Not Run status.
Question: How do I preserve the execution from step 2.?
Using Azure DevOps, I am creating a release pipeline in which I would like to have one stage having 1 job with 5 steps. First three steps are same task types but with different variables, and I would like to make them parallel so some flow would go like:
Job
parallel: step1, step2, step3
then: step4 (after all 3 parallel steps succeeded/failed)
then: step5 (after step4 is done)
This is the current job setup
I am not sure how to set up Control Options - run this task for all of these steps. I would need somehow to set the first three to run immediately (maybe Custom condition "always()") and step 4 and step 5 to run sequentially after previous steps are done.
Step 5 can be: Even if the previous task has failed unless the deployment was cancelled, but I am not sure if I set the same setting for step 4 will it consider only step 3 as previous or all three previous (step1 - step3) tasks.
Also for Execution plan Parallelism I guess it's ok to set multi-agent to three since I would have max 3 steps executing in parallel overall.
parallel: step1, step2, step3
If you have 5 task in one agent job, and just want to run previous three tasks parallel first, I'm afraid to say that this does not supported in Azure Devops.
While you put several tasks in one agent job, that's means the task will and must running in order. And also, as you mentioned in the second pic, the specified in Multi-agent is used for run agent job parallel, rather than run task parallel.
Fortunately, until now, there has been such suggestion raised by other user in our official Developer Community. And there are many users has the same demand with you. You can vote and comment there. Our Product Group team will take your suggestions kindly. If it has enough votes which means its high priority, and the team will consider it seriously.
I have a stage with two jobs (build and deploy) which is giving me a lot of trouble for the past 2 days.
Yesterday it started to fail about 1 every 4 times I run the stage. The stage is cancelled by itself. First I thought it might be a problem with my code but if I rerun the same execution it failed some of the times.
Today although, I haven't manage to complete a single run (I tried like 20 times in the last 3 hours). Some of the times the build job is cancelled, some others the deploy job.
Anybody facing the same problem? I cannot find where the issue is coming from...
Thanks!