[JIRA] [workflow-plugin] (JENKINS-31425) should be able to specify multiple users or groups for the submitter of an input step
Title: Message Title Sam Gleske edited a comment on JENKINS-31425 Re: should be able to specify multiple users or groups for the submitter of an input step I have mispoken. I appear to have likely run up against a bug in the GitHub OAuth plugin and the behavior I was talking about is not directly related to multiple users or groups in this issue. However, this would be a killer feature for us :). I apologize if there's been any ruffled feathers due to my comments. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31425) should be able to specify multiple users or groups for the submitter of an input step
Title: Message Title Sam Gleske commented on JENKINS-31425 Re: should be able to specify multiple users or groups for the submitter of an input step I have mispoken. I appear to have likely run up against a bug in the GitHub OAuth plugin and the behavior I talking about is not directly related to multiple users or groups in this issue. However, this would be a killer feature for us . I apologize if there's been any ruffled feathers due to my comments. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vmware-vrealize-orchestrator-plugin] (JENKINS-34178) There *may* be a problem with the vm@VC:VirtualMachine parameter name.
Title: Message Title Agila Govindaraju commented on JENKINS-34178 Re: There *may* be a problem with the vm@VC:VirtualMachine parameter name. This worked for me. Can you please try. I am really sorry that I am asking you to try a lot of options. 'connectionURL%252Fvmmoref %252F is nothing but / So for ex: test.eng.abc.com/vm-99 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves-plugin] (JENKINS-7641) Slaves hang when archiving artifacts
Title: Message Title Nicholas Klopfer-Webber commented on JENKINS-7641 Re: Slaves hang when archiving artifacts We have just started experiencing the same problem, and its killing our build farm. Its happening across platforms as mentioned before and does not seem specific to how the connection is launched. Both ssh from the master or webstart from a slave have the same problem. Some information that might help. We don't always have artifacts, they are only present if tests fail and leave behind what they expected to be created which we can manually inspect later. Could it be because it didn't find anything? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34827) Jenkins 1.596.2 crashes JVM on running build (triggerd by gerrit comment)
Title: Message Title Lee Dongik updated an issue Jenkins / JENKINS-34827 Jenkins 1.596.2 crashes JVM on running build (triggerd by gerrit comment) Change By: Lee Dongik Summary: Jnkeins Jenkins 1.596.2 crashes JVM on running build (triggerd by gerrit comment) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-ext-plugin] (JENKINS-33856) jira-ext-plugin fails to parse commit message for JIRA ticket in certain patterns
Title: Message Title Sergey Leonovich commented on JENKINS-33856 Re: jira-ext-plugin fails to parse commit message for JIRA ticket in certain patterns I am sorry I cannot share the script. It was written in Python ising jira module. Look here for more details: http://jira.readthedocs.io/en/latest/ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [publish-over-ssh-plugin] (JENKINS-27963) Please add support for jenkins pipeline plugin to publish-over-ssh
Title: Message Title Ashudeep Budhiraja commented on JENKINS-27963 Re: Please add support for jenkins pipeline plugin to publish-over-ssh Thanks Peter. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31425) should be able to specify multiple users or groups for the submitter of an input step
Title: Message Title Sam Gleske edited a comment on JENKINS-31425 Re: should be able to specify multiple users or groups for the submitter of an input step That requires a passphrase to deploy if I understand correctly.I'd rather have groups support prioritized. Pipelines can't be considered enterprise ready in any capacity in my opinion without this. To assume, "dev's can't create AD groups" is a naive and bad assumption to have. We're using GitHub OAuth and Dev's manage their own groups in a fully self service manner. I'll reach out to my support rep for and try to get this because this is essentially such a big blocker I would consider shunning Jenkins if I knew about it before getting enterprise support on the roadmap sooner . To all who read this be aware. I appreciate the workaround but I think this requires a bit more finesse. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31425) should be able to specify multiple users or groups for the submitter of an input step
Title: Message Title Sam Gleske edited a comment on JENKINS-31425 Re: should be able to specify multiple users or groups for the submitter of an input step That requires a passphrase to deploy if I understand correctly.I'd rather have groups support prioritized. Pipelines can't be considered enterprise ready in any capacity in my opinion without this. To assume, "dev's can't create AD groups" is a naive and bad assumption to have. We're using GitHub OAuth and Dev's manage their own groups in a fully self service manner. I'll reach out to my support rep for this because this is essentially such a big blocker I would consider shunning Jenkins if I knew about it before getting enterprise support.To all who read this be aware. I appreciate the workaround but I think this requires a bit more finesse. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31425) should be able to specify multiple users or groups for the submitter of an input step
Title: Message Title Sam Gleske commented on JENKINS-31425 Re: should be able to specify multiple users or groups for the submitter of an input step That requires a passphrase to deploy if I understand correctly. I'd rather have groups support prioritized. Pipelines can't be considered enterprise ready in any capacity in my opinion without this. To assume, "dev's can't create AD groups" is a naive and bad assumption to have. We're using GitHub OAuth and Dev's manage their own groups in a fully self service manner. I'll reach out to my support rep for this because this is essentially such a big blocker I would consider shunning Jenkins if I knew about it before getting enterprise support. To all who read this be aware. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title Sam Gleske commented on JENKINS-25791 Re: User.impersonate throws ClassCastException when using GitHub auth This is going to require someone to patch who is more expert than I at development. To date I've mostly just merged other people's pull requests and made releases (though I have made minor improvements here and there). Hopefully, someone is willing to step up and contribute a fix. I'll work on it when I can but I imagine it will take a huge time investment from me (more than I have). Though, if a fix is proposed I have no problem reviewing it, merging, and releasing. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31425) should be able to specify multiple users or groups for the submitter of an input step
Title: Message Title
James Nord commented on JENKINS-31425
Re: should be able to specify multiple users or groups for the submitter of an input step
there is a hacky workaround
create a credential in the same folder as the job - with some magic value... in the workflow read that magic value. in the workflow have the input ask for the magic value. whilst it is not the same loop. if it is the same it is approved. only give the magic value to people that are "approvers"
def magicValue
node {
withCredentials([[$class: 'StringBinding', credentialsId: 'production_magic', variable: 'tmpMagicValue']]) {
magicValue = env.tmpMagicValue
}
}
// send some email notification
while (true) {
def pass = input id: 'ApproveIt', message: 'Please enter the magic value to approve the build', parameters: [[$class: 'com.michelin.cio.hudson.plugins.passwordparam.PasswordParameterDefinition', defaultValue: 'bogus', description: 'The magic token to show you have rights to push to production', name: 'authentication token']]
if (magicValue != pass) {
echo "incorrect value entered"
}
else {
echo "Push to production approved by magic"
break;
}
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34740) All XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 All XHR requests fail under certain conditions when an underscore is present in the hostname Change By: Roy Tinker When accessing via a hostname with an underscore, I'm seeing problems in several other places throughout Jenkins -- but the problems all disappear if I access via a hostname without an underscore (which I'm doing by adding an alternate name for the Jenkins server's IP address in my machine's hosts file) XHR requests fail . Here 's are a few I could compile in 10 minutes examples :* At /configureSecurity/: XHR calls to /descriptorByName/hudson.security.GlobalMatrixAuthorizationStrategy/checkName?value=%5Busername%5D return either 403 (if logged in) or 200 but blank response (if anonymous w/anonymous granted Administer)* At /configureSecurity/: clicking Save or Apply results in an error where an ActiveDirectorySecurityRealm failed to instantiate in org.kohsuke.stapler.Stapler.tryInvoke (Stapler.java:796)* At /configure: XHR call to /$stapler/bound/[a GUID]/render returns 404 Not Found* At /configure: all other XHR calls executed on load (/checkAdminAddress, checkDefaultSuffix, checkGitUrl, etc.) return 200 OK but have an empty response.This issue is present in 1.6, 2.2, and 2.3. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [core] (JENKINS-34740) Many XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 Many XHR requests fail under certain conditions when an underscore is present in the hostname Change By: Roy Tinker When accessing via a hostname with an underscore, many (or perhaps even all; I haven't enumerated) XHR requests fail -- either with a 403 unauthorized (when logged in) or with a 200 OK but blank response (if I log in as anonymous, with anonymous granted Administer privileges).Here are a few examples:* At /configureSecurity/: XHR calls to /descriptorByName/hudson.security.GlobalMatrixAuthorizationStrategy/checkName?value=%5Busername%5D return either 403 (if logged in) or 200 but blank response (if anonymous w/anonymous granted Administer)* At /configureSecurity/: clicking Save or Apply results in an error where an ActiveDirectorySecurityRealm failed to instantiate in org.kohsuke.stapler.Stapler.tryInvoke (Stapler.java:796)* At /configure: XHR call to /$stapler/bound/[a GUID]/render returns 404 Not Found* At /configure: all other XHR calls executed on load (/checkAdminAddress, checkDefaultSuffix, checkGitUrl, etc.) return 200 OK but have an empty response.This issue is has been tested and found present in 1.6, 2.2, and 2.3 (I haven't tested any other versions) .In 2.0+, this results in several major functionality blockers -- e.g. the New Item page is blank. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] [core] (JENKINS-34740) Many XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 Many XHR requests fail under certain conditions when an underscore is present in the hostname Change By: Roy Tinker Attachment: screenshot275124.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34740) All XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 All XHR requests fail under certain conditions when an underscore is present in the hostname Change By: Roy Tinker When accessing via a hostname with an underscore, all (or many) XHR requests fail -- either with a 403 unauthorized (when logged in) or with a 200 OK but blank response (if I log in as anonymous, with anonymous granted Administer privileges) . Here are a few examples:* At /configureSecurity/: XHR calls to /descriptorByName/hudson.security.GlobalMatrixAuthorizationStrategy/checkName?value=%5Busername%5D return either 403 (if logged in) or 200 but blank response (if anonymous w/anonymous granted Administer)* At /configureSecurity/: clicking Save or Apply results in an error where an ActiveDirectorySecurityRealm failed to instantiate in org.kohsuke.stapler.Stapler.tryInvoke (Stapler.java:796)* At /configure: XHR call to /$stapler/bound/[a GUID]/render returns 404 Not Found* At /configure: all other XHR calls executed on load (/checkAdminAddress, checkDefaultSuffix, checkGitUrl, etc.) return 200 OK but have an empty response.This issue is present in 1.6, 2.2, and 2.3. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34740) Many XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 Many XHR requests fail under certain conditions when an underscore is present in the hostname Change By: Roy Tinker When accessing via a hostname with an underscore, many (or perhaps even all; I haven't enumerated) XHR requests fail -- either with a 403 unauthorized (when logged in) or with a 200 OK but blank response (if I log in as anonymous, with anonymous granted Administer privileges).Here are a few examples:* At /configureSecurity/: XHR calls to /descriptorByName/hudson.security.GlobalMatrixAuthorizationStrategy/checkName?value=%5Busername%5D return either 403 (if logged in) or 200 but blank response (if anonymous w/anonymous granted Administer)* At /configureSecurity/: clicking Save or Apply results in an error where an ActiveDirectorySecurityRealm failed to instantiate in org.kohsuke.stapler.Stapler.tryInvoke (Stapler.java:796)* At /configure: XHR call to /$stapler/bound/[a GUID]/render returns 404 Not Found* At /configure: all other XHR calls executed on load (/checkAdminAddress, checkDefaultSuffix, checkGitUrl, etc.) return 200 OK but have an empty response.This issue is present in 1.6, 2.2, and 2.3. In 2.0+, this results in several major functionality blockers -- e.g. the New Item page is blank. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [core] (JENKINS-34740) Many XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 Many XHR requests fail under certain conditions when an underscore is present in the hostname Change By: Roy Tinker When accessing via a hostname with an underscore, all many (or many perhaps even all; I haven't enumerated ) XHR requests fail -- either with a 403 unauthorized (when logged in) or with a 200 OK but blank response (if I log in as anonymous, with anonymous granted Administer privileges).Here are a few examples:* At /configureSecurity/: XHR calls to /descriptorByName/hudson.security.GlobalMatrixAuthorizationStrategy/checkName?value=%5Busername%5D return either 403 (if logged in) or 200 but blank response (if anonymous w/anonymous granted Administer)* At /configureSecurity/: clicking Save or Apply results in an error where an ActiveDirectorySecurityRealm failed to instantiate in org.kohsuke.stapler.Stapler.tryInvoke (Stapler.java:796)* At /configure: XHR call to /$stapler/bound/[a GUID]/render returns 404 Not Found* At /configure: all other XHR calls executed on load (/checkAdminAddress, checkDefaultSuffix, checkGitUrl, etc.) return 200 OK but have an empty response.This issue is present in 1.6, 2.2, and 2.3. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34740) Many XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 Many XHR requests fail under certain conditions when an underscore is present in the hostname Change By: Roy Tinker Summary: All Many XHR requests fail under certain conditions when an underscore is present in the hostname Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34740) All XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
All XHR requests fail under certain conditions when an underscore is present in the hostname
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared.Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in When accessing via a blank page. No items show up.!screenshot275124.png|thumbnail!In the console hostname with an underscore , I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I 'm _not_ authenticated as anonymous (even though the X seeing problems in several other places throughout Jenkins - You - Are-Authenticated-As header says so) -- see but the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} (so it's not equal to the true suborigin) -- which may be the trigger that is causing the problem.Changes that fix the problem:- Reverting to Jenkins 1.6- Using problems all disappear if I access via a hostname without an underscore , Changes that do not fix the problem:- Switching to HTTP ( i.e. using httpPort=80 and eliminating httpsPort=443)JENKINS-34648 doesn't describe the issue which I'm having. I suspect my issue may be another problem caused doing by adding an alternate name for the same commit - that Jenkins server 's why I named the external-monitor-job-plugin IP address in the components list my machine's hosts file) . Here's a few I could compile in 10 minutes: Note * At /configureSecurity/ : RFC 952 restricts hostnames XHR calls to letters, hyphens, and numerals /descriptorByName/hudson . However, later I18n-oriented standards allow encoding other characters in hostnames security . In practice, there are a lot of hostnames GlobalMatrixAuthorizationStrategy/checkName?value=%5Busername%5D return either 403 (if logged in the wild with underscores, especially in internal Windows domains ) or 200 but blank response ( NetBIOS names are allowed to have underscores if anonymous w/anonymous granted Administer ) * At /configureSecurity/: clicking Save or Apply results in an error where an ActiveDirectorySecurityRealm failed to instantiate in org . Further reading kohsuke.stapler.Stapler.tryInvoke (Stapler.java : http 796)* At /configure : XHR call to / $stapler / stackoverflow.com bound / questions [a GUID] / 2180465 render returns 404 Not Found* At / can-domain-name-subdomains- configure: all other XHR calls executed on load (/checkAdminAddress, checkDefaultSuffix, checkGitUrl, etc.) return 200 OK but have - an -underscore-in-it empty response. This issue is present in 1.6, 2.2, and 2.3.
[JIRA] [core] (JENKINS-34740) All XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title Roy Tinker edited a comment on JENKINS-34740 Re: All XHR requests fail under certain conditions when an underscore is present in the hostname A few more details: For the itemCategories XHR, the extra headers disappear and the server returns 200 OK (instead of 403 Not Authorized) if I grant Administer privileges to the Anonymous user and then access as anonymous... but the response itself is still blank and therefore the page is blank. When accessing via a hostname with an underscore, I'm seeing problems in several other places throughout Jenkins -- but the problems all disappear if I access via a hostname without an underscore (which I'm doing by adding an alternate name for the Jenkins server's IP address in my machine's hosts file). Here's a few I could compile in 10 minutes:* At /configureSecurity/: XHR calls to /descriptorByName/hudson.security.GlobalMatrixAuthorizationStrategy/checkName?value=%5Busername%5D return either 403 (if logged in) or 200 but blank response (if anonymous w/anonymous granted Administer)* At /configureSecurity/: clicking Save or Apply results in an error where an ActiveDirectorySecurityRealm failed to instantiate in org.kohsuke.stapler.Stapler.tryInvoke (Stapler.java:796)* At /configure: XHR call to /$stapler/bound/[a GUID]/render returns 404 Not Found* At /configure: all other XHR calls executed on load (/checkAdminAddress, checkDefaultSuffix, checkGitUrl, etc.) return 200 OK but have an empty response. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34740) All XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title Roy Tinker commented on JENKINS-34740 Re: All XHR requests fail under certain conditions when an underscore is present in the hostname Just modified the title to reflect my latest understanding of the problem. Will provide more details when possible. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34740) All XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 All XHR requests fail under certain conditions when an underscore is present in the hostname Change By: Roy Tinker Labels: https security url Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34740) All XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 All XHR requests fail under certain conditions when an underscore is present in the hostname Change By: Roy Tinker Component/s: external-monitor-job-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34740) All XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 All XHR requests fail under certain conditions when an underscore is present in the hostname Change By: Roy Tinker Summary: Cannot create new items after upgrade to 2.2 All XHR requests fail under certain conditions when an underscore is present in the hostname Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname
Title: Message Title Roy Tinker commented on JENKINS-34740 Re: Cannot create new items after upgrade to 2.2 when underscore is present in the hostname I just downgraded back to 1.6, and I'm noticing that the persistent system problems are still there – just different. So I can create a new item now, but most XHR requests are still failing. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34826) Promoted builds do not receive parameter values defined at the job level
Title: Message Title Oleg Nenashev commented on JENKINS-34826 Re: Promoted builds do not receive parameter values defined at the job level Workaround: create parameter definitions in the Manual approval dialog. It is not a perfect solution Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-34825) Jobs in Folders should show credentials bound in the credential domain
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-34825 Jobs in Folders should show credentials bound in the credential domain Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/May/13 11:00 PM Priority: Critical Reporter: Joel Brown Credentials "bound" to the folder do not show in the credentials dropdown Repro: Install the Folders plugin Create a Folder Configure the Folder to have a Credential Domain, then a dd a Perforce Password credential to that domain Create a job within the folder with SCM Perforce. View credentials from the dropdown Expected: pick from global credentials and the credential just added in the folder's credential domain. Actual: only global credentials. I do have project team specific folders on the master and each has a local credential store
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-34821) HP_RUN_ID not available in parameterized builds
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-34821 HP_RUN_ID not available in parameterized builds Change By: Christopher Orr Labels: security-170 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title Christopher Orr commented on JENKINS-25791 Re: User.impersonate throws ClassCastException when using GitHub auth See also JENKINS-34775, for the breakage caused by the fix for SECURITY-243. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34826) Promoted builds do not receive parameter values defined at the job level
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34826 Promoted builds do not receive parameter values defined at the job level Change By: Oleg Nenashev Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-oauth-plugin] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Christopher Orr assigned an issue to Andrey Stroilov Jenkins / JENKINS-34775 Broken jobs after upgrade to 1.651.2 security update Change By: Christopher Orr Assignee: Andrey Stroilov Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-oauth-plugin] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-34775 Broken jobs after upgrade to 1.651.2 security update Change By: Christopher Orr Labels: security-243 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-oauth-plugin] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Christopher Orr commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update This is related to the fix for SECURITY-243 mentioned here: https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 Enabling the system property mentioned in that part of the security advisory should temporarily work around this problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-oauth-plugin] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-34775 Broken jobs after upgrade to 1.651.2 security update Change By: Christopher Orr Component/s: google-oauth-plugin Component/s: core Component/s: ghprb-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34826) Promoted builds do not receive parameter values defined at the job level
Title: Message Title Hidden Maverick created an issue Jenkins / JENKINS-34826 Promoted builds do not receive parameter values defined at the job level Issue Type: Bug Assignee: Oleg Nenashev Components: core, promoted-builds-plugin Created: 2016/May/13 11:02 PM Environment: * Operating system: CentOS 7.2.1511 with latest updates applied using "yum update" as of 2016-05-13. * Java runtime version: 1.7.0_101-mockbuild_2016_04_21_13_43-b00 * Jenkins version: 1.651.2 * Promoted Builds Plugin version: 2.26 Priority: Major Reporter: Hidden Maverick The security issue related to arbitrary build parameters (described in the link https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11) was addressed by Jenkins 1.651.2. Unfortunately, this security fix caused freestyle jobs containing build parameters to break if they include promoted builds that attempt to access the build parameters defined at the job level. Downgrading to Jenkins 1.651.1 allowed the affected jobs to function again.
[JIRA] [export-params-plugin] (JENKINS-34783) Parameters not written to slave after upgrade to latest LTS
Title: Message Title Christopher Orr commented on JENKINS-34783 Re: Parameters not written to slave after upgrade to latest LTS Stefan Toresson: Are you able to narrow down which of the two plugins is having the problem? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34824) Automated sorting of Build Executor Status based upon actively running jobs.
Title: Message Title Matthew Kruer created an issue Jenkins / JENKINS-34824 Automated sorting of Build Executor Status based upon actively running jobs. Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/May/13 10:56 PM Environment: Jenkins ver. 1.642.3 Java ver. 1.7 Priority: Minor Reporter: Matthew Kruer Right now I have 18 Build Nodes, each with at least 6 executors. This make the list over 3 pages long in. Because not all the executors are always running on all the nodes executors, and because the executors list is so long, without actively looking for down the page you do not see what is running. So an Idea for improvement is to allow the view to bubble sort, and collapse "idle" executors The current view of the Build Executor Status Node A 1 Idle 2 Idle 3 Idle 4 Idle Node B 1 Idle 2 Idle 3 Idle 4 Idle Node C 1 Idle 2 Idle 3 Idle 4 Idle The Idea is the hide the builder executors on nodes so it does not show non-running Executor Node A (0/4) Node B (0/4) Node C (0/4) Updated Idea Build kicks off on Node C (Node C is moved to the top of the list and Executor 2 is show to be running) Node C (0/4) 2 Running Job 1 Node A (0/4) Node B (0/4)
[JIRA] [workflow-plugin] (JENKINS-34638) org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.Random
Title: Message Title Ashudeep Budhiraja commented on JENKINS-34638 Re: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.Random Thanks Kieran, Works after adding to Signatures already approved: field java.util.ArrayList size method java.util.Random nextInt new java.util.Random staticMethod java.lang.Math abs int staticMethod java.lang.Math random Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34638) org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.Random
Title: Message Title Ashudeep Budhiraja edited a comment on JENKINS-34638 Re: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.Random Thanks Kieran,Works after adding to list of "* Signatures already approved *" :* field java.util.ArrayList size* method java.util.Random nextInt* new java.util.Random* staticMethod java.lang.Math abs int* staticMethod java.lang.Math random* Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [export-params-plugin] (JENKINS-34783) Parameters not written to slave after upgrade to latest LTS
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-34783 Parameters not written to slave after upgrade to latest LTS Change By: Christopher Orr Labels: security-170 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34811) Environment Variables not being created
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-34811 Environment Variables not being created Change By: Christopher Orr Labels: build git jenkins plugin scm security-170 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34811) Environment Variables not being created
Title: Message Title Christopher Orr commented on JENKINS-34811 Re: Environment Variables not being created This is a duplicate of JENKINS-34762 (or at least has the same case). See also https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-34801) Parametrization for matrix jobs does not work
Title: Message Title Christopher Orr closed an issue as Duplicate Duplicate of JENKINS-34758; see also https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170 Jenkins / JENKINS-34801 Parametrization for matrix jobs does not work Change By: Christopher Orr Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-17742) Pick Up Committer from Upstream Job
Title: Message Title Alex Earl commented on JENKINS-17742 Re: Pick Up Committer from Upstream Job I think that would be a new provider Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-17742) Pick Up Committer from Upstream Job
Title: Message Title Jim Searle commented on JENKINS-17742 Re: Pick Up Committer from Upstream Job Is it possible to add all upstream committers since last success to this Provider? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Hidden Maverick updated an issue Jenkins / JENKINS-34758 Parameters are not passed to child jobs in multi-configuration projects Change By: Hidden Maverick Comment: Thanks for letting me know. I'll redirect my issue to the appropriate bug report. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Hidden Maverick commented on JENKINS-34758 Re: Parameters are not passed to child jobs in multi-configuration projects Thanks for letting me know. I'll redirect my issue to the appropriate bug report. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Hidden Maverick updated an issue Jenkins / JENKINS-34758 Parameters are not passed to child jobs in multi-configuration projects Change By: Hidden Maverick Comment: I have confirmed that this issue also affects jobs that contain promoted builds using the latest Promoted Builds Plugin, with Jenkins 1.651.2 running on CentOS 7.2.1511. The build parameters defined in a job are not passed to the promoted builds, causing the job to break.Downgrading to Jenkins 1.651.1 allowed the affected jobs to function again. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-34758 Parameters are not passed to child jobs in multi-configuration projects Change By: Christopher Orr Labels: lts security-170 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-34753) Sec-170-releated: gerrit-trigger needs to declare parameters
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-34753 Sec-170-releated: gerrit-trigger needs to declare parameters Change By: Christopher Orr Labels: security-170 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-34762) PR status cannot be updated due to filtered parameters
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-34762 PR status cannot be updated due to filtered parameters Change By: Christopher Orr Labels: security-170 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-34762) PR status cannot be updated due to filtered parameters
Title: Message Title Christopher Orr commented on JENKINS-34762 Re: PR status cannot be updated due to filtered parameters Nicholas Brown: If you use that plugin, and you're seeing issues due to the fix for SECURITY-170, could you please file a new bug for that? Also adding it to the wiki page of affected plugins would be helpful. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Christopher Orr commented on JENKINS-34758 Re: Parameters are not passed to child jobs in multi-configuration projects Hidden Maverick: This is a bug report for the matrix plugin (multi-configuration project type); if you're having an issue with another plugin, please file a separate issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-binding-plugin] (JENKINS-34823) Credentials masks nonexistent secrets between all chars when withCredentials is passed an empty list
Title: Message Title
Brian Ray updated an issue
Jenkins / JENKINS-34823
Credentials masks nonexistent secrets between all chars when withCredentials is passed an empty list
Change By:
Brian Ray
First reported here in a comment under JENKINS-24805.Minimal reproduction script is:{code:java}node() { withCredentials( [] ) { echo 'Test of the credentials binding decorator' }}{code}So, passing an empty list of credentials--my concrete use case constructs the list based on upstream factors; some of the times there are no credentials to resolve so the list is empty. The relevant part of the log then winds up like this:{noformat}[Pipeline] Bind credentials to variables : Start[Pipeline] withCredentials {[Pipeline] echoTest of the credentials binding decorator[Pipeline] } //withCredentials[Pipeline] Bind credentials to variables : End{noformat}I believe it's because [BindingStep.Filter::Filter builds a zero-length pattern|https://github.com/jenkinsci/credentials-binding-plugin/blob/a2bf336089fc0db8605f67039a1ea97c1fa98ad2/src/main/java/org/jenkinsci/plugins/credentialsbinding/impl/BindingStep.java#L134-L160] in this scenario, which matches like crazy. The obvious workaround is just to not wrap using withCredentials if the credentials list is empty, so it's not a huge deal. I'm also unsure if this issue should be distinct from JIRA-24805.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title
Alfredo Deza edited a comment on JENKINS-25791
Re: User.impersonate throws ClassCastException when using GitHub auth
After upgrading to 2.3 we are hitting this same issue. Some things that are worth noting:* Issue seems intermittent (can't reproduce consistently)* We are using Jenkins 2.3 and breakage started by upgrading to 2.3* Our stacktrace looks the same* It happens even if the build is successful, at the very end: {{ Archiving artifactsFATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationTokenjava.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:644) at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1048) at hudson.model.User.get(User.java:394) at hudson.model.User.get(User.java:363) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:374) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:435) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:350) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:672) at hudson.model.Run.execute(Run.java:1763) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title
Alfredo Deza edited a comment on JENKINS-25791
Re: User.impersonate throws ClassCastException when using GitHub auth
After upgrading to 2.3 we are hitting this same issue. Some things that are worth noting:* Issue seems intermittent (can't reproduce consistently)* We are using Jenkins 2.3 and breakage started by upgrading to 2.3* Our stacktrace looks the same* It happens even if the build is successful, at the very end: {{ Archiving artifactsFATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationTokenjava.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:644) at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1048) at hudson.model.User.get(User.java:394) at hudson.model.User.get(User.java:363) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:374) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:435) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:350) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:672) at hudson.model.Run.execute(Run.java:1763) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-binding-plugin] (JENKINS-34823) Credentials masks nonexistent secrets between all chars when withCredentials is passed an empty list
Title: Message Title
Brian Ray created an issue
Jenkins / JENKINS-34823
Credentials masks nonexistent secrets between all chars when withCredentials is passed an empty list
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
credentials-binding-plugin
Created:
2016/May/13 10:12 PM
Environment:
Jenkins core 1.651.1 Credentials Binding Plugin 1.7 Jenkins master running on Windows Server 2008 R2 Standard SP1 --against Oracle JDK 1.8.0_45 Node agents running on various Windows 2008 + 2012 Servers, CentOS 7 servers --against various Oracle and OpenJDK 1.7 and 1.8 JDKs
Priority:
Minor
Reporter:
Brian Ray
First reported here in a comment under JENKINS-24805.
Minimal reproduction script is:
node() {
withCredentials( [] ) {
echo 'Test of the credentials binding decorator'
}
}
So, passing an empty list of credentials--my concrete use case constructs the list based on upstream factors; some of the times there are no credentials to resolve so the list is empty. The relevant part of the log then winds up like this:
[JIRA] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title
Alfredo Deza edited a comment on JENKINS-25791
Re: User.impersonate throws ClassCastException when using GitHub auth
After upgrading to 2.3 we are hitting this same issue. Some things that are worth noting:* Issue seems intermittent (can't reproduce consistently)* We are using Jenkins 2.3 and breakage started by upgrading to 2.3* Our stacktrace looks the same* It happens even if the build is successful, at the very end:{{ Archiving artifactsFATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationTokenjava.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:644) at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1048) at hudson.model.User.get(User.java:394) at hudson.model.User.get(User.java:363) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:374) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:435) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:350) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:672) at hudson.model.Run.execute(Run.java:1763) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Lee Porte commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update I saw this issue with the previous github-oauth-plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title
Alfredo Deza commented on JENKINS-25791
Re: User.impersonate throws ClassCastException when using GitHub auth
After upgrading to 2.3 we are hitting this same issue. Some things that are worth noting:
Issue seems intermittent (can't reproduce consistently)
We are using Jenkins 2.3 and breakage started by upgrading to 2.3
Our stacktrace looks the same
It happens even if the build is successful, at the very end:
{{ Archiving artifacts FATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken java.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:644) at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1048) at hudson.model.User.get(User.java:394) at hudson.model.User.get(User.java:363) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:374) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:435) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:350) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:672) at hudson.model.Run.execute(Run.java:1763) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Finished: FAILURE }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Alfredo Deza commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update This seems to be linked to the ghprb-plugin but this looks like a github-oauth-plugin issue. We are facing the same problems Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33925) Test framework for Jenkinsfile
Title: Message Title Andrew Bayer commented on JENKINS-33925 Re: Test framework for Jenkinsfile I'm strongly +1 on the JenkinsRule approach. I think the challenge really entirely lies in the "dry-run" matter - how do we determine what behaviors are the ones we should mock/skip/whatever we do? How do we mock/skip/whatever those behaviors? How is that extensible and easy for plugins to support? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Daniel Beck commented on JENKINS-34758 Re: Parameters are not passed to child jobs in multi-configuration projects To everyone experiencing this issue: No need to downgrade, use the system properties mentioned in the warning quoted in an earlier comment to disable this new behavior, at least for a time, while plugins are adapted. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Daniel Beck commented on JENKINS-34758 Re: Parameters are not passed to child jobs in multi-configuration projects Josh Moore Oh shit. I'm sorry that happened. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-34817) Add job-dsl-plugin support for logstash plugin
Title: Message Title rr lai updated an issue Jenkins / JENKINS-34817 Add job-dsl-plugin support for logstash plugin Change By: rr lai Summary: Add job-dsl-plugin support for logstash support plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-34426) Changing project-based settings for AD-Groups shows error
Title: Message Title Andrew Forman commented on JENKINS-34426 Re: Changing project-based settings for AD-Groups shows error I'm seeing the same error occur during new user signup. Authentication is working fine, then the cache/recursive load exception hits. Environment: windows server 2012R2 Jenkins: 2.3 AD plugin: 1.45 May 13, 2016 2:18:52 PM FINE hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider Failed to retrieve user [username] hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user [username]; nested exception is com.google.common.util.concurrent.UncheckedExecutionException: java.lang.IllegalStateException: Recursive load at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:340) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Hidden Maverick commented on JENKINS-34758 Re: Parameters are not passed to child jobs in multi-configuration projects I have confirmed that this issue also affects jobs that contain promoted builds using the latest Promoted Builds Plugin, with Jenkins 1.651.2 running on CentOS 7.2.1511. The build parameters defined in a job are not passed to the promoted builds, causing the job to break. Downgrading to Jenkins 1.651.1 allowed the affected jobs to function again. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter-plugin] (JENKINS-34806) JiraTestResultReporter-plugin: java.lang.NoClassDefFoundError: Could not initialize class org.jenkinsci.plugins.JiraTestResultReporter.JiraTestDa
Title: Message Title Andrei Tuicu resolved as Fixed Hey, guys, Thank you for the report! Everything should be ok in the new version 2.0.1. You might need to wait a bit for the mirrors to be updated until it is shown in the Jenkins update center, or you can download the hpi directly from here[0]. Please let me know if you find any more problems. Thank you, Andrei [0] http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/JiraTestResultReporter/2.0.1/JiraTestResultReporter-2.0.1.hpi Jenkins / JENKINS-34806 JiraTestResultReporter-plugin: java.lang.NoClassDefFoundError: Could not initialize class org.jenkinsci.plugins.JiraTestResultReporter.JiraTestDataPublisher Change By: Andrei Tuicu Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Lee Porte commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update Looks like I'll be downgrading to 2.2 unless there is progress on this issue over the weekend. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Shawn Baker commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update I'm seeing this issue too, and I upgraded from 1.625.3 to 1.651.2. Same old data messages with something about 1.653 as the version. It looked fishy, so I reverted back to 1.625.3. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-34764) Fix PCT against 2.x baseline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34764 Re: Fix PCT against 2.x baseline Code changed in jenkins User: Armando Fernandez Path: pom.xml rest-api/src/main/java/com/cloudbees/workflow/util/ServeJson.java http://jenkins-ci.org/commit/pipeline-stage-view-plugin/41ed688b11c1236c95363a0f3998828c77d1251b Log: JENKINS-34764 Fix PCT against 2.x baseline Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-34764) Fix PCT against 2.x baseline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34764 Re: Fix PCT against 2.x baseline Code changed in jenkins User: Sam Van Oort Path: pom.xml rest-api/src/main/java/com/cloudbees/workflow/util/ServeJson.java http://jenkins-ci.org/commit/pipeline-stage-view-plugin/53c9f5764f9670078717adf70a5352c437a75c79 Log: Merge pull request #13 from armfergom/JENKINS-34764 JENKINS-34764 Fix PCT against 2.x baseline Compare: https://github.com/jenkinsci/pipeline-stage-view-plugin/compare/6f82dcfc46fd...53c9f5764f96 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-20985) TestNG plugin should has a possibility to use thresholds for failed tests
Title: Message Title Chris Everling commented on JENKINS-20985 Re: TestNG plugin should has a possibility to use thresholds for failed tests Cam Spencer, nalin_makar, I don't think that is a bug. The default behavior before the update was to mark the build as UNSTABLE whenever there were test failures. The default failure threshold to FAIL the build is 100%, but the default failure threshold to mark the build as UNSTABLE is 0. The default behavior should not have changed with the update. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-34822) TestNG plugin has incorrect default threshold values
Title: Message Title
Cam Spencer updated an issue
Jenkins / JENKINS-34822
TestNG plugin has incorrect default threshold values
Change By:
Cam Spencer
After updating the TestNG plugin to 1.12, the new feature from JENKINS-20985 caused our tests to pass regardless of failures/skips in our TestNG results. By default, the threshold is set to 100% if users have not configured the plugin yet.{code:java}* Helps resolve XML configs for versions before 1.11 when these new config options were introduced.* See https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility* @return resolved object */ protected Object readResolve() { if (unstableSkips == null) { unstableSkips = unstableOnSkippedTests ? 0 : 100; } if (failedFails == null) { failedFails = 100; } if (failedSkips == null) { failedSkips = 100; } if (thresholdMode == null) { thresholdMode = 2; } return this; }{code}This means that by default, a test will require MORE THAN 100% skips/failures in order to mark the build as unstable/failed from TestNG results. It would make more sense if the default was set to 1 0 , and the thresholdMode set to 1. This way, a single failure/skip will cause the build to be unstable/fail like in previous versions.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [testng-plugin] (JENKINS-34822) TestNG plugin has incorrect default threshold values
Title: Message Title
Cam Spencer updated an issue
Jenkins / JENKINS-34822
TestNG plugin has incorrect default threshold values
Change By:
Cam Spencer
After updating the TestNG plugin to 1.12, the new feature from JENKINS-20985 caused our tests to pass regardless of failures/skips in our TestNG results. By default, the threshold is set to 100% if users have not configured the plugin yet.{code:java}* Helps resolve XML configs for versions before 1.11 when these new config options were introduced.* See https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility* @return resolved object */ protected Object readResolve() { if (unstableSkips == null) { unstableSkips = unstableOnSkippedTests ? 0 : 100; } if (failedFails == null) { failedFails = 100; } if (failedSkips == null) { failedSkips = 100; } if (thresholdMode == null) { thresholdMode = 2; } return this; }{code}This means that by default, a test will require MORE THAN 100% skips/failures in order to mark the build as unstable/failed from TestNG results. It would make more sense if the default was set to 1 % , and the thresholdMode set to be more inline 1. This way, a single failure/skip will cause the build to what be unstable/fail like in previous versions would do .
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving
[JIRA] [testng-plugin] (JENKINS-34822) TestNG plugin has incorrect default threshold values
Title: Message Title Nalin Makar updated an issue Jenkins / JENKINS-34822 TestNG plugin has incorrect default threshold values Change By: Nalin Makar Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-34822) TestNG plugin has incorrect default threshold values
Title: Message Title Cam Spencer updated an issue Jenkins / JENKINS-34822 TestNG plugin has incorrect default threshold values Change By: Cam Spencer Attachment: TestNG Plugin.jpg Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-34822) TestNG plugin has incorrect default threshold values
Title: Message Title
Cam Spencer updated an issue
Jenkins / JENKINS-34822
TestNG plugin has incorrect default threshold values
Change By:
Cam Spencer
After updating the TestNG plugin to 1.12, the new feature from JENKINS-20985 caused our tests to pass regardless of failures/skips in our TestNG results. By default, the threshold is set to 100% if users have not set this up configured the plugin yet.{code:java}* Helps resolve XML configs for versions before 1.11 when these new config options were introduced.* See https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility* @return resolved object */ protected Object readResolve() { if (unstableSkips == null) { unstableSkips = unstableOnSkippedTests ? 0 : 100; } if (failedFails == null) { failedFails = 100; } if (failedSkips == null) { failedSkips = 100; } if (thresholdMode == null) { thresholdMode = 2; } return this; }{code}This means that by default, a test will require MORE THAN 100% skips/failures in order to mark the build as unstable/failed from TestNG results. It would make more sense if the default was set to 1% to be more inline to what previous versions would do.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] [core] (JENKINS-31791) Cannot load job pages due to HistoryWidget hanging
Title: Message Title greg mallett commented on JENKINS-31791 Re: Cannot load job pages due to HistoryWidget hanging Tom FENNELLY, the toList() call mentioned by Daniel Beck is not in HistoryPageFilter, but is in the BuildHistoryWidget. From his stack trace: hudson.widgets.BuildHistoryWidget.getHistoryPageFilter(BuildHistoryWidget.java:81) I have a very similar stack trace and had opened a duplicate of this ticket reporting the same issue: https://issues.jenkins-ci.org/browse/JENKINS-31888. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-34822) TestNG plugin has incorrect default threshold values
Title: Message Title
Cam Spencer created an issue
Jenkins / JENKINS-34822
TestNG plugin has incorrect default threshold values
Issue Type:
Bug
Assignee:
Nalin Makar
Components:
testng-plugin
Created:
2016/May/13 7:46 PM
Environment:
Jenkins 2.2 TestNG Results Plugin 1.12
Priority:
Major
Reporter:
Cam Spencer
After updating the TestNG plugin to 1.12, the new feature from
JENKINS-20985
caused our tests to pass regardless of failures/skips in our TestNG results. By default, the threshold is set to 100% if users have not set this up yet.
* Helps resolve XML configs for versions before 1.11 when these new config options were introduced.
* See https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility
* @return resolved object
*/
protected Object readResolve() {
if (unstableSkips == null) {
unstableSkips = unstableOnSkippedTests ? 0 : 100;
}
if (failedFails == null) {
failedFails = 100;
}
if (failedSkips == null) {
failedSkips = 100;
}
if (thresholdMode == null) {
thresholdMode = 2;
[JIRA] [core] (JENKINS-21720) Don't ask for confirmation when it doesn't make any sense
Title: Message Title
Andrei Tuicu commented on JENKINS-21720
Re: Don't ask for confirmation when it doesn't make any sense
Hello, Antonio Muñiz,
This is just my opinion, but I think that it would be better to allow change events when a select is filled for the first time. For example, if you have a select on which other selects depend; in this case, when the main select is filled, I want my doFill$ {Field}
methods to be called for the dependencies so they are filled based on the value of said main select. In the end, there is an actual change, because that particular select changes from nothing to the first value.
What do you think? In my opinion we shouldn't have this check here: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/lib/form/select/select.js#L51
I'm asking, because it is causing bugs in a plugin that I'm developing. I was relying on that change event.
Thank you, Andrei
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-20985) TestNG plugin should has a possibility to use thresholds for failed tests
Title: Message Title Nalin Makar commented on JENKINS-20985 Re: TestNG plugin should has a possibility to use thresholds for failed tests Cam Spencer, can you please file a separate bug? And, it'll be great if you can give specific information about the properties you are referring to. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34807) Support parameters in SCM Browser URL
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-34807 Support parameters in SCM Browser URL Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34811) Environment Variables not being created
Title: Message Title Mark Waite resolved as Won't Fix The warning message offers one way to work around it. You can either set `-Dhudson.model.ParametersAction.keepUndefinedParameters=true` to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even though it represents a security breach. I believe that another work around is to define a parameter to the job with the name of the parameter you're passing. Jenkins / JENKINS-34811 Environment Variables not being created Change By: Mark Waite Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [testng-plugin] (JENKINS-20985) TestNG plugin should has a possibility to use thresholds for failed tests
Title: Message Title Cam Spencer commented on JENKINS-20985 Re: TestNG plugin should has a possibility to use thresholds for failed tests Hey nalin_makar, I don't think the default threshold value should be 100%. We updated the plugin without noticing this feature, and this was causing tests that failed to show as stable. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Ian Norton updated an issue Jenkins / JENKINS-34758 Parameters are not passed to child jobs in multi-configuration projects Change By: Ian Norton Priority: Critical Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Ian Norton commented on JENKINS-34758 Re: Parameters are not passed to child jobs in multi-configuration projects Josh Moore yikes! my condolences! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31888) BuildHistoryWidget causing job page slowdowns
Title: Message Title greg mallett commented on JENKINS-31888 Re: BuildHistoryWidget causing job page slowdowns I changed this to "Core" for hopefully more visibility. Reading the comments, it seems this is not related to the multijob plugin as I originally thought. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31888) BuildHistoryWidget causing job page slowdowns
Title: Message Title greg mallett updated an issue Jenkins / JENKINS-31888 BuildHistoryWidget causing job page slowdowns Change By: greg mallett Component/s: core Component/s: multijob-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31425) should be able to specify multiple users or groups for the submitter of an input step
Title: Message Title Sam Gleske commented on JENKINS-31425 Re: should be able to specify multiple users or groups for the submitter of an input step Pipeline and Jenkins will not be ready for any enterprise without this. This is a poor decision because: what if your "one deployer" goes on vacation in a team of 20 developers? Is the whole pipeline held hostage? This needs to be highly prioritized. Needs to support Jenkins groups. It needs to support optionally selecting multiple Jenkins groups/users in the same field. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cmakebuilder-plugin] (JENKINS-29142) look for MSVC 15.x toolchain
Title: Message Title Martin Weber resolved as Not A Defect Jenkins / JENKINS-29142 look for MSVC 15.x toolchain Change By: Martin Weber Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-34821) HP_RUN_ID not available in parameterized builds
Title: Message Title John Gregg created an issue Jenkins / JENKINS-34821 HP_RUN_ID not available in parameterized builds Issue Type: Bug Assignee: Ofir Shaked Attachments: hp.patch Components: hp-application-automation-tools-plugin Created: 2016/May/13 6:58 PM Priority: Major Reporter: John Gregg Setting HP_RUN_ID only works if the build is not parameterized. If it is parameterized, HP_RUN_ID does not get passed to subsequent Ant scripts. For it to work with parameterized builds also, you need to check for existing string parameters, merge in the new one, and replace the existing parameters. See the attached patch for a fix. thanks Add Comment
[JIRA] [tap-plugin] (JENKINS-34820) TAP Plugin: Enhanced Test Visualization
Title: Message Title Evan Van Dyke created an issue Jenkins / JENKINS-34820 TAP Plugin: Enhanced Test Visualization Issue Type: New Feature Assignee: Bruno P. Kinoshita Components: tap-plugin Created: 2016/May/13 6:49 PM Priority: Minor Reporter: Evan Van Dyke It would be very helpful to get some more detailed graphs/tables showing on the job pages related to the TAP outputs. Some other test plugins (i.e. Robot) have quite a bit of drill-down capability that would be highly useful. Here are the things our users would certainly appreciate... TAP "Extended Results" visible on main job page Table of all test failures visible on main job page Dashboard Portlet containing details on current test failures Better/dynamic sizing of TAP graphs (especially on high-resolution monitors) Ability to display/depict the status of particular tests vs build (as a big matrix)
[JIRA] [branch-api-plugin] (JENKINS-22242) Add MultiBranchProperty support
Title: Message Title Jesse Glick resolved as Won't Do AbstractFolderProperty> should suffice. Jenkins / JENKINS-22242 Add MultiBranchProperty support Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-34817) Add job-dsl-plugin support for logstash support
Title: Message Title rr lai updated an issue Jenkins / JENKINS-34817 Add job-dsl-plugin support for logstash support Change By: rr lai Job-dsl-plugin is not support logstash plugin. Open this item to add the support for it.logstash :https://wiki.jenkins-ci.org/display/JENKINS/Logstash+Plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-34121) IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3
Title: Message Title Oleg Nenashev commented on JENKINS-34121 Re: IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3 Workaround - Disable JNLP3 protocol. This workaround has been implemented by Stephen and released as remoting 2.59. Should become available in the next weekly, may be a subject for backporting into the next LTS release (1.651.3) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-34819) Allow disabling particular protocols in remoting
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-34819 Allow disabling particular protocols in remoting Issue Type: New Feature Assignee: Unassigned Components: remoting Created: 2016/May/13 6:02 PM Priority: Minor Reporter: Oleg Nenashev It's a post-factum fix for PR: https://github.com/jenkinsci/remoting/pull/83 by @stephenc. It should allow to workaround issues like JENKINS-34121 Add Comment
[JIRA] [active-choices-plugin] (JENKINS-34818) Active Choice reactive parameter cannot access global parameters
Title: Message Title Alon Chanukov created an issue Jenkins / JENKINS-34818 Active Choice reactive parameter cannot access global parameters Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: Screen Shot 2016-05-13 at 10.23.27 AM.png, Screen Shot 2016-05-13 at 10.25.07 AM.png Components: active-choices-plugin Created: 2016/May/13 5:51 PM Environment: Jenkins 2.2 on a windows machine. Active Choices Plug-in 1.4 Priority: Major Reporter: Alon Chanukov In manage_jenkins System i under Global properties-->Environment variables I set a list of variables. I am unable to access any of them in my active choice parameter. see example of my usage below in images. If i simply switch the $DEVICES_MAP_DIR with the path that is shown in the global environment variable it works as expected using the global environment variable it fails. logs
[JIRA] [ec2-plugin] (JENKINS-34382) EC2 plugin doesn't support build blocker on node level
Title: Message Title rr lai closed an issue as Fixed Jenkins / JENKINS-34382 EC2 plugin doesn't support build blocker on node level Change By: rr lai Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
