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

fix(ci): Switch back to actions/setup-java@v3.6.0 #589

Merged
merged 1 commit into from Dec 6, 2022

Conversation

saig0
Copy link
Member

@saig0 saig0 commented Dec 6, 2022

Description

The version v3.7.0 of actions/setup-java was removed. Fix the workflows by using the previous version. See actions/setup-java#422.

Related issues

Failed action: https://github.com/camunda/zeebe-process-test/actions/runs/3626043207

Definition of Done

Not all items need to be done depending on the issue and the pull request.

Code changes:

  • The changes are backwards compatibility with previous versions
  • If it fixes a bug then PRs are created to backport the fix

Testing:

  • There are unit/integration tests that verify all acceptance criterias of the issue
  • New tests are written to ensure backwards compatibility with further versions
  • The behavior is tested manually

Documentation:

  • Javadoc has been written
  • The documentation is updated

The version `v3.7.0` of actions/setup-java was removed. Fix the workflows by using the previous version. See actions/setup-java#422.
@github-actions
Copy link

github-actions bot commented Dec 6, 2022

Test Results

  47 files  ±0    47 suites  ±0   1m 49s ⏱️ -36s
113 tests ±0  113 ✔️ ±0  0 💤 ±0  0 ±0 
362 runs  ±0  362 ✔️ ±0  0 💤 ±0  0 ±0 

Results for commit 3142a7b. ± Comparison against base commit bdb5899.

Copy link
Contributor

@remcowesterhoud remcowesterhoud left a comment

Choose a reason for hiding this comment

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

Interesting decision by them 😅

bors merge

@zeebe-bors-camunda
Copy link
Contributor

Build succeeded:

@zeebe-bors-camunda zeebe-bors-camunda bot merged commit 72edee9 into main Dec 6, 2022
@zeebe-bors-camunda zeebe-bors-camunda bot deleted the fix-github-workflow branch December 6, 2022 08:03
@korthout
Copy link
Member

korthout commented Dec 6, 2022

It might be better to switch the version to the latest major release v3. Such tags are generally moved with every new minor and patch release of the major version. This practice is officially recommended by GH.

Note that this may result in reduced reproducibility. However, since all tags can be moved, the only way to guarantee reproducibility is by pinning specific commit shas.

Likely it is easiest for us when using actions like these (e.g. checkout) to use the major version tag.

zeebe-bors-camunda bot added a commit that referenced this pull request Dec 6, 2022
590: ci: use major version for actions/setup-java r=saig0 a=korthout

## Description

<!-- Please explain the changes you made here. -->

Changes the version used for actions/setup-java in all workflows to major version `v3`.

This should reduce the amount of effort needed to update this action (i.e. no more dependabot pull requests unless a new major version is released).

It should also avoid problems when actions/setup-java removes a specific patch release tag (as has happened before, see pull request mentioned below).

Using a major version is possible because GH recommends moving the major release tags along with the minor and patch releases of that same version.

Note that this may result in reduced reproducibility. However, since all tags can be moved, the only way to guarantee reproducibility is by pinning specific commit shas. Since we don't necessarily depend on a specific version, we should trust the maintainers of the action to adhere to semver.

## Related issues

<!-- Which issues are closed by this PR or are related -->

discussed in #589 (comment)

<!-- Cut-off marker
_All lines under and including the cut-off marker will be removed from the merge commit message_

## Definition of Ready

Please check the items that apply, before requesting a review.

You can find more details about these items in our wiki page about [Pull Requests and Code Reviews](https://github.com/camunda-cloud/zeebe/wiki/Pull-Requests-and-Code-Reviews).

* [ ] I've reviewed my own code
* [ ] I've written a clear changelist description
* [ ] I've narrowly scoped my changes
* [ ] I've separated structural from behavioural changes
-->

## Definition of Done

<!-- Please check the items that apply, before merging or (if possible) before requesting a review. -->

_Not all items need to be done depending on the issue and the pull request._

Code changes:
* [ ] The changes are backwards compatibility with previous versions
* [ ] If it fixes a bug then PRs are created to backport the fix

Testing:
* [ ] There are unit/integration tests that verify all acceptance criterias of the issue
* [ ] New tests are written to ensure backwards compatibility with further versions
* [ ] The behavior is tested manually

Documentation:
* [ ] Javadoc has been written
* [ ] The documentation is updated


Co-authored-by: Nico Korthout <nico.korthout@camunda.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.

None yet

3 participants