mirror of https://gerrit.osmocom.org/osmo-ci
Make sure that each time osmocom-nightly-packages.sh and osmocom-next-packages.sh runs, we get a different date appended to the versions, even if it runs twice on the same day (e.g. because the jenkins job was triggered manually). This is in preparation to let all packages depend on a specific version (with that date) of the conflicting dummy package. DT in osmocom-latest-packages.sh is adjusted for consistency (though it is not appended to the package versions, only used in the commit message when pushing the latest packages). Related: OS#4733 Change-Id: I7f08c694a549f1b3dd938a68e05082f2c31fdb92 |
||
---|---|---|
.. | ||
osmo-depcheck | ||
repo-install-test | ||
cat-testlogs.sh | ||
common-obs-conflict.sh | ||
common-obs.sh | ||
common.sh | ||
docker-cleanup.sh | ||
jenkins_jobs.ini.example | ||
osmo-build-dep.sh | ||
osmo-build.sh | ||
osmo-ci-docker-rebuild.sh | ||
osmo-clean-workspace.sh | ||
osmo-deps.sh | ||
osmo-layer1-headers.sh | ||
osmocom-build-old-tags-against-master.sh | ||
osmocom-latest-packages.sh | ||
osmocom-list-commits.sh | ||
osmocom-next-packages.sh | ||
osmocom-nightly-packages.sh | ||
osmocom-obs-link.sh | ||
osmocom-release-tarballs.sh | ||
repo-install-test.sh | ||
requirements.txt | ||
verify_log_statements.py | ||
verify_value_string_arrays_are_terminated.py |