On a jenkins instance we have the jira trigger plugin and it does not trigger some builds. I could not find a way to recreate the issue, so I would say it randomly happens.
I've enabled the advanced logs as per the documentation (https://github.com/jenkinsci/jira-trigger-plugin#troubleshooting) , but, for the webhooks that are working and received I see the details with fields, change log and everything, while for the ones that do not work I see just the word: "Discarded", without any other details. Nobody is closing the builds or anything in Jenkins.
What could "discarded" mean?
Thank you!
Related
When some of my GithubActions jobs has failed, I don't have the possibility to re-run the specific failing job, only "Re-run all jobs". Is there any way to achieve this?
This is all working now in GitHub, the caveat is you can only run "specific jobs in a workflow run up to 30 days after its initial run."
https://docs.github.com/en/actions/managing-workflow-runs/re-running-workflows-and-jobs#reviewing-previous-workflow-runs
I’m the workflow file you want to be able to manually trigger, add workflow_dispatch to the “on:” clause. Then go to the actions tab on github, select the action and you should see the option to manually run it. Before asking this type of question, please use google next time. When looking for “triggger github workflow manually” the first result is a article written by github on how to do it. https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow
Unfortunately, re-run a single job is not possible yet.
Their repository does have an Open Issue to implement this feature.
https://github.com/actions/runner/issues/432
The good news is it is officially in their roadmap and is scheduled for Q1 2022.
https://github.com/github/roadmap/issues/271
Gitea recommends a separate Gitea Plugin for Jenkins. I'm puzzled why two identical builds are triggered when a PR is created.
I'm trying to achieve the following:
Without a PR, a push to a branch should NOT trigger a build
Every time a PR is requested in Gitea, a build is triggered for the PR.
If a new revision pushed to the branch for which a PR is created, another check build should be triggered
It's kinda working... But for some reasons two builds are created. Could someone please explain, what are these pipeline/head and pipeline/pr-master builds, and why there are two of them?
Here is the relevant part of my Jenkins configuration. I understand that this selection is a "legacy" one, however it's the only one that allows me to build only on PR. If I select the "recommended" one, then every push triggers a build, which is not what I want.
Thanks!
Answering my own question. Awwww what a silly sausage I am. The only thing that needed to be done was removing the "Discover branches" behaviour. And, naturally, it stops discovering "just branches" :) For some reasons I did not realise I can remove the default behaviours.
I need to get the results of my jenkins builds on my website. I already set up jenkins that when someone pushes on my repository the project will be build. Now I need the information if the build failed on my homepage, to enable/disable the download button. Theres the next question is it possible to get the latest build through jenkins?
I already found HTML Publisher Plugin but I dont think that this would solve my problem?
Best regards
John
The way this is traditionally done is with a build passing or failing icon, that lets users know that a build failed
https://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin
I have a strange use case here I know, but basically I have a CI / CD solution that starts be a developer creating a zip file of a set of resources. This zip is then sucked in to SVN via the tools internal programs.
Currently the solution works, using the FSTRigger to poll for an updated zip. When it see it, then the process kicks off and we're happy.
going forward I'd like the builds to be triggered by a Jira job reaching a certain status and have been looking at the Jira trigger plugin. It looks like it will help satisfy me with regards the triggering of the build and passing data from Jira to Jenkins to use for delivery notes etc. However it would still depend on the zip file being in a certain location to be picked up.
I'm wondering if it's possible to attach the zip to the Jira task and then as part of the task status hitting 'build' kick off the Jenkins job and copy the zip so it can be picked up by by the Jenkins build task.
for reasons to complex to mention, checking the zip into svn first won't really work.
When your Jenkins build is triggered via jira-trigger-plugin, you would be able to access JIRA_ISSUE_KEY environment variable that contains the JIRA issue which status has changed.
With the JIRA issue key, you can hit Get Issue JIRA REST API to retrieve the issue details. The issue details would contain the attachment information, which would then be able to be used for downloading the zip in Jenkins.
Curently, Jenkins JIRA is polluting the comments in JIRA page, especially with matrix builds.
We had an issue with a couple of user comments and many hudson comments.
Every build, it records the changes.
Any idea to get rid of this issue?
Per Jenkins wiki, user has an option to turn updates on and off in Post-build Actions settings.
To turn off, make sure that there's no check mark set at "Updated relevant JIRA issues"