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
Add a step to the build job which writes detail on the commit into a version.txt file. Put the file in the same folder as the output (derived object) from the Maven (or Gradle) build process.
Discuss (make notes)
Which commit?
Should you record the commit on the issue branch?
...or the commit you committed earlier on the master branch?
how are they different?
how about making a note on both?
Is there something you can do - to ensure (guarantee) that the two branches are always pointing to same commit?
Add a step that uploads (all) the derived objects as artifacts.
The text was updated successfully, but these errors were encountered:
build
job which writes detail on the commit into aversion.txt
file. Put the file in the same folder as the output (derived object) from the Maven (or Gradle) build process.master
branch?The text was updated successfully, but these errors were encountered: