[JIRA] [ldap-plugin] (JENKINS-33448) LDAP config error when Manager Password is empty
Title: Message Title
Jiri Sedlak created an issue
Jenkins / JENKINS-33448
LDAP config error when Manager Password is empty
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
ldap-plugin
Created:
10/Mar/16 7:13 AM
Environment:
jenkins 1.652 with ldap-plugin version 1.11 installed on Centos7
Priority:
Major
Reporter:
Jiri Sedlak
I get following stack trace when I try to save configuretion with filled 'Manager DN' but with empty 'Manager Password'
{{javax.servlet.ServletException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ldapUserSearch': Cannot resolve reference to bean 'initialDirContextFactory' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'initialDirContextFactory': Error setting property values; nested exception is org.springframework.beans.PropertyBatchUpdateException; nested PropertyAccessExceptions (1) are: PropertyAccessException 1: org.springframework.beans.MethodInvocationException: Property 'managerPassword' threw exception; nested exception is java.lang.IllegalArgumentException: Manager password must not be empty or null. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at
[JIRA] [docker-plugin] (JENKINS-33437) Add network field
Title: Message Title Fabrice Bois resolved as Fixed Issue resolved; pull request: https://github.com/jenkinsci/docker-plugin/pull/384 Jenkins / JENKINS-33437 Add network field Change By: Fabrice Bois Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-plugin] (JENKINS-33437) Add network field
Title: Message Title Fabrice Bois started work on JENKINS-33437 Change By: Fabrice Bois Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership-plugin] (JENKINS-33447) Add the "Reset ownership" action to Manage Ownership pages
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-33447 Add the "Reset ownership" action to Manage Ownership pages Issue Type: New Feature Assignee: Oleg Nenashev Components: ownership-plugin Created: 10/Mar/16 6:57 AM Priority: Major Reporter: Oleg Nenashev This improvement has been proposed by Markus Eisenmann. Seems I've missed this feature in my Folder plugin integration TODO list. A helpful feature (for us), would be the ownership-inheritance on subordinate jobs in a (cloudbees-) folder. If I overwrite the ownership of a job, there's no possibility to revert to inherited ownership. To prevent the need to manually edit the job-configuration, a button - like "Clear Ownership" - would be helpful. For example, to clean ownership (if no longer needed) or in this case, to revert to inherited (folder-) ownership. Add Comment
[JIRA] [jira-plugin] (JENKINS-33446) JIRA plugin: NPE When Jira Release version parameter defined
Title: Message Title Michael Barzilovich created an issue Jenkins / JENKINS-33446 JIRA plugin: NPE When Jira Release version parameter defined Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 10/Mar/16 4:03 AM Priority: Major Reporter: Michael Barzilovich Steps to reproduce: Jenkins: 1.652 JiraPlugin: 2.2 Add JIRA Release Version Parametr Build. Actual result: Started by user Mikhail Barzilovich [EnvInject] - Loading node environment variables. Building on master in workspace /var/lib/jenkins/workspace/Jira-verparam-test ERROR: Build step failed with exception java.lang.NullPointerException at hudson.plugins.jira.versionparameter.JiraVersionParameterValue.buildEnvironment(JiraVersionParameterValue.java:28) at hudson.model.ParametersAction.buildEnvVars(ParametersAction.java:89) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:950) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:88) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:64) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at
[JIRA] [git-client-plugin] (JENKINS-33433) jobs fail to "parse changelog" for pull requests with "catch-up" merges from destination branch
Title: Message Title Mark Waite edited a comment on JENKINS-33433 Re: jobs fail to "parse changelog" for pull requests with "catch-up" merges from destination branch The stack trace seems to indicate that a null pointer exception is happening in the [google-source-plugin|https://github.com/jenkinsci/google-source-plugin/blob/master/src/main/java/com/google/jenkins/plugins/metadata/scm/SourceMetadata.java#L62]. It does not seem willing to accept that sometimes the value of branch may be null.I don't know what would have changed between the previous plugin versions and the new plugin versions which would cause that. Can you provide more information about your configuration and the job which is showing that null pointer exception? As far as I can tell, the google source plugin has not changed since its original 0.1 release in 2014, so this must be due to one of the changes in either the git plugin or the git client plugin. I don't understand what you mean by a "pull request that has a catch-up". Can you explain further which source control system you're using (github, bitbucket, gitlab, something else) and how the pull request is represented which is causing the null pointer exception? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-33433) jobs fail to "parse changelog" for pull requests with "catch-up" merges from destination branch
Title: Message Title Mark Waite commented on JENKINS-33433 Re: jobs fail to "parse changelog" for pull requests with "catch-up" merges from destination branch The stack trace seems to indicate that a null pointer exception is happening in the google-source-plugin. It does not seem willing to accept that sometimes the value of branch may be null. I don't know what would have changed between the previous plugin versions and the new plugin versions which would cause that. Can you provide more information about your configuration and the job which is showing that null pointer exception? As far as I can tell, the google source plugin has not changed since its original 0.1 release in 2014, so this must be due to one of the changes in either the git plugin or the git client plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-33445) GitScmSource does not return tags via retrieve method
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-33445 GitScmSource does not return tags via retrieve method Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-33445) GitScmSource does not return tags via retrieve method
Title: Message Title Chris Smart created an issue Jenkins / JENKINS-33445 GitScmSource does not return tags via retrieve method Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 10/Mar/16 3:32 AM Labels: git Priority: Minor Reporter: Chris Smart Currently the GitScmSource class does not expose tags in the list of branches that are returned via the retrieve method. This means that plugins which make use of this class are unable to build against specific tags, for example the multi-branch-plugin[1]. [1] https://wiki.jenkins-ci.org/display/JENKINS/Multi-Branch+Project+Plugin Add Comment
[JIRA] [core] (JENKINS-32190) UsageStatistics Page Decorator may get called during initialization.
Title: Message Title dogfood commented on JENKINS-32190 Re: UsageStatistics Page Decorator may get called during initialization. Integrated in jenkins_main_trunk #4497 Revert " JENKINS-32190 Make UsageStatistics#isDue check Jenkins init (Revision b2013edbf7a4d40df2bc05a1e219d8599e642961) Result = SUCCESS kohsuke : b2013edbf7a4d40df2bc05a1e219d8599e642961 Files : core/src/main/java/hudson/model/UsageStatistics.java Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32190) UsageStatistics Page Decorator may get called during initialization.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32190 Re: UsageStatistics Page Decorator may get called during initialization. Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/model/UsageStatistics.java http://jenkins-ci.org/commit/jenkins/b67bb4c602192c39b28a58dba808f20ab4cb7e36 Log: Merge pull request #2109 from jenkinsci/ JENKINS-32190 Revert JENKINS-32190 fix Compare: https://github.com/jenkinsci/jenkins/compare/f56ace54d173...b67bb4c60219 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-33372) Perforce:Publish assets override new changes
Title: Message Title Guy Oh commented on JENKINS-33372 Re: Perforce:Publish assets override new changes Thanks Paul I did try to use different WorkSpace and eliminate the unnecessary Section (it is not one file only) however it seems that the process doesn't take the mapping into account as the relevant stream it is attached to has its own mapping which seems to override the configuration I put in It seems to me that i'll have to create a designated stream (possibly virtual stream) that will be connected to my Development stream and filter unnecessary path from there. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33444) Archiving artifacts are a prerequisite for testing
Title: Message Title Alastair D'Silva created an issue Jenkins / JENKINS-33444 Archiving artifacts are a prerequisite for testing Issue Type: Improvement Assignee: huybrechts Components: core, parameterized-trigger-plugin Created: 10/Mar/16 1:44 AM Environment: Jenkins 1.650 Parameterized Trigger Plugin 2.30 Labels: artifacts parameterized-trigger Priority: Minor Reporter: Alastair D'Silva Use case: Build should be marked as unstable if a downstream test job fails. In order to achieve this, the Parameterized Trigger plugin must be used to launch the test job during the build phase. The test job requires the artifacts to be present. Unfortunately, If the trigger is placed in the post-build step, it cannot alter the state of the build. Further, if used in a multi-configuration project, the trigger is executed in the scope of the parent job, rather than the child, so the particular axis information, workspace, and other child job specific bits of information are not
[JIRA] [ec2-plugin] (JENKINS-32690) Cannot manually provision new slave if one already exists
Title: Message Title Patrick Mihelich commented on JENKINS-32690 Re: Cannot manually provision new slave if one already exists Similar problem here. It takes ~45 minutes to complete our init script on a brand new instance. When deploying an updated AMI, I'd like to spin up 10-15 instances ahead of time. Letting them spin up one by one to catch up with demand over a whole day is painful. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck-plugin] (JENKINS-33442) Cppcheck plugin cannot find results file if the workspace path contains an encoded '/' (%2F)
Title: Message Title Alastair D'Silva commented on JENKINS-33442 Re: Cppcheck plugin cannot find results file if the workspace path contains an encoded '/' (%2F) This pull request fixes this issue: https://github.com/jenkinsci/cppcheck-plugin/pull/30 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multi-branch-project-plugin] (JENKINS-32255) Multi-branch multi-configuration projects
Title: Message Title Alastair D'Silva commented on JENKINS-32255 Re: Multi-branch multi-configuration projects This pull request adds support for multibranch matrix projects: https://github.com/jenkinsci/multi-branch-project-plugin/pull/136 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [amazon-ecs-plugin] (JENKINS-30984) ECS plugin fails to launch slaves
Title: Message Title Timothy Dalbey commented on JENKINS-30984 Re: ECS plugin fails to launch slaves I have a slightly different issue. I'm running the Docker Jenkins Container https://hub.docker.com/_/jenkins/ and I think I have the ECS Plugin correctly configured. The security group is wide open as well. Here's the error message that I keep getting: Provisioned slave ECS Slave ecs debian failed to launch java.lang.IllegalStateException: ECS Slave ecs-45a76c70683 (ecs task arn:aws:ecs:us-east-1:711200063112:task/d3af9497-0d9b-4069-a41c-d3ea49180c6e) is not connected after 100 seconds at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:278) at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:218) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) I have attempted -v /var/run/docker.sock:/var/run/docker.sock -v $(which docker):/bin/docker to no avail. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck-plugin] (JENKINS-33442) Cppcheck plugin cannot find results file if the workspace path contains an encoded '/' (%2F)
Title: Message Title Alastair D'Silva created an issue Jenkins / JENKINS-33442 Cppcheck plugin cannot find results file if the workspace path contains an encoded '/' (%2F) Issue Type: Bug Assignee: Gregory Boissinot Components: cppcheck-plugin Created: 09/Mar/16 11:52 PM Environment: Jenkins 1.650 Cppcheck Plugin 1.21 Labels: cppcheck Priority: Blocker Reporter: Alastair D'Silva When using this plugin with the Multibranch plugin (https://wiki.jenkins-ci.org/display/JENKINS/Multi-Branch+Project+Plugin), Cppcheck fails to find the XML results file if the branch name contains a '/' (encoded as '%2F' on the filesystem). This is because the XML parser is trying to decode the encoded characters itself, replacing the '%2F' with a '/'. Opening the file directly in the Cppcheck plugin and passing a stream to the XML parser instead fixes the problem. This may be related to JENKINS-30026?
[JIRA] [credentials-plugin] (JENKINS-31863) Sort Credentials list by name
Title: Message Title Andrae Raymond commented on JENKINS-31863 Re: Sort Credentials list by name Moving to major. This is a real pain point for instances with many credentials. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-31863) Sort Credentials list by name
Title: Message Title Andrae Raymond updated an issue Jenkins / JENKINS-31863 Sort Credentials list by name Change By: Andrae Raymond Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-33441) GitSCMSource: Includes & excludes match more than expected
Title: Message Title Alastair D'Silva commented on JENKINS-33441 Re: GitSCMSource: Includes & excludes match more than expected Fixed by the following pull request: https://github.com/jenkinsci/git-plugin/pull/383 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-33440) Maven build with submodules with junit reports overwrite xunit attached reports
Title: Message Title Dan Dumont commented on JENKINS-33440 Re: Maven build with submodules with junit reports overwrite xunit attached reports This may not be an issue strictly with submodules. Our single module builds that do this always generate unit test reports without surefire or maven-integrated plugins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-33441) GitSCMSource: Includes & excludes match more than expected
Title: Message Title
Alastair D'Silva created an issue
Jenkins / JENKINS-33441
GitSCMSource: Includes & excludes match more than expected
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
09/Mar/16 10:43 PM
Environment:
Jenkins 1.650 Git Plugin 2.4.2
Labels:
git scm
Priority:
Blocker
Reporter:
Alastair D'Silva
When filtering branches with the Multibranch plugin (https://wiki.jenkins-ci.org/display/JENKINS/Multi-Branch+Project+Plugin), user supplied filters in includes/excludes matches more than is expected.
For example, including 'master' matches both 'master' & 'foo/master'.
Attempts to anchor the substring match do not work, as the characters are quoted before being passed to the regex engine.
The following patch addresses the problem by anchoring each element at the start & end: @@ -318,7 +319,7 @@ public abstract class AbstractGitSCMSource extends SCMSource { if (wildcard.startsWith("*") ||
[JIRA] [core] (JENKINS-33414) Provide an API to allow detecting if running on the Jenkins JVM
Title: Message Title dogfood commented on JENKINS-33414 Re: Provide an API to allow detecting if running on the Jenkins JVM Integrated in jenkins_main_trunk #4496 Result = UNSTABLE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33425) Log shutdown progress and make more resilient to errors
Title: Message Title dogfood commented on JENKINS-33425 Re: Log shutdown progress and make more resilient to errors Integrated in jenkins_main_trunk #4496 [FIXED JENKINS-33425] Refactored the cleanUp() method to log progress (Revision ce5efbc3517632a9c5ce2265d5e996dda13d0e10) JENKINS-33425 w00t we can use addSuppressed (Revision f421f32944b18a5457282be688a2afd844b567bf) JENKINS-33425 Better timer cancellation (Revision 42ff7850bd5ea938d62dc463bd609dfe0fc5f639) Result = UNSTABLE stephen connolly : ce5efbc3517632a9c5ce2265d5e996dda13d0e10 Files : core/src/main/java/jenkins/model/Jenkins.java stephen connolly : f421f32944b18a5457282be688a2afd844b567bf Files : core/src/main/java/jenkins/model/Jenkins.java stephen connolly : 42ff7850bd5ea938d62dc463bd609dfe0fc5f639 Files : core/src/main/java/jenkins/model/Jenkins.java Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] [xunit-plugin] (JENKINS-33440) Maven build with submodules with junit reports overwrite xunit attached reports
Title: Message Title Dan Dumont created an issue Jenkins / JENKINS-33440 Maven build with submodules with junit reports overwrite xunit attached reports Issue Type: Bug Assignee: Gregory Boissinot Attachments: Capture.png Components: xunit-plugin Created: 09/Mar/16 10:05 PM Priority: Minor Reporter: Dan Dumont Our maven build has a few submodules and one of them performs a single unit test with surefire. In another module we run some unit tests without surefire and output to junit format. At the end we want to use this plugin to aggregate the 2 junit result files, but when we do that, the ones that come from maven always overwrite the ones specified by this plugin. The only way we get to see the graph properly is when the other module fails to produce a junit report. The maven-generated report gets included whether or not I specify it in the xunit config, as long as it exists.
[JIRA] [copyartifact-plugin] (JENKINS-30027) Ability to unzip artifacts
Title: Message Title Martin Weber commented on JENKINS-30027 Re: Ability to unzip artifacts TeamCity has a great syntax to specify zipping.and unzipping. See https://confluence.jetbrains.com/display/TCD9/Configuring+General+Settings#ConfiguringGeneralSettings-PathsPatterns Would be very useful if the Archive Artifacts publisher supports the same syntax for zipping, too. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-33084) Git Parameter plugin should prune stale remote branches
Title: Message Title michael giroux commented on JENKINS-33084 Re: Git Parameter plugin should prune stale remote branches Thanks for the support. Will watch for the update. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33416) Add more filters [Job Filter Plugin]
Title: Message Title Ludovic Fernandez commented on JENKINS-33416 Re: Add more filters [Job Filter Plugin] https://github.com/jenkinsci/job-dsl-plugin/pull/777 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33416) Add more filters [Job Filter Plugin]
Title: Message Title Ludovic Fernandez updated an issue Jenkins / JENKINS-33416 Add more filters [Job Filter Plugin] Change By: Ludovic Fernandez Add support for filters from Job Filter Plugin. See pull request : https://github.com/jenkinsci/job-dsl-plugin/pull/773 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33416) Add more filters [Job Filter Plugin]
Title: Message Title Ludovic Fernandez commented on JENKINS-33416 Re: Add more filters [Job Filter Plugin] https://github.com/jenkinsci/job-dsl-plugin/pull/778 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33425) Log shutdown progress and make more resilient to errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33425 Re: Log shutdown progress and make more resilient to errors Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/f56ace54d173020724d4f3199359df8a191fa311 Log: Merge pull request #2103 from stephenc/jenkins-33425 [FIXED JENKINS-33425] Refactored the cleanUp() method to log progress and push for completion Compare: https://github.com/jenkinsci/jenkins/compare/c5759f957b85...f56ace54d173 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33425) Log shutdown progress and make more resilient to errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33425 Re: Log shutdown progress and make more resilient to errors Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/42ff7850bd5ea938d62dc463bd609dfe0fc5f639 Log: JENKINS-33425 Better timer cancellation Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33425) Log shutdown progress and make more resilient to errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33425 Re: Log shutdown progress and make more resilient to errors Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/ce5efbc3517632a9c5ce2265d5e996dda13d0e10 Log: [FIXED JENKINS-33425] Refactored the cleanUp() method to log progress and push for completion Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33425) Log shutdown progress and make more resilient to errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33425 Re: Log shutdown progress and make more resilient to errors Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/f421f32944b18a5457282be688a2afd844b567bf Log: JENKINS-33425 w00t we can use addSuppressed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33425) Log shutdown progress and make more resilient to errors
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-33425 Log shutdown progress and make more resilient to errors Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32571) Preserve original security settings after calling CLICommandInvoker.invoke()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32571 Re: Preserve original security settings after calling CLICommandInvoker.invoke() Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/cli/CLICommandInvoker.java http://jenkins-ci.org/commit/jenkins-test-harness/e1d92561782987d8a6b51285a81790bd52f378ec Log: Merge pull request #6 from pjanouse/ JENKINS-32571 -invoke [FIXED JENKINS-32571] Preserve original security settings after calling CommandInvoker.invoke() Compare: https://github.com/jenkinsci/jenkins-test-harness/compare/1d32b054ae59...e1d925617829 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32571) Preserve original security settings after calling CLICommandInvoker.invoke()
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32571 Preserve original security settings after calling CLICommandInvoker.invoke() Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32571) Preserve original security settings after calling CLICommandInvoker.invoke()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32571 Re: Preserve original security settings after calling CLICommandInvoker.invoke() Code changed in jenkins User: Ing. Pavel Janousek Path: src/main/java/hudson/cli/CLICommandInvoker.java http://jenkins-ci.org/commit/jenkins-test-harness/07e5d6ab711786b1cf02d13e03abbc14c4ca6dd9 Log: JENKINS-32571 Preserve original security settings after calling CommandInvoker.invoke() Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-32535) Improve test coverage of CLI commands 'add-job-to-view' and 'remove-job-from-view'
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32535 Improve test coverage of CLI commands 'add-job-to-view' and 'remove-job-from-view' Change By: Jesse Glick Labels: testing Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32571) Preserve original security settings after calling CLICommandInvoker.invoke()
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32571 Preserve original security settings after calling CLICommandInvoker.invoke() Change By: Jesse Glick Labels: testing Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-33084) Git Parameter plugin should prune stale remote branches
Title: Message Title Boguslaw Klimas commented on JENKINS-33084 Re: Git Parameter plugin should prune stale remote branches Hi, The solution to this problem is https://github.com/jenkinsci/git-parameter-plugin/pull/13, I plans put it to in release 0.4.1. https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30749) Jenkins should be secure out of the box by default
Title: Message Title Daniel Beck resolved as Fixed Fixed towards 2.0. Jenkins / JENKINS-30749 Jenkins should be secure out of the box by default Change By: Daniel Beck Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33439) Support CloudBees Docker Build and Publish plugin 1.2
Title: Message Title Ludovic Fernandez commented on JENKINS-33439 Re: Support CloudBees Docker Build and Publish plugin 1.2 https://github.com/jenkinsci/job-dsl-plugin/pull/776 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33416) Add more filters [Job Filter Plugin]
Title: Message Title Ludovic Fernandez updated an issue Jenkins / JENKINS-33416 Add more filters [Job Filter Plugin] Change By: Ludovic Fernandez Issue Type: Improvement New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33439) Support CloudBees Docker Build and Publish plugin 1.2
Title: Message Title Ludovic Fernandez created an issue Jenkins / JENKINS-33439 Support CloudBees Docker Build and Publish plugin 1.2 Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 09/Mar/16 8:17 PM Environment: Support CloudBees Docker Build and Publish plugin 1.2 Priority: Minor Reporter: Ludovic Fernandez Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-30749) Jenkins should be secure out of the box by default
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30749 Re: Jenkins should be secure out of the box by default Code changed in jenkins User: kzantow Path: core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/model/UpdateCenter.java core/src/main/java/hudson/security/FullControlOnceLoggedInAuthorizationStrategy.java core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java core/src/main/java/jenkins/install/InstallState.java core/src/main/java/jenkins/install/InstallUtil.java core/src/main/java/jenkins/install/SetupWizard.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/config.jelly core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/_entryForm.jelly core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/_entryFormPage.jelly core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/addUser.jelly core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/firstUser.jelly core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/setupWizardFirstUser.jelly core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/signup.jelly core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/signupWithFederatedIdentity.jelly core/src/main/resources/jenkins/install/SetupWizard/authenticate-security-token.jelly core/src/main/resources/jenkins/install/SetupWizard/index.jelly core/src/main/resources/jenkins/install/SetupWizard/proxy-configuration.jelly core/src/main/resources/jenkins/install/pluginSetupWizard.properties core/src/main/resources/jenkins/model/Jenkins/login.jelly core/src/main/resources/jenkins/model/Jenkins/loginError.jelly core/src/main/resources/lib/layout/html.jelly core/src/main/resources/lib/layout/layout.jelly test/src/test/java/hudson/model/UpdateCenterPluginInstallTest.java war/src/main/js/api/securityConfig.js war/src/main/js/pluginSetupWizard.js war/src/main/js/pluginSetupWizardGui.js war/src/main/js/templates/firstUserPanel.hbs war/src/main/js/templates/incompleteInstallationPanel.hbs war/src/main/js/templates/offlinePanel.hbs war/src/main/js/templates/pluginSelectionPanel.hbs war/src/main/js/templates/proxyConfigPanel.hbs war/src/main/js/templates/setupCompletePanel.hbs war/src/main/js/templates/successPanel.hbs war/src/main/js/templates/welcomePanel.hbs war/src/main/js/util/jenkins.js war/src/main/less/pluginSetupWizard.less war/src/test/js/pluginSetupWizard-spec.js http://jenkins-ci.org/commit/jenkins/5368c96404d415451bb657aea8073834c8bd815b Log: JENKINS-30749 - make Jenkins secure out of the box: create initial admin user with difficult password (based on UUID) force login with password as security token force initial admin user creation
[JIRA] [winstone-jetty] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Daniel Beck commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors Yoann Dubreuil Winstone 3.x is on Jetty 9.2.15: https://github.com/jenkinsci/winstone/blob/d016188767386d8b9f64e728b6a98e39cab695a8/pom.xml#L250 So https://github.com/jenkinsci/jenkins/pull/2108 should do the trick. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [kubernetes-plugin] (JENKINS-33419) "Kubernetes Service Account" credential does not show up
Title: Message Title Linus Arver commented on JENKINS-33419 Re: "Kubernetes Service Account" credential does not show up Thank you for the explanation Carlos Sanchez; I am new to Jenkins and k8s and was not aware of the implications. I think it might be worth considering adding in your explanation to the official README though, for those simply trying to set everything up for the first time. The current screenshots at https://wiki.jenkins-ci.org/display/JENKINS/Kubernetes+Plugin and https://github.com/jenkinsci/kubernetes-plugin both use a "Kubernetes Service Account" credential type and it may not be immediately clear to someone new to these techs the requirements to set it up. I'll file a pull request later today if you don't mind for the README (I'm not sure how the Jenkins wiki page editing works). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [kubernetes-plugin] (JENKINS-33419) "Kubernetes Service Account" credential does not show up
Title: Message Title Linus Arver closed an issue as Not A Defect Jenkins / JENKINS-33419 "Kubernetes Service Account" credential does not show up Change By: Linus Arver Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [winstone-jetty] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Elijah Zupancic commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors Thanks for your prompt action. That fix looks like it will solve the problem but it makes me sad. It is doing math to determine the thread count by computing the number of cores available. In the container world, we are seeing things like CPU shares or fair-share scheduling algorithms used to dice up CPU while exposing all of the cores to the OS. This leads to a bunch of weird performance problems especially if CPU to thread affinity is set. This way of configuring applications is not going to be sustainable long-term based on where OS containerization is heading. I'll add a feature request after this issue is fixed to allow for the manual configuration of the number of threads for acceptors, selectors, etc. Once again - thanks for your work. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33438) replay-pipeline CLI command should have a consoleOutput option
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33438 Re: replay-pipeline CLI command should have a consoleOutput option Code changed in jenkins User: Jesse Glick Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayCommand.java http://jenkins-ci.org/commit/workflow-plugin/1d45a6ea661f84f3588668bc0c9a023510303cd9 Log: Deleting comment now filed as JENKINS-33438. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [winstone-jetty] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Yoann Dubreuil commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors Thanks for the attachments, it's pretty clear that glibc is not to blame here, with only 200Mb of RSS for the process. DropWizard team hit the same issue, which was fixed in Jetty after their report. Daniel Beck I think we should consider upgrading Jetty to 9.2.2.v20140723 to get this fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33438) replay-pipeline CLI command should have a consoleOutput option
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-33438 replay-pipeline CLI command should have a consoleOutput option Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 09/Mar/16 7:47 PM Priority: Minor Reporter: Jesse Glick This should do this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-31838) Virtual thread dump uses phony filenames
Title: Message Title Jesse Glick commented on JENKINS-31838 Re: Virtual thread dump uses phony filenames Even more desirable for JENKINS-32727 : we would like to refer to Jenkinsfile and servers.groovy, not Main script and Script1. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-plugin] (JENKINS-33437) Add network field
Title: Message Title Fabrice Bois created an issue Jenkins / JENKINS-33437 Add network field Issue Type: New Feature Assignee: Fabrice Bois Components: docker-plugin Created: 09/Mar/16 7:43 PM Labels: plugin jenkins docker Priority: Minor Reporter: Fabrice Bois Currently, if your slaves need another container for their execution, they can use the links to relate them. But if you are in a multi-host environment; you can not use the link system. You must use the network parameter. Add Comment
[JIRA] [publish-over-ssh-plugin] (JENKINS-27963) Please add support for jenkins pipeline plugin to publish-over-ssh
Title: Message Title vijaysl commented on JENKINS-27963 Re: Please add support for jenkins pipeline plugin to publish-over-ssh The sshagent doesn't appear to support username password authentication Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [log-parser-plugin] (JENKINS-33436) List of warnings/errors/infos UX improvements
Title: Message Title Patrick Szalapski started work on JENKINS-33436 Change By: Patrick Szalapski Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [log-parser-plugin] (JENKINS-33436) List of warnings/errors/infos UX improvements
Title: Message Title Patrick Szalapski commented on JENKINS-33436 Re: List of warnings/errors/infos UX improvements What is the next step toward getting this pull request approved? I am happy to take further action if required. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-33386) Shared project in Visual Studio solution not being pulled into workspace
Title: Message Title Olivier Dagenais commented on JENKINS-33386 Re: Shared project in Visual Studio solution not being pulled into workspace I forgot to mention that the Cloaked paths feature was first made available in version 4.1.0. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-33386) Shared project in Visual Studio solution not being pulled into workspace
Title: Message Title Olivier Dagenais resolved as Not A Defect Hi Andrew, If I understand correctly, your TFVC repo looks something like this: $/Example/ Share/ SharedProject.csproj Project/ Solution.sln OtherProject/ Solution.sln ...and it sounds like you set the Project path field to $/Example/Project, is that correct? In that case, the behaviour is expected. Until JENKINS-4542 is implemented, here's how you can make your scenario work: Set the Project path field to $/Example Add $/Example/OtherProject and any other paths under $/Example you don't need/want to the Cloaked paths field I also encourage you to consider keeping SharedProject separate, releasing a NuGet package for it and having Project, OtherProject, etc. consume the NuGet package. Please let me know if that works for you. Thanks! - Oli Jenkins / JENKINS-33386 Shared project in Visual Studio solution not being pulled into workspace Change By: Olivier Dagenais Status: Open Resolved Assignee: redsolo Andrew Luck Resolution: Not A Defect
[JIRA] [log-parser-plugin] (JENKINS-33436) List of warnings/errors/infos UX improvements
Title: Message Title Patrick Szalapski created an issue Jenkins / JENKINS-33436 List of warnings/errors/infos UX improvements Issue Type: Improvement Assignee: Patrick Szalapski Components: log-parser-plugin Created: 09/Mar/16 7:23 PM Priority: Minor Reporter: Patrick Szalapski Wish for these two UX improvements: "Show only this" link to same results frameset More compact list of errors/warnings/infos with ellipses, which expand when hovered. I implemented these items in pull request 17: https://github.com/jenkinsci/log-parser-plugin/pull/17. Add Comment
[JIRA] [core] (JENKINS-23507) FilePath.installIfNecessaryFrom does not follow HTTP 30x redirects
Title: Message Title Jacquelin Delacrose started work on JENKINS-23507 Change By: Jacquelin Delacrose Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-31863) Sort Credentials list by name
Title: Message Title Andrae Raymond edited a comment on JENKINS-31863 Re: Sort Credentials list by name I 've added commit and would like to make a pull request for a fix .Here is the after result of a list containing 27 entries.!http://s27.postimg.org/57dhrf7bn/sorted.png! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23507) FilePath.installIfNecessaryFrom does not follow HTTP 30x redirects
Title: Message Title Jacquelin Delacrose assigned an issue to Jacquelin Delacrose Jenkins / JENKINS-23507 FilePath.installIfNecessaryFrom does not follow HTTP 30x redirects Change By: Jacquelin Delacrose Assignee: Jacquelin Delacrose Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-31863) Sort Credentials list by name
Title: Message Title Andrae Raymond edited a comment on JENKINS-31863 Re: Sort Credentials list by name I've added commit and pull request.Here is the after result of a list containing 27 entries. !http://s27.postimg.org/57dhrf7bn/sorted.png! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-31863) Sort Credentials list by name
Title: Message Title Andrae Raymond commented on JENKINS-31863 Re: Sort Credentials list by name I've added commit and pull request. Here is the after result of a list containing 27 entries. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-31863) Sort Credentials list by name
Title: Message Title Andrae Raymond updated an issue Jenkins / JENKINS-31863 Sort Credentials list by name Change By: Andrae Raymond As I user, I would like to see the credentials list sorted.Currently, we have a lot of credentials which creates a long unorganized list. it is hard to find credentials to use due to it being unsorted by name.This can be very severe for a large organization that uses Jenkins. It causes duplicates and difficulty finding accounts especially accounts with similar names. !http://example.com/image.png! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-31863) Sort Credentials list by name
Title: Message Title Andrae Raymond updated an issue Jenkins / JENKINS-31863 Sort Credentials list by name Change By: Andrae Raymond As I user, I would like to see the credentials list sorted.Currently, we have a lot of credentials which creates a long unorganized list. it is hard to find credentials to use due to it being unsorted by name.This can be very severe for a large organization that uses Jenkins. It causes duplicates and difficulty finding accounts especially accounts with similar names.!http:// example s12 . com postimg.org / image 5boefgix9/unsorted .png! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-33435) TFS SDK fails with TF14045 when encountering an unrecognized identity
Title: Message Title Olivier Dagenais created an issue Jenkins / JENKINS-33435 TFS SDK fails with TF14045 when encountering an unrecognized identity Issue Type: Bug Assignee: Olivier Dagenais Components: tfs-plugin Created: 09/Mar/16 7:05 PM Environment: TFS 2015 Priority: Minor Reporter: Olivier Dagenais A user reported a build failing with a stacktrace like the following: Listing workspaces from http://:8080/tfs/... FATAL: hudson.remoting.ProxyException: com.microsoft.tfs.core.exceptions.TECoreException: TF14045: The identity is not a recognized identity. java.lang.RuntimeException: hudson.remoting.ProxyException: com.microsoft.tfs.core.exceptions.TECoreException: TF14045: The identity is not a recognized identity. at hudson.plugins.tfs.model.Server.execute(Server.java:110) at hudson.plugins.tfs.model.Workspaces.getListFromServer(Workspaces.java:33) at hudson.plugins.tfs.model.Workspaces.populateMapFromServer(Workspaces.java:42) at hudson.plugins.tfs.model.Workspaces.exists(Workspaces.java:68) at hudson.plugins.tfs.actions.CheckoutAction.getProject(CheckoutAction.java:82) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:50) at
[JIRA] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-33434 no post build step to set status to 'success' Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 09/Mar/16 7:01 PM Priority: Minor Reporter: Jae Gangemi there is only a post build step to set the status to 'pending', which doesn't make a lot of sense and i don't want to use a post build action to set this. Add Comment This message was sent by
[JIRA] [core] (JENKINS-32190) UsageStatistics Page Decorator may get called during initialization.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32190 Re: UsageStatistics Page Decorator may get called during initialization. Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/model/UsageStatistics.java http://jenkins-ci.org/commit/jenkins/b2013edbf7a4d40df2bc05a1e219d8599e642961 Log: Revert " JENKINS-32190 Make UsageStatistics#isDue check Jenkins init level before generating stats." This reverts commit d8a13ac07c4357eb74ab45a03955c0db430e3aa9. I noticed a strange drop in usage statistics from the mid Jan 2016, which corresponds to the time this change was released in the wild, and further drop when LTS 1.642.2 is released with this change at the end of Feb. I spent some time trying to determine how this might cause instances to stop sending data, but I couldn't come up with any. I left those notes in JENKINS-32190 . There was some strange behaviours, but none explains what this is. So I'd like to back out this change and see if that makes any impact on the stats collection. If it backs up, then we know empirically this change is to blame, so that would justify spending further effort or come up with a fix from a different angle. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-31863) Sort Credentials list by name
Title: Message Title Andrae Raymond updated an issue Jenkins / JENKINS-31863 Sort Credentials list by name Change By: Andrae Raymond As I user, I would like to see the credentials list sorted.Currently, we have a lot of credentials which creates a long unorganized list. it is hard to find credentials to use due to it being unsorted by name. This can be very severe for a large organization that uses Jenkins. It causes duplicates and difficulty finding accounts especially accounts with similar names. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xshell-plugin] (JENKINS-33431) Single variable that includes multiple arguments does not work on Linux.
Title: Message Title
Mike Murray updated an issue
Jenkins / JENKINS-33431
Single variable that includes multiple arguments does not work on Linux.
Change By:
Mike Murray
This cmd works using shell command on Linux and XShell on Windows, but not XShell on Linux. $JYTHON/xyz.py --showConfigThis is the value of JYTHON: JYTHON=$ { JAVA } -jar $ { JYTHON_JAR } -Dpython.path=$ { PYTHON_LOC } $ { PYTHON_LOC } Using the individual variables works using XShell on Linux: $ { JAVA } -jar $ { JYTHON_JAR } -Dpython.path=$ { PYTHON_LOC } $ { PYTHON_LOC } /xyz.py --showConfigI think the reason for this is that linux treats each variable as a single argument. This is the reason Ant has vs support to distinguish handling of spaces within args on linux. (See: https://ant.apache.org/manual/using.html#arg)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-33433) jobs fail to "parse changelog" for pull requests with "catch-up" merges from destination branch
Title: Message Title
Max Kovgan created an issue
Jenkins / JENKINS-33433
jobs fail to "parse changelog" for pull requests with "catch-up" merges from destination branch
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-client-plugin, git-plugin
Created:
09/Mar/16 6:41 PM
Environment:
* {{jenkins}}: {{1.652}} * {{git-plugin}}: {{2.4.2}} * {{git-client-plugin}}: {{1.19.6}}
Priority:
Minor
Reporter:
Max Kovgan
the latest git + git-client combination that worked is:
plugin
version
git
2.4.1
[JIRA] [xshell-plugin] (JENKINS-33431) Single variable that includes multiple arguments does not work on Linux.
Title: Message Title
Mike Murray updated an issue
Jenkins / JENKINS-33431
Single variable that includes multiple arguments does not work on Linux.
Change By:
Mike Murray
This cmd works using shell command on Linux and XShell on Windows, but not XShell on Linux. $ { JYTHON } /xyz.py --showConfigThis is the value of JYTHON: JYTHON=${JAVA} -jar ${JYTHON_JAR} -Dpython.path=${PYTHON_LOC} ${PYTHON_LOC}Using the individual variables works using XShell on Linux: ${JAVA} -jar ${JYTHON_JAR} -Dpython.path=${PYTHON_LOC} ${PYTHON_LOC}/xyz.py --showConfigI think the reason for this is that linux treats each variable as a single argument. This is the reason Ant has vs support to distinguish handling of spaces within args on linux. (See: https://ant.apache.org/manual/using.html#arg)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [dropdown-viewstabbar-plugin] (JENKINS-33432) upgrading dropdown views tabbar to 1.7 results in hang while displaying listview
Title: Message Title Jay Berkenbilt created an issue Jenkins / JENKINS-33432 upgrading dropdown views tabbar to 1.7 results in hang while displaying listview Issue Type: Bug Assignee: Unassigned Attachments: plugins.tsv, stacktrace.txt Components: dropdown-viewstabbar-plugin Created: 09/Mar/16 6:22 PM Environment: Ubuntu 14.04 LTS with 1.642.2 debian package; Oracle Java 1.8u45. Installed plugin list attached. Priority: Minor Reporter: Jay Berkenbilt Our Jenkins installation has over 75K jobs and about 1600 views. Upon upgrading the dropdown views tabbar plugin from 1.6 to 1.7, any attempt to retrieve the contents of a view through the web UI would hang. The attached stack trace is from a thread dump of Jenkins while trying to get the contents of a view by just visiting the main page. Other operations within Jenkins, such as going directly to a job or build or to the configuration interface work fine. We observe this behavior with or without the option to show job counts. We also verified that we see the same
[JIRA] [xshell-plugin] (JENKINS-33431) Single variable that includes multiple arguments does not work on Linux.
Title: Message Title
Mike Murray created an issue
Jenkins / JENKINS-33431
Single variable that includes multiple arguments does not work on Linux.
Issue Type:
Bug
Assignee:
Unassigned
Components:
xshell-plugin
Created:
09/Mar/16 6:19 PM
Environment:
x-shell 0.10 Jenkins ver. 1.607 Linux 2.6.32-573.7.1.el6.x86_64
Labels:
plugin xshell variables arguments linux
Priority:
Minor
Reporter:
Mike Murray
This cmd works using shell command on Linux and XShell on Windows, but not XShell on Linux. $ {JYTHON}
/xyz.py --showConfig
This is the value of JYTHON: JYTHON=$ {JAVA} -jar ${JYTHON_JAR} -Dpython.path=${PYTHON_LOC} ${PYTHON_LOC} Using the individual variables works using XShell on Linux: ${JAVA}
-jar $ {JYTHON_JAR}
-Dpython.path=$ {PYTHON_LOC} ${PYTHON_LOC}
/xyz.py --showConfig
[JIRA] [core] (JENKINS-32190) UsageStatistics Page Decorator may get called during initialization.
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-32190 Re: UsageStatistics Page Decorator may get called during initialization. One surprising discovery is that Jenkins goes through multiple cycles of initializations. Basically, each time executeReactor happens. Once from the constructor (the canonical boot sequence that I can think of), then once more from resolveDependantPlugins() (I don't know what this does — I suspect it shouldn't run a new reactor but I need to check), then every time Jenkins gets reloaded. Still, the end state should be always COMPLETED, so it still doesn't quite explain. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-12040) Subversion plugin fails to check out files specified in svn:externals
Title: Message Title Tomalak Geret'kal updated an issue Jenkins / JENKINS-12040 Subversion plugin fails to check out files specified in svn:externals Change By: Tomalak Geret'kal Summary: Subversion plugin fails to check out files specified in snv svn :externals Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-12040) Subversion plugin fails to check out files specified in snv:externals
Title: Message Title Tomalak Geret'kal commented on JENKINS-12040 Re: Subversion plugin fails to check out files specified in snv:externals I discovered that (unlike with my desktop SVN client), the SVN plugin requires the external's destination directory to be a working copy. It won't be automatically created to host the external. I think that this behaviour is probably fine but it caught me by surprise as my repository was accidentally not set up this way, and I'd never noticed due to my SVN client working around it automatically. So check that the destination path exists. I can't quite tell for sure from your report. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [winstone-jetty] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title
Elijah Zupancic edited a comment on JENKINS-33412
Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors
[~danielbeck] You are completely correct. I did the bulk of my testing with winstone-2.9 and I lightly tested with winstone-3.1. I made a mistake with my network setup. I just validated that winstone-3.1 also works correctly and updated the bug to that effect.I would still recommend upgrading the next version of Jenkins to winstone-3.1 in order to fix this bug because this seems like one of those messy things that if you have a fix by upgrading a core library - it is just better doing it that way.That said, read below if we want to go down the root cause analysis route: I work at Joyent and if any developers want environment in which this can be reproduced, please email me your public key (elijah.zupan...@joyent.com) and I will create an instance.[~ydubreuil] The behavior is present across different operating systems including one's that do not use glibc as part of their JVM implementation (e.g. SmartOS). When I was inspecting the application with a debugger, the best that I could tell was that even though a request had come in, EPOLL would not wake and a processing thread would not be dispatched. We see that winstone recieves the request (when FINE logging is enabled):{code:none}FINE: created SCEP@3c108ef8{l(/97.113.3.1:54175)<->r(/165.225.168.215:8443),s=0,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=0}-{SslConnection@56a764e3 SSL NOT_HANDSHAKING i/o/u=-1/-1/-1 ishut=false oshut=false {AsyncHttpConnection@23fe1e75,g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-14,l=0,c=0},r=0}}{code}However, the process just continues to sleep after this.Here's the output from /proc/PID/status when it is in a hung state:{code:none}Name: javaState: S (sleeping)Tgid: 1673Ngid: 0Pid:1673PPid: 1672TracerPid: 0Uid:1000100010001000Gid:1000100010001000FDSize: 256Groups: 4 24 27 30 46 110 111 1000 NStgid: 1673NSpid: 1673NSpgid: 1672NSsid: 1551VmPeak: 8983212 kBVmSize: 8983208 kBVmLck: 0 kBVmPin: 0 kBVmHWM:199776 kBVmRSS:199276 kBVmData: 8922448 kBVmStk: 136 kBVmExe: 4 kBVmLib: 17216 kBVmPTE: 1080 kBVmPMD:48 kBVmSwap:0 kBThreads:98SigQ: 0/15699SigPnd: ShdPnd: NSsid: 1551VmPeak: 8983212 kBVmSize: 8983208 kBVmLck: 0 kBVmPin: 0 kBVmHWM:199776 kBVmRSS:199276 kBVmData: 8922448 kBVmStk: 136 kBVmExe: 4 kBVmLib: 17216 kBVmPTE: 1080 kBVmPMD:48 kBVmSwap:0 kBThreads:98SigQ: 0/15699SigPnd: ShdPnd: SigBlk: SigIgn: SigCgt: 200181005ccfCapInh: CapPrm: CapEff: CapBnd: 003fSeccomp:0Cpus_allowed: ,Cpus_allowed_list: 0-47Mems_allowed: ,0001Mems_allowed_list: 0voluntary_ctxt_switches:3nonvoluntary_ctxt_switches: 1{code :none }
Add Comment
[JIRA] [subversion-plugin] (JENKINS-32582) List Subversion Tags default tag fails for Poll SCM trigger
Title: Message Title Tomalak Geret'kal commented on JENKINS-32582 Re: List Subversion Tags default tag fails for Poll SCM trigger Can confirm: Jenkins 1.652, Subversion plugin 2.5.7, CentOS 7.2, JRE 1.8.0.71 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [winstone-jetty] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title
Elijah Zupancic commented on JENKINS-33412
Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors
Daniel Beck You are completely correct. I did the bulk of my testing with winstone-2.9 and I lightly tested with winstone-3.1. I made a mistake with my network setup. I just validated that winstone-3.1 also works correctly and updated the bug to that effect.
I would still recommend upgrading the next version of Jenkins to winstone-3.1 in order to fix this bug because this seems like one of those messy things that if you have a fix by upgrading a core library - it is just better doing it that way.
That said, read below if we want to go down the root cause analysis route:
I work at Joyent and if any developers want environment in which this can be reproduced, please email me your public key (elijah.zupan...@joyent.com) and I will create an instance.
Yoann Dubreuil The behavior is present across different operating systems including one's that do not use glibc as part of their JVM implementation (e.g. SmartOS). When I was inspecting the application with a debugger, the best that I could tell was that even though a request had come in, EPOLL would not wake and a processing thread would not be dispatched. We see that winstone recieves the request (when FINE logging is enabled):
FINE: created SCEP@3c108ef8{l(/97.113.3.1:54175)<->r(/165.225.168.215:8443),s=0,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=0}-{SslConnection@56a764e3 SSL NOT_HANDSHAKING i/o/u=-1/-1/-1 ishut=false oshut=false {AsyncHttpConnection@23fe1e75,g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-14,l=0,c=0},r=0}}
However, the process just continues to sleep after this.
Here's the output from /proc/PID/status when it is in a hung state:
Name: java State: S (sleeping) Tgid: 1673 Ngid: 0 Pid: 1673 PPid: 1672 TracerPid: 0 Uid: 1000 1000 1000 1000 Gid: 1000 1000 1000 1000 FDSize: 256 Groups: 4 24 27 30 46 110 111 1000 NStgid: 1673 NSpid: 1673 NSpgid: 1672 NSsid: 1551 VmPeak: 8983212 kB VmSize: 8983208 kB VmLck: 0 kB VmPin: 0 kB VmHWM: 199776 kB VmRSS: 199276 kB VmData: 8922448 kB VmStk: 136 kB VmExe: 4 kB VmLib: 17216 kB VmPTE: 1080 kB VmPMD: 48 kB VmSwap: 0 kB Threads: 98 SigQ: 0/15699 SigPnd: ShdPnd: NSsid: 1551 VmPeak: 8983212 kB VmSize: 8983208 kB VmLck: 0 kB VmPin: 0 kB VmHWM: 199776 kB VmRSS: 199276 kB VmData: 8922448 kB VmStk: 136 kB VmExe: 4 kB VmLib: 17216 kB VmPTE: 1080 kB VmPMD: 48 kB VmSwap: 0 kB Threads: 98 SigQ: 0/15699 SigPnd: ShdPnd: SigBlk: SigIgn: SigCgt: 200181005ccf CapInh: CapPrm: CapEff: CapBnd: 003f Seccomp: 0 Cpus_allowed: , Cpus_allowed_list: 0-47 Mems_allowed: ,0001 Mems_allowed_list: 0 voluntary_ctxt_switches: 3 nonvoluntary_ctxt_switches: 1
[JIRA] [winstone-jetty] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title
Elijah Zupancic updated an issue
Jenkins / JENKINS-33412
Jenkins locks when started in HTTPS mode on a host with 37+ processors
Change By:
Elijah Zupancic
*Summary*Using Winstone 3 2 . 1 9 (i.e. the embedded Jetty wrapper) or below it will not run in HTTPS mode on hosts with 37 cores/processors or more. This problem replicates regardless of the JDK or the operating system.*Reproduction*The easiest way to reproduce the error is to use qemu to virtualize a 37 core system. You can do that with the -smp parameter. For example, for testing I run:{code:none}qemu-system-x86_64 -hda ubuntu.img -m 4096 -smp 48{code}Once you have a VM with more than 37 cores setup, install Jenkins 1.652 and configure it to use HTTPS. Attempt to start it and connect to either the HTTP or the HTTPS port. The connection will time out for either port with the server effectively locked until you send it a SIGTERM. Please refer to the attached log file to see its start process.*Why is this important?*You may ask - who is running Jenkins on that big of a server? Well, with containerization technologies (e.g. Docker) taking a center stage, we are seeing more and more deployments where there is no VM involved and hence a container gets a slice of CPU but has visibility to all of the processors on a system. The official Docker image of Jenkins suffers from this defect. Sure a user can set up their own reverse proxy to run TLS through, but it adds unneeded complexity for users looking to containerize their Jenkins environment.*Solution*I've done the work of reducing the surface area of root cause analysis. I removed the entire jenkins war from the jenkins winstone runner (https://github.com/jenkinsci/winstone) and ran a simple hello world war instead. With HTTPS enabled, the issue still reproduced. It took a lot of fiddling to determine that it was exactly at 37 cores in which the hang occurred.Lastly, I tried the exact same reproduction steps with winstone-3. 2-SNAPSHOT 1 . Luckily, with the upgrade to embedded Jetty in the 3. 2 1 version the issue is resolved._Can we upgrade the next Jenkins release to use the winstone-3. 2 1 component?_This would be the easiest and the best fix. I would be happy to contribute to any efforts that would allow for us to get this into a release.
Add Comment
[JIRA] [core] (JENKINS-32190) UsageStatistics Page Decorator may get called during initialization.
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-32190 Re: UsageStatistics Page Decorator may get called during initialization. This appears to be causing a regression. We noticed that the usage stats dropped a big time in Feb, and upon closer looking of log files, it appears that the # of usage reports started to decline around the time when this was introduced, and further more when this was backported into LTS. Still investigating how this might have caused a regression Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [winstone-jetty] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Elijah Zupancic updated an issue Jenkins / JENKINS-33412 Jenkins locks when started in HTTPS mode on a host with 37+ processors Change By: Elijah Zupancic Environment: Jenkins 1.652org.jenkins-ci:winstone 2.9 , 3.0, 3.1 Testing in the Linux JDK 1.7 and 1.8 as well as the Solaris JDK 1.7 1.8 (both OpenJDK and OracleJDK). Reproduces in Ubuntu, Debian, CentOS and SmartOS. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [poll-mailbox-trigger-plugin] (JENKINS-27575) Please add possibility to handle the attachment of mail to this plugin
Title: Message Title Justin Nguyen commented on JENKINS-27575 Re: Please add possibility to handle the attachment of mail to this plugin After reading and rereading your question about adding pmt_attachment, I have a better sense of what the pmt_* variables are now. And I understand now what you meant by "the plugin will just inject the `pmt_attachmentsDirectory` variable straight into the job for you". Sorry, I'm a little new to configuring jobs in Jenkins. When I added my own pmt_attachmentDirectory property into the Advanced Email Properties box, it overwrote the exact information that I was trying to get at – the timestamp-named directory in which the attachments were downloaded into. I thought the pmt_* variables were user defined input variables into your plugin code. They are actually output variables from your plugin code and are made available as input to user-defined scripts, i.e. perl testme.pl %pmt_attachmentDirectory%. In any case, the changes that you are currently making are worthwhile and will make the plugin more robust. On the question of whether or not to add the pmt_attachment or not, I wouldn't bother. I would leave that up to the user to extract that information using a script. It's an easy enough algorithm to loop through the contents of a directory using a half decent scripting language. Looping through an undefined length of pmt_attachment_n variables requires a bit more involved algorithm. Thanks a million for being generous enough to share your work! Fantastic plugin! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
Title: Message Title dogfood commented on JENKINS-26580 Re: For JNLP slaves the master-slave communication should be encrypted Integrated in jenkins_main_trunk #4494 JENKINS-26580 Initial implementation of JNLP3-connect protocol (Revision 9bb35a78b8298930adf978046e9f6c53c6853e27) JENKINS-26580 Updated implementation of Jnlp3 protocol (Revision e9f5caa13fa1a3d1bf602ec9d67dac75f3310889) Result = UNSTABLE akshay_abd : 9bb35a78b8298930adf978046e9f6c53c6853e27 Files : core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol3.java pom.xml core/src/main/java/jenkins/slaves/JnlpSlaveHandshake.java akshay_abd : e9f5caa13fa1a3d1bf602ec9d67dac75f3310889 Files : core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol3.java Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33430) Stage view UI loses history when stages are changed
Title: Message Title Antonio Muñiz assigned an issue to Unassigned Jenkins / JENKINS-33430 Stage view UI loses history when stages are changed Change By: Antonio Muñiz Assignee: Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23244) Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master
Title: Message Title Matthew Mitchell commented on JENKINS-23244 Re: Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master (FYI this installation is around 6-7k builds a day) Even in the case of walking newer builds, it seems like this woudl be super expensive. Maybe it's better to keep an index of buildname/number to machine to avoid loading the metadata at all? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33430) Stage view UI visualization
Title: Message Title Marco Lijoi created an issue Jenkins / JENKINS-33430 Stage view UI visualization Issue Type: Improvement Assignee: Antonio Muñiz Components: pipeline-stage-view-plugin Created: 09/Mar/16 4:32 PM Priority: Minor Reporter: Marco Lijoi I'm using the Pipeline Plugin and Stage View plugin with a pipeline script loaded from SCM. Stages can change between builds, but when this happen, the Stage View is re-initialized and I lose the view history of builds. Is it possible to mantain old builds and their UI visualization ? Add Comment
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33430) Stage view UI loses history when stages are changed
Title: Message Title Marco Lijoi updated an issue Jenkins / JENKINS-33430 Stage view UI loses history when stages are changed Change By: Marco Lijoi Summary: Stage view UI visualization loses history when stages are changed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Omar Ahmad updated an issue Jenkins / JENKINS-28289 JNLP slave should exclude non proxy hosts when connecting via HTTP proxy Change By: Omar Ahmad Comment: Hi, I have chosen this week to upgrade Jenkins core to the LTS release from last month (1.642.2) and I am facing this issue when attempting to connect slaves to the master. Is there an easy way I can upgrade the remoting component from 2.53.3 to 2.56 which contains fixes, (I tried replacing the JAR in the /war/WEB-INF/lib directory but without success as the master still serves version 2.53.3), so that I can get the upgrade working? Or should I wait for the next LTS release? Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [poll-mailbox-trigger-plugin] (JENKINS-27575) Please add possibility to handle the attachment of mail to this plugin
Title: Message Title Justin Nguyen commented on JENKINS-27575 Re: Please add possibility to handle the attachment of mail to this plugin Yeah, that screen shot looks awesome. You rock! Looking forward to the changes. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy-plugin] (JENKINS-33392) Following the 'Role Strategy Plugin' instructions gets me locked out of Jenkins
Title: Message Title Will Sheppard commented on JENKINS-33392 Re: Following the 'Role Strategy Plugin' instructions gets me locked out of Jenkins Thanks, I have managed to reset security so I have access again. I am not able to reproduce what I did before - I'm not getting locked out anymore, so I guess it was something stupid I did and not the instructions fault! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33414) Provide an API to allow detecting if running on the Jenkins JVM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33414 Re: Provide an API to allow detecting if running on the Jenkins JVM Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/ProxyConfiguration.java http://jenkins-ci.org/commit/jenkins/21f1c29c896af998b4df07c5e43cdda5a3562621 Log: JENKINS-33414 Cover one final theoretical race condition Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33414) Provide an API to allow detecting if running on the Jenkins JVM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33414 Re: Provide an API to allow detecting if running on the Jenkins JVM Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/ProxyConfiguration.java core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/c5759f957b8546e79d8c185ecd459a220baff857 Log: Merge pull request #2104 from stephenc/jenkins-33414-followup JENKINS-33414 Ensure that the tests do not leave the JVM marker flag set Compare: https://github.com/jenkinsci/jenkins/compare/6d3e05439643...c5759f957b85 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33414) Provide an API to allow detecting if running on the Jenkins JVM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33414 Re: Provide an API to allow detecting if running on the Jenkins JVM Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/ef2451b8c88780813d88f5ad1830f030af898379 Log: JENKINS-33414 Ensure that the tests do not leave the JVM marker flag set Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [_unsorted] (JENKINS-33429) Can't change my password
Title: Message Title Justin Nguyen created an issue Jenkins / JENKINS-33429 Can't change my password Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 09/Mar/16 4:13 PM Environment: Firefox Priority: Minor Reporter: Justin Nguyen I just created a login for jenkins-ci.org yesterday and can't seem to find a way to change my temp password. I googled how one would go about it and found that I should go to my Profile and select Change Password on the left hand nav panel. However, the only option I have on the left hand side is "Test Session" link. Add Comment
