[JIRA] (JENKINS-60132) Add support for AWS parameter store as a backend for storing credentials
Title: Message Title C created an issue Jenkins / JENKINS-60132 Add support for AWS parameter store as a backend for storing credentials Issue Type: New Feature Assignee: Chris Kilding Components: aws-secrets-manager-credentials-provider-plugin Created: 2019-11-11 14:11 Priority: Minor Reporter: C Particularly, storing credentials as secure strings parameters can have a lower cost relative to secrets manager. https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-securestring.html Questions: Does this belong in its own project/plugin or is there opportunity for code reuse as part of aws-secrets-manager-credentials-provider-plugin? Is there opportunity to reuse the conventions, such as tagging, that were defined when adding multiple credential support (JENKINS-58339)? Any other comments? Add Comment
[JIRA] (JENKINS-58339) Support new types of credentials
Title: Message Title C commented on JENKINS-58339 Re: Support new types of credentials Chris Kilding - I'll open another issue on it, but curious what you think about using parameter store as a backend. Do you think that having that functionality in this plugin (so the plugin can scan either secrets manager, or parameter store) is a good idea? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200452.1562229894000.10579.1573133760283%40Atlassian.JIRA.
[JIRA] (JENKINS-58476) findFiles has recursion error when passed a method call for the value of the glob parameter
Title: Message Title Coltrey Mather created an issue Jenkins / JENKINS-58476 findFiles has recursion error when passed a method call for the value of the glob parameter Issue Type: New Feature Assignee: rsandell Components: pipeline-utility-steps-plugin Created: 2019-07-12 16:07 Priority: Trivial Reporter: Coltrey Mather I get the following error when running the following script in a pipeline job. Jenkins ver. 2.121.3 pipeline-utility-steps-plugin 2.1.0 java.lang.StackOverflowError: Excessively nested closures/functions at WorkflowScript.getPath(WorkflowScript:3) - look for unbounded recursion - call depth: 1025 at com.cloudbees.groovy.cps.impl.CpsFunction.invoke(CpsFunction.java:28) at com.cloudbees.groovy.cps.impl.CpsCallableInvocation.invoke(CpsCallableInvocation.java:40) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:62) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixName(FunctionCallBlock.java:77) at sun.reflect.GeneratedMethodAccessor136.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) at
[JIRA] (JENKINS-15925) Change delimiter of SecurityGroups from comma to pipe
Title: Message Title Coltrey Mather commented on JENKINS-15925 Re: Change delimiter of SecurityGroups from comma to pipe Supriya Nandi how has this issue been resolved? The above PR has not been merged... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34071) Allow filtering by BitBucket Cloud projects
Title: Message Title Coltrey Mather commented on JENKINS-34071 Re: Allow filtering by BitBucket Cloud projects Michel Zanini Now that PR-127 and PR-128 are merged, do you have everything you need to publish your plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49532) autogenerated keystore should not be kept in temp directory
Title: Message Title Coltrey Mather commented on JENKINS-49532 Re: autogenerated keystore should not be kept in temp directory If the file does not exist, shouldn't it be re-created? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49747) java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)
Title: Message Title
Coltrey Mather updated an issue
Jenkins / JENKINS-49747
java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)
Change By:
Coltrey Mather
I'm not sure why /tmp/saml-jenkins-keystore-5345145658381646927.jks ceased to exist (it was created/working and there have been no system restarts or Jenkins restarts). I have no log or any way of finding out what caused that file to be removed.That said - because this file is created by the saml plugin/pac4j, if it does not exist and the plugin needs it - it should be re-created.This error prevented users from authenticating and was fixed by a restart of Jenkins. I am using saml-plugin 1.0.5 with Azure AD and retrieving metadata from a URL every 1 minute. WARNING: Error while serving [https://tst-jenkins/securityRealm/commenceLogin|https://tst-jenkins.privacystar.com/securityRealm/commenceLogin] {{java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)}} \{\{ at java.io.FileInputStream.open0(Native Method)}} \{\{ at java.io.FileInputStream.open(FileInputStream.java:195)}} \{\{ at java.io.FileInputStream.(FileInputStream.java:138)}} \{\{ at java.io.FileInputStream.(FileInputStream.java:93)}} \{\{ at org.pac4j.core.util.CommonHelper.newFileInputStream(CommonHelper.java:312)}} {{Caused: org.pac4j.core.exception.TechnicalException}} \{\{ at org.pac4j.core.util.CommonHelper.newFileInputStream(CommonHelper.java:314)}} \{\{ at org.pac4j.core.util.CommonHelper.getInputStreamFromName(CommonHelper.java:304)}} \{\{ at org.pac4j.core.util.CommonHelper$1.getInputStream(CommonHelper.java:348)}} \{\{ at org.pac4j.saml.crypto.KeyStoreCredentialProvider.(KeyStoreCredentialProvider.java:66)}} \{\{ at org.pac4j.saml.crypto.KeyStoreCredentialProvider.(KeyStoreCredentialProvider.java:90)}} \{\{ at org.pac4j.saml.client.SAML2Client.initCredentialProvider(SAML2Client.java:174)}} \{\{ at org.pac4j.saml.client.SAML2Client.internalInit(SAML2Client.java:111)}} \{\{ at org.pac4j.core.util.InitializableWebObject.init(InitializableWebObject.java:24)}} \{\{ at org.jenkinsci.plugins.saml.OpenSAMLWrapper.createSAML2Client(OpenSAMLWrapper.java:145)}} \{\{ at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:45)}} \{\{ at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:30)}} \{\{ at org.jenkinsci.plugins.saml.OpenSAMLWrapper.get(OpenSAMLWrapper.java:65)}} \{\{ at org.jenkinsci.plugins.saml.SamlSecurityRealm.doCommenceLogin(SamlSecurityRealm.java:238)}} \{\{ at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)}} \{\{ at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)}} \{\{ at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)}} \{\{ at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)}} \{\{ at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129)}} \{\{ at
[JIRA] (JENKINS-49747) java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)
Title: Message Title Coltrey Mather commented on JENKINS-49747 Re: java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory) Looking at at org.jenkinsci.plugins.saml.OpenSAMLWrapper.createSAML2Client() and org.jenkinsci.plugins.saml.BundleKeyStore.init() it seems like the keystore should've been recreated, but I'm not familiar enough to follow what is really going on there. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49747) java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)
Title: Message Title Coltrey Mather updated an issue Jenkins / JENKINS-49747 java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory) Change By: Coltrey Mather Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49747) java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)
Title: Message Title
Coltrey Mather updated an issue
Jenkins / JENKINS-49747
java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)
Change By:
Coltrey Mather
I'm not sure why /tmp/saml-jenkins-keystore-5345145658381646927.jks ceased to exist (it was created/working and there have been no system restarts or Jenkins restarts). I have no log or any way of finding out what caused that file to be removed.That said - because this file is created by the saml plugin/pac4j, if it does not exist and Jenkins the plugin needs it - it should be re-created.This error prevented users from authenticating and was fixed by a restart of Jenkins. I am using saml-plugin 1.0.5 with Azure AD and retrieving metadata from a URL every 1 minute. {{java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)}} \{\{ at java.io.FileInputStream.open0(Native Method)}} \{\{ at java.io.FileInputStream.open(FileInputStream.java:195)}} \{\{ at java.io.FileInputStream.(FileInputStream.java:138)}} \{\{ at java.io.FileInputStream.(FileInputStream.java:93)}} \{\{ at org.pac4j.core.util.CommonHelper.newFileInputStream(CommonHelper.java:312)}} {{Caused: org.pac4j.core.exception.TechnicalException}} \{\{ at org.pac4j.core.util.CommonHelper.newFileInputStream(CommonHelper.java:314)}} \{\{ at org.pac4j.core.util.CommonHelper.getInputStreamFromName(CommonHelper.java:304)}} \{\{ at org.pac4j.core.util.CommonHelper$1.getInputStream(CommonHelper.java:348)}} \{\{ at org.pac4j.saml.crypto.KeyStoreCredentialProvider.(KeyStoreCredentialProvider.java:66)}} \{\{ at org.pac4j.saml.crypto.KeyStoreCredentialProvider.(KeyStoreCredentialProvider.java:90)}} \{\{ at org.pac4j.saml.client.SAML2Client.initCredentialProvider(SAML2Client.java:174)}} \{\{ at org.pac4j.saml.client.SAML2Client.internalInit(SAML2Client.java:111)}} \{\{ at org.pac4j.core.util.InitializableWebObject.init(InitializableWebObject.java:24)}} \{\{ at org.jenkinsci.plugins.saml.OpenSAMLWrapper.createSAML2Client(OpenSAMLWrapper.java:145)}} \{\{ at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:45)}} \{\{ at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:30)}} \{\{ at org.jenkinsci.plugins.saml.OpenSAMLWrapper.get(OpenSAMLWrapper.java:65)}} \{\{ at org.jenkinsci.plugins.saml.SamlSecurityRealm.doCommenceLogin(SamlSecurityRealm.java:238)}} \{\{ at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)}} \{\{ at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)}} \{\{ at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)}} \{\{ at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)}} \{\{ at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129)}} \{\{ at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)}} \{\{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)}} {{Caused:
[JIRA] (JENKINS-49747) java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)
Title: Message Title
Coltrey Mather updated an issue
Jenkins / JENKINS-49747
java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)
Change By:
Coltrey Mather
I'm not sure why /tmp/saml-jenkins-keystore-5345145658381646927.jks ceased to exist (it was created/working and there have been no system restarts or Jenkins restarts). I have no log or any way of finding out what caused that file to be removed.That said - because this file is created by the saml plugin/pac4j, if it does not exist and Jenkins needs it - it should be re-created.This error prevented users from authenticating and was fixed by a restart of Jenkins. I am using saml-plugin 1.0.5 with Azure AD and retrieving metadata from a URL every 1 minute. {{java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)}} \ { \ { at java.io.FileInputStream.open0(Native Method)}} \ { \ { at java.io.FileInputStream.open(FileInputStream.java:195)}} \ { \ { at java.io.FileInputStream.(FileInputStream.java:138)}} \ { \ { at java.io.FileInputStream.(FileInputStream.java:93)}} \ { \ { at org.pac4j.core.util.CommonHelper.newFileInputStream(CommonHelper.java:312)}}{{Caused: org.pac4j.core.exception.TechnicalException}} \ { \ { at org.pac4j.core.util.CommonHelper.newFileInputStream(CommonHelper.java:314)}} \ { \ { at org.pac4j.core.util.CommonHelper.getInputStreamFromName(CommonHelper.java:304)}} \ { \ { at org.pac4j.core.util.CommonHelper$1.getInputStream(CommonHelper.java:348)}} \ { \ { at org.pac4j.saml.crypto.KeyStoreCredentialProvider.(KeyStoreCredentialProvider.java:66)}} \ { \ { at org.pac4j.saml.crypto.KeyStoreCredentialProvider.(KeyStoreCredentialProvider.java:90)}} \ { \ { at org.pac4j.saml.client.SAML2Client.initCredentialProvider(SAML2Client.java:174)}} \ { \ { at org.pac4j.saml.client.SAML2Client.internalInit(SAML2Client.java:111)}} \ { \ { at org.pac4j.core.util.InitializableWebObject.init(InitializableWebObject.java:24)}} \ { \ { at org.jenkinsci.plugins.saml.OpenSAMLWrapper.createSAML2Client(OpenSAMLWrapper.java:145)}} \ { \ { at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:45)}} \ { \ { at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:30)}} \ { \ { at org.jenkinsci.plugins.saml.OpenSAMLWrapper.get(OpenSAMLWrapper.java:65)}} \ { \ { at org.jenkinsci.plugins.saml.SamlSecurityRealm.doCommenceLogin(SamlSecurityRealm.java:238)}} \ { \ { at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)}} \ { \ { at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)}} \ { \ { at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)}} \ { \ { at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)}} \ { \ { at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129)}} \ { \ { at
[JIRA] (JENKINS-49747) java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)
Title: Message Title
Coltrey Mather created an issue
Jenkins / JENKINS-49747
java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)
Issue Type:
New Feature
Assignee:
Ivan Fernandez Calvo
Components:
saml-plugin
Created:
2018-02-26 15:31
Priority:
Minor
Reporter:
Coltrey Mather
I'm not sure why /tmp/saml-jenkins-keystore-5345145658381646927.jks ceased to exist (it was created/working and there have been no system restarts or Jenkins restarts). I have no log or any way of finding out what caused that file to be removed. That said - because this file is created by the saml plugin/pac4j, if it does not exist and Jenkins needs it - it should be re-created. This error prevented users from authenticating and was fixed by a restart of Jenkins. java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory) {{ at java.io.FileInputStream.open0(Native Method)}} {{ at java.io.FileInputStream.open(FileInputStream.java:195)}} {{ at java.io.FileInputStream.(FileInputStream.java:138)}} {{ at java.io.FileInputStream.(FileInputStream.java:93)}} {{ at org.pac4j.core.util.CommonHelper.newFileInputStream(CommonHelper.java:312)}} Caused: org.pac4j.core.exception.TechnicalException {{ at org.pac4j.core.util.CommonHelper.newFileInputStream(CommonHelper.java:314)}} {{ at org.pac4j.core.util.CommonHelper.getInputStreamFromName(CommonHelper.java:304)}} {{ at org.pac4j.core.util.CommonHelper$1.getInputStream(CommonHelper.java:348)}} {{ at org.pac4j.saml.crypto.KeyStoreCredentialProvider.(KeyStoreCredentialProvider.java:66)}} {{ at org.pac4j.saml.crypto.KeyStoreCredentialProvider.(KeyStoreCredentialProvider.java:90)}} {{ at org.pac4j.saml.client.SAML2Client.initCredentialProvider(SAML2Client.java:174)}} {{ at org.pac4j.saml.client.SAML2Client.internalInit(SAML2Client.java:111)}} {{ at org.pac4j.core.util.InitializableWebObject.init(InitializableWebObject.java:24)}} {{ at
[JIRA] (JENKINS-43178) Can't send email to unknown email address
Title: Message Title
Coltrey Mather updated an issue
Jenkins / JENKINS-43178
Can't send email to unknown email address
Change By:
Coltrey Mather
Comment:
-Setting -Dhudson.tasks.MailSender.SEND_TO_UNKNOWN_USERS=true also seems to have no impact.- Setting hudson.tasks.MailSender.SEND_TO_USERS_WITHOUT_READ=true also seems to have no impact. I set this using the script console and later builds did not seem to pick it up. {code:java}System.setProperty("hudson.tasks.MailSender.SEND_TO_USERS_WITHOUT_READ", "true"){code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43178) Can't send email to unknown email address
Title: Message Title
Coltrey Mather edited a comment on JENKINS-43178
Re: Can't send email to unknown email address
- Setting -Dhudson.tasks.MailSender.SEND_TO_UNKNOWN_USERS=true also seems to have no impact. - jenkins 22399 1846 1 07:00 ? 00:06:38 java -Djenkins Setting hudson . install.runSetupWizard=false -Dhudson. tasks.MailSender. SEND_TO_UNKNOWN_USERS SEND_TO_USERS_WITHOUT_READ =true -jar jenkins also seems to have no impact . war --httpPort=8080 --httpListenAddress=127 I set this using the script console and later builds did not seem to pick it up . 0 {code:java}System . 0 setProperty("hudson . 1 tasks.MailSender.SEND_TO_USERS_WITHOUT_READ", "true"){code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43178) Can't send email to unknown email address
Title: Message Title Coltrey Mather commented on JENKINS-43178 Re: Can't send email to unknown email address Setting -Dhudson.tasks.MailSender.SEND_TO_UNKNOWN_USERS=true also seems to have no impact. jenkins 22399 1846 1 07:00 ? 00:06:38 java -Djenkins.install.runSetupWizard=false -Dhudson.tasks.MailSender.SEND_TO_UNKNOWN_USERS=true -jar jenkins.war --httpPort=8080 --httpListenAddress=127.0.0.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42394) Error loading shared library (404 on BitBucket) during a replay of a previous build
Title: Message Title Coltrey Mather updated an issue Jenkins / JENKINS-42394 Error loading shared library (404 on BitBucket) during a replay of a previous build Change By: Coltrey Mather Component/s: bitbucket-branch-source-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41907) Evaluate to obtain IdP Metadata from URL
Title: Message Title Coltrey Mather commented on JENKINS-41907 Re: Evaluate to obtain IdP Metadata from URL +1 - Azure AD supports this and their metadata changes occasionally, requiring a manual update to the metadata xml (and an outage for users until that update happens). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31804) Jenkins tells ec2 to spin up a node, aws spins up the node, but hudson/jenkins slave service never gets the memo and builds hang
Title: Message Title Coltrey Mather commented on JENKINS-31804 Re: Jenkins tells ec2 to spin up a node, aws spins up the node, but hudson/jenkins slave service never gets the memo and builds hang For those of you who are terminating nodes manually, you can add something like this to your slave init script - it'll add a cron entry to shutdown if slave.jar isn't around. (crontab -l 2>/dev/null; echo "*/5 * * * * sleep 120 ; ps -ef|grep -v grep|grep slave.jar >&1 > /dev/null || sudo -n shutdown -h now") | crontab - Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather commented on JENKINS-37289 Re: authentication issue instant is too old or in the future Based on Andrew's comment, we can re-resolve this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather commented on JENKINS-37289 Re: authentication issue instant is too old or in the future Ivan Fernandez Calvo That has been my issue in the past (although I still have users who need to clear their login cookies every 2-3 weeks or so). Specifically with Azure, it seems like the idp metadata is changing (possibly without notice) every few months. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather commented on JENKINS-37289 Re: authentication issue instant is too old or in the future Andrew Conti If you go into private browsing mode (clear all cookies) and still can't login, double-check that the idp metadata hasn't changed on the Azure side. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40786) s3 plugin PR-94 breaks pipeline step() usage
Title: Message Title Coltrey Mather commented on JENKINS-40786 Re: s3 plugin PR-94 breaks pipeline step() usage I have confirmed your test results on my test system as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40786) s3 plugin PR-94 breaks pipeline step() usage
Title: Message Title
Coltrey Mather created an issue
Jenkins / JENKINS-40786
s3 plugin PR-94 breaks pipeline step() usage
Issue Type:
Bug
Assignee:
Alexander A
Components:
s3-plugin
Created:
2017/Jan/03 9:40 PM
Priority:
Major
Reporter:
Coltrey Mather
See comments at: https://github.com/jenkinsci/s3-plugin/pull/94 here's a an example and a stack trace, and I realize this comment might be on the wrong commit thread, but I think when the constructor was changed, it broke compatibility. Downgrading to 0.10.9 from 0.10.11 solved the issue (also I have more recently confirmed that 0.10.10 was also working). When I was troubleshooting, I pulled up the syntax generator and it looked like some things may've changed...: Here's a minimal example for a pipeline script, just set BUCKET to something the "jenkins_bucket" s3 publisher profile is authorized to write.
node() {
BUCKET="some_test_bucket/path/test/"
sh 'touch foo'
step([$class: 'S3BucketPublisher',
dontWaitForConcurrentBuildCompletion: false,
entries: [[bucket: $BUCKET,
excludedFile: '',
flatten: true,
gzipFiles: false,
keepForever: false,
managedArtifacts: false,
noUploadOnFailure: false,
selectedRegion: 'us-east-1',
showDirectlyInBrowser: false,
sourceFile: 'foo',
storageClass: 'STANDARD',
uploadFromSlave: false,
useServerSideEncryption: false]],
profileName: 'jenkins_bucket',
userMetadata: []
])
}
This is the 0.10.11 syntax generator example, the generated values for consoleLogLEvel and pluginFailureResultConstraint are one of the things that made me question the constructor change:
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather resolved as Fixed Jenkins / JENKINS-37289 authentication issue instant is too old or in the future Change By: Coltrey Mather Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather commented on JENKINS-37289 Re: authentication issue instant is too old or in the future Adjusting the max lifetime to 864000 seems to be working for now. Thank you. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather edited a comment on JENKINS-37289 Re: authentication issue instant is too old or in the future I'm using Azure AD and have read that Azure AD auth tokens last 1 hour and refresh tokens last 24 hours, SAML Max lifetime is set to default (24*60*60 = 86400) I'll try 7776000 - if this is too high, will it cause other problems? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather commented on JENKINS-37289 Re: authentication issue instant is too old or in the future I'm using Azure AD and have read that Azure AD auth tokens last 1 hour and refresh tokens last 24 hours, SAML Max lifetime is set to default (24*60*60 = 86400) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather edited a comment on JENKINS-37289 Re: authentication issue instant is too old or in the future I installed 0.12 and received the same message today...log below.Oct 04, 2016 1:47:02 PM SEVERE org.pac4j.saml.sso.Saml2ResponseValidator validateSamlSSOResponseCurrent assertion validation failed, continue with the next oneorg.pac4j.saml.exceptions.SamlException: Authentication issue instant is too old or in the future at org.pac4j.saml.sso.Saml2ResponseValidator.validateAuthenticationStatements(Saml2ResponseValidator.java:469) at org.pac4j.saml.sso.Saml2ResponseValidator.validateAssertion(Saml2ResponseValidator.java:250) at org.pac4j.saml.sso.Saml2ResponseValidator.validateSamlSSOResponse(Saml2ResponseValidator.java:161) at org.pac4j.saml.sso.Saml2ResponseValidator.validateSamlResponse(Saml2ResponseValidator.java:103) at org.pac4j.saml.client.Saml2Client.retrieveCredentials(Saml2Client.java:324) at org.pac4j.saml.client.Saml2Client.retrieveCredentials(Saml2Client.java:95) at org.pac4j.core.client.BaseClient.getCredentials(BaseClient.java:211) at org.jenkinsci.plugins.saml.SamlSecurityRealm.doFinishLogin(SamlSecurityRealm.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:196) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:49) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:44) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:106) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:44) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather commented on JENKINS-37289 Re: authentication issue instant is too old or in the future I installed 0.12 and received the same message today...log below. Oct 04, 2016 1:47:02 PM SEVERE org.pac4j.saml.sso.Saml2ResponseValidator validateSamlSSOResponse Current assertion validation failed, continue with the next one org.pac4j.saml.exceptions.SamlException: Authentication issue instant is too old or in the future at org.pac4j.saml.sso.Saml2ResponseValidator.validateAuthenticationStatements(Saml2ResponseValidator.java:469) at org.pac4j.saml.sso.Saml2ResponseValidator.validateAssertion(Saml2ResponseValidator.java:250) at org.pac4j.saml.sso.Saml2ResponseValidator.validateSamlSSOResponse(Saml2ResponseValidator.java:161) at org.pac4j.saml.sso.Saml2ResponseValidator.validateSamlResponse(Saml2ResponseValidator.java:103) at org.pac4j.saml.client.Saml2Client.retrieveCredentials(Saml2Client.java:324) at org.pac4j.saml.client.Saml2Client.retrieveCredentials(Saml2Client.java:95) at org.pac4j.core.client.BaseClient.getCredentials(BaseClient.java:211) at org.jenkinsci.plugins.saml.SamlSecurityRealm.doFinishLogin(SamlSecurityRealm.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:196) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:49) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:44) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:106) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:44) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather updated an issue Jenkins / JENKINS-37289 authentication issue instant is too old or in the future Change By: Coltrey Mather Environment: Jenkins 2.17 with saml-plugin 0. 6 12 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather reopened an issue Jenkins / JENKINS-37289 authentication issue instant is too old or in the future Change By: Coltrey Mather Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather updated an issue Jenkins / JENKINS-37289 authentication issue instant is too old or in the future Change By: Coltrey Mather Environment: Jenkins 2.17 with saml-plugin 0.12 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather commented on JENKINS-37289 Re: authentication issue instant is too old or in the future Denys Digtiar Ben sent an email asking for this to be re-assigned, but I don't see another clear owner in the docs/commit history. Any suggestions? Thank you. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather commented on JENKINS-37289 Re: authentication issue instant is too old or in the future Thank you. Ben McCann do you have a release schedule for this plugin? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather commented on JENKINS-37289 Re: authentication issue instant is too old or in the future The link looks like a fix for how logging works - does this mean that logging preempts the authentication and shows an error instead of actually acknowledging authentication? Both sides of that commit call client.setMaximumAuthenticationLifetime(this.maximumAuthenticationLifetime);, which seems to be the good stuff... Is there a release that includes this fix? Last official was 7/29, so wouldn't include that commit. Is there a release schedule for the plugin? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36047) Read users do not have permission to view Snippet Generator and Step Reference
Title: Message Title Coltrey Mather commented on JENKINS-36047 Re: Read users do not have permission to view Snippet Generator and Step Reference Jesse Glickv hudson.model.Item.ExtendedRead is what I gave in config.xml, not Item.VIEW_CONFIGURATION. Not sure if it's just a terminology thing, but the source was definitely checking for hudson.model.Item.ExtendedRead Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36307) "Can not read hook payload" exception whenever a hook is received
Title: Message Title Coltrey Mather commented on JENKINS-36307 Re: "Can not read hook payload" exception whenever a hook is received Antonio Muñiz Any estimate on a release date? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title
Coltrey Mather commented on JENKINS-34958
Re: Getting "Your Authorization Token has expired" when using ECR credentials
For my pipeline scripts, I've been using get-login before every call that needs it and haven't seen this issue. However, I'm not using the ecr plugin and I am using the machine IAM role for authentication/authorization. ex: sh "`aws ecr get-login --region $ {region} ` && docker push $ {tag} "
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Coltrey Mather commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Any ETA on fixing the delete issue? Deleting all the build history when there's a transient bitbucket error is impacting me as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather updated an issue Jenkins / JENKINS-37289 authentication issue instant is too old or in the future Change By: Coltrey Mather Attachment: SAMLException.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather created an issue Jenkins / JENKINS-37289 authentication issue instant is too old or in the future Issue Type: Bug Assignee: Ben McCann Components: saml-plugin Created: 2016/Aug/09 7:57 PM Environment: Jenkins 2.17 with saml-plugin 0.6 Labels: SAML2 ServiceProvider Priority: Major Reporter: Coltrey Mather Authenticating with Azure AD (cloud-only) returns: "authentication issue instant is too old or in the future" in the Jenkins log. I've read that Azure AD auth tokens last 1 hour and refresh tokens last 24 hours, SAML Max lifetime is set to default (24*60*60 = 86400) Add Comment
[JIRA] (JENKINS-36047) Read users do not have permission to view Snippet Generator and Step Reference
Title: Message Title Coltrey Mather edited a comment on JENKINS-36047 Re: Read users do not have permission to view Snippet Generator and Step Reference I've Validated that granting the ExtendedRead permission grants the access needed to view the snippet generator wuthout without having additional access to modify the job configuration (although, they can view job config). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36047) Read users do not have permission to view Snippet Generator and Step Reference
Title: Message Title Coltrey Mather commented on JENKINS-36047 Re: Read users do not have permission to view Snippet Generator and Step Reference I've Validated that granting the ExtendedRead permission grants the access needed to view the snippet generator wuthout having additional access to modify the job configuration (although, they can view job config). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36047) Read users do not have permission to view Snippet Generator and Step Reference
Title: Message Title Coltrey Mather commented on JENKINS-36047 Re: Read users do not have permission to view Snippet Generator and Step Reference Looking through the Snippetizer source, it looks like https://wiki.jenkins-ci.org/display/JENKINS/Extended+Read+Permission+Plugin may be the solution. I'll be testing it this week. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36307) "Can not read hook payload" exception whenever a hook is received
Title: Message Title Coltrey Mather commented on JENKINS-36307 Re: "Can not read hook payload" exception whenever a hook is received Antonio Muñiz I see that PR-10 has been merged. Do you have an estimate on when you'll release? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34644) Stage View Shows Excessively Long Full Run Time Figures
Title: Message Title Coltrey Mather commented on JENKINS-34644 Re: Stage View Shows Excessively Long Full Run Time Figures Sam, does it require a build for the stage view avg time to update? I'm running 2.6 now and still see a branch with a ~2y avg build time, but I haven't build since the new version was installed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36307) "Can not read hook payload" exception whenever a hook is received
Title: Message Title Coltrey Mather commented on JENKINS-36307 Re: "Can not read hook payload" exception whenever a hook is received Antonio Muñiz Can you tell me when this fix will be released? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34644) Stage View Shows Excessively Long Full Run Time Figures
Title: Message Title
Coltrey Mather commented on JENKINS-34644
Re: Stage View Shows Excessively Long Full Run Time Figures
Sam Van Oort This is a multibranch pipeline, so maybe it's different ... but this just gives me an NPE...I've verified that this is a build number with a negative durationMillis and pauseDurationMillis Jenkins.instance.getItem('p-j-d/master').getBuildByNumber(25).execution.currentHeads.get(0).actions
java.lang.NullPointerException: Cannot invoke method getBuildByNumber() on null object
at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:91)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:35)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
at Script1.run(Script1.groovy:1)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:585)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:623)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:594)
at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:142)
at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:114)
at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
at hudson.util.RemotingDiagnostics.executeGroovy(RemotingDiagnostics.java:111)
at jenkins.model.Jenkins._doScript(Jenkins.java:4043)
at jenkins.model.Jenkins.doScript(Jenkins.java:4015)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)
at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:49)
at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:44)
at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:106)
at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:44)
at
[JIRA] (JENKINS-34644) Stage View Shows Excessively Long Full Run Time Figures
Title: Message Title Coltrey Mather commented on JENKINS-34644 Re: Stage View Shows Excessively Long Full Run Time Figures For complete-ishness, here's 100.xml: "workflow-support@2.1"> "org.jenkinsci.plugins.workflow.cps.nodes.StepAtomNode" plugin="workflow-cps@2.3"> 99 100 org.jenkinsci.plugins.workflow.steps.SleepStep "workflow-api@2.1"> 1467300509547 I think the answer is yes: [root@jenkins-master1 workflow]# grep TimingAction -A1 * 100.xml:"workflow-api@2.1"> 100.xml- 1467300509547 100.xml: 100.xml- -- 101.xml:"workflow-api@2.1"> 101.xml- 1467300569571 101.xml: 101.xml- -- 102.xml:"workflow-api@2.1"> 102.xml- 1467300570898 102.xml: 102.xml- -- 103.xml:"workflow-api@2.1"> 103.xml- 1467300570899 103.xml: 103.xml- -- 104.xml:"workflow-api@2.1"> 104.xml- 1467300570900 104.xml: 104.xml- -- 105.xml:"workflow-api@2.1"> 105.xml- 1467300630933 105.xml: 105.xml- -- 106.xml:"workflow-api@2.1"> 106.xml- 1467300632244 106.xml: 106.xml- -- 107.xml:"workflow-api@2.1"> 107.xml- 1467300632244 107.xml: 107.xml- -- 108.xml:"workflow-api@2.1"> 108.xml- 1467300632245 108.xml: 108.xml- -- 109.xml:"workflow-api@2.1"> 109.xml- 1467300634605 109.xml: 109.xml- -- 10.xml:"workflow-api@2.1"> 10.xml- 1467299613477 10.xml: 10.xml- -- 110.xml:"workflow-api@2.1"> 110.xml- 1467300634606 110.xml: 110.xml- -- 111.xml:"workflow-api@2.1"> 111.xml- 1467300646581 111.xml: 111.xml- -- 112.xml:"workflow-api@2.1"> 112.xml- 1467300646587 112.xml: 112.xml- -- 113.xml:"workflow-api@2.1"> 113.xml- 1467300646624 113.xml: 113.xml- -- 114.xml:"workflow-api@2.1"> 114.xml- 1467300646688 114.xml: 114.xml- -- 115.xml:"workflow-api@2.1"> 115.xml- 1467300646745 115.xml: 115.xml- -- 11.xml:"workflow-api@2.1"> 11.xml- 1467299613478 11.xml: 11.xml- -- 12.xml:"workflow-api@2.1"> 12.xml- 1467299613479 12.xml: 12.xml- -- 13.xml:"workflow-api@2.1"> 13.xml- 1467299614366 13.xml: 13.xml- -- 14.xml:"workflow-api@2.1"> 14.xml- 1467299614605 14.xml: 14.xml- -- 15.xml:"workflow-api@2.1"> 15.xml- 1467299614605 15.xml: 15.xml- -- 16.xml:"workflow-api@2.1"> 16.xml- 1467299615321 16.xml: 16.xml- -- 17.xml:"workflow-api@2.1"> 17.xml- 1467299615960 17.xml: 17.xml- -- 18.xml:"workflow-api@2.1"> 18.xml- 1467299615961 18.xml: 18.xml- -- 19.xml:"workflow-api@2.1"> 19.xml- 1467299615962 19.xml: 19.xml- -- 20.xml:"workflow-api@2.1"> 20.xml- 1467299615962 20.xml: 20.xml- -- 21.xml:"workflow-api@2.1"> 21.xml- 1467299616246 21.xml: 21.xml- -- 22.xml:"workflow-api@2.1"> 22.xml- 1467299680467 22.xml: 22.xml- -- 23.xml:"workflow-api@2.1"> 23.xml- 1467299951871 23.xml: 23.xml- -- 24.xml:"workflow-api@2.1"> 24.xml- 1467300121319 24.xml: 24.xml- -- 25.xml:"workflow-api@2.1"> 25.xml- 1467300121337 25.xml:
[JIRA] (JENKINS-34644) Stage View Shows Excessively Long Full Run Time Figures
Title: Message Title Coltrey Mather commented on JENKINS-34644 Re: Stage View Shows Excessively Long Full Run Time Figures It does not include parallel structures, but it is in a finally block. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34644) Stage View Shows Excessively Long Full Run Time Figures
Title: Message Title
Coltrey Mather commented on JENKINS-34644
Re: Stage View Shows Excessively Long Full Run Time Figures
j smith asked me to add this - this is one branch in a pipeline multibranch job:
[{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/wfapi/describe"
},
"changesets": {
"href": "/job/p-c-b/job/PSAE-61/4/wfapi/changesets"
},
"artifacts": {
"href": "/job/p-c-b/job/PSAE-61/4/wfapi/artifacts"
}
},
"id": "4",
"name": "#4",
"status": "SUCCESS",
"startTimeMillis": 1467303127055,
"endTimeMillis": 1467303874774,
"durationMillis": 742082,
"queueDurationMillis": 5637,
"pauseDurationMillis": 0,
"stages": [{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/11/wfapi/describe"
}
},
"id": "11",
"name": "Clean workspace",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303132692,
"durationMillis": 1061,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/14/wfapi/describe"
}
},
"id": "14",
"name": "Checkout source",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303133753,
"durationMillis": 1877,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/17/wfapi/describe"
}
},
"id": "17",
"name": "Build App",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303135630,
"durationMillis": 189881,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/27/wfapi/describe"
}
},
"id": "27",
"name": "Package Cookbook",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303325511,
"durationMillis": 23010,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/36/wfapi/describe"
}
},
"id": "36",
"name": "Publish to S3",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303348521,
"durationMillis": 5144,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/39/wfapi/describe"
}
},
"id": "39",
"name": "Archive site",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303353665,
"durationMillis": 2667,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/45/wfapi/describe"
}
},
"id": "45",
"name": "Opsworks auto deployment",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303356332,
"durationMillis": 314976,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/87/wfapi/describe"
}
},
"id": "87",
"name": "Test",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303671308,
"durationMillis": 1951,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/93/wfapi/describe"
}
},
"id": "93",
"name": "Opsworks Tear Down",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303673259,
"durationMillis": 201515,
"pauseDurationMillis": 0
}]
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/3/wfapi/describe"
},
"changesets": {
"href": "/job/p-c-b/job/PSAE-61/3/wfapi/changesets"
},
"artifacts": {
[JIRA] (JENKINS-36307) "Can not read hook payload" exception whenever a hook is received
Title: Message Title Coltrey Mather commented on JENKINS-36307 Re: "Can not read hook payload" exception whenever a hook is received I also get this error when bitbucket is triggering a web-hook for a created pull request. Push triggers are received and work fine, PRs are not. Bitbucket cloud Jenkins v2.11 bitbucket-branch-source-plugin v1.5 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-28156) Add support for executing HP Performance Center rest calls on build slave in master/slave environment
Title: Message Title Coltrey Mather commented on JENKINS-28156 Re: Add support for executing HP Performance Center rest calls on build slave in master/slave environment I issues this pull request: https://github.com/hpsa/hp-application-automation-tools-plugin/pull/26 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-28156) Add support for executing HP Performance Center rest calls on build slave in master/slave environment
Title: Message Title Coltrey Mather edited a comment on JENKINS-28156 Re: Add support for executing HP Performance Center rest calls on build slave in master/slave environment I issues issued thispullrequest:https://github.com/hpsa/hp-application-automation-tools-plugin/pull/26 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-28156) Add support for executing HP Performance Center rest calls on build slave in master/slave environment
Title: Message Title Coltrey Mather commented on JENKINS-28156 Re: Add support for executing HP Performance Center rest calls on build slave in master/slave environment I see. I'll fork hpsa, make changes and make a pull request. FYI The jenkinsci is still the repo in the github link at https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools 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-28156) Add support for executing HP Performance Center rest calls on build slave in master/slave environment
Title: Message Title Coltrey Mather commented on JENKINS-28156 Re: Add support for executing HP Performance Center rest calls on build slave in master/slave environment Avishai Moshka Although taking a different approach than I did in the files attached here, I did create a pull request - https://github.com/jenkinsci/hp-application-automation-tools-plugin/pull/1 I also think that's broken, 'though, even 'though it passed all tests - I'm not really a good developer and when I load the hpi I build, it doesn't show the hp options in the config pages, but I see no errors during install or anything like that. I'd appreciate someone experienced to look at it and see what I've done wrong. diffs here: https://github.com/jenkinsci/hp-application-automation-tools-plugin/pull/1/files 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-28156) Add support for executing HP Performance Center rest calls on build slave in master/slave environment
Coltrey Mather created JENKINS-28156 Add support for executing HP Performance Center rest calls on build slave in master/slave environment Issue Type: New Feature Assignee: Ofir Shaked Attachments: config.jelly, PcBuilderOnSlave.java, PcModelOnSlave.java Components: hp-application-automation-tools-plugin Created: 29/Apr/15 1:23 PM Description: In order to support network zoning restrictions, please implement functionality to execute performance center rest calls on the build slave. I have attached an implementation of this that extends the PCBuilder class, although I'm not sure it's complete or meets your standards. If you have advice on what else needs to be done, please tell me. Project: Jenkins Priority: Minor Reporter: Coltrey Mather This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
