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

[10.0.x] kie-issues#1613: Add CI :: Check license headers GitHub Actions workflow #1811

Closed
wants to merge 3 commits into from

Conversation

jomarko
Copy link
Contributor

@jomarko jomarko commented Nov 18, 2024

This is partial fix of the issue apache/incubator-kie-issues#1613 as we open one PR per repository.
Please make sure your PR meets the following requirements:

  • You have read the contributors guide
  • Pull Request title is properly formatted: [Issue XXXX] Subject
  • Pull Request contains link to the JIRA issue
  • Pull Request contains description of the issue
  • Pull Request does not include fixes for issues other than the main ticket
  • Your feature/bug fix has a testcase that verifies it
  • You've tested the new feature/bug fix in an actual OpenShift cluster
  • You've added a RELEASE_NOTES.md entry regarding this change
How to retest this PR or trigger a specific build:
  • (Re)run Jenkins tests
    Please add comment: Jenkins [test|retest] this
How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

@kie-ci3
Copy link
Contributor

kie-ci3 commented Nov 18, 2024

PR job #14 was: ABORTED
Possible explanation: Most probably a timeout, please review

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/10.0.x/job/pullrequest/job/kogito-images.build-and-test/14/display/redirect
See console log:

Console Logs Build KIE » kogito » 10.0.x » pullrequest » kogito-images.build-image #83 completed: FAILURE
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
Failed in branch kogito-data-index-postgresql
Build KIE » kogito » 10.0.x » pullrequest » kogito-images.build-image #81 completed: FAILURE
Build KIE » kogito » 10.0.x » pullrequest » kogito-images.build-image #82 completed: FAILURE
[Pipeline] }
Build KIE » kogito » 10.0.x » pullrequest » kogito-images.build-image #80 completed: FAILURE
[Pipeline] }
[Pipeline] // stage
[Pipeline] // stage
[Pipeline] }
Failed in branch kogito-jobs-service-ephemeral
[Pipeline] }
Failed in branch kogito-jobs-service-postgresql
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
Failed in branch kogito-jit-runner
Build KIE » kogito » 10.0.x » pullrequest » kogito-images.build-image #78 completed: FAILURE
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
Failed in branch kogito-base-builder
Build KIE » kogito » 10.0.x » pullrequest » kogito-images.build-image #84 completed: ABORTED
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
Failed in branch kogito-jobs-service-allinone
Click here to forcibly terminate running steps
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
Failed in branch kogito-data-index-ephemeral
[Pipeline] // parallel
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] script
[Pipeline] {
[Pipeline] sh
+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/10.0.x/job/pullrequest/job/kogito-images.build-and-test/14/api/json?depth=0'
[Pipeline] readJSON
[Pipeline] sh

@jomarko jomarko changed the title [10.0.x] kie-issues#1613: Add CI :: Check license headers GitHub Actions workflow [10.0.x] kie-issues#1613: Add CI :: Check license headers GitHub Actions workflow Nov 18, 2024
@porcelli
Copy link
Contributor

we don't need this, as this repo is not active on main anymore.

and for 10.0.0. release the individual repos content like .rat-exclude, DISCLAIMER, LEGAL, etc... will be removed for source anyway.

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.

6 participants