Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

CLOUD-869 Enhance Jenkinsfile to skip builds for specified non-trigger files #809

Merged
merged 12 commits into from
Feb 11, 2025

Conversation

ptankov
Copy link
Contributor

@ptankov ptankov commented Jan 17, 2025

CLOUD-869 Powered by Pull Request Badge

CHANGE DESCRIPTION

Problem:
Short explanation of the problem.

Cause:
Short explanation of the root cause of the issue if applicable.

Solution:
Short explanation of the solution we are providing with this PR.

CHECKLIST

Jira

  • Is the Jira ticket created and referenced properly?
  • Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
  • Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

  • Is an E2E test/test case added for the new feature/change?
  • Are unit tests added where appropriate?

Config/Logging/Testability

  • Are all needed new/changed options added to default YAML files?
  • Did we add proper logging messages for operator actions?
  • Did we ensure compatibility with the previous version or cluster upgrade process?
  • Does the change support oldest and newest supported PS version?
  • Does the change support oldest and newest supported Kubernetes version?

@pull-request-size pull-request-size bot added the size/L 100-499 lines label Jan 17, 2025
@ptankov ptankov changed the title Enhance Jenkinsfile to skip builds for specified non-trigger files CLOUD-869 Enhance Jenkinsfile to skip builds for specified non-trigger files Jan 17, 2025
@ptankov ptankov marked this pull request as ready for review January 20, 2025 12:33
eleo007
eleo007 previously approved these changes Jan 23, 2025
jvpasinatto
jvpasinatto previously approved these changes Jan 27, 2025
gkech
gkech previously approved these changes Jan 27, 2025
@ptankov ptankov dismissed stale reviews from jvpasinatto and gkech via d5341bc January 28, 2025 18:58
…nd streamline cluster stages with source file stashing and use updated credentials ID for cloud secret file
@JNKPercona
Copy link
Collaborator

Test name Status
version-service passed
async-ignore-annotations passed
auto-config passed
config passed
config-router passed
demand-backup passed
gr-demand-backup passed
gr-demand-backup-haproxy passed
gr-finalizer passed
gr-haproxy passed
gr-ignore-annotations passed
gr-init-deploy passed
gr-one-pod passed
gr-recreate passed
gr-scaling passed
gr-scheduled-backup passed
gr-security-context passed
gr-self-healing passed
gr-tls-cert-manager passed
gr-users passed
haproxy passed
init-deploy passed
limits passed
monitoring passed
one-pod passed
operator-self-healing passed
recreate passed
scaling passed
scheduled-backup passed
service-per-pod passed
sidecars passed
smart-update passed
tls-cert-manager passed
users passed
We run 34 out of 34

commit: c29a7f6
image: perconalab/percona-server-mysql-operator:PR-809-c29a7f6f

@ptankov ptankov merged commit 6cedb30 into main Feb 11, 2025
16 checks passed
@ptankov ptankov deleted the CLOUD-869 branch February 11, 2025 14:44
mgumz pushed a commit to travelping/percona-server-mysql-operator that referenced this pull request Feb 12, 2025
…r files (percona#809)

* Enhance Jenkinsfile to skip builds for specified non-trigger files

* Add .e2eignore file to exclude specified files and directories from end-to-end tests

* CLOUD-869 Fallback to merge-base if commit hash is invalid

* Inverting the check to test whether the previous build's result is anything other than SUCCESS

* Refactor Jenkins pipeline to remove unused popArtifactFile function and streamline cluster stages with source file stashing and use updated credentials ID for cloud secret file
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
size/L 100-499 lines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants