[JIRA] [git-plugin] (JENKINS-32824) Ignore specific users in Git plugin isn't working correctly if i was working in all the branches at the same job
Title: Message Title Aya Serry updated an issue Jenkins / JENKINS-32824 Ignore specific users in Git plugin isn't working correctly if i was working in all the branches at the same job Change By: Aya Serry *Requirements:*I want one job, to get the source code from GIT repository, make some tests and then push some changes on the same repository. - This job should be triggered once the source code is changed. - This job should should work on *all the branches*. *Job Description:*+Source Code Management:+ Branches to build: ** Additional Behaviours: Polling ignores commits from specific users: I have put my name. +Build Triggers:+Using "git notifyCommit" I have added a hook on gitlab to trigger the build on Jenkins.On "Build Triggers" section, I'm checking "Poll SCM" option.+Add, Commit & Push:+ I made the add and the commit using windows batch. Push: using git publisher, on "Add branches" i have added the name of the repository.*Problem:*The excluded user is not excluded all the time, which some times cause an infinite loop, and sometimes cause a lot of extra unnecessary builds.After a lot of investigations, i have checked the source code of the plugin, and i have understood the some reasons of the problem:1) The plugin is depending on the *last build revision*, to get "From" & "To" revision number, and this generate a problem, because the "From" of the last build could be for another branch, so it will git all the old revisions and sure this revision contains users not listed in the "Excluded users list", thus a new build will be triggered.2) If there were changes in three branches for example, and 2 branches should be ignored, but the third one should trigger a build, the three branches will be triggered.These are the problems i have discovered till now, could anyone tell me when these issues will be fixed? we are blocked a month ago on this problem, and no one is answering us. Add Comment
[JIRA] [_unsorted] (JENKINS-32796) Can't update plugins: incorrect checksum
Title: Message Title David Zschille commented on JENKINS-32796 Re: Can't update plugins: incorrect checksum Yes, seems that it was a temporarily error, it's gone now. Perhaps somehow connected to INFRA-557 , which i had at the same time. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-32806) "Failed to run task: 'gulp bundle test --no-color'" while building
Title: Message Title Oliver Gondža commented on JENKINS-32806 Re: "Failed to run task: 'gulp bundle test --no-color'" while building rm -rf war/node_modules did the trick, thanks. Not sure how mvn clean -cleanNode should work. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-32806) "Failed to run task: 'gulp bundle test --no-color'" while building
Title: Message Title Oliver Gondža resolved as Cannot Reproduce Jenkins / JENKINS-32806 "Failed to run task: 'gulp bundle test --no-color'" while building Change By: Oliver Gondža Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cucumber-testresult-plugin] (JENKINS-24457) VERY poor performance with large test history when viewing results.
Title: Message Title James Nord commented on JENKINS-24457 Re: VERY poor performance with large test history when viewing results. Vitaliy Skrypnyk to be clear you are 100% correct and this is by design. There is no guarantee that previous builds have finished when the later build completes. This is the same in the junit plugin. The slow behavior is due to Memory pressure - if you had more memory available then the prior results would be in memory and would not need to be loaded and parsed - although there is potential that some thing could be improved in this area. > Cucumber plugin calculates fail age separately for each scenario this is still required as you do not need to view all scenarios - they can be viewed individually, so calculating this for all scenarios when you are viewing a single scenario will be equally sub-optimal. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [next-executions-plugin] (JENKINS-32652) XSS in Possible Next Executions widget
Title: Message Title Ignacio Albors commented on JENKINS-32652 Re: XSS in Possible Next Executions widget Thank you for the warning. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [_unsorted] (JENKINS-32310) url is not working due to admin server is down
Title: Message Title Oleg Nenashev resolved as Incomplete No response from the requester Jenkins / JENKINS-32310 url is not working due to admin server is down Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [_unsorted] (JENKINS-31947) Jobs hanging in Build Executor even if it is finished
Title: Message Title Oleg Nenashev resolved as Incomplete No response. Resolving the issue as Incomplete. Please reopen it if you're ready to provide more info Jenkins / JENKINS-31947 Jobs hanging in Build Executor even if it is finished Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [integrity-plugin] (JENKINS-32677) Don't see labels applied to the codebase
Title: Message Title Oleg Nenashev commented on JENKINS-32677 Re: Don't see labels applied to the codebase I do not understand the request at all. Could you please provide screenshots and reproduction steps? BTW I'll move it to the right plugin component Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [integrity-plugin] (JENKINS-32677) Don't see labels applied to the codebase
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-32677 Don't see labels applied to the codebase Change By: Oleg Nenashev Component/s: integrity-plugin Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [integrity-plugin] (JENKINS-32677) Don't see labels applied to the codebase
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-32677 Don't see labels applied to the codebase Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [_unsorted] (JENKINS-32796) Can't update plugins: incorrect checksum
Title: Message Title Oleg Nenashev closed an issue as Not A Defect Jenkins / JENKINS-32796 Can't update plugins: incorrect checksum Change By: Oleg Nenashev Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [next-executions-plugin] (JENKINS-32652) XSS in Possible Next Executions widget
Title: Message Title Ignacio Albors closed an issue as Fixed Jenkins / JENKINS-32652 XSS in Possible Next Executions widget Change By: Ignacio Albors Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-build-step-plugin] (JENKINS-24071) Docker build step tries to build on master and not slave
Title: Message Title Ebrahim Moshaya commented on JENKINS-24071 Re: Docker build step tries to build on master and not slave any update on this? We need to be able to execute docker commands on slaves... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [branch-api-plugin] (JENKINS-31860) java.lang.ClassCastException: jenkins.branch.MultiBranchProject$3 cannot be cast to hudson.security.SidACL
Title: Message Title Jesse Glick commented on JENKINS-31860 Re: java.lang.ClassCastException: jenkins.branch.MultiBranchProject$3 cannot be cast to hudson.security.SidACL Fixed? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-32553) svn: PROPFIND request failed
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-32553 svn: PROPFIND request failed Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-32553) svn: PROPFIND request failed
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-32553 svn: PROPFIND request failed Change By: Oleg Nenashev Component/s: subversion-plugin Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-32553) svn: PROPFIND request failed
Title: Message Title Oleg Nenashev commented on JENKINS-32553 Re: svn: PROPFIND request failed Fixed the component Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [_unsorted] (JENKINS-32798) apt-get: Failed to fetch http://pkg.jenkins-ci.org
Title: Message Title Oleg Nenashev commented on JENKINS-32798 Re: apt-get: Failed to fetch http://pkg.jenkins-ci.org Moving the issue to the INFRA project, increasing priority Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [copyartifact-plugin] (JENKINS-32664) Copy Artifact plugin parameter passing via curl throws exception
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-32664 Copy Artifact plugin parameter passing via curl throws exception Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [copyartifact-plugin] (JENKINS-32664) Copy Artifact plugin parameter passing via curl throws exception
Title: Message Title Oleg Nenashev commented on JENKINS-32664 Re: Copy Artifact plugin parameter passing via curl throws exception ikedam No, I don't. Seems I have not removed the assignee after moving this issue from _unsorted Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-23518) GitHub webhooks and concurrent builds don't work
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-23518 GitHub webhooks and concurrent builds don't work Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-23518) GitHub webhooks and concurrent builds don't work because git plugin won't poll concurrently
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-23518 GitHub webhooks and concurrent builds don't work because git plugin won't poll concurrently Change By: Mark Waite Summary: GitHub webhooks and concurrent builds don't work because git plugin won't poll concurrently Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cucumber-plugin] (JENKINS-32804) Cucumber 'pretty' reports are not displayed
Title: Message Title Christopher Orr commented on JENKINS-32804 Re: Cucumber 'pretty' reports are not displayed I would guess that this is a Content Security Policy issue, which should supposedly be fixed in the next release: https://github.com/jenkinsci/cucumber-reports-plugin/issues/7#issuecomment-180856563 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-32290) New build jobs show running for 46 years and counting until it goes to completion
Title: Message Title Sabarish Venkatraman commented on JENKINS-32290 Re: New build jobs show running for 46 years and counting until it goes to completion The bug filed was seen in Jenkins v1.597 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-32824) Ignore specific users in Git plugin isn't working correctly if i was working in all the branches at the same job
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-32824 Ignore specific users in Git plugin isn't working correctly if i was working in all the branches at the same job Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-18079) GitHub Push always builds if workspace is on offline slave node
Title: Message Title Kanstantsin Shautsou edited a comment on JENKINS-18079 Re: GitHub Push always builds if workspace is on offline slave node Works as designed , not a bug, closed . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-19994) Unable to delete workspace
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-19994 Unable to delete workspace Change By: Kanstantsin Shautsou Component/s: github-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [template-project-plugin] (JENKINS-27378) Build when a change is pushed to GitHub so follow Use SCM from another project
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-27378 Build when a change is pushed to GitHub so follow Use SCM from another project Change By: Kanstantsin Shautsou Component/s: github-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-23518) GitHub webhooks and concurrent builds don't work
Title: Message Title Kanstantsin Shautsou commented on JENKINS-23518 Re: GitHub webhooks and concurrent builds don't work That's happens because github-plugin only kicks git scm polling that do linear builds because of it's design. Github-plugin has nothing specific to concurrent builds AFAIK. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-22593) GitHub plugin doesn't build with inverse build strategy turned on
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-22593 GitHub plugin doesn't build with inverse build strategy turned on Change By: Kanstantsin Shautsou Component/s: git-plugin Component/s: github-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-32371) Excessive wait times to clear build/node assocation after job completes
Title: Message Title Matthew Mitchell commented on JENKINS-32371 Re: Excessive wait times to clear build/node assocation after job completes Saw this again, but in low GC pressure situation. See stack trace here. dotnet_corefx/nativecomp_ubuntu_release_prtest build 1848 spent around 20 mins waiting to finish Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [remoting] (JENKINS-32825) Deadlock in Channel Abort
Title: Message Title Andres Rodriguez created an issue Jenkins / JENKINS-32825 Deadlock in Channel Abort Issue Type: Bug Assignee: Andres Rodriguez Components: remoting Created: 07/Feb/16 8:39 PM Environment: Jenkins 1.625.3 Windows slaves (JNLP) Priority: Minor Reporter: Andres Rodriguez Deadlock situations similar to those described in remoting#36 However, in these cases the other side of the stack trace was: "NioChannelHub keys=3 gen=41: Computer.threadPoolForRemoting [#2]" id=224 (0xe0) state=BLOCKED cpu=76% - waiting to lock <0x28a9d2ba> (a hudson.remoting.Channel) owned by "Computer.threadPoolForRemoting [#5] for XXX" id=249 (0xf9) at hudson.remoting.Channel.terminate(Channel.java:833) at hudson.remoting.Channel$1.terminate(Channel.java:509) at hudson.remoting.AbstractByteArrayCommandTransport$1.terminate(AbstractByteArrayCommandTransport.java:71) at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:637) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at
[JIRA] [remoting] (JENKINS-32825) Deadlock in Channel Abort
Title: Message Title Andres Rodriguez started work on JENKINS-32825 Change By: Andres Rodriguez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-18079) GitHub Push always builds if workspace is on offline slave node
Title: Message Title Kanstantsin Shautsou commented on JENKINS-18079 Re: GitHub Push always builds if workspace is on offline slave node My summary is the next: Nothing can be done with current trigger in github-plugin. Migration to notifyCommit is impossible and will break existed installations. github-plugin is generic and contains ancient push trigger that kicks git scm polling. That's why git scm runs offline builds. If you want to have other kind of triggers you can wrote separate plugin. I'm in process of writing native GH polling/triggering of builds without git poll under https://github.com/jenkinsci/github-integration-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-18079) GitHub Push always builds if workspace is on offline slave node
Title: Message Title Kanstantsin Shautsou resolved as Not A Defect Works as designed. Jenkins / JENKINS-18079 GitHub Push always builds if workspace is on offline slave node Change By: Kanstantsin Shautsou Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-32252) Possible issue with how triggers are started
Title: Message Title Kanstantsin Shautsou commented on JENKINS-32252 Re: Possible issue with how triggers are started Not a github-plugin issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [multi-branch-project-plugin] (JENKINS-32252) Possible issue with how triggers are started
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-32252 Possible issue with how triggers are started Change By: Kanstantsin Shautsou Component/s: github-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-32824) Ignore specific users in Git plugin isn't working correctly if i was working in all the branches at the same job
Title: Message Title Mark Waite commented on JENKINS-32824 Re: Ignore specific users in Git plugin isn't working correctly if i was working in all the branches at the same job I don't think those issues will be fixed any time soon. I work on the git plugin and the git client plugin in my personal time, trying my best to carefully advance those two plugins without regressing them. I think that the use case you're describing is quite different from the use case which the plugin implements. I doubt that the use case you're describing could be implemented without major risks of incompatibility with existing use cases. You might want to evaluate other alternatives, like one of the multi-branch plugins. I'm currently using a multi-branch plugin that automatically creates and deletes jobs for each branch that matches a pattern specified in the job definition. I'm not sure that will be enough to resolve your use case, but I think it is a more likely chance that you could start with that, and then propose pull requests as necessary to the git plugin to give it the exclude capability you want, but in the context of a multi-branch use case. I find the automatically created and deleted jobs easier to understand than the git plugin's intermixing of multiple branches into the history of a single job. If that isn't workable for you, then you could consider paying someone to implement what you're seeking. I'm not available in that way, since my employer won't allow that, but there are probably others who are available. You could approach Cloudbees or Praqma or one of the other companies which provide commercial support for Jenkins, and could negotiate with them to seek the solution for your use case. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [workflow-plugin] (JENKINS-32819) Pipeline compilation error detection broken when using CSRF detection
Title: Message Title Antonio Muñiz commented on JENKINS-32819 Re: Pipeline compilation error detection broken when using CSRF detection Wondering what would be better: to add required headers or use the Ajax object from the forked prototype. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-18079) GitHub Push always builds if workspace is on offline slave node
Title: Message Title Alex Gray commented on JENKINS-18079 Re: GitHub Push always builds if workspace is on offline slave node All of our builds run on temporarily slaves too, so we get bitten by this. It's horrible. Our hacky workaround is as follows: Have the build be done on the "master" node (since master is always online) Have a build step that triggers another job that gets executed on a "slave" node that actually does the build. It works because the master is always online and thus always the job's workspace. It's crappy because it takes 2 builds: 1 on the master, 1 on a slave. Oh, and make sure you pass in the git hash to the slave job, because someone can make a commit in between the time it takes launch the second build. Super crappy, but it's a lot better than have a bazilion needless builds being fired. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-23518) GitHub webhooks and concurrent builds don't work
Title: Message Title Kanstantsin Shautsou assigned an issue to Mark Waite Jenkins / JENKINS-23518 GitHub webhooks and concurrent builds don't work Change By: Kanstantsin Shautsou Assignee: Kohsuke Kawaguchi Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-23518) GitHub webhooks and concurrent builds don't work
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-23518 GitHub webhooks and concurrent builds don't work Change By: Kanstantsin Shautsou Component/s: git-plugin Component/s: core Component/s: github-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-22593) GitHub plugin doesn't build with inverse build strategy turned on
Title: Message Title Kanstantsin Shautsou commented on JENKINS-22593 Re: GitHub plugin doesn't build with inverse build strategy turned on Inverse build strategy is the git-plugin feature. githubPushTrigger doesn't do anything specific in this case - it only kick GitSCM polling. Please disable github push trigger, enable standard time based Poll scm and ensure that it works. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-32371) Excessive wait times to clear build/node assocation after job completes
Title: Message Title Matthew Mitchell updated an issue Jenkins / JENKINS-32371 Excessive wait times to clear build/node assocation after job completes Change By: Matthew Mitchell Attachment: jenkins-job-ending-hang.txt Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-32824) Ignore specific users in Git plugin isn't working correctly if i was working in all the branches at the same job
Title: Message Title Aya Serry created an issue Jenkins / JENKINS-32824 Ignore specific users in Git plugin isn't working correctly if i was working in all the branches at the same job Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 07/Feb/16 5:48 PM Environment: Jenkins ver. 1.638 GIT plugin ver. 1.19.0 Labels: GITLAB excludedUsers Priority: Blocker Reporter: Aya Serry Requirements: I want one job, to get the source code from GIT repository, make some tests and then push some changes on the same repository. This job should be triggered once the source code is changed. This job should should work on all the branches.
[JIRA] [core] (JENKINS-32371) Excessive wait times to clear build/node assocation after job completes
Title: Message Title
Matthew Mitchell commented on JENKINS-32371
Re: Excessive wait times to clear build/node assocation after job completes
This code from the LogRotator looks pretty suspect (line 150). The initial call to size() as well as copy itself will iterate the list. I'm not quite sure what the solution here is, but avoiding the loading of all the builds is probably important. I wonder if you could almost just estimate the number of builds kept around based on some cached initial build number (lowest known build number) and the maximum build number. It wouldn't be exact, but it would be fast.
if(artifactNumToKeep!=null && artifactNumToKeep!=-1) { List> builds = job.getBuilds(); for (Run r : copy(builds.subList(Math.min(builds.size(), artifactNumToKeep), builds.size( { if (shouldKeepRun(r, lsb, lstb)) { continue; }
LOGGER.log(FINE, " {0}
is to be purged of artifacts", r); r.deleteArtifacts(); } }
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-32371) Excessive wait times to clear build/node assocation after job completes
Title: Message Title Matthew Mitchell edited a comment on JENKINS-32371 Re: Excessive wait times to clear build/node assocation after job completes Saw this again, but in low GC pressure situation. See stack trace here. dotnet_corefx/nativecomp_ubuntu_release_prtest build 1848 spent around 20 mins waiting to finish [^jenkins-job-ending-hang.txt] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-32824) Ignore specific users in Git plugin isn't working correctly if i was working in all the branches at the same job
Title: Message Title Aya Serry updated an issue Jenkins / JENKINS-32824 Ignore specific users in Git plugin isn't working correctly if i was working in all the branches at the same job Change By: Aya Serry *Requirements:*I want one job, to get the source code from GIT repository, make some tests and then push some changes on the same repository. - This job should be triggered once the source code is changed. - This job should should work on *all the branches*. *Job Description:*+Source Code Management:+ Branches to build: ** Additional Behaviours: Polling ignores commits from specific users: I have put my name.+Build Triggers:+Using "git notifyCommit" I have added a hook on gitlab to trigger the build on Jenkins.On "Build Triggers" section, I'm checking "Poll SCM" option.+Add, Commit & Push:+ I made the add and the commit using windows batch. Push: using git publisher, on "Add branches" i have added the name of the repository.*Problem:*The excluded user is not excluded all the time, which some times cause an infinite loop, and sometimes cause a lot of extra unnecessary builds.After a lot of investigations, i have checked the source code of the plugin, and i have understood the some reasons of the problem:1) The plugin is depending on the *last build revision*, to get "From" & "To" revision number, and this generate a problem, because the "From" of the last build could be for another branch, so it will git all the old revisions and sure this revision contains users not listed in the "Excluded users list", thus a new build will be triggered.2) If there were changes in three branches for example, and 2 branches should be ignored, but the third one should trigger a build, the three branches will be triggered.These are the problems i have discovered till now, could anyone tell me when these issues will be fixed? we are blocked a month ago on this problem, and no one is answering us. Add Comment
[JIRA] [copyartifact-plugin] (JENKINS-32664) Copy Artifact plugin parameter passing via curl throws exception
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-32664 Copy Artifact plugin parameter passing via curl throws exception Change By: ikedam Assignee: ikedam Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [copyartifact-plugin] (JENKINS-32664) Copy Artifact plugin parameter passing via curl throws exception
Title: Message Title ikedam resolved as Not A Defect Not supported. Jenkins uses Structured form submission, which builds up request contents with _javascript_. Jenkins doesn't ensure its behavior for broken request contents. That is, Jenkins ensures its behavior only for requests built with web browsers. Requests weitten manually and sent with curl are not supported. Jenkins / JENKINS-32664 Copy Artifact plugin parameter passing via curl throws exception Change By: ikedam Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-21336) ADMINISTER should not imply RUN_SCRIPTS
Title: Message Title
ikedam updated an issue
Jenkins / JENKINS-21336
ADMINISTER should not imply RUN_SCRIPTS
Change By:
ikedam
Anyone with {{RUN_SCRIPTS}} can go to {{/script}} and immediately grant themselves other permissions (or disable security altogether, or worse), so it is strictly more powerful than anything else, including {{ADMINISTER}}. Yet the {{impliedBy}} link normally grants {{RUN_SCRIPTS}} automatically to anyone with {{ADMINISTER}}, which is backward.Less obviously, with {{UPLOAD_PLUGINS}} you could do much the same, if you spent a moment writing a custom plugin with a malicious initializer and building an hpi file, then installing it dynamically. This leaves a bit more of an audit trail, but only barely. (Maybe {{SecurityListener}} should be notified whenever a script is run or a custom plugin uploaded, and by whom?)If (as is common) all these permissions are granted together to administrators and not at all to other users, there is no problem, but the illogical {{impliedBy}} relationship together with the relatively innocuous-sounding permission descriptions combine to make even many experienced Jenkins administrators unaware of the risks. t At a minimum, the descriptions of these three permissions must clearly state what they allow users to do and the implications.Next, {{ADMINISTER}} should no longer be taken to imply {{RUN_SCRIPTS}} or {{UPLOAD_PLUGINS}}, since such implications give the misleading impression that these are weaker permissions. They should need to be explicitly granted.(There is an unfortunate settings compatibility issue, that authorization strategy configurations which previously granted {{ADMINISTER}} explicitly to a user with the expectation that {{RUN_SCRIPTS}} would be granted implicitly would after such an update no longer grant {{RUN_SCRIPTS}}, since existing strategies typically serialize only granted permissions and make no mention of denied permissions. If popular strategies were fixed to distinguish implicitly from explicitly granted permissions, perhaps they could perform a one-time settings upgrade in which {{RUN_SCRIPTS}} were assumed granted to users previously having {{ADMINISTER}}.)Possibly {{RUN_SCRIPTS}} and {{UPLOAD_PLUGINS}} should even be made to imply {{ADMINISTER}}, as in effect they do.Note that it is possible to configure a customized system whereby some users get {{ADMINISTER}} but not either of the two other permissions mentioned here, as for example *.ci.cloudbees.com does. One of the changes needed is for the authorization strategy to ignore {{impliedBy}} for these cases. With {{CONFIGURE_UPDATECENTER}} you could perhaps trick someone with {{ADMINISTER}} into installing a "trojan horse" the next time they updated something, though you might be stymied by the signature check. There are other permissions which could be used to compromise a stock system, such as {{Computer.CONFIGURE}} (with {{CommandLauncher}}), or simply having nonzero executors on the master, so such a lockdown has to extend beyond the ACL unless various other operations in Jenkins are made to perform stricter checks.
[JIRA] [git-plugin] (JENKINS-32707) Git plugin built the same commit 1300 times
Title: Message Title Mark Waite commented on JENKINS-32707 Re: Git plugin built the same commit 1300 times Is your job that ran many times configured to allow concurrent builds? Jenkins jobs by default are not configured to allow concurrent builds. That was a critical part of the race condition described in JENKINS-31731. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [integrity-plugin] (JENKINS-32826) Polling failure on jobs with same name in different folders
Title: Message Title Bernd Spickers created an issue Jenkins / JENKINS-32826 Polling failure on jobs with same name in different folders Issue Type: Bug Assignee: Cletus D'Souza Components: integrity-plugin Created: 08/Feb/16 7:01 AM Environment: Jenkins 1.644, integrity-plugin 1.36, Cloudbees Folder plugin 5.1 Priority: Minor Reporter: Bernd Spickers Hi, I faced following problem if I setup jobs with the same name but located in different folders (cloudbees folder plugin). Except one job, all the others failed in SCM polling (using integrity-plugin) with "Table x not found". I tried the check the code and found that it looks like that the plugin uses Job.getName() instead of Job.getFullName() to store data. May be this the reason for the problem ? As for jobs with same name in different folders getName() returns only the name (without folders) where getFullName() includes the folder information and makes them unique. As I am fixed to old PTC version, a patch on 1.36 is welcome. Regards, Bernd
