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

HPCC4J-682 Spark-HPCC Release workflow broken #794

Merged
merged 1 commit into from
Feb 4, 2025

Conversation

jpmcmu
Copy link
Contributor

@jpmcmu jpmcmu commented Feb 4, 2025

  • Updated Spark-HPCC pom to use toplevel pom profile configuration
  • Removed contact info for previous developer

Signed-off-by: James McMullan [email protected]

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change is a breaking change (fix or feature that will cause existing behavior to change).

Checklist:

  • I have created a corresponding JIRA ticket for this submission
  • My code follows the code style of this project.
    • I have applied the Eclipse code-format template provided.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the HPCC Systems CONTRIBUTORS document (https://github.com/hpcc-systems/HPCC-Platform/wiki/Guide-for-contributors).
  • The change has been fully tested:
    • This change does not cause any existing JUnits to fail.
    • I have include JUnit coverage to test this change
    • I have performed system test and covered possible regressions and side effects.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Premature optimization
    • This change fixes the problem, not just the symptom

Testing:

- Updated Spark-HPCC pom to use toplevel pom profile configuration
- Removed contact info for previous developer

Signed-off-by: James McMullan [email protected]
@jpmcmu jpmcmu requested a review from rpastrana February 4, 2025 16:00
Copy link

github-actions bot commented Feb 4, 2025

Jira Issue: https://hpccsystems.atlassian.net/browse/HPCC4J-682

Jirabot Action Result:
Assigning user: [email protected]
Workflow Transition To: Merge Pending
Updated PR

@rpastrana rpastrana merged commit b7adb36 into hpcc-systems:candidate-9.10.x Feb 4, 2025
5 of 7 checks passed
Copy link

github-actions bot commented Feb 4, 2025

Jirabot Action Result:
Added fix version: 9.10.2
Workflow Transition: 'Resolve issue'

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