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
馃敀 Read Signing Key Id and 馃帄 Test & Version could be parallelised before 馃敀 Push Release Commit:
馃帄 Test & Version doesn't really need to know the GPG key id or email address, though it currently does make some commits, and that needs some email address.
A quick option to fix the issue might be to use a stub email address in 馃帄 Test & Version, though we would need to make sure that 馃敀 Push Release Commit ends up using the correct committer address if it's cherry-picking those commits from 馃帄 Test & Version.
A better option may be to switch from communicating between jobs using bare-git-repo, and instead just have 馃帄 Test & Version output just the crucial version number. The subsequent jobs do need to know which file to modify (ie version.sbt), how to construct the version tag (ie, add a v prefix) and also the snapshot version number of the next version.
The text was updated successfully, but these errors were encountered:
馃敀 Read Signing Key Id
and馃帄 Test & Version
could be parallelised before馃敀 Push Release Commit
:馃帄 Test & Version
doesn't really need to know the GPG key id or email address, though it currently does make some commits, and that needs some email address.A quick option to fix the issue might be to use a stub email address in
馃帄 Test & Version
, though we would need to make sure that馃敀 Push Release Commit
ends up using the correct committer address if it's cherry-picking those commits from馃帄 Test & Version
.A better option may be to switch from communicating between jobs using bare-git-repo, and instead just have
馃帄 Test & Version
output just the crucial version number. The subsequent jobs do need to know which file to modify (ie version.sbt), how to construct the version tag (ie, add av
prefix) and also the snapshot version number of the next version.The text was updated successfully, but these errors were encountered: