[JIRA] (JENKINS-55065) Support a fallback/backup auth mechanism
Title: Message Title Will Freeman commented on JENKINS-55065 Re: Support a fallback/backup auth mechanism We're facing an issue where we're having to consider removing the SAML plugin, for the same reasons. Our use case is the same, our SSO provider does not allow for service users, so a user must manually log in, and it times out regularly forcing a re-login. That means we cannot use any of the reporting features from Jenkins on our dashboard screens. It seems, with this plugin, there is absolutely no mechanism to allow us to view the reports from our monitors, except for granting Anonymous users far more access than is safe. While I agree the core should support multiple security methods, that is likely a long way off and a lot of work. Is there something we could implement for service users within this plugin that would skip the SAML and use some other basic form of authentication? 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-42755) BFA fails to catch pipeline related exceptions
Title: Message Title Will Freeman commented on JENKINS-42755 Re: BFA fails to catch pipeline related exceptions The timestamps thing I expect, however, we experience the exact same issue as the OP. It appears anything output from stderr is not processed by BFA on the build run, but only after in the subsequent scan. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Will Freeman updated an issue Jenkins / JENKINS-45643 Bitbucket PRs are blocked by excluded branches not being able to report progress Change By: Will Freeman Component/s: bitbucket-branch-source-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-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Will Freeman edited a comment on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress Note; this is a full on blocker for us, causing huge headaches on a daily basis. One example of the behaviour is as follows (in addition to others listed above): # Build triggered, updates Bitbucket commit build status as 'build in progress', build starts # Job is marked as disabled (can be because PR is merged, branch is gone, or simply that the configuration of the job has changed) # Bitbucket status is frozen as 'in progress', regardless of if the job finishes. I believe this all hinges on the fact that a disabled job never fires an update if the job is disabled, regardless of the build state, and whether the PR exists/is closed, etc. Triggers are fired on change, not poll.You can also simulate by opening a pull request, closing it before the build finishes, then opening another PR with the exact same head, and you'll never be able to merge that PR (unless you push yet another change). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Will Freeman commented on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress Note; this is a full on blocker for us, causing huge headaches on a daily basis. One example of the behaviour is as follows: Build triggered, updates Bitbucket commit build status as 'build in progress', build starts Job is marked as disabled (can be because PR is merged, branch is gone, or simply that the configuration of the job has changed) Bitbucket status is frozen as 'in progress', regardless of if the job finishes. I believe this all hinges on the fact that a disabled job never fires an update if the job is disabled, regardless of the build state, and whether the PR exists/is closed, etc. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Will Freeman edited a comment on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress Note; this is a full on blocker for us, causing huge headaches on a daily basis. One example of the behaviour is as follows (in addition to others listed above) : # Build triggered, updates Bitbucket commit build status as 'build in progress', build starts # Job is marked as disabled (can be because PR is merged, branch is gone, or simply that the configuration of the job has changed) # Bitbucket status is frozen as 'in progress', regardless of if the job finishes. I believe this all hinges on the fact that a disabled job never fires an update if the job is disabled, regardless of the build state, and whether the PR exists/is closed, etc. 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-47882) Unable to connect MongoDB with MONGODB-CR authentication
Title: Message Title Will Freeman commented on JENKINS-47882 Re: Unable to connect MongoDB with MONGODB-CR authentication Note; I am able to connect just fine with mongo v3.4.18 and BFA v1.20.0, but after upgrading to BFA v1.21.0 it can no longer connect. Rolling back, the connection returns. I'm guessing there may be some migration instructions that are required? 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-54497) Too many Bitbucket git checkouts on Master at the same time
Title: Message Title Will Freeman created an issue Jenkins / JENKINS-54497 Too many Bitbucket git checkouts on Master at the same time Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-11-06 18:38 Environment: Jenkins 2.149 bitbucket branch source 2.2.14 Priority: Major Reporter: Will Freeman When configured to trigger PR builds when an upstream branch changes, if there is hundreds of PRs open, the Jenkins Master fires the initial checkout to get the Jenkinsfile all at the same time on the master. This means literally, that several hundred git operations get called at the same time, stressing out the file system on the master to the point that the master stops responding. Especially when that repository is very large. It also puts tremendous load on the upstream Bitbucket server, which starts throttling at a certain point. Even with reference repositories in use. It seems that there needs to be a configuration option to control how many of these git operations are allowed to fire on the master at the same time. This effectively brings down our Jenkins master daily.
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Will Freeman commented on JENKINS-53775 Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin Also seeing this error pop up fairly consistently when a number of PR builds all fire at the same time on a multibranch job. After the error, the jobs all stick around until the master is rebooted. 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-54278) Pipeline builds fail when cleanWs() in post stage
Title: Message Title Will Freeman commented on JENKINS-54278 Re: Pipeline builds fail when cleanWs() in post stage If I upgrade to 0.36, yes, similar situation although I can occasionally get this to fire by running a build not triggered by SCM changes as well.. Keeping it at 0.35 I cannot reproduce. 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-54278) Pipeline builds fail when cleanWs() in post stage
Title: Message Title Will Freeman created an issue Jenkins / JENKINS-54278 Pipeline builds fail when cleanWs() in post stage Issue Type: Bug Assignee: Oliver Gondža Components: ws-cleanup-plugin Created: 2018-10-26 18:20 Environment: Plugin version 0.36 Priority: Blocker Reporter: Will Freeman Pipeline builds fail when cleanWs() in post stage. Reverting to 0.35 works. Error reported: Required context class hudson.FilePath is missing Perhaps you forgot to surround the code with a step that provides this, such as: node Error when executing cleanup post condition: java.lang.IllegalArgumentException: Failed to prepare cleanWs step at org.jenkinsci.plugins.workflow.cps.DSL.invokeDescribable(DSL.java:401) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:181) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor672.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at
[JIRA] (JENKINS-37345) Throttle automatic git checkout to prevent timeouts/overload on first indexing
Title: Message Title Will Freeman updated an issue Jenkins / JENKINS-37345 Throttle automatic git checkout to prevent timeouts/overload on first indexing Change By: Will Freeman Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37345) Throttle automatic git checkout to prevent timeouts/overload on first indexing
Title: Message Title Will Freeman edited a comment on JENKINS-37345 Re: Throttle automatic git checkout to prevent timeouts/overload on first indexing I'm also seeing this problem at scale. Even with small < 1GB 100MB git repositories and thousands of PR's over time, this is an issue.We need a way to throttle the total number of git processes spawned up on the master, as it is currently boundless and can bring a system down.Latest version of every plugin, still a problem, other issue seems to elude to reducing the number of times a checkout is done vs. the fact that it can start hundreds, even thousands all at the same time, and it's not configurable.I suggest - JENKINS-33273 - is NOT a duplicate. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37345) Throttle automatic git checkout to prevent timeouts/overload on first indexing
Title: Message Title Will Freeman edited a comment on JENKINS-37345 Re: Throttle automatic git checkout to prevent timeouts/overload on first indexing I'm also seeing this problem at scale. Even with small <1GB git repositories and thousands of PR's over time, this is an issue.We need a way to throttle the total number of git processes spawned up on the master, as it is currently boundless and can bring a system down.Latest version of every plugin, still a problem, other issue seems to elude to reducing the number of times a checkout is done vs. the fact that it can start hundreds, even thousands all at the same time, and it's not configurable. I suggest JENKINS-33273 is NOT a duplicate. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37345) Throttle automatic git checkout to prevent timeouts/overload on first indexing
Title: Message Title Will Freeman reopened an issue I'm also seeing this problem at scale. Even with small <1GB git repositories and thousands of PR's over time, this is an issue. We need a way to throttle the total number of git processes spawned up on the master, as it is currently boundless and can bring a system down. Latest version of every plugin, still a problem, other issue seems to elude to reducing the number of times a checkout is done vs. the fact that it can start hundreds, even thousands all at the same time, and it's not configurable. Jenkins / JENKINS-37345 Throttle automatic git checkout to prevent timeouts/overload on first indexing Change By: Will Freeman Resolution: Duplicate Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
