[JIRA] (JENKINS-59786) PrimaryBranchHealthMetric only reports the worst metric of the primary branch, not all metrics of the primary branch
Title: Message Title Stephen Connolly updated JENKINS-59786 Jenkins / JENKINS-59786 PrimaryBranchHealthMetric only reports the worst metric of the primary branch, not all metrics of the primary branch Change By: Stephen Connolly Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202516.1571130672000.7639.1571131681677%40Atlassian.JIRA.
[JIRA] (JENKINS-59786) PrimaryBranchHealthMetric only reports the worst metric of the primary branch, not all metrics of the primary branch
Title: Message Title Stephen Connolly started work on JENKINS-59786 Change By: Stephen Connolly Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202516.1571130672000.7636.1571131681290%40Atlassian.JIRA.
[JIRA] (JENKINS-59786) PrimaryBranchHealthMetric only reports the worst metric of the primary branch, not all metrics of the primary branch
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-59786 PrimaryBranchHealthMetric only reports the worst metric of the primary branch, not all metrics of the primary branch Issue Type: Bug Assignee: Stephen Connolly Components: branch-api-plugin Created: 2019-10-15 09:11 Priority: Minor Reporter: Stephen Connolly JENKINS-56903 added the ability to report the health of the primary branch, but as currently implemented it only reports the worst health rather than all the health metrics, reducing the utility of the feature from the original design. Should report all the metrics from the primary branch Add Comment
[JIRA] (JENKINS-56984) Basic Branch 1.3 thows AbstractMethodError not Fully Backwards Compatible
Title: Message Title Stephen Connolly commented on JENKINS-56984 Re: Basic Branch 1.3 thows AbstractMethodError not Fully Backwards Compatible The 1.3.1 release of basic-branch-build-strategies should fix the incorrect usage of SPI issue that causes this exception, not closing this however as the API changes required to fix the behavioural regressions introduced in the initial implementation of JENKINS-38552 will need to be replicated for these too 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-56999) Folders wiki page and plugin incorrect
Title: Message Title Stephen Connolly updated JENKINS-56999 Jenkins / JENKINS-56999 Folders wiki page and plugin incorrect Change By: Stephen Connolly Status: Fixed but Unreleased Closed 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-56999) Folders wiki page and plugin incorrect
Title: Message Title Stephen Connolly updated JENKINS-56999 Jenkins / JENKINS-56999 Folders wiki page and plugin incorrect Change By: Stephen Connolly Status: Open Fixed but Unreleased Resolution: Done 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-38552) Multibranch pipeline (re)creation intelligence
Title: Message Title Stephen Connolly commented on JENKINS-38552 Re: Multibranch pipeline (re)creation intelligence chirs damour can you file an issue the AbstractMethodError and assign to Félix Belzunce Arcos as this is another fire he needs to put out 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-47154) GitHub Rate Limits are compared using the Jenkins master time not the http response's Date
Title: Message Title Stephen Connolly commented on JENKINS-47154 Re: GitHub Rate Limits are compared using the Jenkins master time not the http response's Date I have yet to see an actual project where a larger burst results in better behaviour. I suggest you build a custom version of the plugin as I predict you will come to the same conclusion once you see the side-effect of a larger burst. I believe you only need to change this line: https://github.com/jenkinsci/github-branch-source-plugin/blob/c3cc6c52992ccdf9f7fd03dc7e56264cfb3f1f26/src/main/java/org/jenkinsci/plugins/github_branch_source/Connector.java#L584 probably the `Math.max(200, rateLimit.limit / 5)` to `Math.max(200, rateLimit.limit * 4 / 5)` which would swap from 1:4 to 4:1 between burst and normal quotas 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-47154) GitHub Rate Limits are compared using the Jenkins master time not the http response's Date
Title: Message Title Stephen Connolly commented on JENKINS-47154 Re: GitHub Rate Limits are compared using the Jenkins master time not the http response's Date Carmen Alvarez said: Current quota has 3104 remaining (331 over budget). Next quota of 5000 in 50 min. It would be nice to be able to disable this check, and just take the risk that a quota limit may be reached during a job. I don't think that would actually be the case for us, given that we have plenty of requests remaining. So it may help to understand how the plugin manages the quota. The quota gets divided into three parts: Burst (this is about 15-20%) Normal (this is about 75-80%) Exception (this is about 5%) The idea is that the Normal quota is divided up over the whole hour. The Burst quota is for "bursty" use cases. The Exception quota is in case any requests accidentally use more than we have managed (because all your Jenkins instances are - per the GitHub ToS - supposed to be using the same API Key, so if you have 5 masters, without the Exception quota, 4 of them could erroneously think that there is an API call unused and then they would fail) Further complications arise because the GitHub API Java client library we are using does not make it easy to predict how many API calls will be made. For example, if you ask for a list of all the repositories in an organization... that is a paged API and the GitHub API Java client library will just return an Iterator that masks all the background API calls while you iterate the list... it may even serve the request from cached state... so the API call can be anywhere from 0 to infinite requests (realistically no more than 3-4 requests for most organizations)... its worse for listing PRs where you can have many thousands and the page size is typically 50-100. So what we do (all numbers are from memory and for illustrative purposes only): is we use a linear allocation strategy for the Normal quota... e.g. we allow approx 4000 requests per hour, at 10 minutes into the hour the budget says we should have 4000*(60-10)/60 requests left in the Normal quota, e.g. . Then we add on the Exception quota (approx 150) This gives the budget plan for now, i.e. +150 = 3483 requests should be remaining If the actual requests remaining is more than this number, the request will be made. If the requests remaining is less than this number then you get the log message you see. For example if the requests remaining is 3104 then we have spent 379 requests more than the budget. Since we know the rate at which the Normal quota will be divided out, we can then sleep until such a time as the spend will be expected to be back within budget, at 66 requests per minute that overspend of 379 will be back on track if we make no more requests for the next approx 6 minutes. So what has happened is: in the first 10 minutes
[JIRA] (JENKINS-56917) Inability to control triggers on multibranch children of an organization folder
Title: Message Title Stephen Connolly updated JENKINS-56917 Jenkins / JENKINS-56917 Inability to control triggers on multibranch children of an organization folder Change By: Stephen Connolly Status: Fixed but Unreleased Closed 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-56903) Health metric that reports only the primary branch
Title: Message Title Stephen Connolly updated JENKINS-56903 Jenkins / JENKINS-56903 Health metric that reports only the primary branch Change By: Stephen Connolly Status: Fixed but Unreleased Closed Released As: 2. 3 4 . 1 0 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-56917) Inability to control triggers on multibranch children of an organization folder
Title: Message Title Stephen Connolly updated JENKINS-56917 Jenkins / JENKINS-56917 Inability to control triggers on multibranch children of an organization folder Change By: Stephen Connolly Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.4.0 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-56917) Inability to control triggers on multibranch children of an organization folder
Title: Message Title Stephen Connolly updated JENKINS-56917 Jenkins / JENKINS-56917 Inability to control triggers on multibranch children of an organization folder Change By: Stephen Connolly Status: In Progress Review 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-56917) Inability to control triggers on multibranch children of an organization folder
Title: Message Title Stephen Connolly started work on JENKINS-56917 Change By: Stephen Connolly Status: Open In Progress 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-56917) Inability to control triggers on multibranch children of an organization folder
Title: Message Title Stephen Connolly started work on JENKINS-56917 Change By: Stephen Connolly Status: Open In Progress 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-56917) Inability to control triggers on multibranch children of an organization folder
Title: Message Title Stephen Connolly updated JENKINS-56917 Jenkins / JENKINS-56917 Inability to control triggers on multibranch children of an organization folder Change By: Stephen Connolly Status: In Progress Review 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-56903) Health metric that reports only the primary branch
Title: Message Title Stephen Connolly updated JENKINS-56903 Jenkins / JENKINS-56903 Health metric that reports only the primary branch Change By: Stephen Connolly Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.3.1 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-56917) Inability to control triggers on multibranch children of an organization folder
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-56917 Inability to control triggers on multibranch children of an organization folder Issue Type: New Feature Assignee: Stephen Connolly Components: branch-api-plugin Created: 2019-04-05 15:00 Priority: Minor Reporter: Stephen Connolly 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-56903) Health metric that reports only the primary branch
Title: Message Title Stephen Connolly updated JENKINS-56903 Jenkins / JENKINS-56903 Health metric that reports only the primary branch Change By: Stephen Connolly Status: In Progress Review 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-56903) Health metric that reports only the primary branch
Title: Message Title Stephen Connolly started work on JENKINS-56903 Change By: Stephen Connolly Status: Open In Progress 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-56903) Health metric that reports only the primary branch
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-56903 Health metric that reports only the primary branch Issue Type: New Feature Assignee: Stephen Connolly Components: branch-api-plugin Created: 2019-04-05 09:28 Priority: Minor Reporter: Stephen Connolly A health reporting strategy for multibranch projects that reports only the health of the primary branch. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56658) BranchBuildStrategy implementations need to be able to log rationale
Title: Message Title Stephen Connolly resolved as Fixed Jenkins / JENKINS-56658 BranchBuildStrategy implementations need to be able to log rationale Change By: Stephen Connolly Status: In Progress Resolved Resolution: Fixed Released As: 2.2.0 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-56658) BranchBuildStrategy implementations need to be able to log rationale
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-56658 BranchBuildStrategy implementations need to be able to log rationale Change By: Stephen Connolly Summary: BranchBuildStrategy implementations need to be able to log rational rationale 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-56660) If the child class overrides a method and marks the override as final Util.isOverridden should return true
Title: Message Title
Stephen Connolly created an issue
Jenkins / JENKINS-56660
If the child class overrides a method and marks the override as final Util.isOverridden should return true
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-03-21 11:28
Priority:
Critical
Reporter:
Stephen Connolly
See https://github.com/jenkinsci/jenkins/blob/2263ad03ab8aa481caa3918c8671b1d605514b15/core/src/main/java/hudson/Util.java#L1345 What is wrong with final methods in the derived class
public class Parent {
public Object doThing() {}
}
public class Child extends Parent {
@Override
public final Object doThing() { ... }
}
assert Util.isOverridden(Parent.class, Child.class, "doThing") : "Sadly this is not true for the past 4 years"
Add Comment
[JIRA] (JENKINS-56658) BranchBuildStrategy implementations need to be able to log rational
Title: Message Title Stephen Connolly started work on JENKINS-56658 Change By: Stephen Connolly Status: Open In Progress 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-56658) BranchBuildStrategy implementations need to be able to log rational
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-56658 BranchBuildStrategy implementations need to be able to log rational Issue Type: Improvement Assignee: Stephen Connolly Components: branch-api-plugin Created: 2019-03-21 10:44 Priority: Minor Reporter: Stephen Connolly The branch build strategies need access to the TaskListener of the log file so that if they need to explain why they are taking actions the user can see the rationale Add Comment This message was sent
[JIRA] (JENKINS-56656) Mock API needs a way to simulate untrusted change requests
Title: Message Title Stephen Connolly resolved as Fixed Jenkins / JENKINS-56656 Mock API needs a way to simulate untrusted change requests Change By: Stephen Connolly Status: Open Resolved Resolution: Fixed Released As: 2.3.1 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-56656) Mock API needs a way to simulate untrusted change requests
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-56656 Mock API needs a way to simulate untrusted change requests Issue Type: Improvement Assignee: Stephen Connolly Components: scm-api-plugin Created: 2019-03-21 10:26 Priority: Minor Reporter: Stephen Connolly The test harness need to add support for a flag that enabled a mock change request as untrsuted Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-51865) Stage locks are created for skipped stages in declarative pipeline
Title: Message Title Stephen Connolly commented on JENKINS-51865 Re: Stage locks are created for skipped stages in declarative pipeline Ok that is an acceptable workaround for my use case 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-51865) Stage locks are created for skipped stages in declarative pipeline
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-51865 Stage locks are created for skipped stages in declarative pipeline Change By: Stephen Connolly Attachment: Screenshot 2019-01-30 at 10.56.27.png 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-51865) Stage locks are created for skipped stages in declarative pipeline
Title: Message Title
Stephen Connolly commented on JENKINS-51865
Re: Stage locks are created for skipped stages in declarative pipeline
so `quantity:0` doens't work as that is the default value and seems to indicate "grab all". I'm now trying:
pipeline {
stages {
stage('Example stage') {
when { branch 'master' }
options { lock resource: "${BRANCH_NAME=='master' ? 'example resource':'dummy'}" }
steps { // ... }
}
}
}
We'll see if that is an acceptable workaround for my use case
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-51865) Stage locks are created for skipped stages in declarative pipeline
Title: Message Title
Stephen Connolly commented on JENKINS-51865
Re: Stage locks are created for skipped stages in declarative pipeline
Andrew Bayer perhaps we could work around this by using an _expression_ in the quantity of the lock, e.g.
pipeline {
stages {
stage('Example stage') {
when { _expression_ { false } }
options { lock resource: 'example resource', quantity: expr ? 1 : 0 }
steps { // ... }
}
}
}
What I do not know is if declarative supports numerical expressions
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-55683) Endless loop on login when using OpenID plugin after upgrading to 2.160 / 2.150.2, preventing user authentication
Title: Message Title Stephen Connolly assigned an issue to Wadeck Follonier Jenkins / JENKINS-55683 Endless loop on login when using OpenID plugin after upgrading to 2.160 / 2.150.2, preventing user authentication Change By: Stephen Connolly Assignee: Stephen Connolly Wadeck Follonier 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-54517) Broken links to gitea web UI in Jenkins job sidebar
Title: Message Title Stephen Connolly commented on JENKINS-54517 Re: Broken links to gitea web UI in Jenkins job sidebar Christian Fochler there is no point assigning this issue to me as it would give people the false impression that I am actively working on it or that I do not want others to work on it. When I next have a window of time to work on the gitea plugin I will review any open issues and decide which ones I'm working on. If others want to work on this they are more than welcome to create a pull request which I will review and, if appropriate, merge and release. My priority for the Gitea plugin is tag support, which is currently blocked by gaps in the Gitea API (which the Gitea team is working on). Once the Gitea team reports back to me that they have delivered all that is required for tag support, I'll request a time box to work on the Gitea plugin... until then I am relying on PRs from others which I can review. 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-54517) Broken links to gitea web UI in Jenkins job sidebar
Title: Message Title Stephen Connolly assigned an issue to Unassigned Jenkins / JENKINS-54517 Broken links to gitea web UI in Jenkins job sidebar Change By: Stephen Connolly Assignee: Stephen Connolly 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-53098) Gitea Plugin documentation missing
Title: Message Title Stephen Connolly updated JENKINS-53098 Jenkins / JENKINS-53098 Gitea Plugin documentation missing Change By: Stephen Connolly Status: Open Fixed but Unreleased Resolution: Duplicate 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-53098) Gitea Plugin documentation missing
Title: Message Title Stephen Connolly updated JENKINS-53098 Jenkins / JENKINS-53098 Gitea Plugin documentation missing Change By: Stephen Connolly Status: Fixed but Unreleased Closed 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-48960) Org folders repository folder never runs scans on repository
Title: Message Title Stephen Connolly commented on JENKINS-48960 Re: Org folders repository folder never runs scans on repository Jim Klimov so the correct solution to that would be something like the GitHub SNS plugin (if it was updated to replicate events correctly... last time I checked it wasn't ) Andy Airey The point is that those are not issues for the branch-api plugin itself, they are issues with the SCM sources... or the SCMs themselves... or your environment. Polling is exceedingly expensive in terms of overhead to check and also in terms of delay of notification. Especially when you have an entire organization of repositories to scan. For something like GitHub or Bitbucket Cloud, because of API limits, polling may not even be in any way practicable. If you are really stuck, then there are other paths you can take, for example the Apache Software Foundation uses its own custom org folder and event forwarding... https://github.com/stephenc/asf-gitpubsub-jenkins-plugin (also see the video series where I show how this was developed https://www.youtube.com/watch?v=W8BRtJmq_2Y=PLvBBnHmZuNQLXcL6CBZPKbX9OstMNIhTV ... note that the video is real time development of the plugin. The only code I wrote was during the video recordings) 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-48960) Org folders repository folder never runs scans on repository
Title: Message Title Stephen Connolly commented on JENKINS-48960 Re: Org folders repository folder never runs scans on repository Andy Airey then fix your webhooks 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-48960) Org folders repository folder never runs scans on repository
Title: Message Title Stephen Connolly commented on JENKINS-48960 Re: Org folders repository folder never runs scans on repository There are two periodic scans "configured". One is user configurable, namely the one at the org folder level. The other is not currently configurable, namely the one at the branch folder level. Now the way this is designed is on the basis that you will set up webhooks because "polling must die" to quote a blog post from KK ages back. So the periodic scanning is more to cover two cases: 1. To allow controlled pruning of orphaned items. For technical reasons, the code was actually written originally to allow multiple sources in the same org folder. So you could have one source be a github organization and another be a bitbucket team. Then if you moved a repository from the bitbucket team to the github organization the multibranch project would still stay there. This was to mirror the fact that a multibranch project can have multiple sources. However this was too confusing, so we locked the org folders to one source only. In any case, because there originally could be (and for a multibranch project there still can be) multiple things that can claim ownership of a child name, we cannot decide if an event that a name has been deleted by one source will actually result in the deletion of the child. We have to ask all the candidate sources in the priority order: "is this yours?" until we get someone answering "yes"... So the orphaned item strategy only runs with a full scan. This also allows the orphaned item strategy to correctly decide the order in which orphans should be removed. 2. Events may be dropped or lost. We should find those changes eventually. The scan fills that gap. If you have webhooks set up correctly then you only need scanning say once per day or less frequently. All the cron triggers store a random offset as a transient field. This random offset is used to decide when in the `H` portion of a trigger rule to actually pick. The periodic folder trigger converts the times into rules like H * * * * (for hourly) or H H * * * (for daily) so this transient field is important that it remain consistent. What I think is happening is that the org folder scan is resetting the transient field. So if your org folder is scanning every 5 minutes, you will have a 5 in 60 chance that the transient gets reset to a value in the next 5 minutes. Of course we have two H's for the daily scan that the multibranch has. So basically if my theory that the transient is getting reset is correct then there is a 1 in 288 chance that the transient will have a value resulting in a scan during the next 5 minutes... and then the transient gets reset again. Each 5 minute interval gas a 287 in 288 chance of not scanning... so we are naïvely looking at the probability of a multibranch project not scanning being (287/288)^288 = 0.36... it's actually worse, because that is actually the probability of it checking whether a scan is due... and if the transient field for H is being cleared then so too will this one: https://github.com/jenkinsci/cloudbees-folder-plugin/blob/23367538c5c6b405a3ba63d8033ca459aa2f65a0/src/main/java/com/cloudbees/hudson/plugins/folder/computed/PeriodicFolderTrigger.java#L71 and so if we win the 63% lottery then one of those will run through to initialize lastTriggered to a random value https://github.com/jenkinsci/cloudbees-folder-plugin/blob/23367538c5c6b405a3ba63d8033ca459aa2f65a0/src/main/java/com/cloudbees/hudson/plugins/folder/computed/PeriodicFolderTrigger.java#L211-L217 So if my theory is correct then you would expect:
[JIRA] (JENKINS-47077) "Periodically if not otherwise run" interval does not trigger index scan
Title: Message Title Stephen Connolly commented on JENKINS-47077 Re: "Periodically if not otherwise run" interval does not trigger index scan Subfolders have their own period of scanning that is not the period of the parent 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-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Stephen Connolly commented on JENKINS-54864 Re: github multibranch builds fail to build with latest branch api update And just in case somebody says "who'd call your branches PR-*?" suppose you are using JIRA and your JIRA project ID is PR... then it might make extreme sense to name all your branches by the JIRA ID that they are developing... so that JIRA ID PR-5612 is in the branch PR-5612... if you are using an SCMSource that doesn't have Change Requests... perhaps you rolled a custom one similar to https://github.com/stephenc/asf-gitpubsub-jenkins-plugin for your own in-house GIT hosting... You might not want to build any of the OPS ticket branches on your Jenkins, so you just set the automatic building to master,PR-* So if we are going to embed the logic to figure these things out into code... we should handle the above! 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-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title
Stephen Connolly edited a comment on JENKINS-54864
Re: github multibranch builds fail to build with latest branch api update
So if somebody can come up with an _expression_ parser for the old configuration string that can reliably distinguish between:* {{PR- \ *}} means build all *branches* whos names begin with {{PR-}} such as {{PR-foobar}} and do not build pull requests because our SCMSource doesn't even have the concept. * {{PR- \ *}} means build all *pull-requests* but we don't want to accidentally build branches with names that begin with {{PR-}} because we just want to build the {{master}} branch.* {{CR- \ *}} means build all *pull-requests* because our SCMSource calls them Change Requests and uses {{CR-}} as the prefixI would be happy to merge.Until then, the least risk (given that building a branch can result in deploying things into production or expose secrets to a build that isn't trusted) is to err on the side of "if we don't know, do nothing".In any case, we could argue that the old `Automatic branch project triggering` has a bug of _requiring_ you to know to add {{PR- \ *}} in order to build pull requests... just that people were relying on the bug!
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-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Stephen Connolly commented on JENKINS-54864 Re: github multibranch builds fail to build with latest branch api update So if somebody can come up with an _expression_ parser for the old configuration string that can reliably distinguish between: PR- means build all *branches whos names begin with PR- such as PR-foobar and do not build pull requests because our SCMSource doesn't even have the concept. PR- means build all *pull-requests but we don't want to accidentally build branches with names that begin with PR- because we just want to build the master branch. CR- means build all *pull-requests because our SCMSource calls them Change Requests and uses CR- as the prefix I would be happy to merge. Until then, the least risk (given that building a branch can result in deploying things into production or expose secrets to a build that isn't trusted) is to err on the side of "if we don't know, do nothing". In any case, we could argue that the old `Automatic branch project triggering` has a bug of requiring you to know to add PR-* in order to build pull requests... just that people were relying on the bug! 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Stephen Connolly commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher https://github.com/jenkinsci/jenkins/pull/3786 should 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Stephen Connolly commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher Ahhh do we need a readResolve to set the authenticator! 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-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Stephen Connolly commented on JENKINS-54864 Re: github multibranch builds fail to build with latest branch api update I suspect you had "Automatic branch project triggering" configured to something like master, PR-* This gets mapped to matching branches that have the set of names as automatic build, but doesn't include Pull requests in automatic builds. As a workaround, just add Pull Requests to the build strategies and pull requests should start building. If somebody is interested in fixing this you would need to: Establish that all SCMSource implementations only use PR- as the prefix for pull requests... if there is an SCMSource implementation that uses something like CR- then we cannot fix this issue as we would not know if PR-* is intended to target branches that start with PR- or pull requests. If we know that PR- is guaranteed to only apply to pull requests, then modify the migration so that it parses the "Automatic branch project triggering" value, pulls out the PR- ones and adds named branch build strategies for all others. If there is any PR- entries then add the change request build strategy 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Stephen Connolly commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher Daniel Beck its hard to see how JENKINS-48755 could cause this issue: The code path should be identical to that in place before when the URL is not https... and from the reported exception, the URL is http://ftp-nyc.osuosl.org/pub/jenkins/updates/current/update-center.json which is http so jenkins48775workaround (Proxy,URL) should be a no-op The only possible risk of a delta is from the refactoring in this method because that Authenticator was written to use the inverse if condition. I have re-read it 10 times and the refactoring looks sound... but perhaps I am mistaken 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-54861) don't trigger initial build after branch detection
Title: Message Title Stephen Connolly assigned an issue to Unassigned Jenkins / JENKINS-54861 don't trigger initial build after branch detection Change By: Stephen Connolly Assignee: Stephen Connolly 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-54861) don't trigger initial build after branch detection
Title: Message Title Stephen Connolly commented on JENKINS-54861 Re: don't trigger initial build after branch detection You should be able to write your own branch build strategy in a custom extension plugin 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-52397) Org Scan blows up when repository has no tags
Title: Message Title Stephen Connolly commented on JENKINS-52397 Re: Org Scan blows up when repository has no tags https://github.com/jenkinsci/github-branch-source-plugin/commit/3079fd6d0609bf0a6387729c0da756ed08abfabc was merged... just waiting on rsandell to cut a release... or you could take the snapshot build from https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fgithub-branch-source-plugin/detail/master/82/artifacts 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-47859) `Automatic branch project triggering » Branch names to build automatically` must die
Title: Message Title Stephen Connolly updated JENKINS-47859 Jenkins / JENKINS-47859 `Automatic branch project triggering » Branch names to build automatically` must die Change By: Stephen Connolly Status: In Review Resolved Assignee: Stephen Connolly Resolution: Fixed Released As: 2.1.0 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-47077) "Periodically if not otherwise run" interval does not trigger index scan
Title: Message Title Stephen Connolly resolved as Fixed Jenkins / JENKINS-47077 "Periodically if not otherwise run" interval does not trigger index scan Change By: Stephen Connolly Status: Open Resolved Assignee: Stephen Connolly Resolution: Fixed Released As: 6.7 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-54206) Merged PRs not being removed from multibranch
Title: Message Title Stephen Connolly commented on JENKINS-54206 Re: Merged PRs not being removed from multibranch Does the other one have an orphaned strategy configured? 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-52397) Org Scan blows up when repository has no tags
Title: Message Title Stephen Connolly commented on JENKINS-52397 Re: Org Scan blows up when repository has no tags culprit looks to be https://github.com/kohsuke/github-api/commit/a17ce04552ddd3f6bd8210c740184e6c7ad13ae4 I have asked rsandell to see if he can drive https://github.com/jenkinsci/github-branch-source-plugin/pull/191 over the finish line 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-45478) Add support for utm_ query parameters
Title: Message Title Stephen Connolly updated JENKINS-45478 Jenkins / JENKINS-45478 Add support for utm_ query parameters Change By: Stephen Connolly Status: In Review Resolved Assignee: Stephen Connolly Resolution: Fixed Released As: 2.3.0 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-54206) Merged PRs not being removed from multibranch
Title: Message Title Stephen Connolly resolved as Incomplete Marking as incomplete until more info is provided... likely this is build logs being requested to be kept in which case functioning as designed Jenkins / JENKINS-54206 Merged PRs not being removed from multibranch Change By: Stephen Connolly Status: Reopened Resolved Resolution: Incomplete 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-54206) Merged PRs not being removed from multibranch
Title: Message Title Stephen Connolly commented on JENKINS-54206 Re: Merged PRs not being removed from multibranch The most likely reason is somebody is requesting that the build logs be kept: https://github.com/jenkinsci/cloudbees-folder-plugin/blob/f313065f5fb613c4fedf78627a9cddee7a600388/src/main/java/com/cloudbees/hudson/plugins/folder/computed/DefaultOrphanedItemStrategy.java#L252-L271 and if you request the build logs be kept then we'll honour that request 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-54206) Merged PRs not being removed from multibranch
Title: Message Title Stephen Connolly commented on JENKINS-54206 Re: Merged PRs not being removed from multibranch Go to the Scan Repository Log screen, i.e. the one with the URL that ends in `/indexing/console`. Scroll down to the bottom and see what the orphaned item strategy is printing out. I'd expect something like: 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-54206) Merged PRs not being removed from multibranch
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-54206 Merged PRs not being removed from multibranch Change By: Stephen Connolly Attachment: Screenshot 2018-11-16 at 09.10.24.png 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-54206) Merged PRs not being removed from multibranch
Title: Message Title Stephen Connolly commented on JENKINS-54206 Re: Merged PRs not being removed from multibranch as reporter you should be able to reopen 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-54206) Merged PRs not being removed from multibranch
Title: Message Title Stephen Connolly commented on JENKINS-54206 Re: Merged PRs not being removed from multibranch Very strange... because it is working for me 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-29647) java.lang.NoClassDefFoundError thrown by jenkins slave while the class is in the class path.
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-29647 java.lang.NoClassDefFoundError thrown by jenkins slave while the class is in the class path. Change By: Stephen Connolly Assignee: Stephen Connolly 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-42280) Nullpointer on BasicSSHUserPrivateKey passphrase
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-42280 Nullpointer on BasicSSHUserPrivateKey passphrase Change By: Stephen Connolly Assignee: Stephen Connolly 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-47226) Provide easy access to git branch name in (single branch) Pipeline build
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-47226 Provide easy access to git branch name in (single branch) Pipeline build Change By: Stephen Connolly Assignee: Stephen Connolly 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-47699) Cannot use user-scoped credentials from pipeline input step parameters
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-47699 Cannot use user-scoped credentials from pipeline input step parameters Change By: Stephen Connolly Assignee: Stephen Connolly 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-48772) Overescaped description of credentials
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-48772 Overescaped description of credentials Change By: Stephen Connolly Assignee: Stephen Connolly 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-48226) MultiBranch doesn't distinguish Branches and PRs
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-48226 MultiBranch doesn't distinguish Branches and PRs Change By: Stephen Connolly Assignee: Stephen Connolly 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-53210) Scan Organisation no longer triggering project scans
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-53210 Scan Organisation no longer triggering project scans Change By: Stephen Connolly Assignee: Stephen Connolly 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-52600) credentials plugin uses Restricted jenkins.util.xml.XMLUtils
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-52600 credentials plugin uses Restricted jenkins.util.xml.XMLUtils Change By: Stephen Connolly Assignee: Stephen Connolly 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-38533) Checkout the pull request merge refs directly
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-38533 Checkout the pull request merge refs directly Change By: Stephen Connolly Assignee: Stephen Connolly 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-53098) Gitea Plugin documentation missing
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-53098 Gitea Plugin documentation missing Change By: Stephen Connolly Assignee: Stephen Connolly 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-32980) Make it easier to use JNLP slaves with self-signed TLS certificates on Jenkins
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-32980 Make it easier to use JNLP slaves with self-signed TLS certificates on Jenkins Change By: Stephen Connolly Assignee: Stephen Connolly 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-53806) Class-based DomainSpecification filter for more flexibility of restricting credentials
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-53806 Class-based DomainSpecification filter for more flexibility of restricting credentials Change By: Stephen Connolly Assignee: Stephen Connolly 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-44360) '%' in branch name causes Windows multi-branch job failures
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-44360 '%' in branch name causes Windows multi-branch job failures Change By: Stephen Connolly Assignee: Stephen Connolly 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-49717) no token field in Openshift OAuth token credential type
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-49717 no token field in Openshift OAuth token credential type Change By: Stephen Connolly Assignee: Stephen Connolly 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-45540) Refactor id-and-description tear-off
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-45540 Refactor id-and-description tear-off Change By: Stephen Connolly Assignee: Stephen Connolly 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-45235) UpdateCenter fails to find newer plugin versions from additional sites
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-45235 UpdateCenter fails to find newer plugin versions from additional sites Change By: Stephen Connolly Assignee: Stephen Connolly 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-20075) Support moving credentials between credential stores
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-20075 Support moving credentials between credential stores Change By: Stephen Connolly Assignee: Stephen Connolly 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-49051) Add event field to BranchEventCause
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-49051 Add event field to BranchEventCause Change By: Stephen Connolly Assignee: Stephen Connolly 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-42228) Javascript error credentials select
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-42228 _javascript_ error credentials select Change By: Stephen Connolly Assignee: Stephen Connolly 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-54052) MultibranchProject ignores quietPeriod
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-54052 MultibranchProject ignores quietPeriod Change By: Stephen Connolly Assignee: Stephen Connolly 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-45771) Disable shallow clone when we know a merge will take place
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-45771 Disable shallow clone when we know a merge will take place Change By: Stephen Connolly Assignee: Stephen Connolly 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-52386) credentials() parameter does not support HTML in description
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-52386 credentials() parameter does not support HTML in description Change By: Stephen Connolly Assignee: Stephen Connolly 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-45254) credential ID accepts a too narrow set of characters
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-45254 credential ID accepts a too narrow set of characters Change By: Stephen Connolly Assignee: Stephen Connolly 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-25863) Jenkins tries to build jobs on nodes that are removed
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-25863 Jenkins tries to build jobs on nodes that are removed Change By: Stephen Connolly Assignee: Stephen Connolly 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-41073) MultiBranch projects should veto SCM Polling
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-41073 MultiBranch projects should veto SCM Polling Change By: Stephen Connolly Assignee: Stephen Connolly 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-40293) "Add" button should allow opening the dialogue with a specific "Kind" of credential pre-selected
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-40293 "Add" button should allow opening the dialogue with a specific "Kind" of credential pre-selected Change By: Stephen Connolly Assignee: Stephen Connolly 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-41072) Poll the GitHub Events API as an alternative to webhook
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-41072 Poll the GitHub Events API as an alternative to webhook Change By: Stephen Connolly Assignee: Stephen Connolly 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-52796) Jenkins Showing 403 forbidden on clicking of apply and submit button of system configuration
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-52796 Jenkins Showing 403 forbidden on clicking of apply and submit button of system configuration Change By: Stephen Connolly Assignee: Stephen Connolly 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-20073) Add an action to allow moving credentials between credential domains
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-20073 Add an action to allow moving credentials between credential domains Change By: Stephen Connolly Assignee: Stephen Connolly 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-53176) How to safely rotate master.key and hudson.util.Secret?
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-53176 How to safely rotate master.key and hudson.util.Secret? Change By: Stephen Connolly Assignee: Stephen Connolly 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-39324) AbstractIdCredentialsListBoxModel signature changes to take ModelObject
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-39324 AbstractIdCredentialsListBoxModel signature changes to take ModelObject Change By: Stephen Connolly Assignee: Stephen Connolly 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-42976) Provide a way to refresh Org Folder metadata without indexing
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-42976 Provide a way to refresh Org Folder metadata without indexing Change By: Stephen Connolly Assignee: Stephen Connolly 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-47859) `Automatic branch project triggering » Branch names to build automatically` must die
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-47859 `Automatic branch project triggering » Branch names to build automatically` must die Change By: Stephen Connolly Assignee: Stephen Connolly 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-46295) Events handling for deleted branches can blow up
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-46295 Events handling for deleted branches can blow up Change By: Stephen Connolly Assignee: Stephen Connolly 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-52799) Powershell not able to get variables when using withCredentials
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-52799 Powershell not able to get variables when using withCredentials Change By: Stephen Connolly Assignee: Stephen Connolly 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-48996) jenkins.branch.MultiBranchProject disregards quick delete and recreation via branch webhooks.
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-48996 jenkins.branch.MultiBranchProject disregards quick delete and recreation via branch webhooks. Change By: Stephen Connolly Assignee: Stephen Connolly 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-49999) Write user and consumer guide for metrics plugin
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-4 Write user and consumer guide for metrics plugin Change By: Stephen Connolly Assignee: Stephen Connolly 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-46536) A pollSCM property in a multibranch pipeline should ignore checking the primary SCM
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-46536 A pollSCM property in a multibranch pipeline should ignore checking the primary SCM Change By: Stephen Connolly Assignee: Stephen Connolly 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.
