You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 18, 2024. It is now read-only.
Describe the bug
Using sfpowerscript in a GitHub + Jenkins environment fails to push to the "changelog" when using generatechangelog
I can release except error w/ pushing to changeLog ; the internal system I am on checks the user's email (as valid) ... When I dug a bit deeper into this I noticed in changelog/ChangelogImpl.ts:pushChangelogToBranch sets the user.name to "sfpowerscripts" and user.email to "sfpowerscripts@dxscale" ... this is causing the failure.
Customer runs checkemail anytime a push occurs (not possible to disable)
To Reproduce
Steps to reproduce the behavior:
Using the latest DockerImage . Run script (bash) in Jenkins
Describe the bug
Using sfpowerscript in a GitHub + Jenkins environment fails to push to the "changelog" when using generatechangelog
I can release except error w/ pushing to changeLog ; the internal system I am on checks the user's email (as valid) ... When I dug a bit deeper into this I noticed in changelog/ChangelogImpl.ts:pushChangelogToBranch sets the user.name to "sfpowerscripts" and user.email to "sfpowerscripts@dxscale" ... this is causing the failure.
Customer runs checkemail anytime a push occurs (not possible to disable)
To Reproduce
Steps to reproduce the behavior:
Using the latest DockerImage . Run script (bash) in Jenkins
sfdx sfpowerscripts:orchestrator:release .... --generatechangelog --branchname changelog
Expected behavior
A clear and concise description of what you expected to happen.
Changelog with pushed release information
Screenshots
If applicable, add screenshots to help explain your problem.
Platform Details (please complete the following information):
Additional context
Add any other context about the problem here.
All is fine if I do not use --generatechangelog --branchname
The text was updated successfully, but these errors were encountered: