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

Add GitHub CI workflow #2

Merged
merged 3 commits into from
May 26, 2022
Merged

Add GitHub CI workflow #2

merged 3 commits into from
May 26, 2022

Conversation

swtwsk
Copy link
Contributor

@swtwsk swtwsk commented May 23, 2022

No description provided.

@github-actions
Copy link
Contributor

There is no coverage information present for the Files changed

Total Project Coverage 93.8% 🍏

@maver1ck
Copy link

Let's wait for Maven Central repo

@github-actions
Copy link
Contributor

There is no coverage information present for the Files changed

Total Project Coverage 93.8% 🍏

@github-actions
Copy link
Contributor

There is no coverage information present for the Files changed

Total Project Coverage 93.8% 🍏

push:
branches:
- main
- develop
Copy link
Collaborator

@kristoffSC kristoffSC May 24, 2022

Choose a reason for hiding this comment

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

We will probably not have a develop branch since I'm opting for using cactus model as a branch strategy.

Also, this rule here "push" -> would be good to set up master as protected branch, so no direct pushes to master will be allowed.

Also It would be very good to run CI (tests) on master AFTER merge to master.
This will ensure that any changes added to master are compatible with current master state.
In my past experience I had many cases where master was failing after merge, although feature branch was ok and passing all tests.

Ideally revert merge if that post merge build fails, but Im not sure if this last step is possible.

Additionally a good "safety" check would be if "merge" to master would not be possible if feature branch is behind master. I know that on GitLab you can configure such a rule -> disable "merge" button" if feature branch is behind master.

This forces developer to always refresh its feature branch and make sure that everything is green.

@github-actions
Copy link
Contributor

There is no coverage information present for the Files changed

Total Project Coverage 93.8% 🍏

pom.xml Outdated Show resolved Hide resolved
pom.xml Outdated Show resolved Hide resolved
@github-actions
Copy link
Contributor

There is no coverage information present for the Files changed

Total Project Coverage 93.8% 🍏

@github-actions
Copy link
Contributor

There is no coverage information present for the Files changed

Total Project Coverage 93.8% 🍏

@swtwsk swtwsk merged commit 6f1829b into main May 26, 2022
@swtwsk swtwsk deleted the ci-cd branch May 26, 2022 14:31
kristoffSC added a commit that referenced this pull request Feb 10, 2023
Signed-off-by: Krzysztof Chmielewski <[email protected]>
kristoffSC added a commit that referenced this pull request Feb 10, 2023
Signed-off-by: Krzysztof Chmielewski <[email protected]>
kristoffSC added a commit that referenced this pull request Feb 10, 2023
Signed-off-by: Krzysztof Chmielewski <[email protected]>
kristoffSC added a commit that referenced this pull request Feb 10, 2023
rc-0.9.0_testRunFix - fix publish build #2
kristoffSC added a commit that referenced this pull request Feb 10, 2023
Signed-off-by: Krzysztof Chmielewski <[email protected]>
kristoffSC added a commit that referenced this pull request Feb 10, 2023
rc-0.9.0_testRunFix - fix publish build #2
kristoffSC added a commit that referenced this pull request Jun 16, 2023
kristoffSC added a commit that referenced this pull request Jul 4, 2023
* HTTP-42-BatchRequest - add support for batch request processing in HTTP sink.

Signed-off-by: Krzysztof Chmielewski <[email protected]>

* HTTP-42-BatchRequest - add support for batch request processing in HTTP sink #2

Signed-off-by: Krzysztof Chmielewski <[email protected]>

* HTTP-42-BatchRequest - add support for batch request processing in HTTP sink #3

Signed-off-by: Krzysztof Chmielewski <[email protected]>

* HTTP-42-BatchRequest - add support for batch request processing in HTTP sink #4

Signed-off-by: Krzysztof Chmielewski <[email protected]>

* HTTP-42-BatchRequest - add support for batch request processing in HTTP sink #5 tests

Signed-off-by: Krzysztof Chmielewski <[email protected]>

* HTTP-42-BatchRequest - add support for batch request processing in HTTP sink #6 tests

Signed-off-by: Krzysztof Chmielewski <[email protected]>

* HTTP-42-BatchRequest - add support for batch request processing in HTTP sink #7 tests

Signed-off-by: Krzysztof Chmielewski <[email protected]>

* HTTP-42-BatchRequest - add support for batch request processing in HTTP sink #8 tests

Signed-off-by: Krzysztof Chmielewski <[email protected]>

* HTTP-42-BatchRequest - add support for batch request processing in HTTP sink #9 tests

Signed-off-by: Krzysztof Chmielewski <[email protected]>

* HTTP-42-BatchRequest - add support for batch request processing in HTTP - doc.

Signed-off-by: Krzysztof Chmielewski <[email protected]>

* HTTP-42-BatchRequest - add support for batch request processing in HTTP sink #9 Java doc

Signed-off-by: Krzysztof Chmielewski <[email protected]>

* HTTP-42-BatchRequest - add support for batch request processing in HTTP sink #10 - changes after Code review - fix typos

Signed-off-by: Krzysztof Chmielewski <[email protected]>

* HTTP-42-BatchRequest - add support for batch request processing in HTTP sink #10 - changes after Code review - fix batch split

Signed-off-by: Krzysztof Chmielewski <[email protected]>

---------

Signed-off-by: Krzysztof Chmielewski <[email protected]>
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.

3 participants