New plugin has the same error

[ksondere]

Downloaded the new plugin and verified the new username and password fields were in place.

Then ran the plugin and it failed with the same error.

xception during execution: javax.script.ScriptException: java.lang.RuntimeException: java.lang.RuntimeException: A 'Run automated tasks as user' and 'Password' properties has to be set in order to use XL Release's API in <script> at line number 3

[zvercodebender]

Which task threw this error? Was it one of the bamboo task such as:

• RunPlan
• TriggerDeployment

[ksondere]

TriggerDeployment

…

On Wed, Sep 18, 2019 at 4:52 PM Rick Broker ***@***.***> wrote: Which task threw this error? Was it one of the bamboo task such as: - RunPlan - TriggerDeployment — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7?email_source=notifications&email_token=AAAUOAQMQRROXNLIJD4HAI3QKKWMFA5CNFSM4IYCEYAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7BV2BI#issuecomment-532897029>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAUOAXZ2XS6G3M2SLTYQWDQKKWMFANCNFSM4IYCEYAA> .

[zvercodebender]

The is strange... The error you reported

A 'Run automated tasks as user' and 'Password' properties has to be set in order to use XL Release's API 

is not directly related to that task, but to the RunAs property in the Release or Template. Can you please try setting the RunAs property and try again. Let me know if you are still getting the same error.

[ksondere]

The problem I have is this. If I set the RunAs property in the template, then all of my other automated tasks fail because this overriddes the shared setting connecton property on them. So...in order function like the other automated plugins I've asked that this plugin also use the shared settings connection credentials. If I set the RunAs property then this negates the effort that was just made to add username and password to this plugin.

…

On Thu, Sep 19, 2019 at 7:39 AM Rick Broker ***@***.***> wrote: The is strange... The error you reported A 'Run automated tasks as user' and 'Password' properties has to be set in order to use XL Release's API is not directly related to that task, but to the RunAs property in the *Release* or *Template*. Can you please try setting the RunAs property and try again. Let me know if you are still getting the same error. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7?email_source=notifications&email_token=AAAUOASQ55VOSEOPDGUUUCDQKN6JLA5CNFSM4IYCEYAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7DP6VY#issuecomment-533135191>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAUOAWPFZFA5RNPMKO33DTQKN6JLANCNFSM4IYCEYAA> .

[zvercodebender]

Would it be possible to create another template that only has the bamboo.TriggerDeployment task and run that to verify that this will recreate the same issue?

[ksondere]

Sure I can do that

[ksondere]

I should mention that this actually by itself won't create the same issue because it's the other automated plugins that fail as soon as I set the RunAs property

[ksondere]

hmm ok, this actually did get further. I did not set the loginAs property, just used the shared credentials.

And this was my log output

Executing triggerBambooDeployment.py

Executing getProjectId() with projectName Service - Auth

Executing getEnvironmentId() with projectId 71565314 and environmentName XL-Release QA

Executing getVersionId() with projectId 71565314 and versionName 3.1.0.222

Executing triggerDeployment() with environmentId 79134733 and versionId 166691471

Exception during execution: KeyError: 'deploymentResultId' in <script> at line number 64

[zvercodebender]

Can you look in Bamboo to see if a deployment was started? Also could you verify that the Deployment job is enabled?

[ksondere]

So I've tested and run the deployment job independant of this and it's working. I then run this and it does not start the deployment job.

[zvercodebender]

Are you starting the job from XL Release with the same user that you are starting the job from the UI? Is there any error in the XL Release log?