[JIRA] (JENKINS-37837) Regression: JWT token not present when logged in on blueocean.io
Title: Message Title Vivek Pandey stopped work on JENKINS-37837 Change By: Vivek Pandey Status: In Progress 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-37837) Regression: JWT token not present when logged in on blueocean.io
Title: Message Title Vivek Pandey started work on JENKINS-37837 Change By: Vivek Pandey 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-37837) Regression: JWT token not present when logged in on blueocean.io
Title: Message Title Vivek Pandey updated JENKINS-37837 Jenkins / JENKINS-37837 Regression: JWT token not present when logged in on blueocean.io Change By: Vivek Pandey Status: In Review 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-37763) Ad number of "queued" and "running" jobs as properties to Pipeline object
Title: Message Title Vivek Pandey commented on JENKINS-37763 Re: Ad number of "queued" and "running" jobs as properties to Pipeline object Cliff Meyers I named these elements numberOfRunningPipelines and numberOfQueuedPipelines to be consistent. 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-37763) Ad number of "queued" and "running" jobs as properties to Pipeline object
Title: Message Title Vivek Pandey updated JENKINS-37763 Jenkins / JENKINS-37763 Ad number of "queued" and "running" jobs as properties to Pipeline object Change By: Vivek Pandey 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-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34239 Re: GitHub Organization Folder not available as a new item without a restart Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/jenkins/branch/CustomOrganizationFolderDescriptor.java src/test/java/jenkins/branch/CustomOrganizationFolderDescriptorTest.java http://jenkins-ci.org/commit/branch-api-plugin/d297b9480b5fddfeacc878f832ef352926fecfd6 Log: [FIXED JENKINS-34239] Need to rerun doAddSpecificDescriptors in case a MultiBranchProjectFactoryDescriptor is added first, then a SCMNavigatorDescriptor. 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-37770) Malformed JSON for /blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject
Title: Message Title Vivek Pandey commented on JENKINS-37770 Re: Malformed JSON for /blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject Hi emanuelez, Its hard to tell where its coming from. I tried build-flow plugin but it did not reproduce problem on latest code base. It will help if there is full stack trace because current stack trace does not show where in blueocean code this exception is coming from. Are you running on latest blueocean? There was recent fix in exposing action data to handle unexpected exception coming in from underlying plugin's action. I would suggest give latest version of blueocean plugin a try if you are not already doing so. 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-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-37323 Ensure that Pipeline Graph can handle stage blocks Change By: Vivek Pandey Priority: Critical Blocker 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-37744) Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation
Title: Message Title Vivek Pandey commented on JENKINS-37744 Re: Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation Once JENKINS-37323 is merged, we can proceed with integrating and testing we work with Kyoto. 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-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title DEREK LU commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job The Pipeline as code can promote for parameter value input, but it holds the executor. Our use case is to provide approval note from one stage to another, which may happen several days later. I have implemented a workaround in our case for now. Let the Manual Approving Job check a file parameter to decide to move forward or not. Then created another job to accept values for the parameter and save it to a file. In the Build pipeline, a string parameter is used to create a link to the parameter entering job, and it is displayed in the reversion box. the links is like Enter Parameters This will popup the job in a lightbox within the build pipeline. It is complicated and just a workaround. We really hope if this issue can get fixed 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-37332) java.io.IOException: Failed to rename during Plugin Update
Title: Message Title Brian Ray commented on JENKINS-37332 Re: java.io.IOException: Failed to rename during Plugin Update Just hit this after upgrading to LTS 2.7.3 on Windows. If my records are correct I was able to update bundled plugins without issue on LTS 2.7.2. Is the workaround simply to downgrade to 2.7.2 until there's a new LTS release with the current fix? Or is there a sneaky hack to stay on 2.7.3 and update the bundled plugins? Thanks 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-37744) Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation
Title: Message Title Vivek Pandey stopped work on JENKINS-37744 Change By: Vivek Pandey Status: In Progress 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-37763) Ad number of "queued" and "running" jobs as properties to Pipeline object
Title: Message Title Vivek Pandey started work on JENKINS-37763 Change By: Vivek Pandey 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-37744) Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation
Title: Message Title Vivek Pandey started work on JENKINS-37744 Change By: Vivek Pandey 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-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title Vivek Pandey updated JENKINS-37323 Jenkins / JENKINS-37323 Ensure that Pipeline Graph can handle stage blocks Change By: Vivek Pandey 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-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-37369 Multibranch Pipeline: Last build information is not propagated to Jenkins View Change By: Jesse Glick Component/s: branch-api-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-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-37369 Multibranch Pipeline: Last build information is not propagated to Jenkins View Change By: Jesse Glick Labels: Pipeline folders multibranch 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-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View
Title: Message Title Jesse Glick commented on JENKINS-37369 Re: Multibranch Pipeline: Last build information is not propagated to Jenkins View The view columns are defined in core, and do not handle folders. 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-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-37369 Multibranch Pipeline: Last build information is not propagated to Jenkins View Change By: Jesse Glick Component/s: core Component/s: workflow-multibranch-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-37951) WithContainerStep.Decorator fails to call DockerTool.getExecutable on toolName
Title: Message Title Jesse Glick commented on JENKINS-37951 Re: WithContainerStep.Decorator fails to call DockerTool.getExecutable on toolName Without the fix for JENKINS-36082 this is a moot point. 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-37951) WithContainerStep.Decorator fails to call DockerTool.getExecutable on toolName
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-37951 WithContainerStep.Decorator fails to call DockerTool.getExecutable on toolName Issue Type: Bug Assignee: Jesse Glick Components: docker-workflow-plugin Created: 2016/Sep/02 11:36 PM Priority: Major Reporter: Jesse Glick So Image.inside does not work inside withTool if you did not in fact have a docker in your $PATH otherwise. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37950) Update demo to use an agent
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-37950 Update demo to use an agent Issue Type: Task Assignee: Jesse Glick Components: docker-workflow-plugin Created: 2016/Sep/02 11:35 PM Priority: Major Reporter: Jesse Glick Need to update demo to also run an agent process using a derivative of the jenkinsci/jnlp-slave image. Would be easier with Docker Compose. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[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 Matthew Reiter Looks a lot like what I did locally. Same issue as mine though AFAICT, if there was no build running when the page loaded, the list is never updated. Can you confirm the same behavior? 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-37949) Quickbooks Support Number 1-844-551-9757 Quickbooks Support Phone Number!!@
Title: Message Title sumit pradhan created an issue Jenkins / JENKINS-37949 Quickbooks Support Number 1-844-551-9757 Quickbooks Support Phone Number!!@ Issue Type: Bug Assignee: Alexander A Components: s3-plugin Created: 2016/Sep/02 11:31 PM Priority: Minor Reporter: sumit pradhan QuickBooks Support phone Number (((1 844 551 9757 )))QuickBooks support phone Number USA Quickbooks Phone Number1-844-551-9757Quickbooks Tech Support phone number @@Call, 1-844-551-9757 for all type help by Quickbooks tech support phone number, 1844-551-9757 Intuit Quickbooks Tech Support Phone Number, 1844-551-9757 Quickbooks Help Desk Phone Number, 1844-551-9757 Quickbooks tech support number, Quickbooks technical support phone number,@@ 1844-551-9757 @ Quickbooks phone number, 1844-551-9757 Quickbooks technical support number, 1844-551-9757 Quickbooks support phone number, 1844-551-9757 Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number, Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline Number, Quickbooks Customer Care Number, Quickbooks support team phone number, @ Quickbooks help number-Quickbooks Helpline Number; Quickbooks help phone number-Quickbooks Helpline Number, Quickbooks Tech Support Toll free Number, Quickbooks Support Telephone Number, Quickbooks Tech Support Telephone number, Quickbooks Tech Support contact number, Quickbooks support contact number, Quickbooks technical support contact number. Call, Quickbooks tech support phone number, Intuit Quickbooks Tech Support Phone Number, Quickbooks Help Desk Phone Number, Quickbooks tech support number, Quickbooks technical support phone number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone number. It is very popular toll free number which provide by Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number,
[JIRA] (JENKINS-37948) Quickbooks Customer Service Number 1-844-551-9757 Quickbooks Customer Service Phone Number!!@
Title: Message Title sumit pradhan created an issue Jenkins / JENKINS-37948 Quickbooks Customer Service Number 1-844-551-9757 Quickbooks Customer Service Phone Number!!@ Issue Type: Bug Assignee: Unassigned Components: safe-restart Created: 2016/Sep/02 11:29 PM Priority: Minor Reporter: sumit pradhan * Quickbooks Customer Service Number 1-844-551-9757 Quickbooks Customer Service Phone Number!!@ QuickBooks Support phone Number (((1 844 551 9757 )))QuickBooks support phone Number USA Quickbooks Phone Number1-844-551-9757Quickbooks Tech Support phone number @@Call, 1-844-551-9757 for all type help by Quickbooks tech support phone number, 1844-551-9757 Intuit Quickbooks Tech Support Phone Number, 1844-551-9757 Quickbooks Help Desk Phone Number, 1844-551-9757 Quickbooks tech support number, Quickbooks technical support phone number,@@ 1844-551-9757 @ Quickbooks phone number, 1844-551-9757 Quickbooks technical support number, 1844-551-9757 Quickbooks support phone number, 1844-551-9757 Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number, Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline Number, Quickbooks Customer Care Number, Quickbooks support team phone number, @ Quickbooks help number-Quickbooks Helpline Number; Quickbooks help phone number-Quickbooks Helpline Number, Quickbooks Tech Support Toll free Number, Quickbooks Support Telephone Number, Quickbooks Tech Support Telephone number, Quickbooks Tech Support contact number, Quickbooks support contact number, Quickbooks technical support contact number. Call, Quickbooks tech support phone number, Intuit Quickbooks Tech Support Phone Number, Quickbooks Help Desk Phone Number, Quickbooks tech support number, Quickbooks technical support phone number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone number. It is very popular toll free number which
[JIRA] (JENKINS-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34239 Re: GitHub Organization Folder not available as a new item without a restart Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/jenkins/branch/CustomOrganizationFolderDescriptor.java src/test/java/jenkins/branch/CustomOrganizationFolderDescriptorTest.java http://jenkins-ci.org/commit/branch-api-plugin/e05c287883ec4b46b4820004d9d540ef70c12cea Log: [FIXED JENKINS-34239] Need to rerun doAddSpecificDescriptors in case a MultiBranchProjectFactoryDescriptor is added first, then a SCMNavigatorDescriptor. 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-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title Jesse Glick updated JENKINS-34239 Jenkins / JENKINS-34239 GitHub Organization Folder not available as a new item without a restart Change By: Jesse Glick Status: In Review 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-37947) Quickbooks Support Number 1-844-551-9757 Quickbooks Support Phone Number!!@
Title: Message Title sumit pradhan assigned an issue to sumit pradhan QuickBooks Support phone Number ###1 844 551 9757 QuickBooks support phone Number USA/canada QuickBooks Support phone Number ###1 844 551 9757 QuickBooks support phone Number USA/canada Quickbooks Phone Number1-844-551-9757Quickbooks Tech Support phone number @@Call, 1-844-551-9757 for all type help by Quickbooks tech support phone number, 1844-551-9757 Intuit Quickbooks Tech Support Phone Number, 1844-551-9757 Quickbooks Help Desk Phone Number, 1844-551-9757 Quickbooks tech support number, Quickbooks technical support phone number,@@ 1844-551-9757 @ Quickbooks phone number, 1844-551-9757 Quickbooks technical support number, 1844-551-9757 Quickbooks support phone number, 1844-551-9757 Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number, Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline Number, Quickbooks Customer Care Number, Quickbooks support team phone number, @ Quickbooks help number-Quickbooks Helpline Number; Quickbooks help phone number-Quickbooks Helpline Number, Quickbooks Tech Support Toll free Number, Quickbooks Support Telephone Number, Quickbooks Tech Support Telephone number, Quickbooks Tech Support contact number, Quickbooks support contact number, Quickbooks technical support contact number. Call, Quickbooks tech support phone number, Intuit Quickbooks Tech Support Phone Number, Quickbooks Help Desk Phone Number, Quickbooks tech support number, Quickbooks technical support phone number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone number. It is very popular toll free number which provide by Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number, Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline Number, Quickbooks Customer Care Number, Quickbooks support team phone number. Call, Quickbooks tech support phone number, Intuit Quickbooks Tech Support Phone Number, Quickbooks Help Desk Phone Number, Quickbooks tech support number, Quickbooks technical support phone number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone number, Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number, Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline Number, Quickbooks Customer Care Number, Quickbooks support team phone number, Quickbooks help number-Quickbooks Helpline Number; Quickbooks help phone number, Quickbooks Helpline Number, Quickbooks Tech Support Toll free Number, Quickbooks Support Telephone Number, Quickbooks Tech Support Telephone number, Quickbooks Tech Support contact number, Quickbooks support contact number, Quickbooks technical support contact number, Quickbooks pro support phone number, Quickbooks payroll support phone number. Quickbooks payroll customer support phone number Quickbooks Support Helpline Number, Quickbooks contact number Quickbooks tech support phone number Quickbooks support team phone number Quickbooks contact number 1844-551-9757 Quickbooks technical help telephone number, Quickbooks technical help contact number, Quickbooks technical support contact number, Quickbooks contact number, Quickbooks contact phone number, Quickbooks contact telephone number, Quickbooks 24 hour contact number, Quickbooks customer support contact number, Quickbooks customer service contact number, Quickbooks official number, Quickbooks official contact number, Quickbooks 844 contact number, Quickbooks toll free number, 844 number for Quickbooks support, Quickbooks 24/7 support phone number Quickbooks PRO support phone number,Quickbooks PRO support phone number,Quickbooks PRO help phone number, Quickbooks PRO technical support number.Quickbooks PRO support number, Quickbooks PRO phone number, Quickbooks PRO tech support number,
[JIRA] (JENKINS-37831) Favoriting on Matrix style project broken
Title: Message Title Vivek Pandey commented on JENKINS-37831 Re: Favoriting on Matrix style project broken Removed my name from assigned, its an UI issue where something in UI is generating path to classic job. 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-37831) Favoriting on Matrix style project broken
Title: Message Title Vivek Pandey assigned an issue to Unassigned Jenkins / JENKINS-37831 Favoriting on Matrix style project broken Change By: Vivek Pandey Assignee: Vivek Pandey 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-37947) Quickbooks Support Number 1-844-551-9757 Quickbooks Support Phone Number!!@
Title: Message Title sumit pradhan created an issue Jenkins / JENKINS-37947 Quickbooks Support Number 1-844-551-9757 Quickbooks Support Phone Number!!@ Issue Type: Bug Assignee: Steven Christou Components: support-core-plugin Created: 2016/Sep/02 11:19 PM Priority: Minor Reporter: sumit pradhan Quickbooks Support Number 1-844-551-9757 Quickbooks Support Phone Number!!@ QuickBooks Support phone Number ###1 844 551 9757 QuickBooks support phone Number USA/canada QuickBooks Support phone Number ###1 844 551 9757 QuickBooks support phone Number USA/canada Quickbooks Phone Number1-844-551-9757Quickbooks Tech Support phone number @@Call, 1-844-551-9757 for all type help by Quickbooks tech support phone number, 1844-551-9757 Intuit Quickbooks Tech Support Phone Number, 1844-551-9757 Quickbooks Help Desk Phone Number, 1844-551-9757 Quickbooks tech support number, Quickbooks technical support phone number,@@ 1844-551-9757 @ Quickbooks phone number, 1844-551-9757 Quickbooks technical support number, 1844-551-9757 Quickbooks support phone number, 1844-551-9757 Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number, Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline Number, Quickbooks Customer Care Number, Quickbooks support team phone number, @ Quickbooks help number-Quickbooks Helpline Number; Quickbooks help phone number-Quickbooks Helpline Number, Quickbooks Tech Support Toll free Number, Quickbooks Support Telephone Number, Quickbooks Tech Support Telephone number, Quickbooks Tech Support contact number, Quickbooks support contact number, Quickbooks technical support contact number. Call, Quickbooks tech support phone number, Intuit Quickbooks Tech Support Phone Number, Quickbooks Help Desk Phone Number, Quickbooks tech support number, Quickbooks technical support phone number, Quickbooks phone number, Quickbooks technical support number,
[JIRA] (JENKINS-37263) Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash)
Title: Message Title Mark Waite edited a comment on JENKINS-37263 Re: Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash) This is not fixed in [git plugin 2.6.0|https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Changelog], released 2 Sep 2016. It worked for me occasionally in my test environment, but there is something wrong with the job or how it is behaving. It fails my tests at least every second test.[~superboum] could you check it with that release in your 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-37263) Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash)
Title: Message Title Mark Waite edited a comment on JENKINS-37263 Re: Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash) This is not fixed in [git plugin 2.6.0|]https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Changelog ] , released 2 Sep 2016. It worked for me occasionally in my test environment, but there is something wrong with the job or how it is behaving. It fails my tests every second test.[~superboum] could you check it with that release in your 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-37263) Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash)
Title: Message Title Mark Waite edited a comment on JENKINS-37263 Re: Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash) This is not fixed in [git plugin 2.6.0| ] https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Changelog], released 2 Sep 2016. It worked for me occasionally in my test environment, but there is something wrong with the job or how it is behaving. It fails my tests every second test.[~superboum] could you check it with that release in your 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-37263) Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash)
Title: Message Title Mark Waite edited a comment on JENKINS-37263 Re: Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash) I believe this This is not fixed in [git plugin 2.6.0|]https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Changelog, released 2 Sep 2016. It worked for me occasionally in my test environment , but there is something wrong with the job or how it is behaving . It fails my tests every second test. [~superboum] could you check it with that release in your 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-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title
Manuel Recena Soto updated an issue
Jenkins / JENKINS-34239
GitHub Organization Folder not available as a new item without a restart
Change By:
Manuel Recena Soto
h5. Steps to reproduce it# Fresh installation of Jenkins ({{Jenkins ver. 2.0-rc-1}})# We choose *Recommended Plugins *option# Items availables are: Freestyle project, Pipeline, External Job, Multi-configuration project, Folder, Multibranch PipelineWhere is GitHub Organization?Only if we acces to {{Manage Plugins >> Installed (tab)}} we see the following message:Warning: This Jenkins instance requires a restart. Changing the state of plugins at this time is strongly discouraged. Restart Jenkins before proceeding.After restarting, we can see the item GitHub Organization.I see here two problems:# We need to restart Jenkins after the wizard installation# The warning message is completely hidden. It is difficult to know that you have to restart.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You
[JIRA] (JENKINS-37263) Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash)
Title: Message Title Mark Waite commented on JENKINS-37263 Re: Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash) I believe this is fixed in [git plugin 2.6.0|]https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Changelog, released 2 Sep 2016. It worked for me in my test environment. Quentin Dufour could you check it with that release in your 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-37946) java.lang.NoSuchMethodError on OSX
Title: Message Title Khai Do created an issue Jenkins / JENKINS-37946 java.lang.NoSuchMethodError on OSX Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2016/Sep/02 10:31 PM Environment: platform: OSX El Capitan (10.11.5) java version "1.8.0_92" Java(TM) SE Runtime Environment (build 1.8.0_92-b14) Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) Jenkins core 1.625.3 Gerrit trigger 2.22.0 Labels: classloader Priority: Major Reporter: Khai Do I'm developing a plugin (https://github.com/zaro0508/verify-status-reporter) on my MAC. When I debug and run this plugin using hpi:run it works fine. When I run jenkins with `java -jar jenkins.war` install the plugin then I get a runtime error (java.lang.NoSuchMethodError). This error happens on my MAC. However when I run it the exact same way on Ubuntu Xenial `java -jar jenkins.war` then it work fine. I think there's something screwy with the classloading on OSX. I notice the error will not happen if I depend on the Jenkins plugin parent pom ver 1.580.1 but when I switch to ver 2.7 to match the Gerrit trigger plugin the problem happens. The dependency is looks like this.. org.jenkins-ci.plugins plugin 2.7 here is the stack trace.. INFO: All Builds are completed for cause: GerritCause: com.sonymobile.tools.gerrit.gerritevents.dto.events.CommentAdded@704e521 silent: false Sep 02, 2016 10:49:23 AM hudson.model.AbstractBuild$AbstractBuildExecution reportError WARNING: Step ‘Post Verification to Gerrit’ aborted due to exception: java.lang.NoSuchMethodError:
[JIRA] (JENKINS-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title Jesse Glick updated JENKINS-34239 Jenkins / JENKINS-34239 GitHub Organization Folder not available as a new item without a restart 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-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title Jesse Glick commented on JENKINS-34239 Re: GitHub Organization Folder not available as a new item without a restart Amending steps to reproduce interactively from JENKINS-33106 to work in 2.7.3 is trickier due to security setup and JENKINS-18114, so it is more manual, but anyway the deployment step looks like java -jar /tmp/WEB-INF/jenkins-cli.jar -s http://localhost:8080/ install-plugin -deploy cloudbees-folder scm-api structs $(pwd)/target/branch-api.hpi workflow-multibranch github-branch-source Note the order of the last two items, which I think is the key. 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-37945) Hover log output on longer stages exceeds the vertical bounds of the overlay box
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-37945 Hover log output on longer stages exceeds the vertical bounds of the overlay box Issue Type: Bug Assignee: Sam Van Oort Attachments: stage-view-1.png, stage-view-2.png Components: pipeline-stage-view-plugin Created: 2016/Sep/02 10:00 PM Priority: Minor Reporter: R. Tyler Croy Basically, have a stage with a lot of steps in it, and you can exceed the vertical and horizontal bounds of the overlay box; screenshots should help clarify. Add Comment
[JIRA] (JENKINS-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title Jesse Glick commented on JENKINS-34239 Re: GitHub Organization Folder not available as a new item without a restart I am ignoring the original issue description, which was about messaging about plugins which request restart (as a workaround for some buggy behavior), and focusing on why the fix of JENKINS-33106 did not suffice to make this plugin not require restart. 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-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-34239 GitHub Organization Folder not available as a new item without a restart Change By: Jesse Glick Component/s: branch-api-plugin Component/s: core 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-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-34239 GitHub Organization Folder not available as a new item without a restart Change By: Jesse Glick 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-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title Jesse Glick started work on JENKINS-34239 Change By: Jesse Glick 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-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title recampbell commented on JENKINS-34239 Re: GitHub Organization Folder not available as a new item without a restart This is still reproducible with Jenkins LTS 2.7.3 and github-organizational-folder 1.4. 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-37944) TAP plugin incorrectly sums the test times
Title: Message Title harschware created an issue Jenkins / JENKINS-37944 TAP plugin incorrectly sums the test times Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: image-2016-09-02-13-59-59-162.png Components: tap-plugin Created: 2016/Sep/02 9:11 PM Environment: Jenkins 2.7.2, tap-plugin 2.0.1 Priority: Major Reporter: harschware The TAP plugin is correctly summing time from tests. As you can see in the screen shot it says 8ms+10ms=18 seconds Add Comment
[JIRA] (JENKINS-31487) Job status not updated in web UI during build
Title: Message Title Matthew Reiter edited a comment on JENKINS-31487 Re: Job status not updated in web UI during build I've attached a patch that works for me... I'm not sure if it's the best approach but might be a good place to start. The patch is relative to version 2.20. [^jobStatus.patch] 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 Matthew Reiter commented on JENKINS-31487 Re: Job status not updated in web UI during build I've attached a patch that works for me... I'm not sure if it's the best approach but might be a good place to start. jobStatus.patch 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 Matthew Reiter updated an issue Jenkins / JENKINS-31487 Job status not updated in web UI during build Change By: Matthew Reiter Attachment: jobStatus.patch 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-37943) ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory
Title: Message Title kiran kiran commented on JENKINS-37943 Re: ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory Hi Raphel, I am beginner in using jenkins, so please let me know if you need any more details in debugging the issue. Thank You 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-37941) folder plugin missing norefresh=true in RelocationAction
Title: Message Title Jesse Glick updated JENKINS-37941 Jenkins / JENKINS-37941 folder plugin missing norefresh=true in RelocationAction Change By: Jesse Glick Status: In Review 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-37943) ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory
Title: Message Title kiran kiran created an issue Jenkins / JENKINS-37943 ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory Issue Type: Bug Assignee: Raphael CHAUMIER Attachments: 14159200_10210837527952946_849118975_n.jpg, 14169472_10210837392829568_93060520_n.jpg, 14218095_10210837528232953_484793147_n.jpg Components: weblogic-deployer-plugin Created: 2016/Sep/02 7:40 PM Environment: Jenkins 1.64, Weblogic 12c windows 2008 Priority: Blocker Reporter: kiran kiran I am trying to deploy EAR on weblogic 12c , with jenkins 1.64. using weblogic deployer plugin. It is failing with above error. Please see the attached settings and error message. This is critical. Please help Add Comment
[JIRA] (JENKINS-37941) folder plugin missing norefresh=true in RelocationAction
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37941 Re: folder plugin missing norefresh=true in RelocationAction Code changed in jenkins User: Valentina Armenise Path: src/main/resources/com/cloudbees/hudson/plugins/folder/relocate/RelocationAction/index.jelly http://jenkins-ci.org/commit/cloudbees-folder-plugin/41509f3675aad38a408d9b136753cb4c6d34866a Log: [FIXED JENKINS-37941] add norefresh=true in index.jelly as suggested @amuniz 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-37942) Build Failure Analyzer: No info added to api/json output for build page
Title: Message Title Tom Hildebrandt created an issue Jenkins / JENKINS-37942 Build Failure Analyzer: No info added to api/json output for build page Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2016/Sep/02 7:28 PM Environment: Ubuntu 14.03 + Firefox 48.0 Priority: Minor Reporter: Tom Hildebrandt After installing the build failure analyzer plugin: Adding /api/json to the a build page displaying a recognized Failure pattern => No output from the build failure analyzer plugin appears in the json output. I assume that this is an unimplemented feature. For the sake of automated build health monitoring, it would be very useful to have BFA cause information injected into the JSON output in that context. Add Comment
[JIRA] (JENKINS-23873) extend changeMerged event with merge commit
Title: Message Title George Young commented on JENKINS-23873 Re: extend changeMerged event with merge commit Looks like a commit by Jan Dohl achieves this result, found in plugin version gerrit-trigger-2.21.0 which creates the GERRIT_NEWREV Jenkins job variable when listening to Gerrit v2.11 streaming ref_updated or change_merged events with the new JSON field new_rev field 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-32767) GitSCMSource can hang in branch indexing, blocking builds
Title: Message Title Mark Waite resolved as Fixed Jenkins / JENKINS-32767 GitSCMSource can hang in branch indexing, blocking builds Change By: Mark Waite Status: In Progress 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-32767) GitSCMSource can hang in branch indexing, blocking builds
Title: Message Title Mark Waite commented on JENKINS-32767 Re: GitSCMSource can hang in branch indexing, blocking builds Included in git plugin 2.6.0, released 2 Sep 2016, at least by virtue of command line git being made the default implementation for the multi-branch 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-35525) Upgrade to Credentials 2.1.0+ API for populating credentials drop-down
Title: Message Title Mark Waite resolved as Fixed Included in git plugin 2.6.0, released 2 Sep 2016. Jenkins / JENKINS-35525 Upgrade to Credentials 2.1.0+ API for populating credentials drop-down Change By: Mark Waite Status: In Progress 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
[JIRA] (JENKINS-37482) AbstractGitSCMSource.retrieve fails due to nonexistent cache directory
Title: Message Title Mark Waite commented on JENKINS-37482 Re: AbstractGitSCMSource.retrieve fails due to nonexistent cache directory Included in git plugin 2.6.0, released 2 Sep 2016. 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-37727) Multibranch pipeline project jobs are not deleted when branches are deleted
Title: Message Title Mark Waite resolved as Fixed Included in git plugin 2.6.0, released 2 Sep 2016. Was never visible in any released version of the plugin. Jenkins / JENKINS-37727 Multibranch pipeline project jobs are not deleted when branches are deleted Change By: Mark Waite Status: In Progress 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
[JIRA] (JENKINS-37297) can't use github deploy keys in Multi-Branch Project Plugin
Title: Message Title Mark Waite resolved as Fixed Included in git plugin 2.6.0, released 2 Sep 2016. Jenkins / JENKINS-37297 can't use github deploy keys in Multi-Branch Project Plugin Change By: Mark Waite 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
[JIRA] (JENKINS-35567) multibranch project and ssh+git broken
Title: Message Title Mark Waite resolved as Fixed Included in git plugin 2.6.0, released 2 Sep 2016. Jenkins / JENKINS-35567 multibranch project and ssh+git broken Change By: Mark Waite 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-36082) Automatic installer fails for Docker 1.11 and latest
Title: Message Title Jesse Glick updated JENKINS-36082 Jenkins / JENKINS-36082 Automatic installer fails for Docker 1.11 and latest 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-36958) Multi-branch maven project can't fetch Gitlab code, cmdline git can fetch same code
Title: Message Title Mark Waite resolved as Fixed Included in git plugin 2.6.0, released 2 Sep 2016. Jenkins / JENKINS-36958 Multi-branch maven project can't fetch Gitlab code, cmdline git can fetch same code Change By: Mark Waite 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
[JIRA] (JENKINS-35565) multibranch project and git broken
Title: Message Title Mark Waite resolved as Fixed Included in git plugin 2.6.0, released 2 Sep 2016. Jenkins / JENKINS-35565 multibranch project and git broken Change By: Mark Waite 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-32790) Unable to serialize
Title: Message Title Jesse Glick updated JENKINS-32790 Jenkins / JENKINS-32790 Unable to serialize 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-33983) Multibranch Pipeline with git uses jgit, but should use git installation that is configured
Title: Message Title Mark Waite resolved as Fixed Included in git plugin 2.6.0, released 2 Sep 2016. Jenkins / JENKINS-33983 Multibranch Pipeline with git uses jgit, but should use git installation that is configured Change By: Mark Waite Status: In Progress 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
[JIRA] (JENKINS-36958) Multi-branch maven project can't fetch Gitlab code, cmdline git can fetch same code
Title: Message Title Mark Waite edited a comment on JENKINS-36958 Re: Multi-branch maven project can't fetch Gitlab code, cmdline git can fetch same code @jgl...@cloudbees.com I think PR424 die in the git client plugin handles 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-37941) folder plugin missing norefresh=true in RelocationAction
Title: Message Title valentina armenise started work on JENKINS-37941 Change By: valentina armenise 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-37846) How to see JIRA issues in jenkins build as part of changelog
Title: Message Title Radek Antoniuk commented on JENKINS-37846 Re: How to see JIRA issues in jenkins build as part of changelog Did you try to setup according to documentation here: https://wiki.jenkins-ci.org/display/JENKINS/JIRA+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-37846) How to see JIRA issues in jenkins build as part of changelog
Title: Message Title Radek Antoniuk closed an issue as Not A Defect Jenkins / JENKINS-37846 How to see JIRA issues in jenkins build as part of changelog Change By: Radek Antoniuk Status: Open Closed Resolution: Not A Defect 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-37941) folder plugin missing norefresh=true in RelocationAction
Title: Message Title valentina armenise updated JENKINS-37941 Jenkins / JENKINS-37941 folder plugin missing norefresh=true in RelocationAction Change By: valentina armenise 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-37846) How to see JIRA issues in jenkins build as part of changelog
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-37846 How to see JIRA issues in jenkins build as part of changelog Change By: Radek Antoniuk Issue Type: Bug Task 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-37673) Running status indicator is clipped on favourite card
Title: Message Title Cliff Meyers updated JENKINS-37673 Jenkins / JENKINS-37673 Running status indicator is clipped on favourite card Change By: Cliff Meyers Status: In Review 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-37702) Unbuilt pipelines show up as unknown if favourited
Title: Message Title Cliff Meyers commented on JENKINS-37702 Re: Unbuilt pipelines show up as unknown if favourited PR: https://github.com/jenkinsci/blueocean-plugin/pull/465 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-37941) folder plugin missing norefresh=true in RelocationAction
Title: Message Title valentina armenise assigned an issue to valentina armenise Jenkins / JENKINS-37941 folder plugin missing norefresh=true in RelocationAction Change By: valentina armenise Assignee: Jesse Glick valentina armenise 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-37941) folder plugin missing norefresh=true in RelocationAction
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-37941 folder plugin missing norefresh=true in RelocationAction Issue Type: Bug Assignee: Jesse Glick Components: cloudbees-folder-plugin Created: 2016/Sep/02 6:08 PM Priority: Minor Reporter: valentina armenise RelocationAction index.jelly is missing norefresh=true https://github.com/jenkinsci/cloudbees-folder-plugin/blob/master/src/main/resources/com/cloudbees/hudson/plugins/folder/relocate/RelocationAction/index.jelly#L6 Add Comment
[JIRA] (JENKINS-37702) Unbuilt pipelines show up as unknown if favourited
Title: Message Title Cliff Meyers commented on JENKINS-37702 Re: Unbuilt pipelines show up as unknown if favourited James Dumay Queued pipelines were actually blue, so they have been changed to gray. Note that right now the only difference between QUEUED and NOT_BUILT is that the latter has a solid circle status indicator, whereas QUEUED is a solid circle with the inner pulsing circle. Let me know if we should refine 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-37702) Unbuilt pipelines show up as unknown if favourited
Title: Message Title Cliff Meyers updated JENKINS-37702 Jenkins / JENKINS-37702 Unbuilt pipelines show up as unknown if favourited Change By: Cliff Meyers 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-37940) Add forParameterMatchingFiles to job-dsl-plugin
Title: Message Title Dan Clayton created an issue Jenkins / JENKINS-37940 Add forParameterMatchingFiles to job-dsl-plugin Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2016/Sep/02 6:04 PM Priority: Minor Reporter: Dan Clayton The job-dsl-plugin support forMatchingFiles which sends the matching files as file parameters, however I would like to leverage sending the file contents as parameters. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-37939) Provide the option to exclude forks
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-37939 Provide the option to exclude forks Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2016/Sep/02 5:55 PM Priority: Minor Reporter: R. Tyler Croy When using the GitHub Organization Folder against my own GitHub account, I would like to be able to only include repositories that I have created, not just forks. For example, if I fork a Jenkins plugin to submit a patch, all of a sudden there's a new Pipeline building on my local Jenkins. I think ti would be ideal to support excluding all forks with a checkbox in the folder configuration Add Comment
[JIRA] (JENKINS-36662) Downstream projects should not be triggered anymore after upstream project pom version is changed
Title: Message Title Arnaud Héritier commented on JENKINS-36662 Re: Downstream projects should not be triggered anymore after upstream project pom version is changed AFAIR the technical issue limitation here is that the trigger between Project A -> Project B is created or updated only after a build of Project B Thus when you are updating the version of project A, project B doesn't yet know that it changed thus the trigger launches project B But after a first useless build of Project B it should remove the trigger. 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Dominic Scheirlinck edited a comment on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit My hacky fix branch is at https://github.com/vend/github-branch-source-plugin/pull/1 - it'll only work for PR builds for now. Comments welcome.In this implementation, each PR event webhook triggers up to two builds (merged/unmerged), and takes about one Github API request to do so (I think, checking the collaborators for .isTrusted? Maybe 2-3 ). Pushes to a PR that is already open won't trigger a build, which is a shame (need to rewrite this logic into a pull event subscriber too). But editing the PR, or adding/removing a label should. 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-14613) Maven job config page loses 'invoke top-level maven targets' setting for 'use private repository'
Title: Message Title Arnaud Héritier commented on JENKINS-14613 Re: Maven job config page loses 'invoke top-level maven targets' setting for 'use private repository' strangely the problem doesn't occur with a classical freestyle job thus it is really a side effect of pre/post build steps in maven jobs which is interfering with maven freestyle builders 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-37850) CLONE - Maven job config page loses 'use private repository' setting for 'invoke top-level maven targets'
Title: Message Title Arnaud Héritier resolved as Duplicate I mark it as duplicated Jenkins / JENKINS-37850 CLONE - Maven job config page loses 'use private repository' setting for 'invoke top-level maven targets' Change By: Arnaud Héritier 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
[JIRA] (JENKINS-14613) Maven job config page loses 'invoke top-level maven targets' setting for 'use private repository'
Title: Message Title Arnaud Héritier commented on JENKINS-14613 Re: Maven job config page loses 'invoke top-level maven targets' setting for 'use private repository' Steve Roth evernat I confirm your bug, I reproduced it (and JENKINS-37850 at the same time). In fact they are the same. The default value of "Use private Maven repository" seems to be forced by the global configuration "Manage Jenkins" > "Maven Project Configuration" > "Local Maven Repository" If you use "Local to the workspace" or "Local to the executor" the option "Use private Maven repository" of 'Invoke top-level Maven targets' pre-build or post build step will be always activated ( JENKINS-14613 ) If you use "Default ( ~/.m2/repository)" the option "Use private Maven repository" of 'Invoke top-level Maven targets' pre-build or post build step will be always deactivated ( JENKINS-37850 ) As far as I can see the value of "Use private Maven repository" is correctly saved in the job configuration thus there is a side effect in the loading of the value when we are displaying the form 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-37850) CLONE - Maven job config page loses 'use private repository' setting for 'invoke top-level maven targets'
Title: Message Title Arnaud Héritier commented on JENKINS-37850 Re: CLONE - Maven job config page loses 'use private repository' setting for 'invoke top-level maven targets' Erich Mauerböck I confirm your bug, I reproduced it (and JENKINS-14613 at the same time). In fact they are the same. The default value of "Use private Maven repository" seems to be forced by the global configuration "Manage Jenkins" > "Maven Project Configuration" > "Local Maven Repository" If you use "Local to the workspace" or "Local to the executor" the option "Use private Maven repository" of 'Invoke top-level Maven targets' pre-build or post build step will be always activated ( JENKINS-14613 ) If you use "Default ( ~/.m2/repository)" the option "Use private Maven repository" of 'Invoke top-level Maven targets' pre-build or post build step will be always deactivated ( JENKINS-37850 ) As far as I can see the value of "Use private Maven repository" is correctly saved in the job configuration thus there is a side effect in the loading of the value when we are displaying the form 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Dominic Scheirlinck commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit My hacky fix branch is at https://github.com/vend/github-branch-source-plugin/pull/1 - it'll only work for PR builds for now. Comments welcome. In this implementation, each PR event webhook triggers up to two builds (merged/unmerged), and takes about one Github API request to do so (I think, checking the collaborators for .isTrusted?). Pushes to a PR that is already open won't trigger a build, which is a shame (need to rewrite this logic into a pull event subscriber too). But editing the PR, or adding/removing a label should. 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-32790) Unable to serialize
Title: Message Title Jesse Glick commented on JENKINS-32790 Re: Unable to serialize Would not work anyway due to JENKINS-36082. Using the Extract *.zip/*.tar.gz installer does not seem to be a viable workaround, because it does not create the directory structure expected by callers, with $TOOL_HOME/bin/docker. 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-37938) Throttle Concurrent Builds plugin causing job config web UI to misalign badly
Title: Message Title Biswajit Roy created an issue Jenkins / JENKINS-37938 Throttle Concurrent Builds plugin causing job config web UI to misalign badly Issue Type: Bug Assignee: Oleg Nenashev Attachments: Jenkins-job-config.png Components: throttle-concurrent-builds-plugin Created: 2016/Sep/02 5:37 PM Environment: All Priority: Major Reporter: Biswajit Roy Enabling Throttle concurrent builds option causes entire job configuration page to go out of bounds. It used to look fine in older Jenkins versions but its breaking the UI since latest Jenkins update. Please see attached for screenshot. Add Comment
[JIRA] (JENKINS-37570) Jenkins starts to response super slow after creating 400 branch jobs from Multi-branch-project
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-37570 Jenkins starts to response super slow after creating 400 branch jobs from Multi-branch-project Change By: Rick Liu Attachment: threaddump-02 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-32635) SNAPSHOT trigger enhacements
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32635 Re: SNAPSHOT trigger enhacements Code changed in jenkins User: Alex Zherebtsov Path: src/main/java/hudson/maven/MavenModuleSet.java src/main/resources/hudson/maven/MavenModuleSet/configure-entries.jelly http://jenkins-ci.org/commit/maven-plugin/c10cfb4dc880964cf10d952ec4109fbe5a6eae56 Log: JENKINS-32635: Fix load/save ignoreUnsuccessfulUpstreams parameter (#78) ignoreUnsuccessfulUpstreams parameter should be captured within triggerByDependency configuration in the form JSON 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-37937) Option "Schedule build when some upstream has no successful builds" is never saved
Title: Message Title Arnaud Héritier resolved as Fixed Fixed in > 2.13 (probably 2.14 or 3.0) Jenkins / JENKINS-37937 Option "Schedule build when some upstream has no successful builds" is never saved Change By: Arnaud Héritier 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
[JIRA] (JENKINS-32635) SNAPSHOT trigger enhacements
Title: Message Title Arnaud Héritier commented on JENKINS-32635 Re: SNAPSHOT trigger enhacements Fixed in 2.13 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-37937) Option "Schedule build when some upstream has no successful builds" is never saved
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-37937 Option "Schedule build when some upstream has no successful builds" is never saved Issue Type: Bug Assignee: Arnaud Héritier Components: maven-plugin Created: 2016/Sep/02 5:07 PM Priority: Minor Reporter: Arnaud Héritier Reported by Alex Zherebtsov as a PR ( https://github.com/jenkinsci/maven-plugin/pull/71 and later https://github.com/jenkinsci/maven-plugin/pull/78) the option "Schedule build when some upstream has no successful builds" added by JENKINS-32635 is never saved. Add Comment
[JIRA] (JENKINS-36082) Automatic installer fails for Docker 1.11 and latest
Title: Message Title Jesse Glick commented on JENKINS-36082 Re: Automatic installer fails for Docker 1.11 and latest AFAICT the original URLs do not work since they now offer a *.tgz package that includes various binaries as well as the client docker/docker. 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-36082) Automatic installer fails for Docker 1.11 and latest
Title: Message Title Jesse Glick started work on JENKINS-36082 Change By: Jesse Glick 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-36082) Automatic installer fails for Docker 1.11 and latest
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-36082 Automatic installer fails for Docker 1.11 and latest Change By: Jesse Glick 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-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Ryan Wallner commented on JENKINS-36544 Re: Allow setting environment variables for dynamic ec2 slaves +1 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.
