Skip to content

fabric8 next version daily check #1856

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 0 commits into from
Closed

fabric8 next version daily check #1856

wants to merge 0 commits into from

Conversation

@csviri
Copy link
Collaborator

@csviri csviri commented Apr 13, 2023 •
edited
Loading

!! DON'T MERGE !!

The goal of this PR is to test the framework with the most recent version of fabric8 client.

@csviri csviri marked this pull request as draft April 13, 2023 10:54
@csviri csviri changed the title fabric8 next version fabric8 next version daily check Apr 27, 2023
@csviri csviri mentioned this pull request Apr 27, 2023
Closed
@csviri csviri force-pushed the fabric8-next-version branch from 7e19a3e to fe9491f Compare April 27, 2023 11:39
metacosm
metacosm reviewed Apr 27, 2023
View reviewed changes
.github/workflows/snapshot-releases.yml Outdated
paths-ignore:
- 'docs/**'
branches: [ main, v1, v2, v3, next ]
branches: [ fabric8-next-version ]
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think we should keep releasing snapshots for main as well. Ideally, on every merge, even, which would mean splitting this out. Don't know. A snapshot a day is probably enough.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

AFAIK it works in a way that, this is not merged, so the github action will for this branch will take into account only the code on this branch. So since this PR never will be merged this should be enough to run the releases daily for this branch, but will work also for main (since that run uses the code from there)

.github/workflows/pr.yml Outdated
on:
schedule:
# Run on end of the day
- cron: '0 0 * * *'
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why was this added? Is it meant to run a build at least once a day?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yes, to run a daily build.

@metacosm metacosm force-pushed the fabric8-next-version branch from cec7be5 to 60b937f Compare April 27, 2023 20:51
@csviri csviri force-pushed the fabric8-next-version branch from 60b937f to c2c6513 Compare May 3, 2023 12:33
@metacosm metacosm force-pushed the fabric8-next-version branch from dd30ae2 to cb97374 Compare May 4, 2023 13:18
@sonarqubecloud
Copy link

sonarqubecloud bot commented May 4, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@csviri csviri force-pushed the fabric8-next-version branch from cb97374 to 756b59f Compare June 13, 2023 11:48
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 16, 2023
@github-actions
Copy link

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the stale label Aug 16, 2023
@csviri csviri removed the stale label Aug 16, 2023
@github-actions
Copy link

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the stale label Oct 16, 2023
@csviri csviri removed the stale label Oct 16, 2023
@github-actions
Copy link

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the stale label Dec 16, 2023
@csviri csviri removed stale needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Dec 17, 2023
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 20, 2023
@github-actions
Copy link

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the stale label Feb 19, 2024
@csviri csviri removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. stale labels Feb 19, 2024
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 19, 2024
@csviri csviri force-pushed the fabric8-next-version branch from 756b59f to 2a19a20 Compare February 19, 2024 09:47
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 19, 2024
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 21, 2024
@csviri csviri force-pushed the fabric8-next-version branch from bdc0b7c to 903267c Compare April 15, 2024 11:23
@openshift-merge-robot openshift-merge-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Apr 15, 2024
@metacosm metacosm force-pushed the fabric8-next-version branch from 903267c to 78c6145 Compare August 21, 2024 09:58
@openshift-merge-robot openshift-merge-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Aug 21, 2024
@openshift-merge-robot
Copy link

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@csviri csviri closed this Jan 2, 2025
@csviri csviri force-pushed the fabric8-next-version branch from 17f6030 to 756c4d1 Compare January 2, 2025 12:06
@metacosm
Copy link
Collaborator

metacosm commented Jan 2, 2025

Why did you close this PR, @csviri?

@csviri
Copy link
Collaborator Author

csviri commented Jan 2, 2025

Hmm, I did not, I just updated it for the main, and since there is no snapshot of fabric8 (tried 7.0.2-SNAPSHOT and 7.1.0-SNAPSHOT) I set it for the latest version, so github closed it. Do you know what is the latest snapshot?

@metacosm
Copy link
Collaborator

metacosm commented Jan 2, 2025

Next version is 7.1-SNAPSHOT.

@csviri
Copy link
Collaborator Author

csviri commented Jan 2, 2025

that cannot be found. Could not find artifact io.fabric8:kubernetes-client-bom:pom:7.1-SNAPSHOT

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 2, 2025
@metacosm
Copy link
Collaborator

metacosm commented Jan 2, 2025

It's possible that they haven't been deployed, yet.

@csviri
Copy link
Collaborator Author

csviri commented Jan 2, 2025

yeah, I gues so, will recreate this PR with that version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@metacosm metacosm metacosm left review comments

Assignees

No one assigned

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@csviri @openshift-merge-robot @metacosm