[JIRA] (JENKINS-37223) Improve diagnosability of Agent protocol
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-37223 Improve diagnosability of Agent protocol Change By: SCM/JIRA link daemon Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37223) Improve diagnosability of Agent protocol
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37223 Re: Improve diagnosability of Agent protocol Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/TcpSlaveAgentListener.java test/src/test/java/hudson/TcpSlaveAgentListenerTest.java http://jenkins-ci.org/commit/jenkins/fab0938ee43b05126fa390d021eeac1673badee5 Log: Merge pull request #2496 from jenkinsci/JENKINS-37223 [FIXED JENKINS-37223] Compare: https://github.com/jenkinsci/jenkins/compare/55203ebeed1b...fab0938ee43b Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37188) 2nd failure emails being sent even when build is successful
Title: Message Title David van Laatum commented on JENKINS-37188 Re: 2nd failure emails being sent even when build is successful I am unable to reproduce are you able to reproduce on a simple job with just this plugin and a shell step to make the build pass or fail? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37038) Jenkins can't send mail
Title: Message Title David van Laatum commented on JENKINS-37038 Re: Jenkins can't send mail I can not explain as I do not know how your environment is set up but I do know that from time to time at work jenkins emails end up in spam and I have to whitelist it again. See https://github.com/jenkinsci/email-ext-plugin/blob/3c3c89a189b419c4a7eaaf4dc6a3a199a5d213cc/src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java#L358-L471 for the exact code that sends the email Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard on Jenkins 2.7
Title: Message Title Keith Zantow updated JENKINS-37232 Jenkins / JENKINS-37232 ATH test fails on NEW ITEM Wizard on Jenkins 2.7 Change By: Keith Zantow Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard on Jenkins 2.7
Title: Message Title Keith Zantow started work on JENKINS-37232 Change By: Keith Zantow Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard on Jenkins 2.7
Title: Message Title Keith Zantow assigned an issue to Keith Zantow Jenkins / JENKINS-37232 ATH test fails on NEW ITEM Wizard on Jenkins 2.7 Change By: Keith Zantow Assignee: Manuel Franco Keith Zantow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37185) Checkout timeout is not honored when used with local branch parameter
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37185 Re: Checkout timeout is not honored when used with local branch parameter Code changed in jenkins User: Quentin Dufour Path: src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/742861e9e83e5775d48f33c99c2827cbe37944ed Log: JENKINS-37185 Add a test to check timeouts on checkout Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37185) Checkout timeout is not honored when used with local branch parameter
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37185 Re: Checkout timeout is not honored when used with local branch parameter Code changed in jenkins User: Quentin Dufour Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/f2c632c6a539d56ee2acf82161bd534e2d86733d Log: JENKINS-37185 Honor checkout timeout Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37185) Checkout timeout is not honored when used with local branch parameter
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37185 Re: Checkout timeout is not honored when used with local branch parameter Code changed in jenkins User: Quentin Dufour Path: src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/4187c8bb3e46e23c48260e524b0e53808da899ce Log: JENKINS-37185 Fix checkTimeout() and its associated tests Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37185) Checkout timeout is not honored when used with local branch parameter
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37185 Re: Checkout timeout is not honored when used with local branch parameter Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/ea305aaa62389c98aeb14e3dd290cbf2f3d04aca Log: Merge pull request #214 from superboum/master JENKINS-37185 Honor checkout timeout Compare: https://github.com/jenkinsci/git-client-plugin/compare/00731f9e3d22...ea305aaa6238 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard on Jenkins 2.7
Title: Message Title Manuel Recena Soto assigned an issue to Manuel Franco Jenkins / JENKINS-37232 ATH test fails on NEW ITEM Wizard on Jenkins 2.7 Change By: Manuel Recena Soto Assignee: Oliver Gondža Manuel Franco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard on Jenkins 2.7
Title: Message Title valentina armenise commented on JENKINS-37232 Re: ATH test fails on NEW ITEM Wizard on Jenkins 2.7 Jenkins 2.0 seems working instead Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard on Jenkins 2.7
Title: Message Title
valentina armenise updated an issue
Jenkins / JENKINS-37232
ATH test fails on NEW ITEM Wizard on Jenkins 2.7
Change By:
valentina armenise
Summary:
ATH test fails on NEW ITEM Wizard on Jenkins 2.7
When running ATH tests agains Jenkins 2. 0 7 the New Item Wizard fails to enable the OK button after the name is inserted and the type of item selected.Some investigation and debugging showed that:1) the item name is inserted and stored with jquery, no warning shown. Validation of OK button fails cause the item time has not been selected yet (OK button not shown yet).2) the item type is selected3) right after selecting the item type a red warning is show on the item name input text ("The field cannot be empty, please enter a valid name")3) the OK button is not shown case now the validation fails on the item name (empty).If while debugging, you click anywhere on the page after the item type is selected, the red warning goes away and the OK button shown. Sending Keys.TAB with selenium (or changing focus) does not work instead.Looks like this condition is false https://github.com/jenkinsci/jenkins/blob/5f9614433ec3bd9057097bbe2af7d445e6cd918e/war/src/main/js/add-item.js#L178.The ATH tests are failing here https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/main/java/org/jenkinsci/test/acceptance/po/JobsMixIn.java#L25
Add Comment
[JIRA] (JENKINS-37212) Jenkins CLI trouble installing plugin hpi
Title: Message Title Daniel Beck commented on JENKINS-37212 Re: Jenkins CLI trouble installing plugin hpi what's the full command line for the CLI you use? No placeholders, everything verbatim including plugin file name. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37200) Firefox CPU spinning
Title: Message Title Daniel Beck commented on JENKINS-37200 Re: Firefox CPU spinning Tom FENNELLY was able to reproduce with the URLs I provided. Good: https://ci.blueocean.io/blue/organizations/jenkins/Acceptance-Tests/activity Bad: https://ci.blueocean.io/blue/organizations/jenkins/admin%2Frestart-blueocean/activity ~140 vs. ~360 entries. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31487) Job status not updated in web UI during build
Title: Message Title Daniel Beck commented on JENKINS-31487 Re: Job status not updated in web UI during build Anyone want to test 1.632 and 1.633 to determine whether this issue was introduced in the latter release, with build history pagination? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31487) Job status not updated in web UI during build
Title: Message Title Daniel Beck commented on JENKINS-31487 Re: Job status not updated in web UI during build Allan BURDAJEWICZ Actually, I was able to observe this in 2.14 for those progress bars that have been present when the page was loaded. Those that appeared later were correctly progressed. That also means that clicking (e.g.) "Status" to load the job index page will effectively halt progress of the build just triggered clicking "Build Now". I suspect that the page redirect due to the parameters form resulted in your observation, but it has nothing to do with parameterized builds. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard
Title: Message Title
valentina armenise updated an issue
Jenkins / JENKINS-37232
ATH test fails on NEW ITEM Wizard
Change By:
valentina armenise
When running ATH tests agains Jenkins 2.0 the New Item Wizard fails to enable the OK button after the name is inserted and the type of item selected.Some investigation and debugging showed that:1) the item name is inserted and stored with jquery, no warning shown. Validation of OK button fails cause the item time has not been selected yet (OK button not shown yet).2) the item type is selected3) right after selecting the item type a red warning is show on the item name input text ("The field cannot be empty, please enter a valid name")3) the OK button is not shown case now the validation fails on the item name (empty).If while debugging, you click anywhere on the page after the item type is selected, the red warning goes away and the OK button shown. Sending Keys.TAB with selenium (or changing focus) does not work instead. Looks like this condition is false https://github.com/jenkinsci/jenkins/blob/5f9614433ec3bd9057097bbe2af7d445e6cd918e/war/src/main/js/add-item.js#L178.The ATH tests are failing here https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/main/java/org/jenkinsci/test/acceptance/po/JobsMixIn.java#L25
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard
Title: Message Title
valentina armenise created an issue
Jenkins / JENKINS-37232
ATH test fails on NEW ITEM Wizard
Issue Type:
Bug
Assignee:
Oliver Gondža
Components:
acceptance-test-harness
Created:
2016/Aug/05 11:46 PM
Environment:
Firefox 41, same behaviour detected on 46. Mac OSX
Priority:
Minor
Reporter:
valentina armenise
When running ATH tests agains Jenkins 2.0 the New Item Wizard fails to enable the OK button after the name is inserted and the type of item selected. Some investigation and debugging showed that: 1) the item name is inserted and stored with jquery, no warning shown. Validation of OK button fails cause the item time has not been selected yet (OK button not shown yet). 2) the item type is selected 3) right after selecting the item type a red warning is show on the item name input text ("The field cannot be empty, please enter a valid name") 3) the OK button is not shown case now the validation fails on the item name (empty). If while debugging, you click anywhere on the page after the item type is selected, the red warning goes away and the OK button shown. Sending Keys.TAB with selenium (or changing focus) does not work instead.
[JIRA] (JENKINS-37223) Improve diagnosability of Agent protocol
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37223 Re: Improve diagnosability of Agent protocol Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/TcpSlaveAgentListener.java http://jenkins-ci.org/commit/jenkins/57846475f7bd270ea9624144bbd54447ff47dedb Log: JENKINS-37223 report the server's address, too Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37223) Improve diagnosability of Agent protocol
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37223 Re: Improve diagnosability of Agent protocol Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/TcpSlaveAgentListener.java http://jenkins-ci.org/commit/jenkins/ab57c02646ded9ebf921cddbf798890bc2a08805 Log: JENKINS-37223 report the server's address, too Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37231) CORS allowed origins list never updated
Title: Message Title Zoltán Nagy updated an issue Jenkins / JENKINS-37231 CORS allowed origins list never updated Change By: Zoltán Nagy Changes to the list of allowed origins are silently ignored. This is a potentially high-impact security risk - the UI shows security settings that are not, in fact, in effect. It's also bad UX.Relevant code:* https://github.com/jenkinsci/cors-filter-plugin/blob/master/src/main/java/org/jenkinsci/plugins/corsfilter/AccessControlsFilter.java#L37 declares the list of allowed origins as an instance property* https://github.com/jenkinsci/cors-filter-plugin/blob/master/src/main/java/org/jenkinsci/plugins/corsfilter/AccessControlsFilter.java#L105 rebuilds the list from the string configuration option if and only if the list is empty The list is not cleared / updated when configuration changes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-37231) CORS allowed origins list never updated
Title: Message Title Zoltán Nagy created an issue Jenkins / JENKINS-37231 CORS allowed origins list never updated Issue Type: Bug Assignee: Udaypal Aarkoti Components: cors-filter Created: 2016/Aug/05 11:16 PM Priority: Major Reporter: Zoltán Nagy Changes to the list of allowed origins are silently ignored. This is a potentially high-impact security risk - the UI shows security settings that are not, in fact, in effect. It's also bad UX. Relevant code: https://github.com/jenkinsci/cors-filter-plugin/blob/master/src/main/java/org/jenkinsci/plugins/corsfilter/AccessControlsFilter.java#L37 declares the list of allowed origins as an instance property https://github.com/jenkinsci/cors-filter-plugin/blob/master/src/main/java/org/jenkinsci/plugins/corsfilter/AccessControlsFilter.java#L105 rebuilds the list from the string configuration option if and only if the list is empty Add Comment
[JIRA] (JENKINS-37229) CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on pipeline job shallow clone
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-37229 CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on pipeline job shallow clone Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37229) CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on shallow clone
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-37229
CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on shallow clone
Change By:
Mark Waite
Red Hat Enterprise Linux 7 includes command line git 1.8.3.1. When the job definition defined in my [jenkins-bugs commit c944ccd|https://github.com/MarkEWaite/jenkins-bugs/commit/c944ccd321a57922e8ce3112c47ee63f5b839394] git repository is evaluated in a multi-branch pipeline job, it fails to clone the repository. The [job definition - commit 426dce753|https://github.com/MarkEWaite/docker/commit/426dce753ac52ebd4dcdd5d06efda17241f3d9f0] shows the problem when run on RHEL 7.The same job definition does not show the problem when run on Ubuntu 14 (git 2.9.2), Debian 8 (git 1.9), or Windows (git 2.9.2) {noformat}Fetching upstream changes from https://github.com/MarkEWaite/jenkins-bugs > git fetch --no-tags --progress https://github.com/MarkEWaite/jenkins-bugs +refs/heads/JENKINS-36507:refs/remotes/bugs-origin/JENKINS-36507 --prune --depth=3 # timeout=3ERROR: Error fetching remote repo 'bugs-origin'hudson.plugins.git.GitException: Failed to fetch from https://github.com/MarkEWaite/jenkins-bugs at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1051) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1082) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: hudson.plugins.git.GitException: Command "git fetch --no-tags --progress https://github.com/MarkEWaite/jenkins-bugs +refs/heads/JENKINS-36507:refs/remotes/bugs-origin/JENKINS-36507 --prune --depth=3" returned status code 128:stdout: stderr: fatal: git fetch-pack: expected shallow listfatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1735) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1478) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315) at
[JIRA] (JENKINS-37228) Offer the possibility to disable the automatic commit comment
Title: Message Title Simon GUEROUT closed an issue as Duplicate Sorry about duplicating this issue ! Jenkins / JENKINS-37228 Offer the possibility to disable the automatic commit comment Change By: Simon GUEROUT Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-37229) CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on pipeline job shallow clone
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-37229 CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on pipeline job shallow clone Change By: Mark Waite Summary: CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on pipeline job shallow clone Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37229) CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on shallow clone
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-37229
CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on shallow clone
Change By:
Mark Waite
Red Hat Enterprise Linux 7 includes command line git 1.8.3.1. When the job definition defined in my [jenkins-bugs commit c944ccd|https://github.com/MarkEWaite/jenkins-bugs/commit/c944ccd321a57922e8ce3112c47ee63f5b839394] git repository is evaluated in a multi-branch pipeline job, it fails to clone the repository. The [job definition - commit 426dce753|https://github.com/MarkEWaite/docker/commit/426dce753ac52ebd4dcdd5d06efda17241f3d9f0] shows the problem when run on RHEL 7.The same job definition does not show the problem when run on Ubuntu 14 (git 2.9.2), Debian 8 (git 1.9), or Windows (git 2.9.2) . Job console output looks like this: {noformat}Fetching upstream changes from https://github.com/MarkEWaite/jenkins-bugs > git fetch --no-tags --progress https://github.com/MarkEWaite/jenkins-bugs +refs/heads/JENKINS-36507:refs/remotes/bugs-origin/JENKINS-36507 --prune --depth=3 # timeout=3ERROR: Error fetching remote repo 'bugs-origin'hudson.plugins.git.GitException: Failed to fetch from https://github.com/MarkEWaite/jenkins-bugs at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1051) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1082) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: hudson.plugins.git.GitException: Command "git fetch --no-tags --progress https://github.com/MarkEWaite/jenkins-bugs +refs/heads/JENKINS-36507:refs/remotes/bugs-origin/JENKINS-36507 --prune --depth=3" returned status code 128:stdout: stderr: fatal: git fetch-pack: expected shallow listfatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1735) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1478) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315) at
[JIRA] (JENKINS-37229) CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on shallow clone
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-37229 CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on shallow clone Issue Type: Improvement Assignee: Mark Waite Components: git-client-plugin, git-plugin Created: 2016/Aug/05 10:24 PM Environment: Red Hat Enterprise Linux 7 Jenkins 2.7.2 Git plugin 2.5.3 (and 3.0.0-beta) Git client plugin 1.19.7 (and 2.0.0-beta) Priority: Minor Reporter: Mark Waite Red Hat Enterprise Linux 7 includes command line git 1.8.3.1. When the job definition defined in my jenkins-bugs commit c944ccd git repository is evaluated in a multi-branch pipeline job, it fails to clone the repository. The job definition - commit 426dce753 shows the problem when run on RHEL 7. The same job definition does not show the problem when run on Ubuntu 14 (git 2.9.2), Debian 8 (git 1.9), or Windows (git 2.9.2) Add Comment
[JIRA] (JENKINS-37230) SCMTrigger uses an inconsistent "spec" member name
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-37230 SCMTrigger uses an inconsistent "spec" member name Issue Type: Bug Assignee: Andrew Bayer Components: core Created: 2016/Aug/05 10:24 PM Labels: community-bee Priority: Minor Reporter: R. Tyler Croy When attempting to use the Pipeline properties step to define the SCMTrigger for a Pipeline I originally tried: properties([ pipelineTriggers([ [$class: "SCMTrigger", spec: "H/10 * * * *"], ]) ]) This resulted in a NPE because the member isn't named spec java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:258) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:372) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerceList(DescribableModel.java:453) at
[JIRA] (JENKINS-37228) Offer the possibility to disable the automatic commit comment
Title: Message Title Simon GUEROUT created an issue Jenkins / JENKINS-37228 Offer the possibility to disable the automatic commit comment Issue Type: Improvement Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Aug/05 10:17 PM Environment: Jenkins 2.16 Bitbucket Branch Source Plugin 1.5 Labels: bitbucket Priority: Major Reporter: Simon GUEROUT Can we have find a way to disable the comment automatically created by the plugin ? We use Bitbucket comments for a specific reason in our team, and with the use of this plugin, people tend to ignore the emails they get from Bitbucket about their commits. It would be really good if this could be disabled in the job configuration or in the pipeline itself ! Add Comment
[JIRA] (JENKINS-31791) Cannot load job pages due to HistoryWidget hanging
Title: Message Title DJ Lee commented on JENKINS-31791 Re: Cannot load job pages due to HistoryWidget hanging Kevin Phillips in my company's Jenkins instance, we were having problems like this with MultiJob and without, as long as there were a ton of builds in the history. Our Jenkins master is on an AWS instance with EBS disk, so the I/O is a bit slower than a physical machine, which is probably a contributing factor. The fix for above will be included in Jenkins 2.17. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31663) Cannot load job summary page for job with huge history
Title: Message Title DJ Lee resolved as Duplicate Jenkins / JENKINS-31663 Cannot load job summary page for job with huge history Change By: DJ Lee Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37203) "Override Authentication Token?" do not work
Title: Message Title Peter Tierno commented on JENKINS-37203 Re: "Override Authentication Token?" do not work Thanks for the report. I'll look into this soon. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37201) Do not store retrived secrets in build.xml.
Title: Message Title Peter Tierno commented on JENKINS-37201 Re: Do not store retrived secrets in build.xml. Thanks for pointing this out. I'll look into it and see about a solution. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37226) Downloading JDK gives ERROR: SEVERE ERROR occurs
Title: Message Title Jesper Jensen updated an issue Jenkins / JENKINS-37226 Downloading JDK gives ERROR: SEVERE ERROR occurs Change By: Jesper Jensen Environment: Windows 2008 server using jre 1.8.0_102 using Jenkins 2.15 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Jesse Glick updated JENKINS-29922 Jenkins / JENKINS-29922 Promote delegates of metasteps to top-level functions, deprecate $class Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Jesse Glick commented on JENKINS-29922 Re: Promote delegates of metasteps to top-level functions, deprecate $class I filed JENKINS-37227 for the follow-up task of updating checkout. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37227) Metastep support for checkout step
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-37227 Metastep support for checkout step Issue Type: New Feature Assignee: Unassigned Components: workflow-plugin Created: 2016/Aug/05 9:21 PM Priority: Major Reporter: Jesse Glick As noted JENKINS-29922, we should extend simplified syntax to the checkout step used with SCMs. Proposed task list: make checkout be a metastep add a @Symbol to a sample SCM, such as hg on MercurialSCM, and verify that hg can then be run like a top-level step define an API by which GenericSCMStep/config.jelly could detect that Snippetizer were passing it a particular delegateDescriptor (like MercurialSCM.DescriptorImpl) and switch to an alternate mode in which f:dropdownDescriptorSelector is replaced by the inlined MercurialSCM/config.jelly investigate whether @Symbol plus tweaks to the parameters on GitSCM and SubversionSCM would allow us to suppress the custom git and subversion step extensions (thus using checkout implicitly) when running on a sufficiently new version of workflow-cps + workflow-scm-step update WorkflowPluginTest.linearFlow (or .parallelTests) to demonstrate that git now automatically accepts, say, extensions
[JIRA] (JENKINS-37226) Downloading JDK gives ERROR: SEVERE ERROR occurs
Title: Message Title Jesper Jensen created an issue Jenkins / JENKINS-37226 Downloading JDK gives ERROR: SEVERE ERROR occurs Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Aug/05 9:20 PM Environment: Windows 2008 server using jre 1.8.0_102 Priority: Major Reporter: Jesper Jensen Jenkins configured to automatically download and install Java from standard download source. 17:10:07 Installing JDK jdk-8u102-oth-JPR 17:10:07 Downloading JDK from http://download.oracle.com/otn-pub/java/jdk/8u102-b14/jdk-8u102-windows-x64.exe 17:10:07 ERROR: SEVERE ERROR occurs 17:10:07 org.jenkinsci.lib.envinject.EnvInjectException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target 17:10:07 at org.jenkinsci.plugins.envinject.service.EnvInjectVariableGetter.getBuildVariables(EnvInjectVariableGetter.java:91) 17:10:07 at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironmentWithoutJobPropertyObject(EnvInjectListener.java:233) 17:10:07 at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:46) 17:10:07 at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:572) 17:10:07 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:492) 17:10:07 at hudson.model.Run.execute(Run.java:1720) 17:10:07 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) 17:10:07 at hudson.model.ResourceController.execute(ResourceController.java:98) 17:10:07 at hudson.model.Executor.run(Executor.java:404) 17:10:07 Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX
[JIRA] (JENKINS-37218) ClassFilter uses Regexs to match String.startsWith patterns
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37218 Re: ClassFilter uses Regexs to match String.startsWith patterns Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/remoting/ClassFilter.java http://jenkins-ci.org/commit/remoting/6664aaec4773fc3a8a8320c9e97c462252ca749b Log: JENKINS-37218 Fix findbugs issues Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37031) tcpSlaveAgentListener should publish supported agent protocols to speed up connection setup
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37031 Re: tcpSlaveAgentListener should publish supported agent protocols to speed up connection setup Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/remoting/Engine.java http://jenkins-ci.org/commit/remoting/d54c88615163d30047e5b4dde8dcd08792032cd4 Log: JENKINS-37031 Address code review comments Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37223) Improve diagnosability of Agent protocol
Title: Message Title Kohsuke Kawaguchi reopened an issue Not yet merged to master Jenkins / JENKINS-37223 Improve diagnosability of Agent protocol Change By: Kohsuke Kawaguchi Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37223) Improve diagnosability of Agent protocol
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-37223 Improve diagnosability of Agent protocol Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37223) Improve diagnosability of Agent protocol
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37223 Re: Improve diagnosability of Agent protocol Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/TcpSlaveAgentListener.java test/src/test/java/hudson/TcpSlaveAgentListenerTest.java http://jenkins-ci.org/commit/jenkins/172df6a7dfca56477c471c381687599c80f5113b Log: [FIXED JENKINS-37223] Added a simple diagnostic HTTP response to the TcpSlaveAgentListener. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37069) Permission denied on durable task directory when using docker.image.inside step on fresh install of jenkins
Title: Message Title Vitor Dantas commented on JENKINS-37069 Re: Permission denied on durable task directory when using docker.image.inside step on fresh install of jenkins Inside the container, the jenkins user and jenkins group don't exist (992:989 on this setup). I checked this by looking at the /etc/passwd and /etc/groups files using docker exec cat . Is it supposed to be that way? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Jesse Glick commented on JENKINS-29922 Re: Promote delegates of metasteps to top-level functions, deprecate $class (Artificial class loading semantics in JenkinsRule probably hid this problem. Updating acceptance tests to prove that things work properly in a more realistic environment.) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37225) Sometimes too many slaves are created and then not pruned
Title: Message Title Benn Linger created an issue Jenkins / JENKINS-37225 Sometimes too many slaves are created and then not pruned Issue Type: Bug Assignee: Jan Roehrich Attachments: jenkins.log Components: amazon-ecs-plugin Created: 2016/Aug/05 7:10 PM Environment: Jenkins ver. 1.651.2 Using the official Docker image, running on an Amazon ECS cluster. Container instance uses official Amazon ECS AMI (64 bit). Amazon EC2 Container Service plugin v 1.4 Running from behind an ELB. Jenkins slaves running on a separate ECS cluster. Priority: Minor Reporter: Benn Linger Occasionally, I'll notice in the Jenkins web interface that there are a bunch (6-12) ECS slaves that are online, but not doing anything. They don't get pruned or stop on their own. I've just been deleting them manually by clearing out all running tasks from ECS when I know no jobs are running, but we're hoping to implement autoscaling for our ECS slaves soon and that's not going to work well if we have a bunch of slaves taking up resources but not really being used. It happened today when we had a job with concurrency allowed running twice at the same time. I'm not sure if that's related or not. Certainly happy to do more troubleshooting, but not sure exactly what to look for. I've got the log for today here that shows it happening. Relevant area starts on line 77 when the first job kicks off (it had been idle prior to that). The jobs got done, but by line 421 it's now saying it's up to 13 computers. After that, there's basically a loop where they all drop at once and then reconnect. Let me know
[JIRA] (JENKINS-32556) Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin
Title: Message Title Daniel Sobral commented on JENKINS-32556 Re: Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin I got the same problem with Stack Pull Request Builder. javax.servlet.ServletException: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:249) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:176) at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145) at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92) at com.marvelution.jenkins.plugins.jira.filter.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:51) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.marvelution.jenkins.plugins.jira.filter.OAuthFilter.doFilter(OAuthFilter.java:87) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at
[JIRA] (JENKINS-37224) Snippet Generator produces incorrect output for "Merge strategy" of "Merge before build" for GIT
Title: Message Title
Daniel Sobral created an issue
Jenkins / JENKINS-37224
Snippet Generator produces incorrect output for "Merge strategy" of "Merge before build" for GIT
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
2016/Aug/05 6:39 PM
Environment:
Jenkins 2.16, Git 2.53, Pipeline SCM Step 2.2
Priority:
Major
Reporter:
Daniel Sobral
When adding the additional behavior of "Merge before build", the "Merge strategy" is generated like this: {{ mergeStrategy: }} This is related to JENKINS-26753 (dup), JENKINS-26619, but that one is resolved and the problem is happening.
Add Comment
[JIRA] (JENKINS-37223) Improve diagnosability of Agent protocol
Title: Message Title Kohsuke Kawaguchi created an issue Jenkins / JENKINS-37223 Improve diagnosability of Agent protocol Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: core Created: 2016/Aug/05 6:38 PM Priority: Minor Reporter: Kohsuke Kawaguchi When troubleshooting the connectivity of JNLP build agents, it'd be nice if the TcpSlaveAgentListener provides more diagnosability. Currently, a protocol is binary, so it prevents the standard diagnostic tools like 'nc' and 'telnet' to work. The situation where this gets frustrating is when you have network middle layers, such as port forwarder, iptables, and other such things. A basic "Ping? Pong!" would help users perform trouble-shooting quickly. Add Comment
[JIRA] (JENKINS-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Jesse Glick commented on JENKINS-29922 Re: Promote delegates of metasteps to top-level functions, deprecate $class Just found that the @Symbol in the junit plugin does not work in Jenkins 1.x, I think because the plugin declares a dependency only on the annotation JAR, when really it needs a dependency on the structs plugin. In Jenkins 2.x, the inclusion of the annotation in core apparently lets it work. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Title: Message Title Logan V commented on JENKINS-21905 Re: intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream I'm seeing this on Jenkins 2.7.1 http://cdn.pasteraw.com/9pfrpe9kd82cbxj82revnqn6gs8ogvk Roughly 40-50 files per build, all log files. We're seeing the failure about 75+% of the time. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol4Handler.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol4PlainHandler.java http://jenkins-ci.org/commit/remoting/2ce2f8ac22816813b413f09b37d2c05151eb1b3a Log: JENKINS-36871 Fix failing tests Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/test/java/org/jenkinsci/remoting/engine/JnlpProtocolHandlerTest.java http://jenkins-ci.org/commit/remoting/ac9bcabdb7a69e0cf8e49ca92ce9cad8fd9b6842 Log: JENKINS-36871 Forgot to test JNLP4-plaintext Compare: https://github.com/jenkinsci/remoting/compare/0529c154be04...ac9bcabdb7a6 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37219) Option to suppress automatic SCM trigger from Jenkinsfile
Title: Message Title Andrew Bayer started work on JENKINS-37219 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37222) Fatal error using the build-name-setter plugin
Title: Message Title Jeff Tresselt created an issue Jenkins / JENKINS-37222 Fatal error using the build-name-setter plugin Issue Type: Bug Assignee: Lev Mishin Components: build-name-setter-plugin Created: 2016/Aug/05 4:54 PM Environment: Jenkins 2.16 build-name-setter plugin v1.6.5 Priority: Minor Reporter: Jeff Tresselt I'm trying to use the build name setter plugin, but getting a fatal error that is preventing my job from running: 11:40:06 Set build name. 11:40:06 FATAL: org/parboiled/transform/ClassNodeInitializer 11:40:06 java.lang.IncompatibleClassChangeError: org/parboiled/transform/ClassNodeInitializer 11:40:06 at org.parboiled.transform.ParserTransformer.extendParserClass(ParserTransformer.java:44) 11:40:06 at org.parboiled.transform.ParserTransformer.transformParser(ParserTransformer.java:38) 11:40:06 at org.parboiled.Parboiled.createParser(Parboiled.java:54) 11:40:06 at org.jenkinsci.plugins.tokenmacro.Parser.process(Parser.java:63) 11:40:06 at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:194) 11:40:06 at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:223) 11:40:06 at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:206) 11:40:06 at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:198) 11:40:06 at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setDisplayName(BuildNameSetter.java:74) 11:40:06 at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setUp(BuildNameSetter.java:57) 11:40:06 at hudson.model.Build$BuildExecution.doRun(Build.java:156) 11:40:06 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) 11:40:06 at hudson.model.Run.execute(Run.java:1720) 11:40:06 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 11:40:06 at
[JIRA] (JENKINS-37210) dynamically load a groovy class and invoke a method in pipeline script
Title: Message Title Oleg Nenashev commented on JENKINS-37210 Re: dynamically load a groovy class and invoke a method in pipeline script There is an "_unsorted" component created specially for such case when you are not sure about the component to be used Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37210) dynamically load a groovy class and invoke a method in pipeline script
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-37210 dynamically load a groovy class and invoke a method in pipeline script Change By: Oleg Nenashev Component/s: workflow-plugin Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37210) dynamically load a groovy class and invoke a method in pipeline script
Title: Message Title Oleg Nenashev assigned an issue to Jesse Glick Jenkins / JENKINS-37210 dynamically load a groovy class and invoke a method in pipeline script Change By: Oleg Nenashev Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37219) Option to suppress automatic SCM trigger from Jenkinsfile
Title: Message Title Andrew Bayer commented on JENKINS-37219 Re: Option to suppress automatic SCM trigger from Jenkinsfile PR up at https://github.com/jenkinsci/workflow-multibranch-plugin/pull/26 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33345) Allow to specify 'Pull Image Secret' to use private docker registries
Title: Message Title Kevin Moser commented on JENKINS-33345 Re: Allow to specify 'Pull Image Secret' to use private docker registries Have create PR: https://github.com/jenkinsci/kubernetes-plugin/pull/65 for this Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21670) Option to anonymize customer labels
Title: Message Title Sam Gleske commented on JENKINS-21670 Re: Option to anonymize customer labels User-defined list of expressions to search and replace can help with job names that have no convention. An enterprise may have keywords which they don't want leaked. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36863) [Gitlab plugin] Credentials drop-down doesn't show API token credential!
Title: Message Title Mark Parker commented on JENKINS-36863 Re: [Gitlab plugin] Credentials drop-down doesn't show API token credential! Having the same issue as well. Jenkins 2.7 and Gitlab 1.3.0 AND Jenkins 1.651.3 and Gitlab 1.3.0. The token appears to get created, because when I try to create another token with the same name, it tells me "This ID already in use" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25053) Record process ID of spawned process on Windows
Title: Message Title Mark Austin commented on JENKINS-25053 Re: Record process ID of spawned process on Windows With some modifications, perhaps using the process of capturing the PID from the attached bat script could help us track things better. AFAIK, the wmic command has been available for quite some time, should go as far back as windows xp and server 2003, so I doubt we'd cause noticeable breakage by calling out to this tool. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25053) Record process ID of spawned process on Windows
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-25053 Record process ID of spawned process on Windows Change By: Mark Austin Attachment: getPID.bat Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/remoting/Engine.java http://jenkins-ci.org/commit/remoting/41841e520b6cfec0bb1179cf33ef969aec230886 Log: JENKINS-36871 Use Blocking-I/O for the clients Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/test/java/org/jenkinsci/remoting/engine/JnlpProtocolHandlerTest.java http://jenkins-ci.org/commit/remoting/0529c154be04e030855a801e65cd0d096ae8130f Log: JENKINS-36871 Test timing is needs longer when dealing with slower build agents Compare: https://github.com/jenkinsci/remoting/compare/19093e34f77f...0529c154be04 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37221) NullPointerException when running JacocoPublisher
Title: Message Title Simon GUEROUT created an issue Jenkins / JENKINS-37221 NullPointerException when running JacocoPublisher Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2016/Aug/05 4:00 PM Environment: Jenkins 2.16 Jacoco 2.1.0-beta1 Labels: plugin jacoco Priority: Blocker Reporter: Simon GUEROUT Running this in my pipeline step([$class: 'JacocoPublisher', execPattern:'build/jacoco/jacoco.exec', classPattern: 'build/classes/main', sourcePattern: 'src/main/java', exclusionPattern: '**/*Test.class']) I end up getting the following NPE : [JaCoCo plugin] Collecting JaCoCo coverage data... [JaCoCo plugin] build/jacoco/jacoco.exec;build/classes/main;src/main/java; locations are configured [JaCoCo plugin] Number of found exec files for pattern build/jacoco/jacoco.exec: 1 [JaCoCo plugin] Saving matched execfiles: /var/lib/jenkins/jobs/BITBUCKET_TEAM_PROJECT/jobs/GIT_PROJECT/branches/v0.0.3/workspace/build/jacoco/jacoco.exec [JaCoCo plugin] Saving matched class directories for class-pattern: build/classes/main:
[JIRA] (JENKINS-37220) Job DSL analogue of multibranch projects & organization folders
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-37220 Job DSL analogue of multibranch projects & organization folders Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2016/Aug/05 3:58 PM Labels: multibranch workflow Priority: Major Reporter: Jesse Glick To provide a more scalable alternative to the endless requested branch-api customizations such as JENKINS-32396, or the tricks based on JENKINS-30519, it would be useful to have a simple way of calling into scm-api implementations from a Job DSL folder (JENKINS-33275). So you could (for example) easily construct the equivalent of a GitHub organization folder, but from a script loop that could do arbitrary customizations to each, such as setting job properties. Need to also implement SCMSourceOwner, HeadByItem, etc. so that the branch source knows that a given generated project is associated with a given branch, which is needed for various purposes. TBD how webhooks should be integrated. The script needs to somehow indicate that changes to a given repository or organization should trigger a regeneration of the folder. May need to create an alternative to SCMTrigger that is keyed off the same criteria that branch-api branch indexing uses, though there are also use cases for traditional SCM polling—it is a little less efficient, but has more configuration options. For Pipeline projects you could use Jenkinsfile, if SCMBinder and SCMVar were generalized a bit, or something else. Needs a lot of design work; at this point this is more of a placeholder issue to collect ideas.
[JIRA] (JENKINS-37219) Option to suppress automatic SCM trigger from Jenkinsfile
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-37219 Option to suppress automatic SCM trigger from Jenkinsfile Issue Type: Bug Assignee: Andrew Bayer Components: workflow-multibranch-plugin Created: 2016/Aug/05 3:51 PM Priority: Critical Reporter: Andrew Bayer While JENKINS-32396 allows suppressing launching of builds due to new commits for an individual branch via UI configuration of the multibranch parent, it does not provide a way to control that behavior from the Jenkinsfile. There should be a JobProperty that provides the same behavior. Add Comment
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Peter McEvoy commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 Happening a lot more recently.. Seems that even after deleting the cache, I need to restart the agents that were using those workspaces. I definitely like not having to setup a tf.exe on the remove slaves, but I'm really not a fan of having to manually clean up caches and restarting remotely... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: LICENSE.md NOTICE http://jenkins-ci.org/commit/remoting/c8be8453dbee9cb3c7156307fa64b5c6a0618149 Log: JENKINS-36871 The code was missing a NOTICE and LICENSE files You'll see why I spotted this next Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: pom.xml src/assembly/agent-load-test.xml src/assembly/agent-load-test/LICENSE.md src/assembly/agent-load-test/NOTICE src/assembly/agent-load-test/README.md src/assembly/agent-load-test/agent-load-test src/assembly/agent-load-test/agent-load-test.bat src/test/java/org/jenkinsci/remoting/engine/HandlerLoopbackLoadStress.java http://jenkins-ci.org/commit/remoting/19093e34f77f6beb0af6d767addb75bee09ef0e6 Log: JENKINS-36871 Add a load testing client This needs its own LICENSE and NOTICE files as it includes things like JUnit Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/remoting/AbstractByteBufferCommandTransport.java http://jenkins-ci.org/commit/remoting/3c0db40c31165dea74cac5791adae4e99c179bad Log: JENKINS-36871 Switch to FastByteBufferQueueInputStream We don't need the general purpose mark support or unbounded reads, so lets get more performance Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/remoting/protocol/ProtocolStack.java http://jenkins-ci.org/commit/remoting/b5656c06abb78a2c384fbcee631107a3b476f164 Log: JENKINS-36871 Halve the number of stack walks when checking if open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol1Handler.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol2Handler.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol3Handler.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol4Handler.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol4PlainHandler.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocolHandler.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocolHandlerFactory.java src/main/java/org/jenkinsci/remoting/engine/LegacyJnlpProtocolHandler.java src/test/java/org/jenkinsci/remoting/engine/JnlpProtocolHandlerTest.java http://jenkins-ci.org/commit/remoting/1edda2be2a24732a2ff184207d859468d69b4877 Log: JENKINS-36871 Blocking I/O is faster when you have very few connections, so allow preference declaration Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/remoting/util/FastByteBufferQueueInputStream.java src/test/java/org/jenkinsci/remoting/util/FastByteBufferQueueInputStreamTest.java http://jenkins-ci.org/commit/remoting/8e595fcd116d0df7f712a1ac41d7188a1b943b6f Log: JENKINS-36871 Stripped back higher performance ByteBufferQueue InputStream implementation Drops support for mark and unbounded read in return for faster performance Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/remoting/util/ByteBufferQueueInputStream.java http://jenkins-ci.org/commit/remoting/74bf4fa676837b682ced32ad684474001e525665 Log: JENKINS-36871 Optimize single byte `read()` performance Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37217) GitHub webhook is not created for new Pipeline
Title: Message Title
Giovanni Tirloni updated an issue
Jenkins / JENKINS-37217
GitHub webhook is not created for new Pipeline
Change By:
Giovanni Tirloni
GitHub webhook is not created when a new Multibranch Pipeline build is added.Jenkins has a GitHub server configured, with proper credentials and it's confirmed to be working in other scenarios. 'Auto-manage hooks' is configured.Tried to create a Multibranch Pipeline build in three different ways:- Specified GitHub project URL only (with proper credentials)- Specified Git repository URL only (with proper credentials)- Specified both GitHub project and Git repository (with proper credentials)In no case the GH webhook was created for the repository. Multibranch Pipeline Logs: None. Pipeline Logs:{noformat}Aug 05, 2016 3:29:51 PM org.jenkinsci.plugins.github.webhook.WebhookManager$1 runINFO: GitHub webhooks activated for job repository-name-here with [] (events: [PUSH, REPOSITORY]){noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/test/java/org/jenkinsci/remoting/util/ByteBufferQueueTest.java http://jenkins-ci.org/commit/remoting/d942165c92e31b6b2e716e61e1ce6c9e74269357 Log: JENKINS-36871 Add some more test cases Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/remoting/protocol/IOHub.java http://jenkins-ci.org/commit/remoting/4b291b3ab370e1ddee8b656c96cef636a86c6573 Log: JENKINS-36871 WIndows!?! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/remoting/util/ByteBufferQueue.java http://jenkins-ci.org/commit/remoting/6cd91459c8b0e263e907ccdad271ba327e020d93 Log: JENKINS-36871 Improve single-byte `get()` performance Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/remoting/protocol/IOHub.java http://jenkins-ci.org/commit/remoting/6da1cb4c1f09583382195b4608a2759d49fd65b3 Log: JENKINS-36871 Using a single final class allows for inlining of hot method Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37217) GitHub webhook is not created for new Pipeline
Title: Message Title Giovanni Tirloni updated an issue Jenkins / JENKINS-37217 GitHub webhook is not created for new Pipeline Change By: Giovanni Tirloni Component/s: workflow-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37217) GitHub webhook is not created for new Pipeline
Title: Message Title Giovanni Tirloni commented on JENKINS-37217 Re: GitHub webhook is not created for new Pipeline Tested with simple Pipeline builds and it's the same issue. Updated ticket to reflect that. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37217) GitHub webhook is not created for new Pipeline
Title: Message Title Giovanni Tirloni updated an issue Jenkins / JENKINS-37217 GitHub webhook is not created for new Pipeline Change By: Giovanni Tirloni Summary: GitHub webhook is not created for new MultiBranch Pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36871 Re: JNLPProtocol4 Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/remoting/protocol/FilterLayer.java src/main/java/org/jenkinsci/remoting/protocol/ProtocolStack.java http://jenkins-ci.org/commit/remoting/75c4cf7c8ee6c2c464300efd8664c648ba6d6eb0 Log: JENKINS-36871 Allow a filter to call `completed()` from both the receive and send sides without bombing out. Prevents stack traces such as ``` Exception in thread "main" java.lang.IllegalStateException: Filter has already been completed at org.jenkinsci.remoting.protocol.FilterLayer.completed(FilterLayer.java:106) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.complete(ConnectionHeadersFilterLayer.java:365) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.doSend(ConnectionHeadersFilterLayer.java:498) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doSend(ProtocolStack.java:691) at org.jenkinsci.remoting.protocol.ApplicationLayer.write(ApplicationLayer.java:157) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.start(ChannelApplicationLayer.java:226) at org.jenkinsci.remoting.protocol.ProtocolStack.init(ProtocolStack.java:202) at org.jenkinsci.remoting.protocol.ProtocolStack.access$700(ProtocolStack.java:107) at org.jenkinsci.remoting.protocol.ProtocolStack$Builder.build(ProtocolStack.java:555) at org.jenkinsci.remoting.engine.JnlpProtocol4PlainHandler.connect(JnlpProtocol4PlainHandler.java:149) at org.jenkinsci.remoting.engine.JnlpProtocolHandler.connect(JnlpProtocolHandler.java:140) at org.jenkinsci.remoting.engine.HandlerLoopbackLoadStress.startClient(HandlerLoopbackLoadStress.java:466) at org.jenkinsci.remoting.engine.HandlerLoopbackLoadStress.main(HandlerLoopbackLoadStress.java:426) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147) ``` Add Comment
[JIRA] (JENKINS-37218) ClassFilter uses Regexs to match String.startsWith patterns
Title: Message Title stephenconnolly updated JENKINS-37218 Jenkins / JENKINS-37218 ClassFilter uses Regexs to match String.startsWith patterns Change By: stephenconnolly Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37218) ClassFilter uses Regexs to match String.startsWith patterns
Title: Message Title stephenconnolly updated JENKINS-37218 Jenkins / JENKINS-37218 ClassFilter uses Regexs to match String.startsWith patterns Change By: stephenconnolly Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37218) ClassFilter uses Regexs to match String.startsWith patterns
Title: Message Title stephenconnolly reopened an issue Jenkins / JENKINS-37218 ClassFilter uses Regexs to match String.startsWith patterns Change By: stephenconnolly Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37218) ClassFilter uses Regexs to match String.startsWith patterns
Title: Message Title stephenconnolly started work on JENKINS-37218 Change By: stephenconnolly Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37218) ClassFilter uses Regexs to match String.startsWith patterns
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-37218 ClassFilter uses Regexs to match String.startsWith patterns Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37218) ClassFilter uses Regexs to match String.startsWith patterns
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37218 Re: ClassFilter uses Regexs to match String.startsWith patterns Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/remoting/ClassFilter.java http://jenkins-ci.org/commit/remoting/c2f1e5d8e49731ce8b34720243623cf6cf9d0217 Log: [FIXED JENKINS-37218] Use String.startsWith() for simple patterns Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37218) ClassFilter uses Regexs to match String.startsWith patterns
Title: Message Title stephenconnolly created an issue Jenkins / JENKINS-37218 ClassFilter uses Regexs to match String.startsWith patterns Issue Type: Improvement Assignee: stephenconnolly Components: remoting Created: 2016/Aug/05 3:24 PM Priority: Minor Reporter: stephenconnolly From profiling connections using the load-testing client in the JENKINS-36871 PR I have notices that there is a lot of work done matching classes in the classfilter against simple regexes. There is a >50% reduction in this portion of CPU work if we replace the simple patterns with String.startsWith calls instead. This also reduces the GC pressure. Add Comment
[JIRA] (JENKINS-31924) GitSCMSource should offer extensions
Title: Message Title Adi Sutanto commented on JENKINS-31924 Re: GitSCMSource should offer extensions Mark Waite, thank you very much! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32018) Multibranch workflow project tracking multiple repositories
Title: Message Title Giovanni Tirloni commented on JENKINS-32018 Re: Multibranch workflow project tracking multiple repositories It seems possible to specify multiple GitHub and Git repositories with version 2.8 of the Pipelines Multibranch plugin. Jesse Glick, can you confirm this is fixed? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37217) GitHub webhook is not created for new MultiBranch Pipeline
Title: Message Title Giovanni Tirloni updated an issue Jenkins / JENKINS-37217 GitHub webhook is not created for new MultiBranch Pipeline Change By: Giovanni Tirloni Environment: Jenkins 2.16 GitHub API Plugin 1.76 GitHub Branch Source Plugin 1.8.1 GitHub Organization Folder Plugin 1.4 GitHub plugin 1.20.0 Pipeline 2.2 Pipeline Multbranch 2.8 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37217) GitHub webhook is not created for new MultiBranch Pipeline
Title: Message Title Giovanni Tirloni created an issue Jenkins / JENKINS-37217 GitHub webhook is not created for new MultiBranch Pipeline Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin, workflow-multibranch-plugin Created: 2016/Aug/05 2:51 PM Environment: Jenkins 2.16 GitHub API Plugin 1.76 GitHub Branch Source Plugin 1.8.1 GitHub Organization Folder Plugin 1.4 GitHub plugin 1.20.0 Pipeline 2.2 Priority: Minor Reporter: Giovanni Tirloni GitHub webhook is not created when a new Multibranch Pipeline build is added. Jenkins has a GitHub server configured, with proper credentials and it's confirmed to be working in other scenarios. 'Auto-manage hooks' is configured. Tried to create a Multibranch Pipeline build in three different ways: Specified GitHub project URL only (with proper credentials) Specified Git repository URL only (with proper credentials) Specified both GitHub project and Git repository (with proper credentials) In no case the GH webhook was created for the repository. Logs: None.
