[JIRA] [build-pipeline-plugin] (JENKINS-27238) Inject parameters on manual build trigger
Title: Message Title Ole Christian Langfjæran commented on JENKINS-27238 Re: Inject parameters on manual build trigger Not knowing the inner workings of the plugin, but is this doable in some way? Would be a an absolutely great feature. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
Title: Message Title Ole Christian Langfjæran commented on JENKINS-24750 Re: Cannot find user credentials when job is triggered with parameters I see and thanks for the reply! Is it strange that "Run as Specific User" still works ikedam? 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] [authorize-project-plugin] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
Title: Message Title Ole Christian Langfjæran updated an issue Jenkins / JENKINS-24750 Cannot find user credentials when job is triggered with parameters Change By: Ole Christian Langfjæran Component/s: authorize-project-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] [ssh-agent-plugin] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
Title: Message Title Ole Christian Langfjæran commented on JENKINS-24750 Re: Cannot find user credentials when job is triggered with parameters Me again. I must have made the last test (many months ago) wrong. That scenario only works if I set And job B uses Run as user 'Superman' And does not work when using "Run as user who triggered the build" The output of those two are the same, eg: Started by upstream project "jobA" build number 4 originally caused by: Started by user Superman Running as Superman But the latter fails with FATAL: [ssh-agent] Could not find specified credentials I'm guessing this is a Authorize plugin bug/problem and not ssh-agent 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-agent-plugin] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
Title: Message Title Ole Christian Langfjran commented on JENKINS-24750 Re: Cannot find user credentials when job is triggered with parameters Hello again. This is resolvable doing this: Given I have a job A And job A has Credentials Parameter named CREDENTIAL And job A triggers job B sending job A's parameters And job B has Credentials Parameter named CREDENTIAL And job B uses ssh-agent And job B gets the chosen credential from Parameter _expression_ And job B uses Authorize Project plugin And job B uses Run as user who triggered the build When I build job A And choose a credential from logged in user Then job B should find the credentials This seems to work fine 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] [authorize-project] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
Ole Christian Langfjæran commented on JENKINS-24750 Cannot find user credentials when job is triggered with parameters Jenkins: 1.580 Parameterized trigger: 2.25 SSH-Agent: 1.5 Authorize project: 1.0.3 If I uncheck "Configure Build Authorization" then it fails with the same output. But of course this time the "Running as Superman" is not printed/run. I could elaborate on why I'd like it to work. Every developer has his own public ssh-key on app-servers Every developer adds his private key to his user When promoting a build the developer must choose a valid ssh-private-key This key is sent to a deploy job Ssh-agent uses the deploy-key and voila. This works well for Global keys or if the deploy job itself is invoked by a logged in user. A workaround might be to restrict the number of users authorized to run the deploy job. 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.
[JIRA] [authorize-project] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
Ole Christian Langfjæran updated JENKINS-24750 Cannot find user credentials when job is triggered with parameters Change By: Ole Christian Langfjæran (23/Sep/14 7:43 AM) Component/s: authorize-project 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.
[JIRA] [authorize-project] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
Ole Christian Langfjæran commented on JENKINS-24750 Cannot find user credentials when job is triggered with parameters Sorry for the extremely late reply Daniel, but yes Parameterized Trigger plugin. Might be that this also is a Authorize Project problem. I have not taken a good look at the code running this and maybe Authorize project uses another form of authorizing than ssh-agent. 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.
[JIRA] [ssh-agent] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
Ole Christian Langfjæran created JENKINS-24750 Cannot find user credentials when job is triggered with parameters Issue Type: Bug Assignee: Unassigned Components: ssh-agent Created: 17/Sep/14 9:07 PM Description: Given I have a job A And job A has Credentials Parameter And job A triggers job B sending job A's parameters And job B has Credentials Parameter And job B uses ssh-agent And job B uses Authorize Project plugin And job B uses Run as user who triggered the build When I build job A And choose a credential from logged in user Then job B should find the credentials The result unfortunately is this: Started by upstream project "jobA" build number 4 originally caused by: Started by user Superman Running as Superman Building in workspace /app/jenkins/jobs/jobB/workspace FATAL: [ssh-agent] Could not find specified credentials [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Java/JNR ssh-agent [ssh-agent] Started. Project: Jenkins Priority: Major Reporter: Ole Christian Langfjæran 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.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Ole Christian Langfjæran commented on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects 1.3.4-SNAPSHOT is indeed bugged with the run button, the retry being the most importent one I think. https://issues.jenkins-ci.org/browse/JENKINS-11105. But passing parameters seems to work for me, unless i do a retry. Using 1.3.4-SNAPSHOT a new "Manual build other projects" is available. Can't remember the exact name as I'm on sickleave for a month from the project. But for the build that is manually triggered, the "triggering" project has to transfer the parameters to the build a second time. As an example if your manual build is a parameterized build with the parameter VERSION, you have to repeat it like so: VERSION=$VERSION Even if the first triggered build had the parameter with exact same name. At least, that's what I've experienced. Hope it helps, and hope a 1.3.4 version could be tagged and uploaded soon. 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/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18170) Remove issues on Github or stop using Jenkins Jira
Ole Christian Langfjæran created JENKINS-18170 Remove issues on Github or stop using Jenkins Jira Issue Type: Task Affects Versions: current Assignee: Unassigned Components: build-pipeline Created: 03/Jun/13 7:47 AM Description: It is confusing using when there's an Issues tab on Github, but issues are maintained here at Jenkins Jira That said I think many, many prefer Github Issues over Jira, so is it worth considering moving again? It would also do contributions and closing issues a whole lot easier. Fix Versions: current Project: Jenkins Priority: Minor Reporter: Ole Christian Langfjæran 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/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18170) Remove issues on Github or stop using Jenkins Jira
Ole Christian Langfjæran commented on JENKINS-18170 Remove issues on Github or stop using Jenkins Jira That said I would gladly help moving issues over to Github. 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/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Ole Christian Langfjæran commented on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects Have you tried using the 1.3.4-SNAPSHOT version? We are using it just to make Manual Parameterized builds available. Bugs on rerun, but otherwise works. Haven't tested on Parameterized downstream project though. But I would much like that a 1.3.4 version was commited with current code all the same. 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/groups/opt_out.
[JIRA] [matrix] (JENKINS-16521) Multi-Project Throttle Categories don't work with Matrix jobs
Ole Christian Langfjæran commented on JENKINS-16521 Multi-Project Throttle Categories dont work with Matrix jobs Same here. Version 1.72 and 1.513 of Jenkins. Is this, https://issues.jenkins-ci.org/browse/JENKINS-12240, supposed to fix it? It is included in version 1.72 according to commits. 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/groups/opt_out.
[JIRA] [matrix] (JENKINS-16521) Multi-Project Throttle Categories don't work with Matrix jobs
Ole Christian Langfjæran commented on JENKINS-16521 Multi-Project Throttle Categories dont work with Matrix jobs Update: Cloned tag 1.7.1 and installed and it seems to work using Category. Created a "Matrix-job" category using "Maximum Total Concurrent Build = 4" and "Maximum Concurrent Builds Per Node = 4". The job itself is configured with "Maximum Concurrent Builds Per Node = 1" and "Maximum Total Concurrent Build = 4". I am not using any slaves though. 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/groups/opt_out.
