[JIRA] (JENKINS-40924) REGRESSION: Queued freestyle jobs do not show up on Activity
Title: Message Title James Dumay assigned an issue to Keith Zantow Jenkins / JENKINS-40924 REGRESSION: Queued freestyle jobs do not show up on Activity Change By: James Dumay Assignee: 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-40924) REGRESSION: Queued freestyle jobs do not show up on Activity
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40924 REGRESSION: Queued freestyle jobs do not show up on Activity Change By: James Dumay Sprint: release candidate tethys 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-40741) Optimization - remove FlowGraphAction from actions response
Title: Message Title Michael Neale updated JENKINS-40741 Jenkins / JENKINS-40741 Optimization - remove FlowGraphAction from actions response Change By: Michael Neale 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-40917) PipelinePage component should check the job type and make sure it's an AbstractPipelineImpl impl
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40917 PipelinePage component should check the job type and make sure it's an AbstractPipelineImpl impl Change By: James Dumay Sprint: post- release candidate 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-40917) PipelinePage component should check the job type and make sure it's an AbstractPipelineImpl impl
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40917 PipelinePage component should check the job type and make sure it's an AbstractPipelineImpl impl Change By: James Dumay Issue Type: Task Bug Sprint: post-release 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-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Gregor Philp updated an issue Jenkins / JENKINS-24824 Asynchronous cleanup not removing renamed workspace directories on slaves Change By: Gregor Philp Attachment: Screen Shot 2017-01-09 at 3.46.57 PM.png 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-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Gregor Philp commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves Hi, we have the same issue still on CentOS Linux 6 and 7 platforms. We'd like these to just be removed and not reported so that we have to manually remove them. We end up with 100s, 1000s of these. It seems this might be related to the problem we're having of the java heap being used up and then our master fails. I then have to restart master. thanks Gregor 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-40928) API to return execution time per stage (when running, or completed, NOT ETA or averages)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40928 API to return execution time per stage (when running, or completed, NOT ETA or averages) Change By: Michael Neale Sprint: tethys 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-35821) API to return per node averages, and ETA based on history of execution
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35821 API to return per node averages, and ETA based on history of execution Change By: Michael Neale Sprint: 1.0-m7 , tethys 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-19934) Add "Job Create" permission to project roles
Title: Message Title Oleg Nenashev commented on JENKINS-19934 Re: Add "Job Create" permission to project roles The permission does not work in such way as you may expect. You still have to enable the global permission and then to enable the Role Strategy project name verifyer in order to get the functionality working. Without the Global permission the plugin thinks that the user cannot create any job (which is a valid 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-40812) Hiera API does not response Jenkins RBAC rules
Title: Message Title Carl Caum commented on JENKINS-40812 Re: Hiera API does not response Jenkins RBAC rules I cannot find any way to write Hiera key/value pairs at all through the HTTP API, regardless of the Jenkins Global Security setting. I believe there's some confusion on how the plugin works. The user was probably expecting Pipeline scripts to not be able to write values if read-only anonymous access is configured. I'm waiting to hear back from the user to confirm. 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-19934) Add "Job Create" permission to project roles
Title: Message Title Harpreet Nain commented on JENKINS-19934 Re: Add "Job Create" permission to project roles ok thanks! Got it. The help text on the project name verifier config was a bit misleading. Noticed that even though it disables the user to configure or run that job that does to follow the pattern, the job still gets created. Would have been neat if it would give an error and not generate unnecessary jobs. 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-38982) User would like to have a fast smart search to find jobs from the dashboard
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38982 User would like to have a fast smart search to find jobs from the dashboard Change By: James Dumay Sprint: atlantic, frank, release candidate, christmas , post-release 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-40858) Some project pages don't display any information (undefined / undefined)
Title: Message Title James Dumay commented on JENKINS-40858 Re: Some project pages don't display any information (undefined / undefined) There isn't right now but feel free to create one. Ideally we want to extend Declarative Pipeline so that it has the matrix capability and we build a great UI for 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-40919) Upgrading to 1.2.0 of the liquibase plugin may result in old-data warning
Title: Message Title Keith Collison resolved as Fixed Jenkins / JENKINS-40919 Upgrading to 1.2.0 of the liquibase plugin may result in old-data warning Change By: Keith Collison 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-40920) Credentials migration fails if project has more than one liquibase builder
Title: Message Title Keith Collison resolved as Fixed Jenkins / JENKINS-40920 Credentials migration fails if project has more than one liquibase builder Change By: Keith Collison 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-40916) Unable to save temporary file in /var/lib/jenkins/jobs/...
Title: Message Title sathwik j stopped work on JENKINS-40916 Change By: sathwik j 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-40916) Unable to save temporary file in /var/lib/jenkins/jobs/...
Title: Message Title sathwik j started work on JENKINS-40916 Change By: sathwik j 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-38982) User would like to have a fast smart search to find jobs from the dashboard
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38982 User would like to have a fast smart search to find jobs from the dashboard Change By: James Dumay Sprint: atlantic, frank, release candidate, christmas 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-38982) User would like to have a fast smart search to find jobs from the dashboard
Title: Message Title James Dumay stopped work on JENKINS-38982 Change By: James Dumay 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-38982) User would like to have a fast smart search to find jobs from the dashboard
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38982 User would like to have a fast smart search to find jobs from the dashboard Change By: James Dumay Sprint: atlantic, frank, tethys, christmas 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-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Gregor Philp edited a comment on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves Hi, we have the same issue still on CentOS Linux 6 and 7 platforms. We'd like these to just be removed and not reported so that we have to manually remove them. We end up with 100s, 1000s of these. !Screen Shot 2017-01-09 at 3.46.57 PM.png|thumbnail! We have latest plugin versions:Workspace Cleanup Plugin - 0.32Resource Disposer Plugin - 0.3and running jenkins master - 2.19.4 It seems this might be related to the problem we're having of the java heap being used up and then our master fails. I then have to restart master.thanksGregor 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-40876) ObjectMetadataAction objectUrl never gets populated for PRs or Branches
Title: Message Title recampbell updated an issue Jenkins / JENKINS-40876 ObjectMetadataAction objectUrl never gets populated for PRs or Branches Change By: recampbell Issue Type: Story Bug 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-40909) Build records cannot be loaded after 2.5 → 2.6 upgrade
Title: Message Title Jesse Glick updated JENKINS-40909 Jenkins / JENKINS-40909 Build records cannot be loaded after 2.5 → 2.6 upgrade 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-38982) User would like to have a fast smart search to find jobs from the dashboard
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-38982 User would like to have a fast smart search to find jobs from the dashboard Change By: James Dumay Assignee: James Dumay 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-40898) Declarative should provide an easy way to disable/enable some steps in an PR context or not
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-40898 Declarative should provide an easy way to disable/enable some steps in an PR context or not Change By: Baptiste Mathus Summary: Declarative should provide an easy way to disable/enable some steps in an PR context or not 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-35849) Developer sees good hover states for all indicator types
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35849 Developer sees good hover states for all indicator types Change By: Michael Neale Sprint: tethys 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-35849) Developer sees good hover states for all indicator types including ETAs
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35849 Developer sees good hover states for all indicator types including ETAs Change By: Michael Neale Summary: Developer sees good hover states for all indicator types including ETAs 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-35849) Developer sees ETAs on hover states for all indicator types
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35849 Developer sees ETAs on hover states for all indicator types Change By: Michael Neale Summary: Developer sees good ETAs on hover states for all indicator types including ETAs 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-40929) Developer can see durations when hovering on indicators
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40929 Developer can see durations when hovering on indicators Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/09 11:51 PM Priority: Major Reporter: James Dumay In Scope Hovering over each node in the graph or anywhere where we display a indicator for a Pipeline (e.g. activity) Running – text: "Running for 2 minutes 32 seconds" Successful – text: "Passed in 2 minutes and 23 seconds" Unstable – text: "Passed in 2 minutes and 23 seconds but marked as unstable." Failed – text: "Failed in 2 minutes and 23 seconds" Not built – text: "Not built" Unknown – text: "Unknown" All text must be i18n'able
[JIRA] (JENKINS-40875) Obtuse error given for when credential is invalid
Title: Message Title recampbell updated an issue Jenkins / JENKINS-40875 Obtuse error given for when credential is invalid Change By: recampbell Issue Type: Story Bug 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-39794) API to check that MBP indexing has completed
Title: Message Title Michael Neale stopped work on JENKINS-39794 Change By: Michael Neale 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-40466) Developer wants to see a message when Jenkins is busy eg: execution is blocked waiting for a node
Title: Message Title James Dumay commented on JENKINS-40466 Re: Developer wants to see a message when Jenkins is busy eg: execution is blocked waiting for a node Vivek Pandey examples from today pipeline { agent { label 'foo' } // While pipeline is blocked, solved by showing the message (no steps) that we have today stages { stage ('first') { agent { label 'bar'} } stage ('second') { parallel( "foo": { agent { label 'baz' } } ) } } } // agent at pipeline level node ('foo') { stage(first) { ... } stage(second) { ... } } // how this translates from Script to Declarative stage ('first') { // StartNode node ('bar') { // We know that this is executing? If so we want to display a synthetic step with CauseOfBlockage msg // Steps } } 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-40930) WorkspaceCleanupThread doesn't work properly with Pipeline jobs
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-40930 WorkspaceCleanupThread doesn't work properly with Pipeline jobs Issue Type: Bug Assignee: Unassigned Components: core, workflow-job-plugin Created: 2017/Jan/10 1:12 AM Priority: Minor Reporter: Andrew Bayer There are a couple aspects to this: If you actually expect persistence in your workspace for some reason (I know, I know) and run the job expecting said persistence monthly, some months you'll discover that your workspace got nuked if you're in a Pipeline job. WorkspaceCleanupThread just looks for AbstractProject when checking if the workspace is the one used by the last build - that should probably be Job instead, at least for the last-built-on check. But then there's the matter of figuring out which workspaces were actually involved in the last build of a Pipeline job, which brings me to... WorkflowJob.getLastBuiltOn() always returns the master. So if we want to have WorkspaceCleanupThread not nuke the workspace(s) used in the last build of a Pipeline job, we actually need to get all workspaces that an ExecutorStep in the last build used. And that brings up a related matter... If you've got multiple workspaces for a single Pipeline job on a single agent (i.e., a @2 etc one as well as the default), say due to parallelization, only the default one gets deleted in the first place. I think this may be the case for other job types as well, but don't quote me on that quite yet. Anyway, that's a problem too. So yeah.
[JIRA] (JENKINS-13277) Global environment variables are not being resolved in Email Notification Recipients list for maven 2/3 projects
Title: Message Title Brent Duffy commented on JENKINS-13277 Re: Global environment variables are not being resolved in Email Notification Recipients list for maven 2/3 projects We are seeing a similar issue with freestyle jobs on Jenkins 2.32.1. The problem we are seeing is that if an environment variable (or build parameter) isn't defined, the variable name is treated as a string literal instead of an empty string. We see this behavior in the "Recipients" field for the built-in "E-mail notification" post-build action as well as the "Project Recipient List" for the "Editable Email Notification" post-build action provided by the email-ext plugin. To replicate this issue, try to refer to an undefined environment variable in one of those fields. The environment variable syntax we're using in the recipient list is: emailaddress1 emailaddress2 $ {TEST_EMAIL_LIST} Basically, emails will always be delivered to emailaddress1 and emailaddress2, but some jobs need to supply additional email addresses via the TEST_EMAIL_LIST build parameter. We have a job that is a downstream to several other jobs. Some of the upstream jobs (but not all) supply TEST_EMAIL_LIST as a build parameter to the downstream job. When the variable is actually defined, everything works as expected, however when it is not defined, both the built-in "Email notification" and the "Editable Email Notification" plugin will try to send an email to the address "$TEST_EMAIL_LIST", which causes an error since it is not a valid address. We would expect that an undefined environment variable would be treated as an empty string, which is how they are treated in the bash shell. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39804) Official Blue Ocean docker container
Title: Message Title James Dumay commented on JENKINS-39804 Re: Official Blue Ocean docker container Michael Neale caught up with R. Tyler Croy. He's going to add a scheduling section to the Jenkinsfile and file a PR. Then it should all just 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-40928) API to return execution time per stage (when running, or completed, NOT ETA or averages)
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-40928 API to return execution time per stage (when running, or completed, NOT ETA or averages) Issue Type: Story Assignee: Vivek Pandey Components: blueocean-plugin Created: 2017/Jan/09 11:47 PM Priority: Major Reporter: Michael Neale We need to be able to show per stage (or parallel branch) duration for then a pipeline is running, or has completed. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-36083) Error handling
Title: Message Title Brody Maclean started work on JENKINS-36083 Change By: Brody Maclean Status: Reopened 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-19934) Add "Job Create" permission to project roles
Title: Message Title Harpreet Nain commented on JENKINS-19934 Re: Add "Job Create" permission to project roles I do see the Create permission in the project roles. Even though the project role has the create permission checked, the user assigned the project role is still not able to create jobs. The only way a use can create jobs is if it is included in the global role. Hence we are unable to restrict the project names due to this limitation. Please advise. 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-39842) Open Blue Ocean button should not try to load /activity for a folder
Title: Message Title James Dumay commented on JENKINS-39842 Re: Open Blue Ocean button should not try to load /activity for a folder Tom FENNELLY feel free to bring that ticket up into the sprint 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-40847) JNLP slave pod gets created even when a different slave is configured
Title: Message Title phil swenson commented on JENKINS-40847 Re: JNLP slave pod gets created even when a different slave is configured I successfully worked around the issue by putting "jnlp" in the container name for the kubernetes container config as suggested by Lars. 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-40923) Need a way to set XCode capabilities
Title: Message Title M Douglas created an issue Jenkins / JENKINS-40923 Need a way to set XCode capabilities Issue Type: New Feature Assignee: Unassigned Components: xcode-plugin Created: 2017/Jan/09 8:49 PM Priority: Major Reporter: M Douglas It's possible to set the capabilities of a project from within XCode, but there's no easy way to do the equivalent from within a Jenkins job. Specifically, I need the ability to set "Push Notifications" to "On", but having control over all the app's capabilities would be even better. Add Comment
[JIRA] (JENKINS-37244) Consistent terminology for builds / pipeline runs
Title: Message Title James Dumay updated JENKINS-37244 Jenkins / JENKINS-37244 Consistent terminology for builds / pipeline runs Change By: James Dumay 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-40854) REGRESSION - Run button is present but looks invisible
Title: Message Title James Dumay resolved as Fixed Jenkins / JENKINS-40854 REGRESSION - Run button is present but looks invisible Change By: James Dumay 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-40672) Display accepted Pipeline input parameters
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40672 Display accepted Pipeline input parameters Change By: James Dumay Issue Type: Bug Improvement 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-40672) Display accepted Pipeline input parameters
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40672 Display accepted Pipeline input parameters Change By: James Dumay *Story* When viewing a previously finished run, a user would like to see the input values populated in the input 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-40672) Display accepted Pipeline input parameters
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40672 Display accepted Pipeline input parameters Change By: James Dumay Summary: Consistent state for completed Display accepted Pipeline input steps parameters 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-40926) Persist accepted input values
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40926 Persist accepted input values Change By: James Dumay *Use case*Developers would like to see the provided input parameters in the UI after the execution of the input step has been completed. This provides additional context about who proceeded on input and what parameters were passed.Today the input step throws away the execution data which means we are unable to later display it to the user. If the Input Step persisted its execution and values then we could build a good API 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-40926) Persist accepted input values
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40926 Persist accepted input values Change By: James Dumay *Use case*Developers would like to see the provided input parameters in the UI after the execution of the input step has been completed. This provides additional context about who proceeded on input and what parameters were passed.Today the input step throws away the execution data which means we are unable to later display it to the user. If the Input Step persisted its execution and values then we could build a good API UI 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-40927) Jenkins failing with Configuring Kubernetes
Title: Message Title tahir raza created an issue Jenkins / JENKINS-40927 Jenkins failing with Configuring Kubernetes Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2017/Jan/09 10:15 PM Priority: Minor Reporter: tahir raza Hello - I have my own Openshift 1.3 Origin Cluster and im launching Jenkins via s2i template. Jenkins docker image was built close to openshift:jenkinsci (Ben Parees: https://github.com/openshift/jenkins) with few customizations plus Ubuntu OS instead of Centos. When Jenkins is launched, it is filled with Kubernetes errors with unknown host. Although I dont think its a Jenkin bug, im looking for assistance. oc describe pod jenkins-openshift5-6-msta8 Name: jenkins-openshift5-6-msta8 Namespace: atat Security Policy: restricted Node: 192.168.54.105/192.168.54.105 Start Time: Mon, 09 Jan 2017 15:43:04 -0600 Labels: deployment=jenkins-openshift5-6 deploymentconfig=jenkins-openshift5 name=jenkins-openshift5 Status: Running IP: 192.168.194.4 Controllers: ReplicationController/jenkins-openshift5-6 Containers: jenkins: Container ID: docker://7edaa4e1e7969f4dca72a7bd3fde4458d1f98de43612fd5f7ce24446d5913253 Image: 192.168.209.251:5000/atat/jenkins-master-openshift@sha256:3a6829f5675b422d32a396880fc3383376d30d6a49d452f546460c36134b46ec Image ID: docker://f812f7844a03d5bccc63b7a558a8cf170f467e5b6a90850839a52eac00441689 Port: Limits: memory: 2Gi Requests: memory: 2Gi State: Running Started: Mon, 09 Jan 2017 15:44:45 -0600 Ready: True Restart Count: 0 Liveness: http-get http://:8080/login delay=120s timeout=3s period=10s #success=1 #failure=30 Readiness: http-get http://:8080/login delay=3s timeout=3s period=10s #success=1 #failure=3 Volume Mounts: /var/lib/jenkins from jenkins-openshift5-data (rw) /var/run/secrets/kubernetes.io/serviceaccount from jenkins-openshift5-token-flzoj (ro) Environment Variables: OPENSHIFT_ENABLE_OAUTH: false OPENSHIFT_ENABLE_REDIRECT_PROMPT: true KUBERNETES_MASTER: https://kubernetes.default:443
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay commented on JENKINS-39794 Re: API to check that MBP indexing has completed That's right Cliff. I think it would be good to know if the indexing stopped with an error or success 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-40919) Upgrading to 1.2.0 of the liquibase plugin may result in old-data warning
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40919 Re: Upgrading to 1.2.0 of the liquibase plugin may result in old-data warning Code changed in jenkins User: propspero238 Path: src/main/java/org/jenkinsci/plugins/liquibase/evaluator/ExecutedChangesetAction.java http://jenkins-ci.org/commit/liquibase-runner-plugin/a764793f69d59364cb14235fdda25e19e5886980 Log: JENKINS-40919 provide migration for rollbackOnly 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-40920) Credentials migration fails if project has more than one liquibase builder
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40920 Re: Credentials migration fails if project has more than one liquibase builder Code changed in jenkins User: propspero238 Path: src/main/java/org/jenkinsci/plugins/liquibase/evaluator/CredentialsMigrator.java src/test/java/org/jenkinsci/plugins/liquibase/evaluator/CredentialsMigratorTest.java src/test/resources/scripted-upgrade-test/oldauth_job_config.xml src/test/resources/scripted-upgrade-test/unsecured-jenkins.xml src/test/resources/scripted-upgrade-test/upgrade-credentials-test.sh src/test/resources/update-test-data.zip http://jenkins-ci.org/commit/liquibase-runner-plugin/40731449b9dba29bc91019d95fab224109225c50 Log: JENKINS-40920 no longer assuming just one liquibase builder per project. Also better way of testing migration 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-40925) "dir" context is not honored by "sh" step
Title: Message Title Roman Safronov updated an issue Jenkins / JENKINS-40925 "dir" context is not honored by "sh" step Change By: Roman Safronov If pipeline has *dir* wrapper, i.e.{code}podTemplate(...) { node('pod') {container('mycontainer') { dir('my/dir/path') {sh 'ls -l' }} }}{code}*shell* step is still executed in the context of workspace root.Same pipeline works as expected (within directory path specified by *dir* step) outside of kubernetes pod. 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-10273) Possibility to use environment variables or parameters
Title: Message Title mcrooney commented on JENKINS-10273 Re: Possibility to use environment variables or parameters Sille Kyatha, I'm not sure that $ {BUILD_NUMBER} format is supported, can you try just $BUILD_NUMBER and report back? 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-40925) "dir" context is not honored by "sh" step
Title: Message Title Roman Safronov created an issue Jenkins / JENKINS-40925 "dir" context is not honored by "sh" step Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2017/Jan/09 9:09 PM Environment: Jenkins 2.32.1 pipeline 2.4 kubernetes-plugin 0.10 Priority: Minor Reporter: Roman Safronov If pipeline has dir wrapper, i.e. podTemplate(...) { node('pod') { container('mycontainer') { dir('my/dir/path') { sh 'ls -l' } } } } shell step is still executed in the context of workspace root. Same pipeline works as expected (within directory path specified by dir step) Add Comment
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40370 Re: Run stage when branch name matches Code changed in jenkins User: Andrew Bayer Path: SYNTAX.md pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/AbstractModelASTCodeBlock.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTWhen.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTWhenExpression.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidator.java pipeline-model-api/src/main/resources/ast-schema.json pipeline-model-declarative-agent/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/DeclarativeAgent.java pipeline-model-declarative-agent/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/DeclarativeAgentDescriptor.java pipeline-model-declarative-agent/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/DeclarativeAgentScript.java pipeline-model-declarative-agent/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/withscript/WithScriptDescribable.java pipeline-model-declarative-agent/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/withscript/WithScriptDescriptor.java pipeline-model-declarative-agent/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/withscript/WithScriptScript.java pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/Utils.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Stage.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/StageConditionals.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidatorImpl.groovy pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl/Any.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl/DockerPipeline.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl/DockerPipelineFromDockerfile.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl/Label.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl/None.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/when/DeclarativeStageConditional.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/when/DeclarativeStageConditionalDescriptor.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/when/DeclarativeStageConditionalScript.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/when/impl/BranchConditional.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/when/impl/EnvironmentConditional.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/when/impl/ExpressionConditional.java pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ClosureModelTranslator.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/Messages.properties
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40370 Re: Run stage when branch name matches Code changed in jenkins User: Andrew Bayer Path: SYNTAX.md pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTPipelineDef.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTWrapper.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTWrappers.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidator.java pipeline-model-api/src/main/resources/ast-schema.json pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/Utils.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Options.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Root.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Wrappers.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/WrappersToMap.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidatorImpl.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ClosureModelTranslator.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/Messages.properties pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/OptionsTranslator.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/WrappersToMapTranslator.groovy pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/OptionsTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ValidatorTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/WrappersTest.java pipeline-model-definition/src/test/resources/errors/invalidWrapperType.groovy pipeline-model-definition/src/test/resources/json/errors/invalidWrapperType.json pipeline-model-definition/src/test/resources/json/multipleWrappers.json pipeline-model-definition/src/test/resources/json/simpleWrapper.json pipeline-model-definition/src/test/resources/multipleProperties.groovy pipeline-model-definition/src/test/resources/multipleWrappers.groovy pipeline-model-definition/src/test/resources/simpleWrapper.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/729dfabcd270c25f0ceaadfd012c019f8da70e74 Log: Merge branch 'master' into JENKINS-40370 Conflicts: pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidator.java pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidatorImpl.groovy pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ValidatorTest.java
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title Andrew Bayer updated JENKINS-40370 Jenkins / JENKINS-40370 Run stage when branch name matches Change By: Andrew Bayer 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-40547) Add testing for durability in Declarative
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40547 Re: Add testing for durability in Declarative Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/DurabilityTest.java http://jenkins-ci.org/commit/pipeline-model-definition-plugin/c22782b108c19fdc27dd3231096c016c67a2e299 Log: Merge pull request #74 from abayer/jenkins-40547 [FIXED JENKINS-40547] Verify durability of Declarative runs 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-39836) CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves
Title: Message Title Kevin Smith resolved as Fixed After some research I recognized that SSHAuthenticator.Matcher did not define a serialVersionUID and was a Serializable class due to CredentialsMatcher. I added a concrete value for this and now every platform and jdk/jre now works successfully. Jenkins / JENKINS-39836 CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves Change By: Kevin Smith Status: Open Resolved Assignee: Nicolas De Loof Kevin Smith Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40926) Persist accepted input values
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40926 Persist accepted input values Issue Type: Bug Assignee: Unassigned Components: pipeline-input-step-plugin Created: 2017/Jan/09 10:03 PM Priority: Major Reporter: James Dumay Use case Developers would like to see the provided input parameters in the UI after the execution of the input step has been completed. This provides additional context about who proceeded on input and what parameters were passed. Today the input step throws away the execution data which means we are unable to later display it to the user. Add Comment
[JIRA] (JENKINS-40921) Build Periodically setting for multibranch pipelines needs clarification
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-40921 Build Periodically setting for multibranch pipelines needs clarification Issue Type: Bug Assignee: Stephen Connolly Components: branch-api-plugin Created: 2017/Jan/09 7:39 PM Environment: O.S.: Ubuntu 15.04 (Vivid) Jenkins Version: 2.32.1 LTS SCM-API 2.0.1-beta-1 JDK version: OpenJDK Runtime Environment (build 1.8.0_45-internal-b14) Labels: ux Priority: Minor Reporter: Karl Shultz Setting the "Build Periodically" setting for a multibranch pipeline job implies that the job will be run at that interval. But the setting is intended to trigger periodic rescans of the repo, not periodic builds. The inline documentation implies that the build will be run periodically, as opposed to the branch indexing. This is misleading: Provides a cron-like feature to periodically execute this project. This feature is primarily for using Jenkins as a cron replacement, and it is not ideal for continuously building software projects. When people first start continuous integration, they are often so used to the idea of regularly scheduled builds like nightly/weekly that they use this feature. However, the point of continuous integration is to start a build as soon as a change is made, to provide a quick feedback to the change. To do that you need to hook up SCM change notification to Jenkins. So, before using this feature, stop and ask yourself if this is really what you want.
[JIRA] (JENKINS-40922) Scan Repository --> Events loading wheel needs explanation
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-40922 Scan Repository --> Events loading wheel needs explanation Issue Type: Bug Assignee: Stephen Connolly Components: branch-api-plugin Created: 2017/Jan/09 7:53 PM Environment: O.S.: Ubuntu 15.04 Jenkins Version: 2.32.1 SCM-API 2.0.1-beta-1 JDK version: OpenJDK Runtime Environment (build 1.8.0_45-internal-b14) Priority: Minor Reporter: Karl Shultz Starting with SCM-API 2.x, the "Scan Repositoy" action now includes an "Events" action underneath it. Unless there are events being processed, this page shows only a loading wheel. While this is behaving as designed, someone new to Jenkins could misinterpret an empty screen with a loading wheel as "Something is happening," or worse, "Something is broken." This issue is to request a brief explanation of what we're waiting for on this screen. Add Comment
[JIRA] (JENKINS-39747) Not all adjunct JavaScript is being coming directly from the browser cache
Title: Message Title James Dumay commented on JENKINS-39747 Re: Not all adjunct _javascript_ is being coming directly from the browser cache Good to know - thanks for looking into it! 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-39836) CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves
Title: Message Title Kevin Smith updated an issue Jenkins / JENKINS-39836 CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves Change By: Kevin Smith Component/s: ssh-credentials-plugin Component/s: git-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-40924) REGRESSION: Queued freestyle jobs do not show up on Activity
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40924 REGRESSION: Queued freestyle jobs do not show up on Activity Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/09 8:56 PM Priority: Major Reporter: James Dumay Problem Queued freestyle jobs do not show up on the Activity tab. They used to be listed there but now they are not. It was also possible to open the run result for them and wait for them to leave the queue. This is important to show as the activity tab doubles as our "queue" UI for a job or Pipeline. To reproduce Create a new freestyle job Force the job to run on a non-existant label Run the job Visit its Activity tab in Blue Ocean Add Comment
[JIRA] (JENKINS-40627) A multibranch project with no branches (only pull requests) breaks when you click on branches tab
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40627 A multibranch project with no branches (only pull requests) breaks when you click on branches tab Change By: James Dumay Sprint: release candidate tethys 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-40370) Run stage when branch name matches
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40370 Re: Run stage when branch name matches Code changed in jenkins User: Andrew Bayer Path: pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStage.java pipeline-model-definition/pom.xml pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/Converter.groovy pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/parser/GroovyShellDecoratorImpl.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BasicModelDefTest.java pipeline-model-definition/src/test/resources/json/parallelPipelineQuoteEscaping.json pipeline-model-definition/src/test/resources/json/parallelPipelineWithSpaceInBranch.json pipeline-model-definition/src/test/resources/libraryAnnotation.groovy pipeline-model-definition/src/test/resources/parallelPipelineQuoteEscaping.groovy pipeline-model-definition/src/test/resources/parallelPipelineWithSpaceInBranch.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/96a34eda839c2436181a9f9889662256d187970f Log: Merge branch 'master' into JENKINS-40370 Conflicts: pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java 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
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40370 Re: Run stage when branch name matches Code changed in jenkins User: Andrew Bayer Path: SYNTAX.md pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTAgent.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTClosureMap.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidator.java pipeline-model-api/src/main/resources/ast-schema.json pipeline-model-declarative-agent/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/DeclarativeAgentDescriptor.java pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Agent.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Root.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Stage.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidatorImpl.groovy pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl/DockerPipeline.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl/DockerPipelineFromDockerfile.java pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ClosureModelTranslator.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/Messages.properties pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl/DockerPipelineFromDockerfileScript.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl/DockerPipelineScript.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/config/FolderConfig/help-dockerLabel.html pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/config/GlobalConfig/help-dockerLabel.html pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AgentTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BasicModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/DurabilityTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ValidatorTest.java pipeline-model-definition/src/test/resources/agentDocker.groovy pipeline-model-definition/src/test/resources/agentDockerEnvSpecLabel.groovy pipeline-model-definition/src/test/resources/agentDockerEnvTest.groovy pipeline-model-definition/src/test/resources/agentDockerWithEmptyDockerArgs.groovy pipeline-model-definition/src/test/resources/agentDockerWithNullDockerArgs.groovy pipeline-model-definition/src/test/resources/agentLabel.groovy pipeline-model-definition/src/test/resources/agentTypeOrdering.groovy pipeline-model-definition/src/test/resources/buildPluginParentPOM.groovy pipeline-model-definition/src/test/resources/dockerGlobalVariable.groovy
[JIRA] (JENKINS-40929) Developer can see durations when hovering on indicators
Title: Message Title James Dumay assigned an issue to Thorsten Scherler Jenkins / JENKINS-40929 Developer can see durations when hovering on indicators Change By: James Dumay Assignee: Thorsten Scherler 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-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40877 Display links to Github PR and Branch on Pipeline Result Change By: James Dumay Priority: Major Critical 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-40596) 400 upon opening direct link of project in a GitHub organization project
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40596 400 upon opening direct link of project in a GitHub organization project Change By: Michael Neale Sprint: release candidate 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-40932) Combine all css into a single file in the JDL
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40932 Combine all css into a single file in the JDL Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/10 3:09 AM Priority: Minor Reporter: James Dumay Seems that we hit the concurrency limit in Chrome when downloading resources which causes loading to block on a cold load. We used GTMetrics's waterfall report to find this. If we can combine all the CSS in JDL together then that removes 3-4 css files we have toninitially download and can let the browser download blueocean.js earlier. In Scope Concat all CSS in the JDL Update Blue Ocean to serve the concatinated CSS Add Comment
[JIRA] (JENKINS-39647) Failed to write defaultParameterValue
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39647 Failed to write defaultParameterValue Change By: James Dumay *Context*If a plugin’s Action fails to serialize it fails the serialization of the rest response. Just like the remote APIs, Blue Ocean returns serialized Actions for many of its responses.For Blue Ocean this is incredibly important as a failed REST call can cause the entire UI to fail and the blame is assigned to Blue Ocean rather than the plugin that threw the exception. There are thousands of plugins and 1000s of ways to make the UI fall over.*In Scope* * If an Actions property fails to serialize then the serialized action should not be visible in the response * * Could we return the error somehow without failing the whole request? We might want to let the user know if we cant render that action (e.g. Test screen shouldn't look like there are no tests if the action breaks)* When serialization failure occurs, the stack trace is logged along with the identity of the plugin providing the action and a link to its wiki page explaining how to file a bug.* Original request*Getting a 500 error when attempting to hit the blue/rest service with Multibranch Pipeline. Looks like it might be an issue with Extensible Choice Paramater plugin.{code:java}java.io.IOException: Failed to write defaultParameterValue at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151) at org.kohsuke.stapler.export.Property.writeTo(Property.java:126) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeValue(Property.java:279) at org.kohsuke.stapler.export.Property.writeValue(Property.java:222) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:139) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Property.writeTo(Property.java:135) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeValue(Property.java:279) at org.kohsuke.stapler.export.Property.writeValue(Property.java:222) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:139) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeTo(Model.java:198) at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:273) at hudson.model.Api.doJson(Api.java:211) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:63) at
[JIRA] (JENKINS-12268) Merge downstream job resuls in a single email
Title: Message Title rajasekaran radhakrishnan updated an issue Jenkins / JENKINS-12268 Merge downstream job resuls in a single email Change By: rajasekaran radhakrishnan Attachment: screenshot-1.png 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-38813) NullPointerException accessing params variable with Subversion tag
Title: Message Title Christopher Head updated an issue Jenkins / JENKINS-38813 NullPointerException accessing params variable with Subversion tag Change By: Christopher Head Environment: 64-bit Oracle JVM 1.8.0_111Jenkins 2. 34 40 Subversion plugin 2.7.1Pipeline plugin 2.4Pipeline: Groovy plugin 2.23 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-31822) Unable to create HTML-report for UFT test
Title: Message Title xiwen zhao commented on JENKINS-31822 Re: Unable to create HTML-report for UFT test This is caused by Jenkins security policy change, please refer to this defect: JENKINS-39123 Current solution (workaround for LR and UFT) – published on the plugin page on jenkins.io - https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools#HPApplicationAutomationTools-ContentSecurityPolicyHeader this issue will be marked as resolved, if you need further help please leave comment in JENKINS-39123 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-31822) Unable to create HTML-report for UFT test
Title: Message Title xiwen zhao resolved as Fixed Jenkins / JENKINS-31822 Unable to create HTML-report for UFT test Change By: xiwen zhao 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-39794) API to check that MBP indexing has completed
Title: Message Title Michael Neale edited a comment on JENKINS-39794 Re: API to check that MBP indexing has completed [~cliffmeyers] yes, we want to show it is busy, until it isn't. Once it has finished, then the final state can be displayed unless there was an error (vivek says that the api can tell you if it is finished with an error or not) . If there was an error, we should show it (I doubt it will be a very nice error, but we will see. With github 90% of the time is permission so we should capture that before setting it up. The reminaining 9.99% is usually API rate limiting or network, and that should be helped by the update to the SCM api and plugins next week. An SSE event will make this work nicely in theory... [~tfennelly] you able to help vivek and cliff here? we might need some more hooks to get MBP and perhaps github org folder events published to the SSE bus, as there doesn't appear to be anything there (may not even be listeners) just yet. Cliff needs to know that a given pipeline has finished indexing at least (and in the case of github org folder scanning for repos, that it has finished). 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-40932) Combine all css into a single file in the JDL
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40932 Combine all css into a single file in the JDL Change By: James Dumay Priority: Critical Major 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-40761) i18n does not changes language in Blueocean when using the Quick Language Switcher for Chrome
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40761 i18n does not changes language in Blueocean when using the Quick Language Switcher for Chrome Change By: James Dumay Priority: Major Minor 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-40924) REGRESSION: Queued freestyle jobs do not show up on Activity
Title: Message Title James Dumay commented on JENKINS-40924 Re: REGRESSION: Queued freestyle jobs do not show up on Activity Keith Zantow let Mic or I know if this one is going to take a long 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-40933) Optimize cold load time by concatinating common JS files
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40933 Optimize cold load time by concatinating common JS files Change By: James Dumay Priority: Critical Major 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-39055) CSS3 Animations not working on IE
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39055 CSS3 Animations not working on IE Change By: Michael Neale Sprint: release candidate 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-39055) CSS3 Animations not working on IE
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39055 CSS3 Animations not working on IE Change By: Michael Neale Sprint: tethys 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-39647) Failed to write defaultParameterValue
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39647 Failed to write defaultParameterValue Change By: James Dumay * Context*If a plugin’s Action fails to serialize it fails the serialization of the rest response. Just like the remote APIs, Blue Ocean returns serialized Actions for many of its responses.For Blue Ocean this is incredibly important as a failed REST call can cause the entire UI to fail and the blame is assigned to Blue Ocean rather than the plugin that threw the exception. There are thousands of plugins and 1000s of ways to make the UI fall over.* In Scope**Original request*Getting a 500 error when attempting to hit the blue/rest service with Multibranch Pipeline. Looks like it might be an issue with Extensible Choice Paramater plugin.{code:java}java.io.IOException: Failed to write defaultParameterValue at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151) at org.kohsuke.stapler.export.Property.writeTo(Property.java:126) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeValue(Property.java:279) at org.kohsuke.stapler.export.Property.writeValue(Property.java:222) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:139) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Property.writeTo(Property.java:135) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeValue(Property.java:279) at org.kohsuke.stapler.export.Property.writeValue(Property.java:222) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:139) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeTo(Model.java:198) at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:273) at hudson.model.Api.doJson(Api.java:211) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:63) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69) at org.kohsuke.stapler.Function.renderResponse(Function.java:119) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:102) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at
[JIRA] (JENKINS-39647) Failed to write defaultParameterValue
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39647 Failed to write defaultParameterValue Change By: James Dumay *In Scope**Original request* Getting a 500 error when attempting to hit the blue/rest service with Multibranch Pipeline. Looks like it might be an issue with Extensible Choice Paramater plugin.{code:java}java.io.IOException: Failed to write defaultParameterValue at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151) at org.kohsuke.stapler.export.Property.writeTo(Property.java:126) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeValue(Property.java:279) at org.kohsuke.stapler.export.Property.writeValue(Property.java:222) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:139) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Property.writeTo(Property.java:135) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeValue(Property.java:279) at org.kohsuke.stapler.export.Property.writeValue(Property.java:222) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:139) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeTo(Model.java:198) at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:273) at hudson.model.Api.doJson(Api.java:211) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:63) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69) at org.kohsuke.stapler.Function.renderResponse(Function.java:119) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:102) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) 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$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at
[JIRA] (JENKINS-40931) Unable to disable 'bundle-audit' analyzer
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40931 Re: Unable to disable 'bundle-audit' analyzer Code changed in jenkins User: stevespringett Path: src/main/java/org/jenkinsci/plugins/DependencyCheck/DependencyCheckBuilder.java src/main/java/org/jenkinsci/plugins/DependencyCheck/DependencyCheckExecutor.java src/main/java/org/jenkinsci/plugins/DependencyCheck/Options.java src/main/resources/org/jenkinsci/plugins/DependencyCheck/DependencyCheckBuilder/global.jelly src/main/resources/org/jenkinsci/plugins/DependencyCheck/DependencyCheckBuilder/global.properties src/main/webapp/help-bundleauditpath.html src/main/webapp/help-python-analyzer-enabled.html src/main/webapp/help-python-distribution-analyzer-enabled.html src/main/webapp/help-python-package-analyzer-enabled.html src/main/webapp/help-rubybundleraudit-analyzer-enabled.html http://jenkins-ci.org/commit/dependency-check-plugin/1aaf93f1a6cfe7e4f4b5a75bb9dd9067b7e93221 Log: Changed Python analyzer configuration into separate Python distribution and Python package analyzers. They were combined before. Added missing Ruby Bundler Audit analyzer and associated bundle-audit path configuration. This resolves JENKINS-40931 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-40934) Poor performance queuing large parallel workloads
Title: Message Title Matthew Mitchell created an issue Jenkins / JENKINS-40934 Poor performance queuing large parallel workloads Issue Type: Bug Assignee: Unassigned Attachments: slowbranches.txt Components: workflow-cps-plugin Created: 2017/Jan/10 4:48 AM Priority: Major Reporter: Matthew Mitchell When the number of parallel branches in pipeline increases a lot, the performance of the pipeline decreases significantly. There appears to be an n^2 algorithm somewhere. ~200 branches - okay 4k branches - glacial Attached is a stack trace taken while the behavior was exibited. I'm pretty sure this ends up n^2: "Running CpsFlowExecution[Ownercorex_full/54:corex_full #54]" Id=421 Group=main RUNNABLE at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.getCurrentHeads(CpsFlowExecution.java:703) locked org.jenkinsci.plugins.workflow.cps.CpsFlowExecution@6ebdc0a3 at org.jenkinsci.plugins.workflow.support.actions.LogActionImpl.isRunning(LogActionImpl.java:152) at org.jenkinsci.plugins.workflow.support.actions.LogActionImpl.access$000(LogActionImpl.java:66) at org.jenkinsci.plugins.workflow.support.actions.LogActionImpl$1.onNewHead(LogActionImpl.java:93) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.notifyListeners(CpsFlowExecution.java:1081) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.notifyNewHead(CpsThreadGroup.java:381) at org.jenkinsci.plugins.workflow.cps.FlowHead.setNewHead(FlowHead.java:119) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:171) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:126) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108)
[JIRA] (JENKINS-34666) JUnit test durations accounted improperly
Title: Message Title Christopher Head updated an issue Jenkins / JENKINS-34666 JUnit test durations accounted improperly Change By: Christopher Head Environment: Linux amd64, Jenkins v2. 34 40 , jUnit plugin v1.19 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-40931) Unable to disable 'bundle-audit' analyzer
Title: Message Title Steve Springett resolved as Fixed Issue resolved and will be available in v1.4.5 Jenkins / JENKINS-40931 Unable to disable 'bundle-audit' analyzer Change By: Steve Springett 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-40931) Unable to disable 'bundle-audit' analyzer
Title: Message Title Steve Springett closed an issue as Fixed Jenkins / JENKINS-40931 Unable to disable 'bundle-audit' analyzer Change By: Steve Springett Status: Resolved Closed 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-39895) Jenkins permission denied error while building
Title: Message Title Eswari Ravinutala stopped work on JENKINS-39895 Change By: Eswari Ravinutala 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-39895) Jenkins permission denied error while building
Title: Message Title Eswari Ravinutala started work on JENKINS-39895 Change By: Eswari Ravinutala 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-25827) rebuild plugin does not support File parameters
Title: Message Title Alisdair Robertson commented on JENKINS-25827 Re: rebuild plugin does not support File parameters I'm having the same problem, Jenkins 2.39 & Rebuild Plugin 1.25. String parameters are replicated OK, but every build I need to re-upload the file parameters. This seems pretty important as the wiki page for the rebuild plugin suggests the plugin has supported file parameters since Version 1.13 (June 11, 2012). 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-12268) Merge downstream job resuls in a single email
Title: Message Title rajasekaran radhakrishnan commented on JENKINS-12268 Re: Merge downstream job resuls in a single email Still I am facing issue.. I am getting groovy script in that code.. I am not getting the values. PFB referenceRegards, Raja 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-40929) Developer can see durations when hovering on indicators
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40929 Developer can see durations when hovering on indicators Change By: James Dumay Priority: Major Critical 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-40929) Developer can see durations when hovering on indicators
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40929 Developer can see durations when hovering on indicators Change By: James Dumay Issue Type: Bug Story 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-40931) Unable to disable 'bundle-audit' analyzer
Title: Message Title Steve Springett created an issue Jenkins / JENKINS-40931 Unable to disable 'bundle-audit' analyzer Issue Type: Bug Assignee: Steve Springett Components: dependency-check-jenkins-plugin Created: 2017/Jan/10 2:34 AM Priority: Minor Reporter: Steve Springett Some analyzers supported by ODC core are not configurable in Jenkins plugin. User reported Ruby bundle-audit. Noticed a few others as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)