[JIRA] (JENKINS-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Benjamin Fuchs commented on JENKINS-31202 Re: Trend Graphs are not shown in Job view for Workflow builds Hi, I'm very interested in resolving this issue. I tried to get as far as I can and I got a trend graph showing up in my workflow:I pushed my changes here: https://github.com/benjaminfuchs/analysis-core-plugin/tree/JENKINS-31202 ...and also had to change the warnings-plugin: https://github.com/benjaminfuchs/warnings-plugin/tree/JENKINS-31202 I got my changes running with: $ mvn hpi:run Right now the trend graph is also shown twice for non-workflow projects, I hope someone has a easy fix for that. I would appreciate some feedback and as I really would like to help resolving this issue! Greetings! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Benjamin Fuchs updated an issue Jenkins / JENKINS-31202 Trend Graphs are not shown in Job view for Workflow builds Change By: Benjamin Fuchs Attachment: trendgraph.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-31202 Re: Trend Graphs are not shown in Job view for Workflow builds Hi, I'm very interested in resolving this issue.I tried to get as far as I can and I got a trend graph showing up in my workflow: !trendgraph.png|thumbnail! I pushed my changes here: https://github.com/benjaminfuchs/analysis-core-plugin/tree/JENKINS-31202...and also had to change the warnings-plugin: https://github.com/benjaminfuchs/warnings-plugin/tree/JENKINS-31202I got my changes running with: $ mvn hpi:run Right now the trend graph is also shown twice for non-workflow projects, I hope someone has a easy fix for that. I would appreciate some feedback and as I really would like to help resolving this issue!Greetings! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Benjamin Fuchs commented on JENKINS-31202 Re: Trend Graphs are not shown in Job view for Workflow builds I created an PR: https://github.com/jenkinsci/analysis-core-plugin/pull/36 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-31202 Re: Trend Graphs are not shown in Job view for Workflow builds I created an a PR: https://github.com/jenkinsci/analysis-core-plugin/pull/36 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Benjamin Fuchs commented on JENKINS-31202 Re: Trend Graphs are not shown in Job view for Workflow builds Hi, some updates: The changes I committed work fine on my instance. I created a PR for the changes on the warnings-plugin depending on this issue: https://github.com/jenkinsci/warnings-plugin/pull/80 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Benjamin Fuchs commented on JENKINS-31202 Re: Trend Graphs are not shown in Job view for Workflow builds Any updates? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-50582) Limit amount of requests sent to BitBucket API
Title: Message Title Benjamin Fuchs commented on JENKINS-50582 Re: Limit amount of requests sent to BitBucket API We are having the same issue, but with the BitbucketServerAPIClient.java We also would like to have an option to specify the maximum number of branches to consider, since it takes a long time to scan all open branches in our case (also 5+ minutes). 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-50582) Limit amount of requests sent to BitBucket API
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-50582 Re: Limit amount of requests sent to BitBucket API We are having the same issue, but with the BitbucketServerAPIClient.javaWe also would like to have an option to specify the maximum number of branches to consider, since it takes a long time to scan all open branches in our case (also 5+ minutes). Currently I would start using this workaround: https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/79e63c5d360a61cd653543730bd5b7f72422a0ac 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-50582) Limit amount of requests sent to BitBucket API
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-50582 Re: Limit amount of requests sent to BitBucket API We are having the same issue, but with the BitbucketServerAPIClient.javaWe also would like to have an option to specify the maximum number of branches to consider, since it takes a long time to scan all open branches in our case (also 5+ minutes).Currently I would start using this workaround: https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/79e63c5d360a61cd653543730bd5b7f72422a0ac 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-50582) Limit amount of requests sent to BitBucket API
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-50582 Re: Limit amount of requests sent to BitBucket API We are having the same issue, but with the BitbucketServerAPIClient.javaWe also would like to have an option to specify the maximum number of branches to consider, since it takes a long time to scan all branches in our case (also 5+ minutes).Currently I would start using this workaround: https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/ 79e63c5d360a61cd653543730bd5b7f72422a0ac fa41e9ba0af15e8c703e164cb5b9976e2a67e267 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-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress We are also having a problem with this issue.1. There is a "branch" build of the "branch" job running2. While its running a pull request is opened for that branch.3. Multibranch scanning gets triggered.4. The PR gets a "PR" project and a "PR" build starts running.(5. I guess the Multibranch scanning has to be triggered again.)6. Now the "branch" project gets disabled while the "branch" job is still running.The "branch" build will now never update its status to Bitbucket.This is a major issue, since the developer cannot merge its PR due to a running job.I found out that this line is the problem when updating the status at the end of the job:https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/3412b4eb5b35b9ade7a4e6cfafcdbf3375789fcb/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L101s is of type NullSCMSource and I guess it is due to the branch being removed from "sources" in:https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/MultiBranchProject.javaI create a workaround for us since this was a blocker:https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/26b9f6ace3745cdd58ae1d43eb05d7eb3108f8f8 What already would help is to update the description in the job config pointing to this issue so it is clear to a new user choosing this option that he will face this race condition. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message
[JIRA] (JENKINS-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress We are also having a problem with this issue.1. There is a "branch" build of the "branch" job running2. While its running a pull request is opened for that branch.3. Multibranch scanning gets triggered.4. The PR gets a "PR" project and a "PR" build starts running.(5. I guess the Multibranch scanning has to be triggered again.)6. Now the "branch" project gets disabled while the "branch" job is still running.The "branch" build will now never update its status to Bitbucket.This is a major issue, since the developer cannot merge its PR due to a running job.I found out that this line is the problem when updating the status at the end of the job:https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/3412b4eb5b35b9ade7a4e6cfafcdbf3375789fcb/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L101s is of type NullSCMSource and I guess it is due to the branch being removed from "sources" in:https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/MultiBranchProject.javaI create a workaround for us since this was a blocker:https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/ commit tree / 26b9f6ace3745cdd58ae1d43eb05d7eb3108f8f8 JENKINS-45643 If there will be now "quickfix" I guess at least the description in the job config should be updated to pointing to this issue so it is clear to a new user choosing this option that he will face this race condition. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Benjamin Fuchs commented on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress We are also having a problem with this issue. 1. There is a "branch" build of the "branch" job running 2. While its running a pull request is opened for that branch. 3. Multibranch scanning gets triggered. 4. The PR gets a "PR" project and a "PR" build starts running. (5. I guess the Multibranch scanning has to be triggered again.) 6. Now the "branch" project gets disabled while the "branch" job is still running. The "branch" build will now never update its status to Bitbucket. This is a major issue, since the developer cannot merge its PR due to a running job. I found out that this line is the problem when updating the status at the end of the job: https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/3412b4eb5b35b9ade7a4e6cfafcdbf3375789fcb/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L101 s is of type NullSCMSource and I guess it is due to the branch being removed from "sources" in: https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/MultiBranchProject.java I create a workaround for us since this was a blocker: https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/26b9f6ace3745cdd58ae1d43eb05d7eb3108f8f8 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
[JIRA] (JENKINS-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress We are also having a problem with this issue.1. There is a "branch" build of the "branch" job running2. While its running a pull request is opened for that branch.3. Multibranch scanning gets triggered.4. The PR gets a "PR" project and a "PR" build starts running.(5. I guess the Multibranch scanning has to be triggered again.)6. Now the "branch" project gets disabled while the "branch" job is still running.The "branch" build will now never update its status to Bitbucket.This is a major issue, since the developer cannot merge its PR due to a running job.I found out that this line is the problem when updating the status at the end of the job:https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/3412b4eb5b35b9ade7a4e6cfafcdbf3375789fcb/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L101s is of type NullSCMSource and I guess it is due to the branch being removed from "sources" in:https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/MultiBranchProject.javaI create a workaround for us since this was a blocker:https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/26b9f6ace3745cdd58ae1d43eb05d7eb3108f8f8 What already would help is to update If ther will be now "quickfix" I guess at least the description in the job config should be updated to pointing to this issue so it is clear to a new user choosing this option that he will face this race condition. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress We are also having a problem with this issue.1. There is a "branch" build of the "branch" job running2. While its running a pull request is opened for that branch.3. Multibranch scanning gets triggered.4. The PR gets a "PR" project and a "PR" build starts running.(5. I guess the Multibranch scanning has to be triggered again.)6. Now the "branch" project gets disabled while the "branch" job is still running.The "branch" build will now never update its status to Bitbucket.This is a major issue, since the developer cannot merge its PR due to a running job.I found out that this line is the problem when updating the status at the end of the job:https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/3412b4eb5b35b9ade7a4e6cfafcdbf3375789fcb/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L101s is of type NullSCMSource and I guess it is due to the branch being removed from "sources" in:https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/MultiBranchProject.javaI create a workaround for us since this was a blocker:https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/26b9f6ace3745cdd58ae1d43eb05d7eb3108f8f8If ther there will be now "quickfix" I guess at least the description in the job config should be updated to pointing to this issue so it is clear to a new user choosing this option that he will face this race condition. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48737) Provide lightweight checkouts for Bitbucket Pull Requests
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-48737 Re: Provide lightweight checkouts for Bitbucket Pull Requests Hi, we are also having this issue with our Bitbucket server.I created a an easy fix for this issue:https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/117 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-48737) Provide lightweight checkouts for Bitbucket Pull Requests
Title: Message Title Benjamin Fuchs commented on JENKINS-48737 Re: Provide lightweight checkouts for Bitbucket Pull Requests Hi, we are also having this issue with our Bitbucket server. I created a easy fix for this issue: https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/117 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-48737) Provide lightweight checkouts for Bitbucket Pull Requests
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-48737 Re: Provide lightweight checkouts for Bitbucket Pull Requests Hi, we are also having this issue with our Bitbucket server.I created an easy fix for this issue:https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/117 Also think that this is related to https://issues.jenkins-ci.org/browse/JENKINS-47617 since if the branch name would be the source branch and not something like PR- it would work without this fix. 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-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress [~therealwaldo] [~thomaskeller] I just created a pull request from my workaround. We are using this already in our productiv system. 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-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Benjamin Fuchs commented on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress Will Freeman I just created a pull request from my workaround. We are using this already in our productiv system. 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.
