[JIRA] (JENKINS-19483) LDAP plugin sets userSearchDN incorrectly
Title: Message Title
Sebastian F. edited a comment on JENKINS-19483
Re: LDAP plugin sets userSearchDN incorrectly
Simlar problem with:Jenkins 2.34LDAP Plugin 1.13Apache Tomcat/8.5.8OpenJDK 1.8.0_111-b15RHEL 6.6Configured the following: {color:#14892c}*ldap://test.srv.mydomain:389*{color}DC=testde,DC=rootdom,DC=netfalseOU=Usercn=\{0} From Log I can see that initialization is correct: {code:java} 29-Nov-2016 07:34: 30.680 INFO [Finalizing set up] org.acegisecurity.ldap.DefaultInitialDirContextFactory.setProviderUrl URL 'ldap://test.srv.mydomain/DC=testde,DC=rootdom,DC=net', root DN is 'DC=testde,DC=rootdom,DC=net'29-Nov-2016 07:34:30.712 INFO [Finalizing set up] org.acegisecurity.providers.ldap.populator.DefaultLdapAuthoritiesPopulator.setGroupSearchBase groupSearchBase is empty. Searches will be performed from the root: DC=testde,DC=rootdom,DC=net{code}29-Nov-2016 07:34: 57.190 WARNING [Handling POST /jenkins/j_acegi_security_check from xxx.xxx.xxx. : https-jsse-nio-8443-exec-2] org.acegisecurity.providers.ldap.authenticator.BindAuthenticator2.handleBindException Failed to bind to LDAP: userDn{color:#14892c}*ldap://testde.rootdom.net:389*{color}/CN=testuser,OU=User,DC=testde,DC=rootdom,DC=net,{color:#d04437}*OU=User,DC=testde,DC=rootdom,DC=net*{color} username=testuser javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A8, comment: AcceptSecurityContext error, data 52e, v1db1^@]What makes me wonder is:# Why it does not use configured ldap server# Why is userSearchBase + RootDN added a second time
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
[JIRA] (JENKINS-32797) Access to check for unprotected/never secured paths
Title: Message Title Oliver Gondža commented on JENKINS-32797 Re: Access to check for unprotected/never secured paths Is this about kerberos-sso plugin only? In case it is, please file an issue for whitelist JNLP connection endpoint. I would be more comfortable addressing it in that plugin rather than in core (as it is the plugin what have unusual security handling). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40013) Unable to set and use global groovy functions
Title: Message Title
aurelien leboulanger commented on JENKINS-40013
Re: Unable to set and use global groovy functions
your sample works for me The issue was with the usage of the @NonCPS annotation
pipeline {
agent none
stages {
stage("foo") {
steps {
getCurrentWorkspacePath("Steve")
}
}
}
}
@NonCPS
static
def getCurrentWorkspacePath(environments) {
def matcher = environments =~ 'export IMAGE_DIR\\s*=\\s*(.+)'
matcher ? matcher[0][1] : null
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40069) git timeout option has no effect
Title: Message Title Martin Stolle commented on JENKINS-40069 Re: git timeout option has no effect Ah sorry, missed that. Thanks for your help. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37044) Plugin does not support Pipeline jobs
Title: Message Title Wisen Tanasa started work on JENKINS-37044 Change By: Wisen Tanasa 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-33777) multijob-plugin: DropDown "Select strategy" is empty
Title: Message Title Nate Liu commented on JENKINS-33777 Re: multijob-plugin: DropDown "Select strategy" is empty this definitely needs to be looked into as retry feature is not working at all Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33777) multijob-plugin: DropDown "Select strategy" is empty
Title: Message Title Nate Liu edited a comment on JENKINS-33777 Re: multijob-plugin: DropDown "Select strategy" is empty This definitely needs to be looked into as retry feature is not working at all.I have exactly the same issue and here's the multijob running node console output:_Finished Build : NPM10.0_980 XXX_980 -20161129-0117 of Job : XXX_Build_For_Test_Ova with status : FAILUREScanning failed job console output using parsing rule file .Parser rules file not found.Failed the build, the failure doesn't match the rules.Build step 'MultiJob Phase' marked build as failure_ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33777) multijob-plugin: DropDown "Select strategy" is empty
Title: Message Title Nate Liu edited a comment on JENKINS-33777 Re: multijob-plugin: DropDown "Select strategy" is empty this This definitely needs to be looked into as retry feature is not working at all .I have exactly the same issue and here's the multijob running node console output:_Finished Build : NPM10.0_980-20161129-0117 of Job : XXX_Build_For_Test_Ova with status : FAILUREScanning failed job console output using parsing rule file .Parser rules file not found.Failed the build, the failure doesn't match the rules.Build step 'MultiJob Phase' marked build as failure_ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33777) multijob-plugin: DropDown "Select strategy" is empty
Title: Message Title Nate Liu updated an issue Jenkins / JENKINS-33777 multijob-plugin: DropDown "Select strategy" is empty Change By: Nate Liu Comment: This definitely needs to be looked into as retry feature is not working at all.I have exactly the same issue and here's the multijob running node console output:_Finished Build : XXX_980-20161129-0117 of Job : XXX_Build_For_Test_Ova with status : FAILUREScanning failed job console output using parsing rule file .Parser rules file not found.Failed the build, the failure doesn't match the rules.Build step 'MultiJob Phase' marked build as failure_ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32797) Access to check for unprotected/never secured paths
Title: Message Title Bryson Gibbons commented on JENKINS-32797 Re: Access to check for unprotected/never secured paths Actually, this is an issue for any plugin that attempts to use Kerberos for signing in through servlet filters; right now, that I know of, this includes Kerberos-sso plugin and negotiatesso plugin. Currently I have duplicated parts of the code in core that are inaccessible to provide the needed functionality (see https://github.com/jenkinsci/negotiatesso-plugin/blob/master/src/main/java/com/github/farmgeek4life/jenkins/negotiatesso/NegSecFilter.java), and now a pull request with Kerberos-sso plugin is looking to also skip authentication for unprotected root actions (https://github.com/jenkinsci/kerberos-sso-plugin/pull/9) Without adding some small lever of access to these functions, any plugin that performs authentication through a servlet filter will have to duplicate code from core, or authenticate access to some paths that actually should be accessible without authentication. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32797) Access to check for unprotected/never secured paths
Title: Message Title Bryson Gibbons edited a comment on JENKINS-32797 Re: Access to check for unprotected/never secured paths Actually, this is an issue for any plugin that attempts to use Kerberos for signing in through servlet filters; right now, that I know of, this includes Kerberos-sso plugin and negotiatesso plugin. Currently I have duplicated parts of the code in core that are inaccessible to provide the needed functionality (see https://github.com/jenkinsci/negotiatesso-plugin/blob/master/src/main/java/com/github/farmgeek4life/jenkins/negotiatesso/NegSecFilter.java), and now a pull request with Kerberos-sso plugin is looking to also skip authentication for unprotected root actions (https://github.com/jenkinsci/kerberos-sso-plugin/pull/9)Without adding some small lever level of access to these functions, any plugin that performs authentication through a servlet filter will have to duplicate code from core, or authenticate access to some paths that actually should be accessible without authentication. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title
Morne Joubert commented on JENKINS-37584
Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
The $ {env.P4_CHANGELIST} is not working for us but the following is currentBuild.getRawBuild().getEnvironment()["P4_CHANGELIST"]
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32797) Access to check for unprotected/never secured paths
Title: Message Title Oliver Gondža commented on JENKINS-32797 Re: Access to check for unprotected/never secured paths It makes sense to provide a way for plugins to tell of path should be protected or not. Commenting on the state of the path as attached (please move this to PR), please consolidate it to one method that accept restOfPath as an argument and performs all of the checks. Provided you do not need the two for some reason. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32797) Access to check for unprotected/never secured paths
Title: Message Title
Oliver Gondža edited a comment on JENKINS-32797
Re: Access to check for unprotected/never secured paths
It makes sense to provide a way for plugins to tell of path should not be protected or not. Commenting on the state of the path as attached (please move this to PR), please consolidate it to one method that accept {{restOfPath}} as an argument and performs all of the checks. Provided you do not need the two for some reason.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32797) Access to check for unprotected/never secured paths
Title: Message Title Bryson Gibbons commented on JENKINS-32797 Re: Access to check for unprotected/never secured paths Will do as one function; after looking at my duplicated code, I was unable to use "Stapler.getCurrentRequest().getRestOfPath()" because at the point I am checking permission requirements the request is still in the filters, and stapler doesn't know about it yet. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39943) Artifactory gradle usage has wrong documentation for GradleDeployer.usesPlugin usage
Title: Message Title Christoph Obexer assigned an issue to Eyal Ben Moshe Jenkins / JENKINS-39943 Artifactory gradle usage has wrong documentation for GradleDeployer.usesPlugin usage Change By: Christoph Obexer Assignee: Eyal Ben Moshe Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40062) Optionally include config.xml files for nodes
Title: Message Title
Antonio Muñiz updated an issue
Jenkins / JENKINS-40062
Optionally include config.xml files for nodes
Change By:
Antonio Muñiz
There is useful diagnosis information in the nodes' config file, like {{ { prefixStartSlaveCmd}} } for example.Having those files in the support bundle would be great.Secrets must be filtered out and the inclusion of this files in the bundle must be optional.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39943) Artifactory gradle usage has wrong documentation for GradleDeployer.usesPlugin usage
Title: Message Title Christoph Obexer commented on JENKINS-39943 Re: Artifactory gradle usage has wrong documentation for GradleDeployer.usesPlugin usage Eyal Ben Moshe Eyal Ben Moshe: Is one of these accounts better than the other one? Why are there two? And which one is supposed to be assigned by default? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26099) Configurable ID for Credentials
Title: Message Title Anudeep Lalam commented on JENKINS-26099 Re: Configurable ID for Credentials Jesse Glick - I am using Jenkins ver. 2.9. I want to customise my Jenkins Credential ID. When I try to configure, the edit option is not present for ID. Please see below. Where can I edit the ID ?? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26099) Configurable ID for Credentials
Title: Message Title Anudeep Lalam updated an issue Jenkins / JENKINS-26099 Configurable ID for Credentials Change By: Anudeep Lalam Attachment: CredentailID.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32797) Access to check for unprotected/never secured paths
Title: Message Title Bryson Gibbons commented on JENKINS-32797 Re: Access to check for unprotected/never secured paths Pull Request: https://github.com/jenkinsci/jenkins/pull/2652 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29649) don't overwrite existing junit-results
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29649 Re: don't overwrite existing junit-results Code changed in jenkins User: Vladislav Ponomarev Path: pom.xml src/main/java/org/tap4j/plugin/util/GraphHelper.java src/test/java/org/tap4j/plugin/PublishersCombinationTest.java src/test/resources/org/tap4j/plugin/PublishersCombinationTest.zip http://jenkins-ci.org/commit/tap-plugin/170bfce788bbd13be50fae603e5b0c2bb78bbd26 Log: Added red testcase for JENKINS-29649 + Jenkins2 pipeline job. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29649) don't overwrite existing junit-results
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29649 Re: don't overwrite existing junit-results Code changed in jenkins User: Vladislav Ponomarev Path: src/main/java/org/tap4j/plugin/TapProjectAction.java src/main/java/org/tap4j/plugin/TapTestResultAction.java src/main/java/org/tap4j/plugin/model/TapStreamResult.java src/main/java/org/tap4j/plugin/model/TapTestResultResult.java src/main/java/org/tap4j/plugin/util/GraphHelper.java http://jenkins-ci.org/commit/tap-plugin/2fbcc63feba07d583c5ec620fa47f5c509ca0f01 Log: Fixing Jenkins 2 part of JENKINS-29649. Making the testcase green, migrating AbstractBuild -> Run to better support Jenkins 2 workflow jobs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37623) No tooltips / image map generated on a graph when one of the previous builds failed before publishing TAP data
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37623 Re: No tooltips / image map generated on a graph when one of the previous builds failed before publishing TAP data Code changed in jenkins User: Vladislav Ponomarev Path: src/main/java/org/tap4j/plugin/TapProjectAction.java http://jenkins-ci.org/commit/tap-plugin/6cde4f7b2326e0a42c01cf29b1353b9036b1be30 Log: [FIXED JENKINS-37623] Tolerate failed builds when generating tooltips. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37623) No tooltips / image map generated on a graph when one of the previous builds failed before publishing TAP data
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37623 Re: No tooltips / image map generated on a graph when one of the previous builds failed before publishing TAP data Code changed in jenkins User: Vladislav Ponomarev Path: src/test/java/org/tap4j/plugin/util/GraphHelperTest.java src/test/resources/org/tap4j/plugin/util/GraphHelperTest.zip http://jenkins-ci.org/commit/tap-plugin/a9193230b3c285ee209531b4f6c2fd3cdbce944d Log: Red testcase for JENKINS-37623 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38149) Pipeline integration: TAP Extended Test Results throws NullPointerException
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38149 Re: Pipeline integration: TAP Extended Test Results throws NullPointerException Code changed in jenkins User: Bruno P. Kinoshita Path: pom.xml src/main/java/org/tap4j/plugin/TapProjectAction.java src/main/java/org/tap4j/plugin/TapTestResultAction.java src/main/java/org/tap4j/plugin/model/TapStreamResult.java src/main/java/org/tap4j/plugin/model/TapTestResultResult.java src/main/java/org/tap4j/plugin/util/GraphHelper.java src/main/resources/index.jelly src/main/resources/org/tap4j/plugin/TapBuildAction/summary.jelly src/main/resources/org/tap4j/plugin/TapProjectAction/floatingBox.jelly src/main/resources/org/tap4j/plugin/TapProjectAction/nodata.jelly src/main/resources/org/tap4j/plugin/TapProjectAction/sidepanel.jelly src/main/resources/org/tap4j/plugin/TapResult/contents.jelly src/main/resources/org/tap4j/plugin/TapResult/index.jelly src/test/java/org/tap4j/plugin/PublishersCombinationTest.java src/test/java/org/tap4j/plugin/util/GraphHelperTest.java src/test/resources/org/tap4j/plugin/PublishersCombinationTest.zip src/test/resources/org/tap4j/plugin/util/GraphHelperTest.zip http://jenkins-ci.org/commit/tap-plugin/b39c1fdea728cf43ba24a4a424742a891e30a7f8 Log: Merge branch 'pr/14' JENKINS-38149: merge part-2 of this issue, thanks to @anenviousguest and @oleg-nenashev Compare: https://github.com/jenkinsci/tap-plugin/compare/2044059d11f9...b39c1fdea728 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-37623) No tooltips / image map generated on a graph when one of the previous builds failed before publishing TAP data
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-37623 No tooltips / image map generated on a graph when one of the previous builds failed before publishing TAP data Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40091) Require support for ZAProxy Plugin using DSL
Title: Message Title rama krishna created an issue Jenkins / JENKINS-40091 Require support for ZAProxy Plugin using DSL Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2016/Nov/29 9:57 AM Priority: Minor Reporter: rama krishna job-dsl-plugin doesnot support ZAProxy Plugin, is there any way to achieve this Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title
Paul Allen commented on JENKINS-37584
Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Thank you for the details; I had seen your comment in the Swarm change, but hadn't had time to try it. The `$ {env.P4_CHANGELIST} ` is used in the unit tests and seems ok, it could be Pipeline versions, but we did test a few combinations. Perhaps it is an assignment or scope issue?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title
Paul Allen edited a comment on JENKINS-37584
Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Thank you for the details; I had seen your comment in the Swarm change, but hadn't had time to try it. The ` $ \ {env.P4_CHANGELIST \ } ` is used in the unit tests and seems ok, it could be Pipeline versions, but we did test a few combinations. Perhaps it is an assignment or scope issue?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40092) can not copy slave.jar after upgrade from 2.31 to 2.34
Title: Message Title Pawel Chudzik created an issue Jenkins / JENKINS-40092 can not copy slave.jar after upgrade from 2.31 to 2.34 Issue Type: Bug Assignee: Unassigned Attachments: jenkins-slave.log Components: core Created: 2016/Nov/29 10:13 AM Priority: Minor Reporter: Pawel Chudzik After upgrade to 2.34 I got this when trying to launch slave agent over ssh: [11/29/16 10:55:03] [SSH] Checking java version of java [11/29/16 10:55:04] [SSH] java -version returned 1.8.0_65. [11/29/16 10:55:04] [SSH] Starting sftp client. [11/29/16 10:55:04] [SSH] SFTP failed. Copying via SCP. [11/29/16 10:55:05] [SSH] Copying latest slave.jar... ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. java.lang.NullPointerException at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769) at org.apache.commons.io.IOUtils.copy(IOUtils.java:1744) at org.apache.commons.io.IOUtils.toByteArray(IOUtils.java:462) at hudson.plugins.sshslaves.SSHLauncher.copySlaveJarUsingSCP(SSHLauncher.java:1098) at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:1059) at hudson.plugins.sshslaves.SSHLauncher.access$300(SSHLauncher.java:137) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:723) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:706) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.la
[JIRA] (JENKINS-38998) Cannot trigger pipeline job
Title: Message Title Yves Schumann commented on JENKINS-38998 Re: Cannot trigger pipeline job Any news here? It's currently some kind of a show stopper as we could not migrate to pipeline jobs... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40093) Blue Ocean: Failed to write lastFinishedBuild
Title: Message Title June Rhodes created an issue Jenkins / JENKINS-40093 Blue Ocean: Failed to write lastFinishedBuild Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/29 10:45 AM Priority: Major Reporter: June Rhodes When BlueOcean makes a REST call to get the dashboard, it starts writing out the JSON and then crashes with the following stack trace: java.io.IOException: Failed to write lastFinishedBuild at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151) at org.kohsuke.stapler.export.Property.writeTo(Property.java:126) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeTo(Property.java:135) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeValue(Property.java:279) at org.kohsuke.stapler.export.Property.writeValue(Property.java:222) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:139) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeTo(Model.java:198) at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:273) at hudson.model.Api.doJson(Api.java:208) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:63) at org.kohsuke.stapler.Http
[JIRA] (JENKINS-40057) Stage view is completely missing for long durations after restarts
Title: Message Title Nash Paz commented on JENKINS-40057 Re: Stage view is completely missing for long durations after restarts Chrome, Internet explorer, will try firefox today for the heck of it. Will try to check tonight, it's a messy jenkins so we have plenty of errors from way before I installed the pipeline plugins. Any particular errors I ought to be looking for? No browser errors I can think of. FYI, stage view frontend is missing when viewing from other comps, as well. Pipeline rest-api is installed, seems fine in the 'installed' tab under plugins. How do I go about checking that it's working? Thanks a million for your time Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40037) Docker builds fail with "Build info capturing failed for docker image..." exception
Title: Message Title Ali Sadik Kumlali commented on JENKINS-40037 Re: Docker builds fail with "Build info capturing failed for docker image..." exception Removing NO_PROXY=.mycompany.com did the trick! Thank you Roman. I noticed I had given some incorrect information. NO_PROXY is needed to bypass our own proxy while accessing Docker Hub directly. I incorrectly said it was needed to access our Artifactory server. Why I needed to access Docker Hub directly then? While following instructions under Make Sure Docker Works With the Artifactory Docker Registry of Jenkins Artifactory Plugin - Setting Up Docker Build Info page, docker pull hello-world command is required to succeed. Now, I understand that the important point here is the push step. By the way; sudo chmod 777 /var/run/docker.sock is still needed. Is this a known issue that has to be mentioned in documentation, or am I doing someting wrong? When Jenkins container is running on a swarm cluster docker pull artifactory.mycompany.com/hello-world succeeds only on the machine Jenkins container runs because we use localhost in HTTP_PROXY url. Using dedicated host for Jenkins container and setting HTTP_PROXY=http://: in http-proxy.conf on each swarm host do not seem to be a good solution. What do you think? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "
[JIRA] (JENKINS-40092) can not copy slave.jar after upgrade from 2.31 to 2.34
Title: Message Title Pawel Chudzik updated an issue Jenkins / JENKINS-40092 can not copy slave.jar after upgrade from 2.31 to 2.34 Change By: Pawel Chudzik Attachment: jenkins-slave.log Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40092) can not copy slave.jar after upgrade from 2.31 to 2.34
Title: Message Title Pawel Chudzik updated an issue Jenkins / JENKINS-40092 can not copy slave.jar after upgrade from 2.31 to 2.34 Change By: Pawel Chudzik Attachment: jenkins-slave.log Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39134) Pipeline fails after restart caused by Just-in-time binding
Title: Message Title Erwin Oldenkamp commented on JENKINS-39134 Re: Pipeline fails after restart caused by Just-in-time binding Can confirm, Downgrading makes it work again. Thank for the "workaround" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40094) Global config.xml only contains a exception
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-40094 Global config.xml only contains a exception Issue Type: Bug Assignee: Antonio Muñiz Components: support-core-plugin Created: 2016/Nov/29 12:26 PM Priority: Major Reporter: Antonio Muñiz --- WARNING: Could not attach /home/support/hudson_home/support/patched100416060363402908.xml as it cannot currently be found --- java.io.FileNotFoundException: /home/support/hudson_home/support/patched100416060363402908.xml (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at hudson.util.IOUtils.copy(IOUtils.java:29) at com.cloudbees.jenkins.support.api.FileContent.writeTo(FileContent.java:63) The generated file is being removed before it is actually added to the bundle. Add Comment
[JIRA] (JENKINS-40094) Global config.xml only contains a exception
Title: Message Title Antonio Muñiz started work on JENKINS-40094 Change By: Antonio Muñiz 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-40095) Enable variable substitution for plugin configuration values
Title: Message Title
Caroline Striessnig created an issue
Jenkins / JENKINS-40095
Enable variable substitution for plugin configuration values
Issue Type:
New Feature
Assignee:
Unassigned
Components:
logstash-plugin
Created:
2016/Nov/29 12:28 PM
Priority:
Minor
Reporter:
Caroline Striessnig
Currently it is not possible to use environment variables for the logstash-plugin configuration. The plugin does not substitute environment variables like $ {var} , $var. It looks like it is a matter of using the "expand(String)" functionality. http://javadoc.jenkins-ci.org/hudson/EnvVars.html#expand(java.lang.String) It would be a useful feature to be able to use environment variables within the plugin configuration.
Add Comment
[JIRA] (JENKINS-40079) Empty credentials list
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-40079 Empty credentials list Change By: Stephen Connolly Component/s: credentials-binding-plugin Component/s: credentials-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-40096) Stage View is missing after Plugin update
Title: Message Title
Sebastian Peters created an issue
Jenkins / JENKINS-40096
Stage View is missing after Plugin update
Issue Type:
Bug
Assignee:
Sam Van Oort
Attachments:
jenkinspipelinenostageview.png
Components:
pipeline-stage-step-plugin, pipeline-stage-view-plugin
Created:
2016/Nov/29 12:35 PM
Environment:
Jenkins 2.9, Jenkins 2.10 Pipeline: Stage Step (pipeline-stage-step): 2.2 Pipeline: Stage View Plugin (pipeline-stage-view): 2.2
Labels:
plugin jenkins stage view pipeline
Priority:
Minor
Reporter:
Sebastian Peters
We're running two legacy Jenkins servers, one running the old 2.9, the other the slightly newer 2.10 version. Due to plugin version mismatches, the stage step plugin on one server would constantly nag that we don't use
stage('Stage 1'){ }
arguments with a block. To get rid of that, we've updated both the Stage Step and Stage View plugin to 2.2 on both Jenkins servers. But now an even worse problem occurred, our pipeline stage view is simply invisible (see attachment). Were there any other plugins we needed to update? Too many projects de
[JIRA] (JENKINS-40079) Empty credentials list
Title: Message Title Stephen Connolly commented on JENKINS-40079 Re: Empty credentials list Secret file and Secret text credential types are not supported by the git plugin (nor should they be IMHO) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40079) Empty credentials list
Title: Message Title Stephen Connolly assigned an issue to Mark Waite Jenkins / JENKINS-40079 Empty credentials list Change By: Stephen Connolly Assignee: Stephen Connolly 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-40079) Empty credentials list
Title: Message Title Stephen Connolly resolved as Not A Defect Unless Mark Waite disagrees with me, this is not a defect. Username/Password and SSH keys are the only credential types supported by Git. Jenkins / JENKINS-40079 Empty credentials list Change By: Stephen Connolly Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubsc
[JIRA] (JENKINS-40079) Empty credentials list
Title: Message Title Stephen Connolly edited a comment on JENKINS-40079 Re: Empty credentials list Unless [~markewaite] disagrees with me, this is not a defect. Username/Password and SSH keys (plus perhaps under certain rare exotic situations TLS client certificates) are the only credential types supported by Git. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40097) Build Executor Status is not aligned with long names
Title: Message Title Bell L created an issue Jenkins / JENKINS-40097 Build Executor Status is not aligned with long names Issue Type: Improvement Assignee: Oleg Nenashev Attachments: bug_jenkins_ui2.JPG Components: _unsorted Created: 2016/Nov/29 12:55 PM Environment: Version 1.651.2 Browser: Chrome Priority: Minor Reporter: Bell L Build Executor Status field is going out of boundaries with long names. The "x" for aborting a job is un-clickable and is overlapping with the job's fields. It's not size (zoom) dependable - exist in each scale. Add Comment
[JIRA] (JENKINS-27911) Install unlimited strength JCE policy files together with JDK (optionally & automatically)
Title: Message Title Klaus Wienert commented on JENKINS-27911 Re: Install unlimited strength JCE policy files together with JDK (optionally & automatically) +1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39015) Support hudson.model.UnprotectedRootAction
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39015 Re: Support hudson.model.UnprotectedRootAction Code changed in jenkins User: Allan Burdajewicz Path: src/main/java/com/sonymobile/jenkins/plugins/kerberossso/KerberosSSOFilter.java src/test/java/com/sonymobile/jenkins/plugins/kerberossso/KerberosFilterTest.java http://jenkins-ci.org/commit/kerberos-sso-plugin/3a1fb355fbac4e60ba1a502b4eb3bc95423c4f58 Log: JENKINS-39015 - Skip authentication for unprotected root actions. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39015) Support hudson.model.UnprotectedRootAction
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39015 Re: Support hudson.model.UnprotectedRootAction Code changed in jenkins User: Oliver Gondža Path: src/main/java/com/sonymobile/jenkins/plugins/kerberossso/KerberosSSOFilter.java src/test/java/com/sonymobile/jenkins/plugins/kerberossso/KerberosFilterTest.java http://jenkins-ci.org/commit/kerberos-sso-plugin/fe5f094f44a1d4faca7a5095f29d0d8c91f6a68a Log: Merge pull request #9 from Dohbedoh/JENKINS-39015 JENKINS-39015 - Skip authentication for unprotected root actions. Compare: https://github.com/jenkinsci/kerberos-sso-plugin/compare/29a99de3c59b...fe5f094f44a1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39894) REGRESSION: SSE broken on MS Edge and IE11
Title: Message Title Tom FENNELLY commented on JENKINS-39894 Re: REGRESSION: SSE broken on MS Edge and IE11 I'll have a look at this as soon as I can, but in the meantime it'd be useful if Jim Klimov could turn on SSE logging in the browser and see if anything is logged in the browser console. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29519) Capability to trigger m2 release plugin from API or command line
Title: Message Title Tom Esh commented on JENKINS-29519 Re: Capability to trigger m2 release plugin from API or command line I would like to see a command line interface to trigger a "maven release build" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29519) Capability to trigger m2 release plugin from API or command line
Title: Message Title Tom Esh edited a comment on JENKINS-29519 Re: Capability to trigger m2 release plugin from API or command line I would like to see a command line interface to trigger a " perform maven release build " Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40037) Docker builds fail with "Build info capturing failed for docker image..." exception
Title: Message Title Roman Gurevitch commented on JENKINS-40037 Re: Docker builds fail with "Build info capturing failed for docker image..." exception Thank you for your comments, we will try to improve the documentation so the setup would be easier. Regarding your comments: You probably had to change permissions to /var/run/docker.sock because of your Jenkins/Docker setup, regularly Jenkins have permissions to access it but because Jenkins runs on Docker container you had to change permissions. Build info is captured via the proxy, so each node has to pass through it. We found an interesting article describing how to configure proxy for Docker swarm: https://technologyconversations.com/2016/08/01/integrating-proxy-with-docker-swarm-tour-around-docker-1-12-series/ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Dirk Kuypers commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Oleg, I am still seeing these issues with 2.34: FATAL: java.util.concurrent.ExecutionException: Invalid object ID 811 iota=812 hudson.remoting.RemotingSystemException: java.util.concurrent.ExecutionException: Invalid object ID 811 iota=812 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:272) at com.sun.proxy.$Proxy85.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1009) at hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:143) at hudson.plugins.clearcase.ClearToolExec.describe(ClearToolExec.java:126) at hudson.plugins.clearcase.base.BaseHistoryAction.parseUpdt(BaseHistoryAction.java:137) at hudson.plugins.clearcase.base.BaseHistoryAction.runLsHistory(BaseHistoryAction.java:156) at hudson.plugins.clearcase.history.AbstractHistoryAction.runAndFilterLsHistory(AbstractHistoryAction.java:259) at hudson.plugins.clearcase.history.AbstractHistoryAction.getChanges(AbstractHistoryAction.java:81) at hudson.plugins.clearcase.AbstractClearCaseScm.saveChangeLog(AbstractClearCaseScm.java:1106) at hudson.plugins.clearcase.AbstractClearCaseScm.checkout(AbstractClearCaseScm.java:395) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Caused by: java.util.concurrent.ExecutionException: Invalid object ID 811 iota=812 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:408) at hudson.remoting.ExportTable.get(ExportTable.java:333) at hudson.remoting.Channel.getExportedObject(Channel.java:660) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:885) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:869) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:94) at java.lang.Thread.run(Unknown Source) at ..remote call to Channel to /10.0.50.50(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:822) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256) ... 18 more Caused by: java.lang.Exception: Object was recently deallocated #811 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Mon Nov 28 20:32:47 CET 2016 at hudson.remoting.ExportTable$Entry.(ExportTable.java:102) at hudson.remoting.ExportTable.export(ExportTable.java:308) at hudson.remoting.Channel.internalExport(Channel.java:656) at hudson.
[JIRA] (JENKINS-40098) The support bundle naming strategy should be modifiable
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-40098 The support bundle naming strategy should be modifiable Issue Type: Improvement Assignee: Baptiste Mathus Components: support-core-plugin Created: 2016/Nov/29 1:17 PM Priority: Minor Reporter: Baptiste Mathus When one has to handle a lot of support bundles coming from different servers, it can make sense to be able to override the default prefix support (see related code). So I think the existing code should be refactored to accept using something like a pluggable strategy. Add Comment
[JIRA] (JENKINS-40057) Stage view is completely missing for long durations after restarts
Title: Message Title Nash Paz updated an issue Jenkins / JENKINS-40057 Stage view is completely missing for long durations after restarts Change By: Nash Paz Attachment: java_err.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-40045) Support for secret key credentials in Git Plugin
Title: Message Title Mark Waite resolved as Duplicate Jenkins / JENKINS-40045 Support for secret key credentials in Git Plugin Change By: Mark Waite 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-40057) Stage view is completely missing for long durations after restarts
Title: Message Title Nash Paz commented on JENKINS-40057 Re: Stage view is completely missing for long durations after restarts java_err.txt Ok, there was an error when inspecting the blank Full stage view in Chrome: http://build01:8080/job/stability_post_nightly1/wfapi/runs?fullStages=true&_=1480420606537 Failed to load resource: the server responded with a status of 500 (Server Error) please see the attached for a full error log. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40099) Job creation takes awhile
Title: Message Title Paul Draper created an issue Jenkins / JENKINS-40099 Job creation takes awhile Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2016/Nov/29 1:23 PM Priority: Minor Reporter: Paul Draper Creating a lot of jobs (say a several dozen) takes a significant amount of time. Logs show that after groovy dsl script finishes, each job takes a second or two. INFO: createOrUpdateConfig for main/paul-build2/validation-test Nov 29, 2016 1:16:45 PM javaposse.jobdsl.plugin.JenkinsJobManagement createOrUpdateConfig Is there anyway to make this faster? Add Comment
[JIRA] (JENKINS-37459) Unresolvable nodeJS installer for WINDOWS with amd64 cpu
Title: Message Title Nikolas Falco closed an issue as Fixed Jenkins / JENKINS-37459 Unresolvable nodeJS installer for WINDOWS with amd64 cpu Change By: Nikolas Falco Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40057) Stage view is completely missing for long durations after restarts
Title: Message Title Nash Paz edited a comment on JENKINS-40057 Re: Stage view is completely missing for long durations after restarts * Chrome, Internet explorer, will try firefox today for the heck of it.* Will try to check tonight, it's a messy jenkins so we have plenty of errors from way before I installed the pipeline plugins. Any particular errors I ought to be looking for?* - No browser errors I can think of - . FYI, stage view frontend is missing when viewing from other comps, as well.* Pipeline rest-api is installed, seems fine in the 'installed' tab under plugins. How do I go about checking that it's working?Thanks a million for your time (y) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Oleg Nenashev reopened an issue Yes, it is the same issue, but with another code. Likely we need a better solution Jenkins / JENKINS-23271 Intermittent Invalid Object ID in remoting module Change By: Oleg Nenashev Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, vis
[JIRA] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Dirk Kuypers commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Could I help out with something where more logging is enabled? I have about 10 of these SonarQube Jobs running every night and at least one of them fails almost every night. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40002) Add description to POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40002 Re: Add description to POM Code changed in jenkins User: Evaristo Gutiérrez Path: pom.xml http://jenkins-ci.org/commit/ant-plugin/087faf3e3ece679d98aa04834dcbc1a739ab0ea4 Log: JENKINS-40002 Add plugin description to POM. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40002) Add description to POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40002 Re: Add description to POM Code changed in jenkins User: Armando Fernández Path: pom.xml http://jenkins-ci.org/commit/ant-plugin/e9815c32a8839c1c3713d18f0577e86bd655d9e1 Log: Merge pull request #24 from varyvol/JENKINS-40002 JENKINS-40002 Add plugin description to POM. Compare: https://github.com/jenkinsci/ant-plugin/compare/0a0a32abe1e1...e9815c32a883 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40002) Add description to POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40002 Re: Add description to POM Code changed in jenkins User: Evaristo Gutiérrez Path: pom.xml http://jenkins-ci.org/commit/ant-plugin/6aff9908ba9271db04445d2199d522b0287a9094 Log: JENKINS-40002 Remove final dot. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35983) Add support to job import jobs in folders
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35983 Re: Add support to job import jobs in folders Code changed in jenkins User: Owen Wood Path: pom.xml src/main/java/org/jenkins/ci/plugins/jobimport/CredentialsUtils.java src/main/java/org/jenkins/ci/plugins/jobimport/JobImportAction.java src/main/java/org/jenkins/ci/plugins/jobimport/RemoteJob.java src/main/java/org/jenkins/ci/plugins/jobimport/RemoteJobUtils.java src/test/java/org/jenkins/ci/plugins/jobimport/JobImportActionTest.java src/test/java/org/jenkins/ci/plugins/jobimport/JobImportClient.java src/test/java/org/jenkins/ci/plugins/jobimport/RemoteJenkins.java src/test/resources/README.md src/test/resources/folder/config.xml src/test/resources/folder/jobs/aFolder/config.xml src/test/resources/folder/jobs/aFolder/jobs/bFreestyleJobInFolder/config.xml src/test/resources/folder/jobs/aFolder/jobs/bMavenJobInFolder/config.xml src/test/resources/folder/jobs/aFolder/xml-api-response.xml src/test/resources/folder/jobs/aFreestyleJobInFolder/config.xml src/test/resources/folder/jobs/aMavenJobInFolder/config.xml src/test/resources/folder/xml-api-response.xml src/test/resources/job/config.xml src/test/resources/xml-api-response.xml http://jenkins-ci.org/commit/job-import-plugin/d33a547d37ec8adbfd5d8023c2248a64cff52614 Log: JENKINS-35983 - Add support to job import jobs in folders Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.co
[JIRA] (JENKINS-35983) Add support to job import jobs in folders
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35983 Re: Add support to job import jobs in folders Code changed in jenkins User: Emilio Escobar Path: pom.xml src/main/java/org/jenkins/ci/plugins/jobimport/CredentialsUtils.java src/main/java/org/jenkins/ci/plugins/jobimport/JobImportAction.java src/main/java/org/jenkins/ci/plugins/jobimport/RemoteJob.java src/main/java/org/jenkins/ci/plugins/jobimport/RemoteJobUtils.java src/test/java/org/jenkins/ci/plugins/jobimport/JobImportActionTest.java src/test/java/org/jenkins/ci/plugins/jobimport/JobImportClient.java src/test/java/org/jenkins/ci/plugins/jobimport/RemoteJenkins.java src/test/resources/README.md src/test/resources/folder/config.xml src/test/resources/folder/jobs/aFolder/config.xml src/test/resources/folder/jobs/aFolder/jobs/bFreestyleJobInFolder/config.xml src/test/resources/folder/jobs/aFolder/jobs/bMavenJobInFolder/config.xml src/test/resources/folder/jobs/aFolder/xml-api-response.xml src/test/resources/folder/jobs/aFreestyleJobInFolder/config.xml src/test/resources/folder/jobs/aMavenJobInFolder/config.xml src/test/resources/folder/xml-api-response.xml src/test/resources/job/config.xml src/test/resources/xml-api-response.xml http://jenkins-ci.org/commit/job-import-plugin/594157a0404b25a87ace3f50c400559fa354e0c0 Log: JENKINS-35983 merged changes from Evildethow PR Compare: https://github.com/jenkinsci/job-import-plugin/compare/d33a547d37ec^...594157a0404b Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-40100) Credentials config not initialized properly.
Title: Message Title Peter Grape created an issue Jenkins / JENKINS-40100 Credentials config not initialized properly. Issue Type: Bug Assignee: Unassigned Components: crx-content-package-deployer-plugin Created: 2016/Nov/29 2:22 PM Environment: Jenkins version 2.7.3, CRX plugin 1.6.2, Credentials Plugin version 2.10 Priority: Major Reporter: Peter Grape The credential plugin config is not initialized properly. Caused by: java.lang.AssertionError: Credentials were not resolved at org.jenkinsci.plugins.graniteclient.GraniteClientConfig.getCredentials(GraniteClientConfig.java:146) at org.jenkinsci.plugins.graniteclient.GraniteClientExecutor.execute(GraniteClientExecutor.java:87) at org.jenkinsci.plugins.graniteclient.GraniteClientExecutor.execute(GraniteClientExecutor.java:69) at org.jenkinsci.plugins.graniteclient.PackageChoiceParameterDefinition.getPackageList(PackageChoiceParameterDefinition.java:134) ... 164 more Add Comment
[JIRA] (JENKINS-40071) Problème intégration JENKINS et ALM 12.21 (upload test result to ALM)
Title: Message Title Roy Lu commented on JENKINS-40071 Re: Problème intégration JENKINS et ALM 12.21 (upload test result to ALM) Have you ever ran the upload step successfully? Or is it the first time you use this step? I want to see how you configure the upload step. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40100) Credentials config not initialized properly.
Title: Message Title Peter Grape updated an issue Jenkins / JENKINS-40100 Credentials config not initialized properly. Change By: Peter Grape The credential plugin config is not initialized properly. I found that the code:"resolveCredentials();"need to be executed in the code in order for the credentials to load properly.I do not have enough knowledge abt your plugin to know exactly where to insert it, but I added the above line to the getCredentials method in the GraniteClientConfig.java file and it works fine for now.Error Stacktrace: Caused by: java.lang.AssertionError: Credentials were not resolvedat org.jenkinsci.plugins.graniteclient.GraniteClientConfig.getCredentials(GraniteClientConfig.java:146)at org.jenkinsci.plugins.graniteclient.GraniteClientExecutor.execute(GraniteClientExecutor.java:87)at org.jenkinsci.plugins.graniteclient.GraniteClientExecutor.execute(GraniteClientExecutor.java:69)at org.jenkinsci.plugins.graniteclient.PackageChoiceParameterDefinition.getPackageList(PackageChoiceParameterDefinition.java:134)... 164 more Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39819) WAR shasum file name is not correct always
Title: Message Title Armando Fernandez started work on JENKINS-39819 Change By: Armando Fernandez Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39819) WAR shasum file name is not correct always
Title: Message Title Armando Fernandez reopened an issue Reopened as I missed the file extension when generating the war shasum file. This PR should fix it. Jenkins / JENKINS-39819 WAR shasum file name is not correct always Change By: Armando Fernandez Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title Jeroen Bogers commented on JENKINS-37584 Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline) We just tried using the environment variables, but found that if you do multiple checkouts in a single pipeline, the env is locked to the first checkout. Or, to be more precise, if you set any of the P4_* environment variables to any arbitrary value the variable is no longer updated by any future p4 actions. For example, if you do: env.P4_CHANGELIST="myOwnValue" checkout scm: [$class: 'PerforceScm', credential: 'XXX', populate: ... (etc, etc) echo env.P4_CHANGELIST You will see that the output shows 'myOwnValue' and not a changelist number as expected. This prevents creating a pipeline that does actions on multiple depots in our 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-34922) NullPointerException Creating and Resolving Issues
Title: Message Title Brendan Arthurs commented on JENKINS-34922 Re: NullPointerException Creating and Resolving Issues I've opened a pull request to resolve this issue - https://github.com/jenkinsci/pagerduty-plugin/pull/2 Waiting on a committer to review / merge Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40098) The support bundle naming strategy should be modifiable
Title: Message Title Jesse Glick started work on JENKINS-40098 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-40098) The support bundle naming strategy should be modifiable
Title: Message Title Jesse Glick updated JENKINS-40098 Jenkins / JENKINS-40098 The support bundle naming strategy should be modifiable 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-40098) The support bundle naming strategy should be modifiable
Title: Message Title Jesse Glick commented on JENKINS-40098 Re: The support bundle naming strategy should be modifiable Please remember to link from PR to JIRA and back, and set the status. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Oleg Nenashev commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Dirk Kuypers Give me several hours. I will create a pull request with a wider solution. Then you will be able to take a PoC from the CI just to verify if it helps Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40037) Docker builds fail with "Build info capturing failed for docker image..." exception
Title: Message Title Ali Sadik Kumlali commented on JENKINS-40037 Re: Docker builds fail with "Build info capturing failed for docker image..." exception Thank you very much for your valuable comments. I am going to add chmod 777 /var/run/docker.sock to docker service's configuration. I do not know what happened but telnet localhost works on every swarm mode although Jenkins service runs on only one node. It seems swarm's internal load balancer directs the traffic successfully. Thus, following comment is not valid anymore: When Jenkins container is running on a swarm cluster docker pull artifactory.mycompany.com/hello-world succeeds only on the machine Jenkins container runs because we use localhost in HTTP_PROXY url. Using dedicated host for Jenkins container and setting HTTP_PROXY=http://: in http-proxy.conf on each swarm host do not seem to be a good solution... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.goog
[JIRA] (JENKINS-38867) Major Optimization: Create and Use FlowNode.getAction w/o TransientActionFactories
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38867 Re: Major Optimization: Create and Use FlowNode.getAction w/o TransientActionFactories Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/model/TransientActionFactory.java http://jenkins-ci.org/commit/jenkins/9ecc77b9badd65d9eabd34d2baad1742d5566894 Log: JENKINS-38867 Since tag for #2582. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title Morne Joubert commented on JENKINS-37584 Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline) Jeroen, does this also happen if you do echo currentBuild.getRawBuild().getEnvironment()["P4_CHANGELIST"] ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39894) REGRESSION: SSE broken on MS Edge and IE11
Title: Message Title Jim Klimov commented on JENKINS-39894 Re: REGRESSION: SSE broken on MS Edge and IE11 I hope I got it right, at least it warned that I had Compatibility View settings clicked on for the Intranet site (that the local VM was considered as). Un-clicking the setting did not change behavior noticeably - at least, any considerable changes are visible only after a refresh (e.g. redding-out of an aborted task, scrolling through stages - otherwise it stays on "Waiting for run to start" for minutes at least). The list of numbered job runs is full this time though, including the currently running job... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title
Jeroen Bogers commented on JENKINS-37584
Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Morne Joubert, it happens there too. What I ran to test it (anonymized and abbreviated):
node {
echo "currentBuild P4_CHANGELIST: " + currentBuild.getRawBuild().getEnvironment()["P4_CHANGELIST"]
checkout poll: false, scm: [$class: 'PerforceScm', credential: '123XYZ', populate: [...], workspace: [...]
echo "currentBuild P4_CHANGELIST: " + currentBuild.getRawBuild().getEnvironment()["P4_CHANGELIST"]
}
node {
echo "currentBuild P4_CHANGELIST: " + currentBuild.getRawBuild().getEnvironment()["P4_CHANGELIST"]
checkout poll: false, scm: [$class: 'PerforceScm', credential: '123XYZ', populate: [...], workspace: [...]
echo "currentBuild P4_CHANGELIST: " + currentBuild.getRawBuild().getEnvironment()["P4_CHANGELIST"]
}
In the example above I use two different workspaces (on different depots, but the same perforce server). The relevant output I see is:
currentBuild P4_CHANGELIST: null
...
P4 Task: syncing files at change: 2498817
...
currentBuild P4_CHANGELIST: 2498817
currentBuild P4_CHANGELIST: 2498817
...
P4 Task: syncing files at change: 2465266
...
currentBuild P4_CHANGELIST: 2498817
So even for that access method, the environment is locked to the first value is 'sees'.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-26828) Add support for installing the NodeJS windows msi
Title: Message Title Nikolas Falco started work on JENKINS-26828 Change By: Nikolas Falco 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-26828) Add support for installing the NodeJS windows msi
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-26828 Add support for installing the NodeJS windows msi Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title
Jeroen Bogers edited a comment on JENKINS-37584
Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
[~mornejoubert], it happens there too.What I ran to test it (anonymized and abbreviated):{noformat}node {echo "currentBuild P4_CHANGELIST: " + currentBuild.getRawBuild().getEnvironment()["P4_CHANGELIST"]checkout poll: false, scm: [$class: 'PerforceScm', credential: '123XYZ', populate: [...], workspace: [...]echo "currentBuild P4_CHANGELIST: " + currentBuild.getRawBuild().getEnvironment()["P4_CHANGELIST"]}node {echo "currentBuild P4_CHANGELIST: " + currentBuild.getRawBuild().getEnvironment()["P4_CHANGELIST"]checkout poll: false, scm: [$class: 'PerforceScm', credential: '123XYZ', populate: [...], workspace: [...]echo "currentBuild P4_CHANGELIST: " + currentBuild.getRawBuild().getEnvironment()["P4_CHANGELIST"]}{noformat}In the example above I use two different workspaces (on different depots, but the same perforce server).The relevant output I see is:{noformat}currentBuild P4_CHANGELIST: null...P4 Task: syncing files at change: 2498817...currentBuild P4_CHANGELIST: 2498817currentBuild P4_CHANGELIST: 2498817...P4 Task: syncing files at change: 2465266...currentBuild P4_CHANGELIST: 2498817{noformat}So even for that access method, the environment is locked to the first value is it 'sees'.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-26828) Add support for installing the NodeJS windows msi
Title: Message Title Nikolas Falco commented on JENKINS-26828 Re: Add support for installing the NodeJS windows msi I've try the PR and does not work. Should be fixed the URL construction Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38089) Unexpected Exception during accessing json pipeline status
Title: Message Title Jesse Glick updated JENKINS-38089 Jenkins / JENKINS-38089 Unexpected Exception during accessing json pipeline status 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-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title
Morne Joubert commented on JENKINS-37584
Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
I "think" I can see the problem. The extention that Paul added to set the env has
@Override
public void buildEnvironmentFor(Run run, EnvVars env, TaskListener listener) throws IOException, InterruptedException {
TagAction tagAction = run.getAction(TagAction.class);
if(tagAction == null) {
return;
}
// Set P4_CHANGELIST value
if (tagAction.getBuildChange() != null) {
String change = tagAction.getBuildChange().toString();
env.put("P4_CHANGELIST", change);
}
From http://javadoc.jenkins-ci.org/hudson/model/Actionable.html#getAction(java.lang.Class) public T getAction(Class type) Gets the action first instance to be found of a specified type that contributed to this build. So my guess is that the code get the first P4Action every time, and I think we want the last ? There is an API to pull all Actions of a particular type
public extends Action> List getActions(Class type)
I would suggest we try that and see if it works if we used the last one in the list.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39819) WAR shasum file name is not correct always
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39819 Re: WAR shasum file name is not correct always Code changed in jenkins User: Armando Fernandez Path: Makefile setup.mk http://jenkins-ci.org/commit/packaging/03c4cd2fe531b810cbf6c220e99653d79248596d Log: JENKINS-39819 Missed extension for WAR shasum file Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39819) WAR shasum file name is not correct always
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39819 Re: WAR shasum file name is not correct always Code changed in jenkins User: R. Tyler Croy Path: Makefile setup.mk http://jenkins-ci.org/commit/packaging/f25a3f6ff7528c6b81d98ff29884eaf4d70fee12 Log: Merge pull request #85 from armfergom/JENKINS-39819-fix JENKINS-39819 Missed extension for WAR shasum file Compare: https://github.com/jenkinsci/packaging/compare/b9f207f9a6c0...f25a3f6ff752 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26099) Configurable ID for Credentials
Title: Message Title Jesse Glick commented on JENKINS-26099 Re: Configurable ID for Credentials Anudeep Lalam the ID can only be customized on new credentials. Once created it is immutable. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39134) Pipeline fails after restart caused by Just-in-time binding
Title: Message Title Jesse Glick commented on JENKINS-39134 Re: Pipeline fails after restart caused by Just-in-time binding Seems implausible that these changes could have triggered such a bug; maybe just tickled something else. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39819) WAR shasum file name is not correct always
Title: Message Title Armando Fernandez resolved as Fixed Jenkins / JENKINS-39819 WAR shasum file name is not correct always Change By: Armando Fernandez Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title Paul Allen commented on JENKINS-37584 Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline) Yes I think that is the issue, another user spotted the use of getAction vs getActions it in a different area: https://github.com/jenkinsci/p4-plugin/pull/32 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title Paul Allen edited a comment on JENKINS-37584 Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline) Yes I think that is the issue, another user spotted the use of getAction vs getActions it in a different area:https://github.com/jenkinsci/p4-plugin/pull/32 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39166) Subversion Plugin ChangeLog Missing for Version 2.7.1
Title: Message Title Michael Paesold commented on JENKINS-39166 Re: Subversion Plugin ChangeLog Missing for Version 2.7.1 True. Does anyone know: should this be auto-generated or is this usually manually done by the maintainer? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
