I have some task schedulers and started from yesterday they stopped working. They worked before, they should run every 5 minutes, but from yesterday are not working anymore automatically. Manually the schedulers are working fine.
It's strange that the Next Run Time column is updated with the correct minute when they should run, but they are not running.
I recreated them, but the issue is not solved.
I've checked in the Services the Task Scheduler service, is running and it is set to Automatic
Can you please advise how to resolve this problem?
Related
I ran into an issue with Jenkins and I can't manage to figure it out. The problem is that, as the title suggest, a pipeline job hangs while a PowerShell is running.
The PowerShell script works with the Az.Monitor module to create alerts for Azure Resources. If I comment this script out, everything works well so I think it's safe to say that it is the problem.
Even so, when I run it in a powershell terminal, it works fine. Even stranger, if I run it in a normal Jenkins job (not a pipeline one), it works fine aswell. I even left the job running overnight.
I saw that someone suggested that maybe some hidden prompts appear while running on Jenkins, but I set the $ConfirmPreference variable to "None" and the issue still happens.
What could be the issue?
For me, the issue was the Durable-Task Jenkins plugin. I downgraded it from version 1.34 to 1.33 and it worked.
This plugin was problematic back in 2017-2018 too with the version 1.15.
I'm currently trying to integrate automatic test execution on the deployment process using Azure Devops but it's causing me an issue where some tests don't run properly.
The application I'm testing has a log-in page and I've set up a couple of tests to see if it opened properly. These ones run smoothly, but the ones that require going through the login process do not.
I've set up some snapshots amidst the process and the result was that I was getting an error on the last step of logging in. I've checked the application logs and the result I got was that no credentials were sent through the request which I found odd since they were displayed on the snapshots.
All the data being inserted was correct, I've checked the endpoints and settings on the agent that was running them and everything seemed fine.
I tried then to run the automated tests through powershell command directly on the same agent and all of them passed with no issue whatsoever.
I've tried changing my task to a powershell command but it still gives me an error.
I have no idea where my issue could be or where I should be even able to start looking for the problem, as clearly it seems that the problem is on the azure devops task but everything seems fine with it, I've tinkered around with the settings a bit but none of them seemed to have any impact on the results I was getting.
I'm using version 2 of the vstest task and am targetting the test assembly that was deployed to the agent. Any idea on what I could be missing or pointers on how to find the solution?
These ones run smoothly, but the ones that require going through the
login process do not
Based on this description, it seems that it will open a new window automatically by the task.
If I'm right, and your test will open a window to login with your private-hosted agent. At this time, the mode of your private-hosted agent must be in interactive which it can allow auto-logon enabled.
Just check this official document for more detail information.
I'm trying to incorporate a test suite that runs nightly on an Azure VM.
As of now, I have a Build process using TFS2015 that publishes my test files, starts the VM, and copies the files.
I'm trying to then use the "PowerShell on Target Machine" task to execute a script that launches a batch file. The reason it'll be executing a batch file is because I can't have the build process wait until that script is finished (it takes around 3 hours for the tasks in the batch file to complete).
My initial logic was to have the powershell script create a task using schtasks. This part works and the task itself is created on the virtual machine, however, it never runs at the scheduled time.
The other issue is that if I manually create these tasks, the task is executed, but everything is executed in the background. I need everything to be executed in the foreground.
I'm aware that this is by design since you should not be able to run foreground processes/applications remotely since it isn't "your session".
So the question will remain, are there any work arounds to this?
I'm trying to do launch selenium webservers and then execute protractor automation tests on the virtual machine. So one batch file starts the selenium server and the second launches protractor with a defined suite. If these are ran in the background (essentially headless) all my tests break.
Any insight would be helpful, or if I need to expand on my question or provide further details please let me know. Thanks.
I'm aware that this doesn't answer your specific question, but have you looked at moving your Selenium tests into VSTS? They're officially supported in the build/release pipelines and other people are taking this approach with protractor here and elsewhere. People are also making it work with TFS.
I am working on a project that uses Codeship to deploy builds. I got up today and saw:
Normally a build takes ~2 minutes, but I have waited on this one for half an hour. Codeship does not show anything being run. Not a single command. And my integration does not show the new application version, either.
How can I fix the hanging build?
Fixed! I just had to stop and restart the build as well as reset the dependency cache. Thanks #mlocher for the help.
If anyone came here from a search engine or something else with the same problem, try to restart the build, restart after resetting the dependency cache, or making another commit with a trivial / no change. This should fix the problem. Otherwise, send codeship a ticket at helpdesk.codeship.com.
We have a perfectly working Talend Workflow which has 4 sub-jobs. One of the jobs needed a change, so we modified it and re-built the job within Talend Open Studio. Copied the jar to our production machine. However, when the Task executed, it failed with a "No Class Def Found" error message.
So, is this not how its supposed to be done? Do we have to re-build and re-deploy the main task and all the sub-jobs even for a minor change in a sub-job? Any ideas?
TIA,
Bee
You need to rebuild and deploy the main job.
I don't know why, mays be have you increased the version of your subjob ?