Further uses #2
Replies: 4 comments 3 replies
|
That's brilliant. The new version with password encryption should help with that use case. I would expect we also may need a linux build. |
|
one can create a windows Jenkins instance, but they're probably not that common (at least in my org) anymore. |
|
Hi, Regards, |
|
Hi - I can reproduce that error when I don't select the correct Workday environment. Are you certain that your implementation tenant is in Portland (wd5)? Could your tenant be in another environment? |
|
Hi, My bad. Our implementation tenant is on https://impl.workday.com which is WD2. I have placed the screenshot of the tenant. I am not able to see WD2 on the selection option. Can you please help me on it? Regards, |
|
Try #7 - That is Atlanta (WD2).
…On Wed, May 25, 2022 at 6:42 AM vivekblackbaud ***@***.***> wrote:
Hi,
Our implementation tenant is on https://impl.workday.com which is WD2. I
have placed the screenshot of the tenant. Would you be able to add the
environment to the executable file?
[image: image]
<https://user-images.githubusercontent.com/92828617/170276467-6d49949e-0026-4d48-88aa-03b520466463.png>
Regards,
Vivek
—
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADE64GQSXZDPUO3IIEZ7TDVLYU4RANCNFSM5CQU2ZVA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Thank you so much for your help. It worked for me. |
Uh oh!
There was an error while loading. Please reload this page.
An important one would be to use a Jenkins instance to upload clars that have been added and/or updated via a GIT pull request. That would allow doing regression testing, peer review, and authorized installations. It would also allow someone to install a .clar even if they have no access to the Production tenant.
All reactions