-
When a build status along with a dropdown is used, it normally means that the outside status is an overall status, and dropdown displays the detailed information. However dropdown here violates that rule, and can be confusing.
Besides doing from files page, you can also run downstream job from commits view, which is more appropriate place as you can see all the commit messages and can be confident on what deployment you are doing against.
-
Maybe separating the dropdown from status icon can avoid the confusion. Something displayed as downstream jobs...
-
Previous Value Current Value empty 3.2.2
-
Previous Value Current Value View dropdown menu of all job in a the build view
Able to run downstream builds from build detail page
-
I see, thanks for you answer.
Side question : how a job is return as failed or success ?
In my CI Job, my dotnet project is built and so error can happen but the job return as success. What can i do to return as failed in theses cases ?
Thanks
-
It replies on return code of your job commands. Make sure to tune commands to return non-zero value if you want to fail the job
-
OneDev
changed state to 'Closed' 6 years ago
Previous Value Current Value Open
Closed
-
OneDev
changed state to 'Released' 6 years ago
Previous Value Current Value Closed
Released
Hi,
After a successful automated build job (ie: a CI), i want to deploy my project using the others jobs of the same project (ie: CD). From the build screen, i have to go in file and use the dropdown menu and run my job. If the dropdown menu were in the build screen, i could do it without changing page.
v3.2.0
my proposal
Thanks