[JIRA] (JENKINS-54010) Support two levels of parallelity in stages
Title: Message Title Alaiksei Savanchuk commented on JENKINS-54010 Re: Support two levels of parallelity in stages Shahaf Duenyas I'm not sure that you are talking about the BlueOcean plugin. Jenkins pipeline already supports multiple levels of parallelism, this is only about Blue Ocean's UI Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55927) Jenkins multibranch pipeline scan is triggered in case of remote pull request merge
Title: Message Title Alaiksei Savanchuk commented on JENKINS-55927 Re: Jenkins multibranch pipeline scan is triggered in case of remote pull request merge Antonio Muñiz Stephen Connolly can you, please, take a look at Joseph Petersen's comment? Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55927) Jenkins multibranch pipeline scan is triggered in case of remote pull request merge
Title: Message Title Alaiksei Savanchuk commented on JENKINS-55927 Re: Jenkins multibranch pipeline scan is triggered in case of remote pull request merge Joseph Petersen, can you, please, take a look at the issue one more time. Should I provide some other additional details? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55927) Jenkins multibranch pipeline scan is triggered in case of remote pull request merge
Title: Message Title
Alaiksei Savanchuk updated an issue
Jenkins / JENKINS-55927
Jenkins multibranch pipeline scan is triggered in case of remote pull request merge
Change By:
Alaiksei Savanchuk
There is such logic in the bitbucket-branch-source plugin: {{if (push.getChanges().isEmpty()) {}} {{ LOGGER.log(Level.INFO, "Received hook from Bitbucket. Processing push event on \{0}/\{1}",}} {{ newObject[]\{owner, repository});}} {{ scmSourceReIndex(owner, repository);}} } And this works in case of * remote pull request merges. * (https://community.atlassian.com/t5/Questions/Pull-requests-Squashed-commits-Remote-Merges/qaq-p/171569) This leads to reindexing of a multibranch pipeline project which can take a lot of time. In my case I have a lot of pull requests(around 150) and build for one of them takes around an hour. These pull requests mostly targeted to the same branch. Because of this we rescan our Bitbucket multibranch pipeline only twice a week because it takes a lot of time to rebuild all of these PRs because the target branch has new changes. And if some pull request is merged remotly remotely this leads to the reindexing which is unexpected. This locks me if this happens in the middle of the day.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google G
[JIRA] (JENKINS-55927) Jenkins multibranch pipeline scan is triggered in case of remote pull request merge
Title: Message Title
Alaiksei Savanchuk updated an issue
Jenkins / JENKINS-55927
Jenkins multibranch pipeline scan is triggered in case of remote pull request merge
Change By:
Alaiksei Savanchuk
There is such logic in the bitbucket-branch-source plugin: {{if (push.getChanges().isEmpty()) {}} {{ LOGGER.log(Level.INFO, "Received hook from Bitbucket. Processing push event on \{0}/\{1}",}} {{ newObject[]\{owner, repository});}} {{ scmSourceReIndex(owner, repository);}} } And this works in case of remote pull request merges. This leads to reindexing of a multibranch pipeline project which can take a lot of time. In my case I have a lot of pull requests(around 150) and build for one of them takes around an hour. These pull requests mostly targeted to the same branch. Because of this we rescan our repository Bitbucket multibranch pipeline only twice a week because it takes a lot of time to rebuild all of these PRs because the target branch has new changes. And if some pull request is merged remotly this leads to the reindexing which is unexpected. This locks me if this happens in the middle of the day.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email
[JIRA] (JENKINS-55927) Jenkins multibranch pipeline scan is triggered in case of remote pull request merge
Title: Message Title
Alaiksei Savanchuk updated an issue
Jenkins / JENKINS-55927
Jenkins multibranch pipeline scan is triggered in case of remote pull request merge
Change By:
Alaiksei Savanchuk
There is such logic in the bitbucket-branch-source plugin: {{if (push.getChanges().isEmpty()) {}}{{ LOGGER.log(Level.INFO, "Received hook from Bitbucket. Processing push event on \{0}/\{1}",}}{{ newObject[]\{owner, repository});}}{{ scmSourceReIndex(owner, repository);}}} And this works in case of remote pull request merges. This leads to reindexing of a multibranch pipeline project which can take a lot of time. In my case I have a lot of pull requests(around 150) and build for one of them takes around an hour. These pull requests mostly targeted to the same branch. Because of this we rescan our repository only twice a week because it takes a lot of time to rebuild all of these PRs because the target branch has new changes. And if some pull request is merged remotly this leads to the reindexing which is unexpected. This locks me if this happens in the middle of the day.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegr
[JIRA] (JENKINS-55927) Jenkins multibranch pipeline scan is triggered in case of remote pull request merge
Title: Message Title Alaiksei Savanchuk updated an issue Jenkins / JENKINS-55927 Jenkins multibranch pipeline scan is triggered in case of remote pull request merge Change By: Alaiksei Savanchuk Summary: Jenkins multibranch pipeline scan is triggered in case of remote pull request merge Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55927) Jenkins scan is triggered in case of remote pull request merge
Title: Message Title
Alaiksei Savanchuk created an issue
Jenkins / JENKINS-55927
Jenkins scan is triggered in case of remote pull request merge
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Screen Shot 2019-02-03 at 12.21.30 AM.png
Components:
bitbucket-branch-source-plugin
Created:
2019-02-02 21:25
Priority:
Major
Reporter:
Alaiksei Savanchuk
There is such logic in the bitbucket-branch-source plugin: if (push.getChanges().isEmpty()) { LOGGER.log(Level.INFO, "Received hook from Bitbucket. Processing push event on {0}/{1}", newObject[]{owner, repository}); scmSourceReIndex(owner, repository); } And this works in case of remote pull request merges. This leads to reindexing of a multibranch pipeline project which can take a lot of time.
Add Comment
[JIRA] (JENKINS-52324) Add Jenkins test results to BitBucket status messages for builds
Title: Message Title Alaiksei Savanchuk closed an issue as Won't Fix Jenkins / JENKINS-52324 Add Jenkins test results to BitBucket status messages for builds Change By: Alaiksei Savanchuk Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54201) Allow the tigger to work without any "node" wrappers
Title: Message Title Alaiksei Savanchuk updated an issue Jenkins / JENKINS-54201 Allow the tigger to work without any "node" wrappers Change By: Alaiksei Savanchuk Hi.Now, the trigger triggerRemoteJob step in pipelines requires to be executed in some "node" block. It would be better to remove this dependency, like the reggular regular build job step. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54201) Allow the tigger to work without any "node" wrappers
Title: Message Title Alaiksei Savanchuk created an issue Jenkins / JENKINS-54201 Allow the tigger to work without any "node" wrappers Issue Type: Improvement Assignee: KaiHsiang Chang Attachments: Console [Jenkins].png Components: parameterized-remote-trigger-plugin Created: 2018-10-23 08:13 Priority: Minor Reporter: Alaiksei Savanchuk Hi. Now, the trigger triggerRemoteJob step in pipelines requires to be executed in some "node" block. It would be better to remove this dependency, like the reggular build job step. Add Comment
[JIRA] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Alaiksei Savanchuk updated an issue Jenkins / JENKINS-28877 Bitbucket Plugin unable to parse Bitbucket webhook response json Change By: Alaiksei Savanchuk Comment: The same problem net.sf.json.JSONException: JSONObject["user"] not found. Jenkins ver. 2.60.3Bitbucket Plugin 1.1.8 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Alaiksei Savanchuk commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json The same problem net.sf.json.JSONException: JSONObject["user"] not found. Jenkins ver. 2.60.3 Bitbucket Plugin 1.1.8 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
