Artifacts not showing up after restoring a deleted build configuration
Hi,
I have deleted by mistake one build configuration in my TeamCity environment. Afterwards, I recreated it successfully using the exact same name and settings.
Now, there is no information displayed on the "Build Configuration Home" view. It is completely empty. I can see that all the builds, that were previously executed (before I deleted my build configuration by mistake), are stored in the host machine hosting the TeamCity server under the following folder:
"../teamcity/data/system/<MY_PROJECT_NAME>/<MY_BUILD_CONFIGURATION_NAME>".
In the folder in question, I can see around 20 folders which are named based on its internal BuildID number. I checked their content and I could see that the published artifacts and the ".teamcity" folder containing the "logs", "properties" and "settigns" are there.
I am confident that "MY_BUILD_CONFIGURATION_NAME" and the build configuration settings that I recreated are exactly the same as they were before deleting by mistake my build configuration.
Question...
Could anyone, pIease, let me know if it is possible to get the build info of those approx. 20 builds showing up again in the "Overview", "History", etc. again?
I am running on TeamCity version 2019.1.3
Hope I described my issue accurately enough.
Thanks, in advance for your help.
Please sign in to leave a comment.
One way to restore removed build configuration would be to follow this instruction (https://youtrack.jetbrains.com/issue/TW-34774#focus=streamItem-27-1320528.0-0). I would like to point out that this would work only if there was no server-side cleanup yet (by default, we have a cleanup running daily at 3 AM server time).
One more thing to mention about artifacts is that TeamCity would follow a fairly simply logic regarding their location; i.e. let`s say you have a project named A, you have a build configuration for this project named Build_A, and by accident this configuration is removed. If you would check <DataStore>\system\artifacts\A\Build_A\, you could locate the folders named after build ID which do contain the artifact. However, if you would copy these files over to any existing build configuration (say, you have Checkout_A under project A, and you copy artifacts over to \A\Checkout_A\<some_build_id>), they would appear under that build. This, perchance, could prove useful in a sense that you could attach them to a first build ran on a newly-restored configuration and preserve artifact history in a way.
There is a feature request to allow a better restore functionality which I have just updated for reference (https://youtrack.jetbrains.com/issue/TW-34774).