Open simone201 opened 3 years ago
Hi @simone201, is the problem still there?
Hi @cdelmonte-zg, yes the problem is still there. The only way to circumvent it now is create a normal Job, enable the trigger on it with Git configured with the proper repository, and then make the Job trigger the Pipeline as its action. I don't think is the proper way to make it work though...
Could you test without the isToApprove
argument (which makes no sense for push):
properties([
pipelineTriggers([
bitBucketTrigger([
[
$class: 'BitBucketPPRRepositoryTriggerFilter',
actionFilter: [
$class: 'BitBucketPPRRepositoryPushActionFilter',
allowedBranches: '',
triggerAlsoIfNothingChanged: true,
triggerAlsoIfTagPush: false,
triggerOnlyIfTagPush: true
]
]
])
])
])
What is really strange (if the posted logs are complete) is that the last log is from BitBucketPPRJobProbe::triggerScm
line 105
and it never seems to reach the loop in line 113:
private void triggerScm(Job<?, ?> job, List<URIish> remotes, BitBucketPPRAction bitbucketAction,
BitBucketPPRObservable observable) {
logger.log(Level.FINE, "Considering to poke {0}", job.getFullDisplayName());
BitBucketPPRTrigger bitbucketTrigger = getBitBucketTrigger(job);
if (bitbucketTrigger != null) {
List<SCM> scmTriggered = new ArrayList<>();
Optional<SCMTriggerItem> item = Optional.ofNullable(SCMTriggerItem.SCMTriggerItems.asSCMTriggerItem(job));
item.ifPresent(i -> i.getSCMs().stream().forEach(scmTrigger -> {
logger.log(Level.FINE, "Considering to use trigger {0}", scmTrigger.toString());
// ...
@cdelmonte-zg we might need to correct docs if the error results from there.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I've created a new Jenkins Pipeline (really simple) with the Jenkinsfile taken from a repository on master branch. I've also declared in the pipeline the following trigger:
as per plugin documentation. I've tried enabling the webhooks in the same repository as the Jenkinsfile, also ran manually the pipeline a couple of times to let it enable the trigger (checked in its configuration) but on TAG PUSH is not triggering the pipeline at all, neither on any other kind of trigger.
Here's the log of the plugin taken from Jenkins:
Any idea why is not triggering the pipeline as expected?
Jenkins Version: 2.263.1 Plugin Version: 2.6.4