-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable propagate argument when triggering child job #1628
Conversation
Signed-off-by: Zelin Hao <zelinhao@amazon.com>
Codecov Report
@@ Coverage Diff @@
## main #1628 +/- ##
============================================
- Coverage 94.67% 94.53% -0.15%
Complexity 13 13
============================================
Files 163 163
Lines 3435 3437 +2
Branches 21 21
============================================
- Hits 3252 3249 -3
- Misses 180 185 +5
Partials 3 3
Continue to review full report at Codecov.
|
Instead add |
Great suggestion! That works from my testing. Working on the change. Thanks! |
Signed-off-by: Zelin Hao <zelinhao@amazon.com>
…rch-project#1628)" This reverts commit e0a34eb. Signed-off-by: Zelin Hao <zelinhao@amazon.com>
Signed-off-by: Zelin Hao zelinhao@amazon.com
Description
Currently our check-for-build jenkins job will fail if its child job fails, which also sends out failure notification. Disabled propagate argument will not propagate the results of child job and continue the workflow on the current job. This job only fails if there is an issue in check-for-build itself.
Issues Resolved
#1627
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.