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

Always write a version report #4620

Merged
merged 1 commit into from
Jan 21, 2025
Merged

Conversation

laeubi
Copy link
Member

@laeubi laeubi commented Jan 21, 2025

Currently only a report file is written if there are actual problems. For using the mojo in automation it is better to always have a report and it allows to see that there are no problems to report so the check was actually performed.

Currently only a report file is written if there are actual problems.
For using the mojo in automation it is better to always have a report
and it allows to see that there are no problems to report so the check
was actually performed.
@laeubi laeubi added the backport-to-tycho-4.0.x Can be added to a PR to trigger an automatic backport of the change label Jan 21, 2025
@laeubi laeubi enabled auto-merge (rebase) January 21, 2025 03:58
Copy link

Test Results

  606 files  ±0    606 suites  ±0   4h 5m 53s ⏱️ - 23m 57s
  434 tests ±0    427 ✅ +3   7 💤 ±0  0 ❌  - 3 
1 302 runs  ±0  1 280 ✅ +3  22 💤 ±0  0 ❌  - 3 

Results for commit 6391585. ± Comparison against base commit fdc0adf.

@laeubi laeubi merged commit 3b83a08 into eclipse-tycho:main Jan 21, 2025
16 checks passed
@eclipse-tycho-bot
Copy link

💚 All backports created successfully

Status Branch Result
tycho-4.0.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-to-tycho-4.0.x Can be added to a PR to trigger an automatic backport of the change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants