[JIRA] (JENKINS-38752) The job link in the detail view for multibranch should link to a filtered activity list of appropriate branch
Title: Message Title
Daniel Beck commented on JENKINS-38752
Re: The job link in the detail view for multibranch should link to a filtered activity list of appropriate branch
FWIW this is the link I'd expect to show me the build history for a specific branch ("it may build now, but how was it yesterday?"). I asked about that on IRC a while back but got no response.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38609) Shared libraries root to be specified in the PATH field
Title: Message Title
Martin Fousek edited a comment on JENKINS-38609
Re: Shared libraries root to be specified in the PATH field
Sure, that's right and we are actually using the the{{ load }} step in ongoing scripting but we incline to keep the inline script (in the definition of the job's Pipeline) as simple as possible. Usually it's only one line like this:runJob(label: 'llg && slave', branch: constants.promotedBranch){{runJob}} is global method which wraps the run into try/catch/finally blocks, handles emails, ..., gets the script name equal to job name and starts processing. Of course we could enhance it here but we wanted to keep the unversioned part of the job definition as short as possible. Except this one helper method, we are using also {{constants}} there so that are already two loads here and we can't forget that this all requires SCM checkout so the structure wouldn't be really simple one line any more.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38609) Shared libraries root to be specified in the PATH field
Title: Message Title
Martin Fousek edited a comment on JENKINS-38609
Re: Shared libraries root to be specified in the PATH field
Sure, that's right and we are actually using the the load step in ongoing scripting but we incline to keep the inline script (in the definition of the job's Pipeline) as simple as possible. Usually it's only one line like this:runJob(label: 'llg && slave', branch: constants.promotedBranch) {{ runJob }} is global method which wraps the run into try/catch/finally blocks, handles emails, ..., gets the script name equal to job name and starts processing. Of course we could enhance it here but we wanted to keep the unversioned part of the job definition as short as possible. Except this one helper method, we are using also{{ constants }} there so that are already two loads here and we can't forget that this all requires SCM checkout so the structure wouldn't be really simple one line any more.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38609) Shared libraries root to be specified in the PATH field
Title: Message Title Martin Fousek commented on JENKINS-38609 Re: Shared libraries root to be specified in the PATH field Sure, that's right and we are actually using the the load step in ongoing scripting but we incline to keep the inline script (in the definition of the job's Pipeline) as simple as possible. Usually it's only one line like this: runJob(label: 'llg && slave', branch: constants.promotedBranch) runJob is global method which wraps the run into try/catch/finally blocks, handles emails, ..., gets the script name equal to job name and starts processing. Of course we could enhance it here but we wanted to keep the unversioned part of the job definition as short as possible. Except this one helper method, we are using also constants there so that are already two loads here and we can't forget that this all requires SCM checkout so the structure wouldn't be really simple one line any more. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38800) remoteUrls are unordered in build data JSON when multiple git repositories are configured
Title: Message Title Mark Waite commented on JENKINS-38800 Re: remoteUrls are unordered in build data JSON when multiple git repositories are configured Can you further explain the use case for multiple git repositories defined in a single Jenkins job? I realize that the git plugin supports it, but I don't understand how it helps you accomplish something whose result can be understood by a user. As far as I can tell, the git plugin code will intertwine changes from each of the repositories as it finds them, checking out the SHA1 from the repositories, building it, displaying changes, etc. I've assumed that the mental model might have been that there is a repository which might be "distant" or "less frequently updated" (some form of central repository) and there are one or more additional repositories which are generally either exact copies or pure supersets of the "distant" repository, but are more accessible to the user or to the Jenkins server. One example of that working model might be the Jenkins official git client plugin (https://github.com/jenkinsci/git-client-plugin) and my fork of that repository (https://github.com/MarkEWaite/git-client-plugin). I keep my fork as a superset of the official repository, so I generally can see anything on my fork that is on the official repository. Thus, I've never actually needed to have a job which references both repositories. I either want the official repository, or I want my repository with my working copies. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-38800) remoteUrls are unordered in build data JSON when multiple git repositories are configured
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-38800 remoteUrls are unordered in build data JSON when multiple git repositories are configured Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38827) Add Git Client support to track where a credential is used
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-38827 Add Git Client support to track where a credential is used Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38766) withRegistry() duplicates registry name
Title: Message Title Richard Lee commented on JENKINS-38766 Re: withRegistry() duplicates registry name See https://github.com/jenkinsci/docker-workflow-plugin/pull/74 for a fix. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38838) Auto cleanup and sync removes files in ignored folder
Title: Message Title
Matthew Douglass updated an issue
Jenkins / JENKINS-38838
Auto cleanup and sync removes files in ignored folder
Change By:
Matthew Douglass
When performing an auto cleanup and sync build, p4-plugin deletes files that are in an ignored folder. This is different behavior from running p4 reconcile at the command line which will not delete files in an ignored folder.At //depot/client/.p4ignore:/Library/Build is set to Auto cleanup and sync, REPLACE, DELETE, Sync with MODTIMELogs show:P4 Task: cleaning workspace to match have list.(p4):cmd:... p4 reconcile -w -f -m /Users/Shared/Jenkins/workspace/km-client-iOS/...p4 reconcile -w -f -m /Users/Shared/Jenkins/workspace/km-client-iOS/...After this step if I dump the contents of the $ \ {workspace}/client/Library folder, it is empty. However, if I run this same reconcile command line on my local machine, the Library folder is left as-is.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message
[JIRA] (JENKINS-38838) Auto cleanup and sync removes files in ignored folder
Title: Message Title
Matthew Douglass created an issue
Jenkins / JENKINS-38838
Auto cleanup and sync removes files in ignored folder
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2016/Oct/07 10:51 PM
Priority:
Major
Reporter:
Matthew Douglass
When performing an auto cleanup and sync build, p4-plugin deletes files that are in an ignored folder. This is different behavior from running p4 reconcile at the command line which will not delete files in an ignored folder. At //depot/client/.p4ignore: /Library/ Build is set to Auto cleanup and sync, REPLACE, DELETE, Sync with MODTIME Logs show: P4 Task: cleaning workspace to match have list. (p4):cmd:... p4 reconcile -w -f -m /Users/Shared/Jenkins/workspace/km-client-iOS/... p4 reconcile -w -f -m /Users/Shared/Jenkins/workspace/km-client-iOS/... After this step if I dump the contents of the $ {workspace} /client/Library folder, it is empty. However, if I run this same reconcile command line on my local machine, the Library folder is left as-is.
Add Comment
[JIRA] (JENKINS-38517) “Local module directory” not supported for external libraries
Title: Message Title Brian Ray commented on JENKINS-38517 Re: “Local module directory” not supported for external libraries If it's an easy change, I think just hiding the field entirely would be best in this context. There's no reason to use the field for external libraries--except maybe one. If the field were suppressed from the UI, nobody'd make the mistake of trying to use it, and no doc would be needed. The only reason it might be useful is if the external loader library were optimizing checkouts between builds when multiple libraries were involved. The Check-out Strategy of using svn update as much as possible is short circuited when the local directory is recycled for the checkout of another library. If each library were checked out in its own directory, svn update would work. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38835) 'make -C demo run' hard to do on OSX
Title: Message Title Richard Lee commented on JENKINS-38835 Re: 'make -C demo run' hard to do on OSX See https://github.com/jenkinsci/docker-workflow-plugin/pull/73 for some potential fixes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16243) Active Directory SSL/TLS authentication does not work with Active Directory Plugin
Title: Message Title ray terrill commented on JENKINS-16243 Re: Active Directory SSL/TLS authentication does not work with Active Directory Plugin Is this still a problem? Running into the exact same issue - socket closed on both 636 and 3269, validated that I can connect outside of Jenkins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38837) Mutibranch project plugin does not respect "Workspace Root Directory" global configuration
Title: Message Title
Brenden Conte created an issue
Jenkins / JENKINS-38837
Mutibranch project plugin does not respect "Workspace Root Directory" global configuration
Issue Type:
Bug
Assignee:
Matthew DeTullio
Components:
multi-branch-project-plugin
Created:
2016/Oct/07 10:12 PM
Environment:
Windows server 2012 64 bit
Priority:
Critical
Reporter:
Brenden Conte
The multibranch project plugin always creates the workspaces to build the branches in "$ {JENKINS_HOME} /jobs/your-multi-branch-project/branches/$ {branchNameEncoded}/workspace", however our configuration has the workspaces on a different drive with much more space, so WORKSPACE is not on the same drive as JENKINS_HOME. This is configured in the global config->Workspace Root Directory (under advanced below Home Directory). Please use "${Workspace Root Directory}/${branchNameEncoded} /workspace" or something similar instead.
Add Comment
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Aaron Wilson commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java I'd love to get an update on this, too. We're seeing it more and more often - I don't know if it's because the size of our stream is getting larger, or if there's something else that is degrading it. It's a big problem if I have to manually log into the jenkins machine and get the latest revision myself every time, which is the only workaround I've managed to find so far. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37566) FindBugs-clean remoting layer
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37566 Re: FindBugs-clean remoting layer Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/remoting/RemoteClassLoader.java http://jenkins-ci.org/commit/remoting/a185cb2aca2c4f47505347420cf979193aca4cee Log: JENKINS-37566 - DP_CREATE_CLASSLOADER_INSIDE_DO_PRIVILEGED i RemoteClassLoader Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37566) FindBugs-clean remoting layer
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37566 Re: FindBugs-clean remoting layer Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/remoting/Launcher.java src/main/java/hudson/remoting/RemoteClassLoader.java src/main/java/hudson/remoting/RemoteInvocationHandler.java src/main/java/hudson/remoting/Which.java src/main/java/org/jenkinsci/remoting/nio/SelectableFileChannelFactory.java src/main/java/org/jenkinsci/remoting/util/ReflectionUtils.java src/test/java/org/jenkinsci/remoting/engine/HandlerLoopbackLoadStress.java src/test/java/org/jenkinsci/remoting/nio/Main.java src/test/java/org/jenkinsci/remoting/protocol/impl/ConnectionHeadersTest.java http://jenkins-ci.org/commit/remoting/755473f7e4fa314b17ac8df12cd362635a24e6c3 Log: JENKINS-37566 - Always run setAccessible() in privileged blocks Resolves 5 FB issues Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37566) FindBugs-clean remoting layer
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37566 Re: FindBugs-clean remoting layer Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/remoting/Launcher.java src/main/java/org/jenkinsci/remoting/util/ReflectionUtils.java http://jenkins-ci.org/commit/remoting/408bc165d43dbf60c97c2e7a61ed747e502451f2 Log: JENKINS-37566 - Fix imports and code formatting Compare: https://github.com/jenkinsci/remoting/compare/755473f7e4fa^...408bc165d43d Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38835) 'make -C demo run' hard to do on OSX
Title: Message Title Richard Lee commented on JENKINS-38835 Re: 'make -C demo run' hard to do on OSX Note: it's possible to get it to work, but several things need to be changed in the Makefile and Dockerfile that may or may not be desirable for linux users. e.g. actually installing docker-machine into the image rather than copying an incompatible executable (you can still volume mount in the OSX socket, tho, so no need to run the machine in the container). Change to use homebrew 'gstat' instead of 'stat'. Manually download jenkins plugins from http://repo.jenkins-ci.org/releases. Etc. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38836) Sandbox does not allow many utility methods
Title: Message Title Maciej Piechotka created an issue Jenkins / JENKINS-38836 Sandbox does not allow many utility methods Issue Type: Improvement Assignee: Unassigned Components: script-security-plugin Created: 2016/Oct/07 9:49 PM Priority: Minor Reporter: Maciej Piechotka Many utility methods are forbidden by sandbox like, for example, flatten or contain. PS. I'm not sure what is correct component. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title Cody D updated an issue Jenkins / JENKINS-36776 Support Windows Server Containers Change By: Cody D Attachment: docker_pipeline_example.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title Cody D updated an issue Jenkins / JENKINS-36776 Support Windows Server Containers Change By: Cody D Attachment: windows-container-pipeline.groovy Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title
Cody D updated an issue
Jenkins / JENKINS-36776
Support Windows Server Containers
Change By:
Cody D
I have Jenkins 2 The Docker . 7.1 running on Centos 7.2, groovy and I'm trying to use the docker pipeline WithContainerStep.java files have linux-specific commands that will fail to run instances of containers on Windows Server 2016 TP5 - https://msdn.microsoft.com/en-us/virtualization/windowscontainers/ with docker /configure_docker_daemon installed. I Docker.groovy invokes CPS ' ve attached a sample pipeline of what I sh ' m trying step in several cases, and tries to do start the container with the 'cat' command .The docker commands seem WithContainerStep whoAmI is using the 'id' utility to hang with: determine the user owning the workspace. {quote}Still waiting to schedule taskWaiting for next available executor{quote}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-32000) durable-task 1.7 breaks workflow bat steps
Title: Message Title Patrick Wolf commented on JENKINS-32000 Re: durable-task 1.7 breaks workflow bat steps Can you reproduce this on the latest version of the durable task plugin? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33456) durable-task 1.8 breaks workflow bat steps
Title: Message Title Patrick Wolf commented on JENKINS-33456 Re: durable-task 1.8 breaks workflow bat steps Can you upgrade to the latest version of this plugin and reproduce? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33904) Jenkinsfile batch steps randomly hang when complete
Title: Message Title Patrick Wolf commented on JENKINS-33904 Re: Jenkinsfile batch steps randomly hang when complete Can you upgrade and verify if this problem still exists Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title Cody D updated an issue Jenkins / JENKINS-36776 Support Windows Server Containers Change By: Cody D Environment: Jenkins 2.7. 1 4 CloudBees Docker Pipeline docker-workflow-plugin 1. 6 9 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title
Cody D commented on JENKINS-36776
Re: Support Windows Server Containers
OK, so I download the docker-workflow-plugin source and started hacking around and I've found a few things that get most of the plugin functionality to work on windows server 2016/windows server containers. 1. src\main\resources\org\jenkinsci\plugins\docker\workflow\Docker.groovy This groovy script has several lines that are calling the CPS 'sh' step. There should be a way to determine the platform and pass the docker command to 'sh' on linux, or 'bat' on windows. For testing purposes I swapped all sh with bat. 2. src\main\java\org\jenkinsci\plugins\docker\workflow\client\DockerClient.java The whoAmI method calls the 'id' utility on linux to determine the GID/UID of the current user. The docker client appends '-u [user]' when starting the container. I don't know if windows has the same behavior of using a SID in the container that matches a user on the windows host, so I commented out this code, returned null, as well as remove -u option from run for testing purposes. 3. src\main\java\org\jenkinsci\plugins\docker\workflow\WithContainerStep.java There's a hardcoded 'cat' command that the container starts with. I changed this to 'cmd' for windows. With these three changes, I was able to successfully pull microsoft/windowsservercore, run the container, then have it stopped and removed. I'm sure build, tag, push would have worked as well, but I didn't get around to testing those features. Unfortunately, if I try to run 'bat' in docker.image().inside{}, the process hangs indefinitely. The WithContainerStep Decorator decorate() is getting called, and the return statement is executed 'return super.launch(starter);', but then trying to debug the durable task, groovy cps, and others was difficult for me.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37479) Unclassified staticMethod java.nio.file.Paths get java.lang.String
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-37479 Unclassified staticMethod java.nio.file.Paths get java.lang.String Change By: Jesse Glick Component/s: script-security-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37479) Unclassified staticMethod java.nio.file.Paths get java.lang.String
Title: Message Title Jesse Glick commented on JENKINS-37479 Re: Unclassified staticMethod java.nio.file.Paths get java.lang.String “Unclassified method” errors generally indicate a bug in the script-security plugin; there is nothing to approve because it means Jenkins was unable to determine what the script was attempting to call. For diagnosis please supply a complete, minimal script reproducing the error. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34163) Retry block in Jenkins workflow script is executed in a different context
Title: Message Title Jesse Glick resolved as Incomplete Please read the standard guide and provide a complete, self-contained, minimal set of steps to reproduce the problem from scratch, including all files, scripts, etc. etc. which would be needed for someone to see your problem occur locally without trying to guess at your intent, plus complete output of your own run for reference. Jenkins / JENKINS-34163 Retry block in Jenkins workflow script is executed in a different context Change By: Jesse Glick Status: Reopened Resolved Assignee: Jesse Glick Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38835) 'make -C demo run' hard to do on OSX
Title: Message Title Richard Lee created an issue Jenkins / JENKINS-38835 'make -C demo run' hard to do on OSX Issue Type: New Feature Assignee: Unassigned Components: docker-workflow-plugin Created: 2016/Oct/07 8:54 PM Priority: Minor Reporter: Richard Lee Getting the demo build working on OSX is tricky, as the Makefile contains many linux-isms, such as the use of 'locate', 'stat -c', trying to volume mount the OSX docker executable into the container, weird problems with copy-plugins not contacting the right maven repository, etc. Add Comment
[JIRA] (JENKINS-31154) 2.0: provide better workflow visualization out of the box
Title: Message Title Jesse Glick commented on JENKINS-31154 Re: 2.0: provide better workflow visualization out of the box The workflow graph is still overly verbose Changes in this area planned anyway. the Retry feature is exclusive to Cloudbees' Jenkins Enterprise The feature name you are probably referring to is checkpoints. Core (OSS) Pipeline supports a Retry feature, which is quite different. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Emory Penney created an issue Jenkins / JENKINS-38834 Freestyle jobs hang in 2.19.1 on Windows 10 Nodes Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Oct/07 8:52 PM Environment: Jenkins 2.19.1 on Ubuntu 14.04 x64 Windows 10 (1607) Connected via JNLP Priority: Critical Reporter: Emory Penney Freestyle jobs hang either at the beginning or the end of execution. I've let a few run for ~18 hours before they eventually crash with errors like these: 07:52:37 java.io.IOException: Unable to get hostname from slave. null 07:52:37 at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:1187) 07:52:37 at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) 07:52:37 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) 07:52:37 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 07:52:37 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) 07:52:37 at hudson.model.Run.execute(Run.java:1720) 07:52:37 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 07:52:37 at hudson.model.ResourceController.execute(ResourceController.java:98) 07:52:37 at hudson.model.Executor.run(Executor.java:404) Reverting back to Jenkins 2.7.4 immediately resolved the issue. Issue was not observed with any Linux/OSX/older Windows
[JIRA] (JENKINS-34581) Please add support for Pipelines to the Powershell plugin
Title: Message Title Jesse Glick commented on JENKINS-34581 Re: Please add support for Pipelines to the Powershell plugin I would vote for the second choice. Probably more robust. Might be easier to implement something like JENKINS-25053 in that mode too. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34489) Pipeline 'bat' does not terminate immediately
Title: Message Title Jesse Glick commented on JENKINS-34489 Re: Pipeline 'bat' does not terminate immediately Possibly WindowsBatchScript needs to override launchWithCookie rather than doLaunch. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38609) Shared libraries root to be specified in the PATH field
Title: Message Title Jesse Glick commented on JENKINS-38609 Re: Shared libraries root to be specified in the PATH field If you are not sharing the library code then you might as well use the load step (or readTrusted if it must happen prior to checkout). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37567) Be able to release remoting without Kohsuke
Title: Message Title Oleg Nenashev commented on JENKINS-37567 Re: Be able to release remoting without Kohsuke The certificate got delayed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28386) Workflow support for Copy to Slave plugin
Title: Message Title Jesse Glick commented on JENKINS-28386 Re: Workflow support for Copy to Slave plugin I will not offer advice on anything that involves nonzero master executors, which is inherently dangerous and unsupportable. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38702) AccuRev for Jenkins Plugin does not display Depots
Title: Message Title Joseph Petersen edited a comment on JENKINS-38702 Re: AccuRev for Jenkins Plugin does not display Depots Can you verify that ACCUREV_HOME is set system wide after a reboot? Since by rebooting you ensure that once Jenkins boot it will have loaded that System Wide Variable.I would suggest using System Properties, Environment Variable GUI over calling set in a command prompt, only sets in command prompt :)Using SETX can be a bit tedious: http://ss64.com/nt/setx.html Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38702) AccuRev for Jenkins Plugin does not display Depots
Title: Message Title Joseph Petersen commented on JENKINS-38702 Re: AccuRev for Jenkins Plugin does not display Depots Can you verify that ACCUREV_HOME is set system wide after a reboot? Since by rebooting you ensure that once Jenkins boot it will have loaded that System Wide Variable. I would suggest using System Properties, Environment Variable over calling set in a command prompt, only sets in command prompt Using SETX can be a bit tedious: http://ss64.com/nt/setx.html Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37566) FindBugs-clean remoting layer
Title: Message Title Oleg Nenashev commented on JENKINS-37566 Re: FindBugs-clean remoting layer Postponed the release for now. Still need to fix 16 bugs and integrate others Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31507) docker.build throw IOExceptions with some sources
Title: Message Title Jesse Glick commented on JENKINS-31507 Re: docker.build throw IOExceptions with some sources The extra whitespace looks suspicious, perhaps you have FROMsomething? As usual, a self-contained, minimal, reproducible test case would expedite a fix (as well as possibly make a workaround obvious). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38833) Remoting 3 release follow-ups
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-38833 Remoting 3 release follow-ups Issue Type: Epic Assignee: Unassigned Components: remoting Created: 2016/Oct/07 8:36 PM Priority: Minor Reporter: Oleg Nenashev Just do the stuff, which has not been completely delivered in remoting 3 due to other assignments Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38832) Add SSH Slaves support for tracking credentials usage
Title: Message Title D P created an issue Jenkins / JENKINS-38832 Add SSH Slaves support for tracking credentials usage Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: ssh-slaves-plugin Created: 2016/Oct/07 8:35 PM Priority: Minor Reporter: D P The credentials plug-in added support for tracking credentials usage, see JENKINS-20139. However the consumer plug-in needs an update to enable this. Please add support. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title Oleg Nenashev resolved as Fixed Marking it as Resolved. We're preparing to the Remoting 3.0 release right now Jenkins / JENKINS-36871 JNLPProtocol4 Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-37564) Remoting 3 - major
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-37564 Remoting 3 - major Change By: Oleg Nenashev Summary: Remoting 3 .0 - major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31425) should be able to specify multiple users or groups for the submitter of an input step
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31425 should be able to specify multiple users or groups for the submitter of an input step Change By: Jesse Glick Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31425) should be able to specify multiple users or groups for the submitter of an input step
Title: Message Title Jesse Glick started work on JENKINS-31425 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31425) should be able to specify multiple users or groups for the submitter of an input step
Title: Message Title Jesse Glick assigned an issue to Emilio Escobar Jenkins / JENKINS-31425 should be able to specify multiple users or groups for the submitter of an input step Change By: Jesse Glick Assignee: Jesse Glick Emilio Escobar Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31425) should be able to specify multiple users or groups for the submitter of an input step
Title: Message Title Jesse Glick updated JENKINS-31425 Jenkins / JENKINS-31425 should be able to specify multiple users or groups for the submitter of an input step Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31425) should be able to specify multiple users or groups for the submitter of an input step
Title: Message Title Jesse Glick updated JENKINS-31425 Jenkins / JENKINS-31425 should be able to specify multiple users or groups for the submitter of an input step Change By: Jesse Glick Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38831) Add Credentials Binding support for tracking credentials usage
Title: Message Title D P created an issue Jenkins / JENKINS-38831 Add Credentials Binding support for tracking credentials usage Issue Type: Improvement Assignee: Unassigned Components: credentials-binding-plugin Created: 2016/Oct/07 8:26 PM Priority: Minor Reporter: D P The credentials plug-in added support for tracking credentials usage, see JENKINS-20139. However the consumer plug-in needs an update to enable this. Please add support. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-38517) “Local module directory” not supported for external libraries
Title: Message Title Jesse Glick commented on JENKINS-38517 Re: “Local module directory” not supported for external libraries Not sure I see how the difference would be visible to a user. Is there something that could be clarified in documentation? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38830) Add SSH Agent support for tracking credential usage
Title: Message Title D P created an issue Jenkins / JENKINS-38830 Add SSH Agent support for tracking credential usage Issue Type: Improvement Assignee: Unassigned Components: ssh-agent-plugin Created: 2016/Oct/07 8:21 PM Priority: Minor Reporter: D P The credentials plug-in added support for tracking credentials usage, see JENKINS-20139. However the consumer plug-in needs an update to enable this. Please add support. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-38829) "Kubernetes server certificate key" not working
Title: Message Title akostadinov created an issue Jenkins / JENKINS-38829 "Kubernetes server certificate key" not working Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Oct/07 8:18 PM Priority: Critical Reporter: akostadinov In JENKINS-29213 a parameter has been added "Kubernetes server certificate key". It has no help but looking at the relevant commit I see it should read PEM formatted server certificate. This doesn't appear to work for me. Jenkins server doesn't use a self-signed certificate, it uses a corporate internal CA thus I put into the field the server certificate and it's CAs. This doesn't work. I tried changing order of certificates to no avail. I think help needs to be added about format and order of certificates so that they can work. Full backtrace: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1884) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:276) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:270) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1341) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:153) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:868) at sun.security.ssl.Handshaker.process_record(Handshaker.java:804) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1016) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1312) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1339)
[JIRA] (JENKINS-20797) UserIdCause should be used, not UserCause
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-20797 UserIdCause should be used, not UserCause Change By: Oleg Nenashev Assignee: Peter Hayes Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20797) UserIdCause should be used, not UserCause
Title: Message Title Oleg Nenashev commented on JENKINS-20797 Re: UserIdCause should be used, not UserCause Agreed. I've integrated only the fix from the pending PR and have not searched for other usages. My bad, to be fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38828) Add pull request builder support for tracking credential usage
Title: Message Title D P created an issue Jenkins / JENKINS-38828 Add pull request builder support for tracking credential usage Issue Type: Improvement Assignee: ben patterson Components: ghprb-plugin Created: 2016/Oct/07 8:16 PM Priority: Minor Reporter: D P The credentials plug-in added support for tracking credentials usage, see JENKINS-20139. However the consumer plug-in needs an update to enable this. Please add support. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-38827) Add Git Client support to track where a credential is used
Title: Message Title D P created an issue Jenkins / JENKINS-38827 Add Git Client support to track where a credential is used Issue Type: Improvement Assignee: Mark Waite Components: git-client-plugin Created: 2016/Oct/07 8:01 PM Priority: Minor Reporter: D P The credentials plug-in added support for tracking credentials usage, see JENKINS-20139. However the consumer plug-in needs an update to enable this. Please add support. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-38826) Add SSH Credential support to track where a credential is used
Title: Message Title D P updated an issue Jenkins / JENKINS-38826 Add SSH Credential support to track where a credential is used Change By: D P Summary: Add SSH Credential support to track where a credential is used Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38826) Add support to track where a credential is used
Title: Message Title D P created an issue Jenkins / JENKINS-38826 Add support to track where a credential is used Issue Type: Improvement Assignee: stephenconnolly Components: ssh-credentials-plugin Created: 2016/Oct/07 7:52 PM Priority: Minor Reporter: D P credentials plug-in added support for tracking credentials usage, see JENKINS-20139. However the consumer plug-in needs an update to enable this. Please add support. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-26008) Use of compression during copying of artifacts cut throughput by a factor of 3
Title: Message Title Thomas de Grenier de Latour commented on JENKINS-26008 Re: Use of compression during copying of artifacts cut throughput by a factor of 3 Just closed JENKINS-30815 as a duplicate of this one, after Carl George pointed it to me. But you can still have a look there for more evidence of how undesirable this compression can be in some cases. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30815) GZip compression of master-slave transfer should be optional
Title: Message Title Thomas de Grenier de Latour closed an issue as Duplicate Yes, thanks, you're absolutely right, my issue is a duplicate. Closing it. Jenkins / JENKINS-30815 GZip compression of master-slave transfer should be optional Change By: Thomas de Grenier de Latour Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-36521) Newline characters in commit logs not parsed correctly
Title: Message Title Shannon Kerr commented on JENKINS-36521 Re: Newline characters in commit logs not parsed correctly Our teams are seeing this same issue. We use Trac+svn and typically our tickets in the form of #1234 are translated into a link to that ticket. When going from 2.5.7 to 2.6 of this plugin, our clickable links are now represented by the raw html and our nicely formatted revision changes list is no longer nicely formatted and more challenging to read around sometimes multiple links throughout the list. I've taken our primary and sandbox Jenkins instances back to 2.5.7 for now. We're using 1.651 and 1642, but I also verified this in my private 2.19.1 instance. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30815) GZip compression of master-slave transfer should be optional
Title: Message Title Carl George commented on JENKINS-30815 Re: GZip compression of master-slave transfer should be optional This is the same issue as JENKINS-26008 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-11046) Project deletion does not wipe out project workspaces
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-11046 Project deletion does not wipe out project workspaces Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Jesse Glick commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace I couldn't easily see any code pertaining to the deletion of the workspaces. here it is Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Title: Message Title John Schroeder commented on JENKINS-27084 Re: SVN authentication fails using subversion plugin v.2.5 I'm getting the: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: authentication cancelled When trying to connect to an Assembla SVN repository via SSH. I am able to connect via HTTP with a username and password but not through SSH. I've tried all of the workarounds listed here with no success. Assembla requires that an environment variable called REPO_NAME be set and forwarded for svn+ssh. The environment variable is set and the SendEnv is configured in ~/.ssh/config: Host subversion.assembla.com SendEnv REPO_NAME It works via the command line as the Jenkins user. Will this be send through the subversion plugin in Jenkins? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27134) Permission for input approval, or choice of Jenkins-specific group as submitter
Title: Message Title Jesse Glick commented on JENKINS-27134 Re: Permission for input approval, or choice of Jenkins-specific group as submitter actually defining it in core would prevent uptake from plugins stephenconnolly proposes some mechanism TBD whereby the API could be defined in core for the long term, with a copy in some plugin permitting it to be used in the near term without a new core dependency. This has been done in the past for certain other APIs, though it can be tricky depending on the case. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27134) Permission for input approval, or choice of Jenkins-specific group as submitter
Title: Message Title Jesse Glick commented on JENKINS-27134 Re: Permission for input approval, or choice of Jenkins-specific group as submitter I don't see any advantage as to why you'd want this to be a specific permission Nor is that currently being proposed. The proposal is simply to extend the permitted values of “submitter” to include not just user IDs and external (e.g., LDAP) groups, but also “Jenkins-local” groups defined by any authorization strategy implementing a new SPI. The current behavior is good enough. Great, then you need not worry. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38690) JNLPv4 Thread storm
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38690 Re: JNLPv4 Thread storm Code changed in jenkins User: James Nord Path: Jenkinsfile http://jenkins-ci.org/commit/remoting/48104c792cb50f02ffd05f968760a38102bf47d2 Log: Merge remote-tracking branch 'origin/master' into JENKINS-38690 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38690) JNLPv4 Thread storm
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38690 Re: JNLPv4 Thread storm Code changed in jenkins User: James Nord Path: src/main/java/org/jenkinsci/remoting/protocol/impl/NIONetworkLayer.java http://jenkins-ci.org/commit/remoting/751cb2e84945cdaf9d00cafd24d983dd83f1196a Log: JENKINS-38690 do not cause a IOHub Thread Storm We should only add the READ interested OPS when we have fully drained the read queue. In the case we had a lot of data to read (where lots >> 8192 bytes) we would read a buffers worth of data add READ to the interested opps then read another buffer in the same thread. If we where reading 81920 bytes for example this would be 9 calls to add READ OPs - which would run on the selctor thread and cause an immediate wakeup to be called followed by a new onReady(). However the onReady will be added as a defered callback and the ops removed, but the read thread is still going and as it takes time will call back again to add interested ops... which will wake the selector see that READ ops are valid and cause a new deffered callback... So do not add read interested ops inside the loop, add it only when we have drained the buffer. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38690) JNLPv4 Thread storm
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38690 Re: JNLPv4 Thread storm Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/remoting/protocol/impl/NIONetworkLayer.java http://jenkins-ci.org/commit/remoting/9c40e36c1cd708a4a92765a4e42a28f5ad97382e Log: Merge pull request #117 from stephenc/jenkins-38690 JENKINS-38690 Do not cause a Thread storm in IOHub Compare: https://github.com/jenkinsci/remoting/compare/b95b144ca1e3...9c40e36c1cd7 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38690) JNLPv4 Thread storm
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38690 Re: JNLPv4 Thread storm Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/remoting/protocol/impl/NIONetworkLayer.java http://jenkins-ci.org/commit/remoting/618a16a823abb11bbb256733218421ea526f5106 Log: JENKINS-38690 Rework to use a more performant loop Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38690) JNLPv4 Thread storm
Title: Message Title Jesse Glick updated JENKINS-38690 Jenkins / JENKINS-38690 JNLPv4 Thread storm Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32746) TestNG Results Trend graph doesn't show all build results
Title: Message Title Swapnil Verma commented on JENKINS-32746 Re: TestNG Results Trend graph doesn't show all build results Upvoting this jira. Please, can we have this jira fixed as per Oleksandr Kulychok suggestion. Thanks in advance. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38825) MultiJob does not build Pipeline jobs
Title: Message Title Andrey Chernih created an issue Jenkins / JENKINS-38825 MultiJob does not build Pipeline jobs Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 2016/Oct/07 4:06 PM Priority: Critical Reporter: Andrey Chernih I am using MultiJob plugin 1.22 and Pipeline plugin 2.4. When I create empty Pipeline job and add it to new multi job, it does not show this job in the list (and does not build it). Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-23642) Cobertura plugin does not publish coverage results for failed build
Title: Message Title Zachary LaCelle commented on JENKINS-23642 Re: Cobertura plugin does not publish coverage results for failed build I'd like to add that I'm having the same issue. Build log says; Skipping Cobertura coverage report as build was not UNSTABLE or better ... But I haven't checked the option to do this. Really need this to work: our unit test failures fail the build intentionally, but I still want to update code coverage for the entire project even if one engineer hasn't repaired their unit testing issues. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20797) UserIdCause should be used, not UserCause
Title: Message Title Mustafa Ulu reopened an issue Release button still triggers UserCause not UserIdCause. See https://github.com/jenkinsci/release-plugin/blob/master/src/main/java/hudson/plugins/release/ReleaseWrapper.java#L695 Jenkins / JENKINS-20797 UserIdCause should be used, not UserCause Change By: Mustafa Ulu Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-38802) Use a more sensible default GC algorithm for jenkins
Title: Message Title Sam Van Oort commented on JENKINS-38802 Re: Use a more sensible default GC algorithm for jenkins Baptiste Mathus Has commented that it is worth adding GC logging by default when we do this. I think that is an excellent idea. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38824) Nullpointer when trying to use params global variable
Title: Message Title
Bryan Keech created an issue
Jenkins / JENKINS-38824
Nullpointer when trying to use params global variable
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2016/Oct/07 3:31 PM
Priority:
Minor
Reporter:
Bryan Keech
Trying to use params global variable and getting null pointer exception. Referencing the build parameter like this works:
node {
echo action
}
But the following causes Nullpointer:
node {
echo params.action
}
Add Comment
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Christian Höltje commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
NO! I don't want to git clone 700MB repositories for twice for every build! I also need to compile code on multiple slaves, then copy stuff around to other slaves and then package stuff up in installers. Local workspaces must not be modified in between.
I totally agree that there needs to be a solution for things like 2.7gb git repositories (we have some) and lots of downloaded dependencies. I'm just saying that the default node() behavior isn't the right place to handle this. I would assume that anyone who needs that ability would use something like the external workspace plugin to do sane caching of data or using something like node('restriction') and ws() to ensure they don't keep getting new (empty) workspaces. With the current model, if you have 10 slaves, each with 4 executors, you have the possibility of needing to clone that repository up to 40 times, with a minimum of 10 (one per slave) per node() invocation.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38736) update guice to release version
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38736 Re: update guice to release version Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/maven-plugin/921e3929a2487c921b5aaabb78438108619fd3c2 Log: JENKINS-38736 Update Sisu Inject to avoid https://github.com/google/guice/issues/899. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38736) update guice to release version
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38736 Re: update guice to release version Code changed in jenkins User: Arnaud Heritier Path: pom.xml http://jenkins-ci.org/commit/maven-plugin/aacd9a67f1a59dbd0c80b45000a674e657d96c2d Log: Merge pull request #80 from jglick/sisu-inject-JENKINS-38736 JENKINS-38736 Update Sisu Inject Compare: https://github.com/jenkinsci/maven-plugin/compare/2e671da7a66f...aacd9a67f1a5 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38823) JenkinsServer.deleteJob with crumbFlag is missing
Title: Message Title Peter Laszlo created an issue Jenkins / JENKINS-38823 JenkinsServer.deleteJob with crumbFlag is missing Issue Type: Improvement Assignee: Karl-Heinz Marbaise Components: java-client-api Created: 2016/Oct/07 3:11 PM Priority: Minor Reporter: Peter Laszlo There is no version of JenkinsServer.deleteJob where it's possible to set crumbFlag Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38672) Git Organization plugin bug
Title: Message Title Jesse Glick resolved as Won't Do The plugin you are using is not open source, so this should not be filed here. Please use support tickets to report issues. Jenkins / JENKINS-38672 Git Organization plugin bug Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For
[JIRA] (JENKINS-38822) Service fails to restart when both .jpi and .hpi files found
Title: Message Title Irina Muchnik created an issue Jenkins / JENKINS-38822 Service fails to restart when both .jpi and .hpi files found Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Oct/07 2:52 PM Environment: Jenkins ver. 2.7.4 plugins: INFO LavaLampNotifier: 1.4 INFO ace-editor: 1.1 INFO analysis-collector: 1.48 INFO analysis-core: 1.79 INFO ansicolor: 0.4.2 INFO ant: 1.4 INFO antisamy-markup-formatter: 1.5 INFO audit-trail: 2.2 INFO authentication-tokens: 1.3 INFO aws-credentials: 1.16 INFO aws-java-sdk: 1.10.50 INFO backup: 1.6.1 INFO blueocean: 1.0.0-b06 INFO blueocean-commons: 1.0.0-b06 INFO blueocean-config: 1.0.0-b06 INFO blueocean-dashboard: 1.0.0-b06 INFO blueocean-events: 1.0.0-b06 INFO blueocean-jwt: 1.0.0-b06 INFO blueocean-personalization: 1.0.0-b06 INFO blueocean-pipeline-api-impl: 1.0.0-b06 INFO blueocean-rest: 1.0.0-b06 INFO blueocean-rest-impl: 1.0.0-b06 INFO blueocean-web: 1.0.0-b06 INFO bootstraped-multi-test-results-report: 1.4.22 INFO bouncycastle-api: 2.16.0 INFO branch-api: 1.11 INFO build-environment: 1.6 INFO build-failure-analyzer: 1.17.1 INFO build-flow-extensions-plugin: 0.1.1 INFO build-flow-plugin: 0.20 INFO build-monitor-plugin: 1.10+build.201608030223 INFO build-timeout: 1.17.1 INFO build-user-vars-plugin: 1.5 INFO buildgraph-view: 1.3.2 INFO checkmarx: 8.2 INFO checkstyle: 3.46 INFO ci-game: 1.25 INFO claim: 2.8 INFO clone-workspace-scm: 0.6 INFO cloudbees-folder: 5.13 INFO cloverphp: 0.5 INFO cobertura: 1.9.8 INFO conditional-buildstep: 1.3.5 INFO config-file-provider: 2.13 INFO copy-to-slave: 1.4.4 INFO copyartifact: 1.38.1 INFO create-fingerprint: 1.2 INFO credentials: 2.1.5 INFO credentials-binding: 1.9 INFO cucumber-reports: 2.8.0 INFO cucumber-testresult-plugin: 0.9.7 INFO custom-job-icon: 0.2 INFO custom-tools-plugin: 0.4.4 INFO cvs: 2.12 INFO cygpath: 1.5 INFO dashboard-view: 2.9.10 INFO depgraph-view: 0.11 INFO disk-usage: 0.28 INFO display-url-api: 0.5 INFO docker-commons: 1.4.1 INFO docker-workflow: 1.8 INFO downstream-buildview: 1.9 INFO durable-task: 1.12 INFO ec2: 1.35 INFO email-ext: 2.51 INFO envinject: 1.93 INFO extended-choice-parameter: 0.75 INFO external-monitor-job: 1.6 INFO favorite: 1.16 INFO filesystem_scm: 1.20 INFO ghprb: 1.33.1 INFO git: 3.0.0 INFO git-client: 2.0.0 INFO git-server: 1.7 INFO github: 1.20.0 INFO github-api: 1.76 INFO github-branch-source: 1.10 INFO github-oauth: 0.24 INFO github-organization-folder: 1.5 INFO gradle: 1.25 INFO groovy: 1.29 INFO handlebars: 1.1.1 INFO htmlpublisher: 1.11 INFO icon-shim: 2.0.3 INFO
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Yury Zaytsev commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. > which sounds like a bug in Python: it should use /usr/bin/env. Just for the record: this isn't a bug by any means. They do it on purpose, because installed modules should be bound to a specific installing interpreter for many reasons. The question is, can they apply some hacks on their side to work around limited shebang path length issue or not, but it's a tangential one, and, in any case, the latest status was that if one could think of something, they'd welcome patches. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38821) Global library class calling another global libraries static method fails
Title: Message Title
Mike Kobit created an issue
Jenkins / JENKINS-38821
Global library class calling another global libraries static method fails
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-global-lib-plugin, workflow-cps-plugin
Created:
2016/Oct/07 2:38 PM
Environment:
Jenkins ver. 2.19 Pipeline: Shared Groovy Libraries - 2.4
Priority:
Minor
Reporter:
Mike Kobit
I ran into a strange issue with with a global library using the legacy way of the Git repository in the workflowLibs folder. When calling another class' static method in the Global library (in this fashion at least) caused the execution to fail. I was trying to write behavior similar to the Checks.checkArg(boolean argument) method. I think an example will help explain at least what I ran into. Code com.mkobit.MyClass
package com.mkobit
class MyClass implements Serializable {
final String myVar
MyClass(final String myVar) {
this.myVar = Objects.requireNonNull(myVar)
}
MyClass(final boolean arg) {
Checks.checkArg(arg)
this.myVar = 'got through'
}
}
com.mkobit.MyClassFactory
package com.mkobit
class MyClassFactory {
static MyClass create() {
new MyClass(null)
}
}
[JIRA] (JENKINS-38702) AccuRev for Jenkins Plugin does not display Depots
Title: Message Title Peter Lingesso commented on JENKINS-38702 Re: AccuRev for Jenkins Plugin does not display Depots Joseph, So I was looking on the master in the jobs directory for the project, and I added the Server, then the Depot and it still doesnt' show in the drop down menu in jenkins. Pete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37295) Redesign the empty states
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-37295 Redesign the empty states Change By: Cliff Meyers * They are all horrible.* Please review them all and redesign themScreens with Existing Empty States* Pipeline Detail** Activity tab: has empty state for when pipeline has no runs** Branches tab: has two empty states, either "no branches" (if a multibranch that has no branches) or "not supported" (if pipeline, freestyle or other)** Pull Requests tab: same as Branches basically, either "no pull requests" or "not supported"* Run Detail** Pipeline tab: empty state for when viewing a queued build** Changes tab: needs state for when build is queued; has empty state state for build that was not triggered as a result of SCM changes** Tests tab: needs state for when build is queued; has empty state for build doesn't publish tests** Artifacts tab: needs state for when build is queued; has empty state for build doesn't publish artifactsScreens that Need New Empty States ( possibly ?)* Pipelines List: should probably have an empty state for when there are no projects in Jenkins (i.e. fresh install).* Organization Pipelines List: this is the same view as above, except it's a list of just the pipelines for a single org. Probably needs copy tweaks for its empty state relative to main Pipelines List. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37295) Redesign the empty states
Title: Message Title Cliff Meyers commented on JENKINS-37295 Re: Redesign the empty states Brody Maclean added details on all the empty states we currently have and which ones should (probably) be added. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37295) Redesign the empty states
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-37295 Redesign the empty states Change By: Cliff Meyers * They are all horrible.* Please review them all and redesign them Screens with Existing Empty States* Pipeline Detail** Activity tab: has empty state for when pipeline has no runs** Branches tab: has two empty states, either "no branches" (if a multibranch that has no branches) or "not supported" (if pipeline, freestyle or other)** Pull Requests tab: same as Branches basically, either "no pull requests" or "not supported"* Run Detail** Pipeline tab: empty state for when viewing a queued build** Changes tab: needs state for when build is queued; has empty state state for build that was not triggered as a result of SCM changes** Tests tab: needs state for when build is queued; has empty state for build doesn't publish tests** Artifacts tab: needs state for when build is queued; has empty state for build doesn't publish artifacts Screens that Need New Empty States ( ? ) * Pipelines List: should probably have an empty state for when there are no projects in Jenkins (i.e. fresh install).* Organization Pipelines List: this is the same view as above, except it's a list of just the pipelines for a single org. Probably needs copy tweaks for its empty state relative to main Pipelines List. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37295) Redesign the empty states
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-37295 Redesign the empty states Change By: Cliff Meyers * They are all horrible.* Please review them all and redesign them Existing Empty States* Pipeline Detail** Activity tab: has empty state for when pipeline has no runs** Branches tab: has two empty states, either "no branches" (if a multibranch that has no branches) or "not supported" (if pipeline, freestyle or other)** Pull Requests tab: same as Branches basically, either "no pull requests" or "not supported"* Run Detail** Pipeline tab: empty state for when viewing a queued build** Changes tab: needs state for when build is queued; has empty state state for build that was not triggered as a result of SCM changes** Tests tab: needs state for when build is queued; has empty state for build doesn't publish tests** Artifacts tab: needs state for when build is queued; has empty state for build doesn't publish artifactsNew Empty States?* Pipelines List: should probably have an empty state for when there are no projects in Jenkins (i.e. fresh install).* Organization Pipelines List: this is the same view as above, except it's a list of just the pipelines for a single org. Probably needs copy tweaks for its empty state relative to main Pipelines List. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. If we generate directory names that are ~80 characters long we can expect trouble. Depends entirely on what you are doing inside those directories. 80 characters is not really that long, and prior to the change directories prefixes could be much longer—unbounded, in fact (as noted in some complaints prior to the fix). (Note that you can customize the prefix length via system property.) PATH_MAX=40 No, anything less than 54 will not work at all, I just neglected to have that issue a warning. already tuned to workaround the shebang PATH limitations This really sounds like a separate issue, possibly in durable-task plugin, which should be filed separately with steps to reproduce from scratch—unless it is a limitation in the tools you are using: all I have seen so far is when you install any Python modules in a local prefix tree, it hardcodes the absolute path to the interpreter into the scripts which sounds like a bug in Python: it should use /usr/bin/env. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38664) bitbucket source plugin fails with bad URL
Title: Message Title John Stephenson commented on JENKINS-38664 Re: bitbucket source plugin fails with bad URL Thanks for your quick response. I finally got past this. Background: I'm currently setting up Jenkins in AWS and haven't setup a DNS entry for the jenkins host machine yet. I don't know if this is relevant but hey yo. For me I had : set in the Jenkins URL field for the jenkins installation but this still didn't work (I didn't change anything here). I did find that the JENKINS_URL env var should be being set. I assume it wasn't as when I explicitly added a new env var within the Jenkins web admin, this worked! The value was a copy+paste job from the Jenkins URL field that's on the same config webpage. Strange but true. Anyway, I'm now onto my next hurdle! Many thanks! John Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Jim Poje commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin We are facing the issue with the p4 software plugin in the case where we have parent/child jobs running. When we triggered the parent's job it captures the P4_CHANGELIST to pass down to the child job. However, in between running the parent job and the child job, if there are changelists submitted to perforce, then the value for P4_CHANGELIST is changed for the child job. This is not good for us since we need to make sure that both the parent and child jobs are syncing down to the same P4_CHANGELIST. Is there anyway that the p4 plugin will allow us to set the P4_CHANGELIST and not use the latest changelist in order for us to ensure that the same P4_CHANGELIST are used by both parent and child jobs? The "Use the upstream project revision" appears to be a solution to resolve, and ask this be prioritized. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38815) ForemanSharedNodeCloud.canProvision(...) has to use a caching mechanism
Title: Message Title Scott Hebert commented on JENKINS-38815 Re: ForemanSharedNodeCloud.canProvision(...) has to use a caching mechanism I was able to reproduce this very easily just by creating a simple Node... "Handling POST /computer/createItem from 10.3.116.222 : RequestHandlerThread[#19]" #96 daemon prio=5 java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:170) at java.net.SocketInputStream.read(SocketInputStream.java:141) at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) at java.io.BufferedInputStream.read(BufferedInputStream.java:345) - locked <0x29cede97> (a java.io.BufferedInputStream) at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1536) - locked <0x5a26222c> (a sun.net.www.protocol.http.HttpURLConnection) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441) - locked <0x5a26222c> (a sun.net.www.protocol.http.HttpURLConnection) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at org.glassfish.jersey.client.internal.HttpUrlConnector._apply(HttpUrlConnector.java:394) at org.glassfish.jersey.client.internal.HttpUrlConnector.apply(HttpUrlConnector.java:285) at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:255) at org.glassfish.jersey.client.JerseyInvocation$1.call(JerseyInvocation.java:684) at org.glassfish.jersey.client.JerseyInvocation$1.call(JerseyInvocation.java:681) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:228) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:444) at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:681) at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:411) at org.glassfish.jersey.client.JerseyInvocation$Builder.get(JerseyInvocation.java:311) at com.redhat.foreman.ForemanAPI.getForemanResponse(ForemanAPI.java:153) at com.redhat.foreman.ForemanAPI.getHostParameterValue(ForemanAPI.java:195) at com.redhat.foreman.ForemanAPI.getHostForQuery(ForemanAPI.java:309) at com.redhat.foreman.ForemanAPI.getCompatibleHosts(ForemanAPI.java:327) at com.redhat.foreman.ForemanSharedNodeCloud.canProvision(ForemanSharedNodeCloud.java:158) at hudson.model.Label.getClouds(Label.java:227) at hudson.model.Label.isEmpty(Label.java:435) at jenkins.model.Jenkins.trimLabels(Jenkins.java:1899) at jenkins.model.Nodes$2.run(Nodes.java:137) at hudson.model.Queue._withLock(Queue.java:1320) at hudson.model.Queue.withLock(Queue.java:1197) at jenkins.model.Nodes.addNode(Nodes.java:132) at jenkins.model.Jenkins.addNode(Jenkins.java:1853) at hudson.model.ComputerSet.doCreateItem(ComputerSet.java:262) - locked <0x6054fcd8> (a hudson.model.ComputerSet) The Foreman host does seem slow today...luckily so...it uncovered this problem...
[JIRA] (JENKINS-38820) Internal Server Error from BitBucket when attempting to index branches
Title: Message Title
Jordan McCoy created an issue
Jenkins / JENKINS-38820
Internal Server Error from BitBucket when attempting to index branches
Issue Type:
Bug
Assignee:
Antonio Muñiz
Components:
bitbucket-branch-source-plugin
Created:
2016/Oct/07 1:59 PM
Environment:
Jenkins 2.19.1, bitbucket-branch-source-plugin 1.8
Priority:
Major
Reporter:
Jordan McCoy
After configuring a new multibranch pipeline job with a bitbucket branch source targeting bitbucket cloud, branch indexing returns this error:
Started
Connecting to https://bitbucket.org using jor...@rigup.com/**
Looking up rigup/rigup-build for branches
FATAL: Failed to recompute children of RigUp Main Build
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 500: INTERNAL SERVER ERROR.
{"error": {"message": "Internal server error", "id": "66ccda07d9d24c928c6f554c39022eb8"}}
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:432)
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getBranches(BitbucketCloudApiClient.java:225)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieveBranches(BitbucketSCMSource.java:323)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:279)
at jenkins.scm.api.SCMSource.fetch(SCMSource.java:148)
at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:294)
at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:157)
at
