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

ci: never time out during release jobs #17271

Merged
merged 1 commit into from
Apr 3, 2024
Merged

Conversation

lenaschoenburg
Copy link
Member

Releasing can take a very long time because maven central is slow. Since its all manual and retry is painful, I think it's fine to just not set a timeout.

Releasing can take a *very* long time because maven central is slow.
Since its all manual and retry is painful, I think it's fine to just not
set a timeout.
@github-actions github-actions bot added the component/zeebe Related to the Zeebe component/team label Apr 3, 2024
@lenaschoenburg lenaschoenburg added backport stable/8.1 backport stable/8.2 Backport a pull request to 8.2.x backport stable/8.3 Backport a pull request to 8.3.x backport stable/8.4 Backport a pull request to 8.4.x labels Apr 3, 2024
Copy link
Contributor

@megglos megglos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙏

@lenaschoenburg
Copy link
Member Author

The rolling update test failed because it couldn't find a docker image for 8.4.6 yet 😆
I deleted the tag now (because the release failed and needs to be retried) so now it should work again.

@lenaschoenburg lenaschoenburg added this pull request to the merge queue Apr 3, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Apr 3, 2024
@lenaschoenburg lenaschoenburg added this pull request to the merge queue Apr 3, 2024
Merged via the queue into main with commit ebb84d4 Apr 3, 2024
37 checks passed
@lenaschoenburg lenaschoenburg deleted the os/never-timeout-release branch April 3, 2024 15:49
@backport-action
Copy link
Collaborator

Successfully created backport PR for stable/8.1:

@backport-action
Copy link
Collaborator

Successfully created backport PR for stable/8.2:

@backport-action
Copy link
Collaborator

Successfully created backport PR for stable/8.3:

@backport-action
Copy link
Collaborator

Successfully created backport PR for stable/8.4:

github-merge-queue bot pushed a commit that referenced this pull request Apr 3, 2024
# Description
Backport of #17271 to `stable/8.1`.

relates to
original author: @oleschoenburg
github-merge-queue bot pushed a commit that referenced this pull request Apr 3, 2024
# Description
Backport of #17271 to `stable/8.2`.

relates to
original author: @oleschoenburg
github-merge-queue bot pushed a commit that referenced this pull request Apr 3, 2024
# Description
Backport of #17271 to `stable/8.4`.

relates to
original author: @oleschoenburg
github-merge-queue bot pushed a commit that referenced this pull request Apr 3, 2024
# Description
Backport of #17271 to `stable/8.3`.

relates to
original author: @oleschoenburg
@Zelldon Zelldon added version:8.2.27 Marks an issue as being completely or in parts released in 8.2.27 version:8.4.7 Marks an issue as being completely or in parts released in 8.4.7 labels May 7, 2024
@Zelldon Zelldon added the version:8.3.11 Marks an issue as being completely or in parts released in 8.3.11 label May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport stable/8.2 Backport a pull request to 8.2.x backport stable/8.3 Backport a pull request to 8.3.x backport stable/8.4 Backport a pull request to 8.4.x component/zeebe Related to the Zeebe component/team version:8.2.27 Marks an issue as being completely or in parts released in 8.2.27 version:8.3.11 Marks an issue as being completely or in parts released in 8.3.11 version:8.4.7 Marks an issue as being completely or in parts released in 8.4.7
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants