The boost-tasks repo from Daniel James included a script release-from-bintray which was used to deploy an archive from bintray to the website. Changing from bintray to artifactory, the "created" timestamp metadata field was used by the earlier script, and should be provided. To solve that, adding a "created" field to the archive's json file, which is a logical place to store the information, alongside the sha hash and commit.
Another small update also: when running ci_boost_release.py multiple times during testing, the program will crash if the destination folder is present. Let's rename the previous folder to ".bck", and continue to create a new bundle, without crashing.
The boost-tasks repo from Daniel James included a script release-from-bintray which was used to deploy an archive from bintray to the website. Changing from bintray to artifactory, the "created" timestamp metadata field was used by the earlier script, and should be provided. To solve that, adding a "created" field to the archive's json file, which is a logical place to store the information, alongside the sha hash and commit.
Another small update also: when running ci_boost_release.py multiple times during testing, the program will crash if the destination folder is present. Let's rename the previous folder to ".bck", and continue to create a new bundle, without crashing.