Status Based Artifacts
JetBrainsd71b228e-1183-4ed4-a002-fac49a3832bb · v—
Publish artifacts based on the build status
Rating distribution
Reviews 8
Download source, compile, install on server. That's all ! Then just Ctrl-X -> Ctrl-V the path to upload from general window to "Build Feature/Staus based artifact". If you need to upload some files when the step is failed, add a new build feature for this case. Very simple and you save many space on your TC server !
Now it's clear, thanks!
Not at all, if that were the case I wouldn't have written it! The plugin and the General Settings paths are two different things for two different purposes.
Do you mean that we need to remove the path in General configuration build settings? Otherwise this plugin is useless?
Ok, then why are we forced to specify the same "Artifact Path" a second time in this plugin?
If you're putting the same paths in General Settings and the plugin, then I'm afraid you're not using it correctly. The plugin makes a decision, based on the build status as illustrated, on whether or not to publish the artifacts you've specified in it. The General Settings page makes no such decision, and always publishes the artifacts you've asked it to (if they exist). Putting the same...
The paths in General Settings will always be published if they exist - the idea of this plugin is to *only* publish for either successful or failed builds. This way people can avoid saving files as artifacts that aren't actually needed, which is helpful if they're particularly large.
Thanks. Another question. Why should I define again the artifact path? I've specified it already in another place (build configuration General settings page).
Similar in “Build”
File Watchers
JetBrains
Bazel for IntelliJ (legacy)
JetBrains
Bazel
JetBrains
GitHub Actions Manager
d-software-inc
Gradle
JetBrains
Just
5f47aa04-3398-4eea-98f1-d27c0a115f9b