Skip to content
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

Merged
merged 2 commits into from
Feb 16, 2022

Conversation

zelinh
Copy link
Member

@zelinh zelinh commented Feb 15, 2022

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

  • Commits are signed per the DCO using --signoff

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.

Signed-off-by: Zelin Hao <zelinhao@amazon.com>
@zelinh zelinh requested a review from a team as a code owner February 15, 2022 22:02
@zelinh zelinh self-assigned this Feb 15, 2022
@codecov-commenter
Copy link

codecov-commenter commented Feb 15, 2022

Codecov Report

Merging #1628 (33953bb) into main (de56d0f) will decrease coverage by 0.14%.
The diff coverage is n/a.

Impacted file tree graph

@@             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              
Impacted Files Coverage Δ
src/system/temporary_directory.py 83.87% <0.00%> (-12.91%) ⬇️
src/system/os.py 92.30% <0.00%> (-7.70%) ⬇️
deployment/lib/identities.ts 100.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update de56d0f...33953bb. Read the comment docs.

@peternied
Copy link
Member

Instead add propagate: false on the build job, see https://www.jenkins.io/doc/pipeline/steps/pipeline-build-step/

@zelinh
Copy link
Member Author

zelinh commented Feb 15, 2022

Instead add propagate: false on the build job, see https://www.jenkins.io/doc/pipeline/steps/pipeline-build-step/

Great suggestion! That works from my testing. Working on the change. Thanks!

Signed-off-by: Zelin Hao <zelinhao@amazon.com>
@zelinh zelinh changed the title Add try catch block to catch the error from child job Add propagate argument when triggering child job Feb 15, 2022
@zelinh zelinh changed the title Add propagate argument when triggering child job Disable propagate argument when triggering child job Feb 15, 2022
@zelinh zelinh linked an issue Feb 16, 2022 that may be closed by this pull request
@zelinh zelinh merged commit e0a34eb into opensearch-project:main Feb 16, 2022
@zelinh zelinh deleted the add-catch-block branch February 16, 2022 00:36
zelinh added a commit to zelinh/opensearch-build that referenced this pull request Feb 16, 2022
…rch-project#1628)"

This reverts commit e0a34eb.

Signed-off-by: Zelin Hao <zelinhao@amazon.com>
zelinh added a commit that referenced this pull request Feb 17, 2022
…#1633)

This reverts commit e0a34eb.

Signed-off-by: Zelin Hao <zelinhao@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants