# Kubernetes plugin's "retries" option and parallelsAlwaysFailFast()

**URL:** <https://community.jenkins.io/t/kubernetes-plugins-retries-option-and-parallelsalwaysfailfast/5548>\
**Category:** Using Jenkins\
**Tags:** kubernetes\
**Created:** [February 1, 2023, 4:33am UTC](https://community.jenkins.io/t/kubernetes-plugins-retries-option-and-parallelsalwaysfailfast/5548 "2023-02-01T04:33:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![fuminori-ido-m](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/fuminori-ido-m/32/3247_2.png) [@fuminori-ido-m](https://community.jenkins.io/u/fuminori-ido-m)\
**Post date:** [February 1, 2023, 4:33am UTC](https://community.jenkins.io/t/kubernetes-plugins-retries-option-and-parallelsalwaysfailfast/5548/1 "2023-02-01T04:33:59Z")

</div>

Is it possible to combine “retries” option of kubernetes plugin with Jenkins parallelsAlwaysFailFast() ?

When I set both in Jenkinsfile as follows:

```auto
pipeline {
    ...
    options { parallelsAlwaysFailFast() }
    stages {
        stage('test') {
            matrix {
                axes { axis { ... }}
                stages {
                    stage('integration') {
                        agent {
                            kubernetes {
                                ...
                                retries 2
                            }
...

```

I expected that a stage fails **after** exceeding max retries(=2) **then** whole jenkins job fails because of parallelsAlwaysFailFast.

However, it actually behaves that a stage fails once **before** exceeding max retries(=2) **then** immediately whole jenkins job fails (because of parallelsAlwaysFailFast ?).

Does this mean kubernetes “retries” option can **not** be used with parallelsAlwaysFailFast ?