use the nightly macro in the ForemanSourceStrategy (#3624)
previously tito would (via our ForemanSourceStrategy) generate versions like foreman-1.22.0-0.201903280802git97b75e70.8.develop.el7.src.rpm because it was prepending 0.<date>git<hash> to the %release macro
but `obal nightly` uses a special `nightly` macro to inject <date>git<hash> into %release.
because of this difference, different jobs would generate different version structures, resulting in nightly packages that can't be upgraded because ForemanSourceStrategy generated a newer version than `obal nightly`.
this commit adjusts ForemanSourceStrategy to also use the same method as `obal nightly`, resulting in foreman-1.22.0-0.8.develop.201903280802git97b75e70.el7.src.rpm for the above example
Added by Evgeni Golov about 5 years ago
use the nightly macro in the ForemanSourceStrategy (#3624)
previously tito would (via our ForemanSourceStrategy) generate versions
like foreman-1.22.0-0.201903280802git97b75e70.8.develop.el7.src.rpm
because it was prepending 0.<date>git<hash> to the %release macro
but `obal nightly` uses a special `nightly` macro to inject
<date>git<hash> into %release.
because of this difference, different jobs would generate different
version structures, resulting in nightly packages that can't be upgraded
because ForemanSourceStrategy generated a newer version than `obal
nightly`.
this commit adjusts ForemanSourceStrategy to also use the same method as
`obal nightly`, resulting in
foreman-1.22.0-0.8.develop.201903280802git97b75e70.el7.src.rpm for the
above example