Skip to content

Jenkinsfile: pickup results from ITs and Maven 3.8.x for build#953

Merged
slawekjaranowski merged 4 commits intomasterfrom
jenkins-tests-reports
Jan 13, 2023
Merged

Jenkinsfile: pickup results from ITs and Maven 3.8.x for build#953
slawekjaranowski merged 4 commits intomasterfrom
jenkins-tests-reports

Conversation

@slawekjaranowski
Copy link
Copy Markdown
Member

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Make sure there is a JIRA issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a JIRA issue. Your pull request should address just this issue, without
    pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [MNG-XXX] SUMMARY,
    where you replace MNG-XXX and SUMMARY with the appropriate JIRA issue.
  • Also format the first line of the commit message like [MNG-XXX] SUMMARY.
    Best practice is to use the JIRA issue title in both the pull request title and in the first line of the commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.
  • You have run the Core IT successfully.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

@slawekjaranowski
Copy link
Copy Markdown
Member Author

Failed test MavenITmng5669ReadPomsOnce on all CI - Jenkis, GitHub ... also locally is broken

@slawekjaranowski
Copy link
Copy Markdown
Member Author

Failed jenkins build is from branch, when we create PR, jenkins not build branch any more and wrong status stay for ever 😄

@psiroky
Copy link
Copy Markdown
Contributor

psiroky commented Jan 13, 2023

Looks good to me (my Jenkins knowledge is little rusty these days though). I can't approve the PR formally, so at least commenting here.

Copy link
Copy Markdown
Member

@olamy olamy left a comment

Choose a reason for hiding this comment

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

don't be shy just push it ;)

@slawekjaranowski slawekjaranowski merged commit c0d942b into master Jan 13, 2023
@slawekjaranowski slawekjaranowski deleted the jenkins-tests-reports branch January 13, 2023 11:00
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.

4 participants