I want to add this trigger : "GitHub hook trigger for GITScm polling" to my pipeline. Do anybody know how can i do it ? I've tried to find in offical documentation but no success.
GitHub hook triggers are not yet supported by the Pipeline syntax.
The official documentation says:
For Pipelines which are integrated with a source such as GitHub or BitBucket, triggers may not be necessary as webhooks-based integration will likely already be present. The triggers currently available are cron, pollSCM and upstream.
So, enabling it through the job configuration page from the Jenkins UI is currently the way to go.
Related
I want to trigger a build before pull request starts for merging (in Azure DevOps). For this option, I have added the Build validation under branch policies. But if I created a new Pull Request, I am getting the message as "Unable to queue build".
Please anyone let me know the option I selected solves my requirement. If yes, how to solve this "Unable to queue build" issue. If no, any option available to achieve my requirement.
Thanks
Your options is achievable, and the problem now is most likely caused by you triggering the pipeline in the wrong repository.
For example, if you create a pipeline from repository 1 and trigger the pipeline in a pull request created from repository 2, the pipeline will not be queued.
Modify your pipeline or PR repository so that the pipeline and PR use the same repository, this should be resolved.
I had the same problem and i changed the branch policy to include the build pipeline:
https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies?view=azure-devops&tabs=browser
Branch policy could be found from:
Repos -> Branches
Click on the 3 dots to the right of the branch that the PR is going to.
I was also facing the same problem, checking pipeline for being disabled or edited anyhow, but no differences.
But by checking the linked work items (tasks/pbis), I saw that one or more had not been completed. After changing the states everything worked fine.
I have recently started using Gitlab and integrated with Jira. Both Gitlab and Jira server are self hosted internally in my corporate environment.
I have come across a requirement where I want to create a branch in Gitlab for a project/issue directly from the JIRA issue.
Is it possible to do it? If yes then how? Is there any plugin required for that?
I have gone through some documentation but I couldn't find anything similar so if anyone has any idea please let me know.
https://docs.gitlab.com/ee/user/project/integrations/jira.html
This is now supported, with GitLab 14.2 (August 2021), in certain condition (Jira Cloud):
Create a GitLab branch from a Jira issue
Users of the GitLab.com for Jira Cloud application can now create GitLab branches directly from a Jira issue’s development panel.
This enables developers to begin work on issues without having to switch tools and lose context.
See Documentation and Issue.
That's not possible using the embedded Gitlab-Jira integration.
In jira, I suppose you have a workflow with statuses and transition. You need to configure a post function on your transition to call Gitlab API from your jira using groovy script.
I've been using Azure Pipelines for a while now and haven't changed my azure-pipelines.yml file here in 2 months. Previously, when there was a new PR, the pipeline would trigger and cause the environment to be built and the tests would be run.
Today, there was a new PR but I noticed that the pipeline was not being triggered. Then, to further test this, I forked, cloned, and branched the repository myself and created another new PR and, again, the pipeline was not triggered.
It's not clear to me where things are getting stuck and it's not clear how one would debug this. I've gone through this Azure DevOps documentation but it wasn't useful. I can manually trigger the pipeline to execute and test the master branch but I don't know how to manually trigger the same thing for a PR. Here's my Azure DevOps page for reference.
As normal, you do not need config pr in YAML script if there's no any special demand, we would do pull request trigger for all branches. But, it start broken from 03-13 21:02 (UTC), which caused by us, you do not do anything wrong.
The fix is preparing with our best.
As Alex said, this is the implicit trigger which YAML support only, if you do not configure pr in YAML explicitly.
To avoid such stuck later, except the method that Alex mentioned: add pr into YAML. You can also make use of UI configuration which performance is very stable until now.
Just go Pipeline definition page => Click on three dots of right corner => Select Trigger:
Then you will see Triggers tab which has Continues integration and Pull request validation display below. Open Pull request validation and enable Override the YAML pull request trigger from here:
Additional, Our team has noticed this broken issue, will update whether it is fixed here once we have any fixed release in progress.
Update 3/18/2020:
Fixed has released to all region. Every one can work github pr trigger as the document shows now.
Working on porting a Jenkins plugin to Azure Dev Ops Pipelines plugin (as per https://learn.microsoft.com/en-us/azure/devops/extend/develop/add-build-task?view=azure-devopsv ) and I've seen in the docs info about how the logging commands can be used to add annotations to the GitHub checks on the PR that's being build. (https://learn.microsoft.com/en-us/azure/devops/pipelines/scripts/logging-commands)
This is great since I don't have to call GitHub APIs myself and create new GitHub App.
But in my tests it doesn't look like Azure Dev Ops Pipelines post the build log on the PR Check. Only annotations are posted. Can we also post the full log of a section that failed on GitHub PR?
If not as plan B, can we get the output of the failed build somehow so that I can manually use GItHub APIs and post it?
I want quickbuild to automatically run on each push detected on a github repository. How can I do that?
I already have a flow that clones and executes mvn deploy but I am missing an automatic trigger.
QuickBuild 5.1 adds the ability of detecting pull requests and trigger relevant builds off them. Refer to the GitHub integration guide for details:
http://wiki.pmease.com/display/QB51/Working+with+GitHub