You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, jobs that have dependency on a previous job use the 'dependencies' flag with dependent job name as value. However, it is seen that these jobs are skipped if the previous stage (in which the dependent job has passed, but some other jobs have failed) has a failure. One of the ways to address this is to use the 'always' directive which will run the job dependencies notwithstanding.
However, what is really needed is a combination of the above, where stage failures should be ignored but dependent job status considered for execution of a current job.
The text was updated successfully, but these errors were encountered:
Currently, jobs that have dependency on a previous job use the 'dependencies' flag with dependent job name as value. However, it is seen that these jobs are skipped if the previous stage (in which the dependent job has passed, but some other jobs have failed) has a failure. One of the ways to address this is to use the 'always' directive which will run the job dependencies notwithstanding.
However, what is really needed is a combination of the above, where stage failures should be ignored but dependent job status considered for execution of a current job.
The text was updated successfully, but these errors were encountered: