Skip to content

HPCC4J-608 Test #36

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.

Sign up for GitHub

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

Jump to bottom
Open
jpmcmu wants to merge 2 commits into
base: master
Choose a base branch
from
Open

HPCC4J-608 Test #36

jpmcmu wants to merge 2 commits into from

Conversation

@jpmcmu
Copy link
Owner

@jpmcmu jpmcmu commented Jul 23, 2024

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:

jpmcmu added 2 commits July 23, 2024 14:38
@jpmcmu
HPCC4J-608 JirabotMerge: Add missing changes
ba0c523 
- Added missing changes
- Updated transition flow logic

Signed-off-by: James McMullan James.McMullan@lexisnexis.com
@jpmcmu
Test
0bfee11
@github-actions
Copy link

github-actions bot commented Jul 23, 2024

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

Jirabot Action Result:
Assigning user: james.mcmullan@lexisnexisrisk.com
Workflow Transition To: Accepted
Error: Transitioning to: "Active" failed with: "'transition' identifier must be an integer" Valid transitions=[{'name': 'Reject', 'id': 141, 'to': 'Resolved'}, {'name': 'Assign as unresourced', 'id': 231, 'to': 'Unresourced'}, {'name': 'Merge Pending', 'id': 291, 'to': 'Merge Pending'}, {'name': 'Schedule', 'id': 171, 'to': 'Planned'}]
Workflow Transition To: Merge Pending
Additional PR: #36

@jpmcmu jpmcmu closed this Jul 23, 2024
@jpmcmu jpmcmu reopened this Jul 23, 2024
@github-actions
Copy link

github-actions bot commented Jul 23, 2024

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

Jirabot Action Result:
Assigning user: james.mcmullan@lexisnexisrisk.com
Workflow Transition To: Merge Pending
Additional PR: #36

@jpmcmu jpmcmu force-pushed the master branch 3 times, most recently from 5de449f to 48ba75e Compare June 25, 2025 12:52
@jpmcmu jpmcmu force-pushed the master branch 2 times, most recently from b4a0cc7 to ff85be3 Compare January 22, 2026 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jpmcmu