I'm getting my feet wet with Jenkins and I've done something bad. Originally, I had a Bitbucket hook that triggered builds. When I had that in place, I could run builds on demand using the Build now link in the sidebar or in the view table. I decided to run job builds nightly instead and now I can't run them on demand. Clicking either Build now link just flashes a tooltip that says "Build scheduled".
I'm not sure what I did, but there are a couple of possibilities:
H H(2-10) * * *
.I've tried reversing both of these, but that hasn't worked. I've also bounced the jenkins
service (many, many times). I may have changed something else relevant, but I don't know what that might've been.
Has anyone else seen something like this?
To troubleshoot Jenkins pipeline failure issues On the Console Output page, check the logs to find the reason for the failure. If required, update the parameters in the deployment input configuration file. Learn about deployment input configuration file parameters at Setting up the deployment input configuration file.
Go to the project page and Click on the failed build number from the 'Build History'. Look for the details: File at which the ERROR has occured, ERROR details. Then Click Workspace on the left and go to the specified file location.
It allows you to configure build triggers and offers project-based security for your Jenkins project. It also offers plugins to help you build steps and post-build actions. The types of actions you can perform in a Jenkins build step or post-build action are quite limited.
This plugin analyzes the causes of failed builds and presents the causes on the build page. It does this by using a knowledge base of build failure causes that is built up from scratch. Saving statistics about failure causes is also possible.
I had the same symptoms, a different problem, and this tip in the comments was helpful:
...find something suspicious in
Jenkins->Manage Jenkins->System Log->All Jenkins Logs
For me it turned out the jobs in the Jobs folder had the wrong owner.
For me, it was that the EC2 instance I was running Jenkins on had run out of memory.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With