Implement integration test pipeline #44

Merged

salcedo merged 5 commits from feat/43 into develop 2025-11-06 14:27:24 +00:00

Conversation 2 Commits 5 Files changed 9 +453 -142

hurui200320 commented 2025-11-06 10:32:59 +00:00

Member

Copy link

This PR implemented ticket #43 with the following changes:

• Unified multiple pipelines into one
• Apply internal integration test from python adapter repo
• Apply updatecli action to update chart for develop and master branches changes.

TODO: when python adapter repo is ready, we should update the action reference to use branch name instead of commit hash

This PR implemented ticket #43 with the following changes: + Unified multiple pipelines into one + Apply internal integration test from python adapter repo + Apply updatecli action to update chart for develop and master branches changes. TODO: when python adapter repo is ready, we should update the action reference to use branch name instead of commit hash

hurui200320 self-assigned this 2025-11-06 10:32:59 +00:00

hurui200320 added 4 commits 2025-11-06 10:32:59 +00:00

ci: merge pipelines to one and apply integration test 019a1fe489

ci: run updatecli shared action to deploy auth-service 8f34766313

ci: update var name, update integration test action ref da8ce1761d

ci: update clevermicro metachart when deploying 0d7b382862

hurui200320 requested reviews from salcedo, stanislav.hejny 2025-11-06 10:33:07 +00:00

forgejo-actions commented 2025-11-06 10:34:35 +00:00

Copy link

Coverage is 89%

Coverage is 89%

hurui200320 added a new dependency 2025-11-06 10:48:31 +00:00

#43 Update pipeline to include integration test and updatecli

salcedo added 1 commit 2025-11-06 13:44:28 +00:00

ci: target auth-service-dev on develop branch. auth-service on master bd28ecf138

forgejo-actions commented 2025-11-06 13:55:08 +00:00

Copy link

Coverage is 89%

Coverage is 89%

salcedo merged commit 2be30ff754 into develop 2025-11-06 14:27:24 +00:00

salcedo referenced this pull request from a commit 2025-11-06 14:27:26 +00:00

Merge pull request 'Implement integration test pipeline' (#44) from feat/43 into develop

hurui200320 referenced this pull request from a commit 2025-11-27 07:27:12 +00:00

Merge pull request 'Implement integration test pipeline' (#44) from feat/43 into develop

Sign in to join this conversation.

Reviewers

No reviewers

salcedo

stanislav.hejny

Labels

Clear labels

  

Blocked

A ticket in a blocked state and unable to complete until some other task is completed first.

  

Bounty

$100

A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$1000

A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$10000

A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$20

A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$2000

A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$250

A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$50

A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$500

A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$5000

A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$750

A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  

MoSCoW

Could have

Could have feature in order to satisfy the epic/legendary.

  

MoSCoW

Must have

Must have feature in order to satisfy the epic/legendary.

  

MoSCoW

Should have

Should have feature in order to satisfy the epic/legendary.

  

Needs feedback

There are questions in the ticket that can not be completed until the project owner provides clarity.

  

Points

1

1 man-hours worth of work for an expert with no learning curve.

  

Points

13

13 man-hours worth of work for an expert with no learning curve.

  

Points

2

2 man-hours worth of work for an expert with no learning curve.

  

Points

21

21 man-hours worth of work for an expert with no learning curve.

  

Points

3

3 man-hours worth of work for an expert with no learning curve.

  

Points

34

34 man-hours worth of work for an expert with no learning curve.

  

Points

5

5 man-hours worth of work for an expert with no learning curve.

  

Points

55

55 man-hours worth of work for an expert with no learning curve.

  

Points

8

8 man-hours worth of work for an expert with no learning curve.

  

Points

88

88 man-hours worth of work for an expert with no learning curve.

  

Priority

Backlog

This ticket has backlogged priority and is not to be worked on yet

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Signed-off: Owner

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Scrum Master

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Tech Lead

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Spike

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  

State

Completed

The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  

State

Duplicate

A ticket that represents the same content as an existing ticket.

  

State

In Progress

A ticket that is actively being developed.

  

State

In Review

A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  

State

Paused

This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  

State

Unverified

All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  

State

Verified

The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  

State

Wont Do

This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  

Type

Bug

Something that doesnt work as intended.

  

Type

Discussion

Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  

Type

Documentation

An error or improvement needed in the documentation.

  

Type

Epic

Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  

Type

Feature

Some new functionality not present.

  

Type

Legendary

A type of Epic which will contain other Epics.

  

Type

Support

Someone needs help using the project.

  

Type

Task

A generic task that doesnt fit into the other type categories.

  

Type

Testing

Work exclusively focusing on fixing or expanding testing.

No labels

Blocked

Bounty

$100

Bounty

$1000

Bounty

$10000

Bounty

$20

Bounty

$2000

Bounty

$250

Bounty

$50

Bounty

$500

Bounty

$5000

Bounty

$750

MoSCoW

Could have

MoSCoW

Must have

MoSCoW

Should have

Needs feedback

Points

1

Points

13

Points

2

Points

21

Points

3

Points

34

Points

5

Points

55

Points

8

Points

88

Priority

Backlog

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Signed-off: Owner

Signed-off: Scrum Master

Signed-off: Tech Lead

Spike

State

Completed

State

Duplicate

State

In Progress

State

In Review

State

Paused

State

Unverified

State

Verified

State

Wont Do

Type

Bug

Type

Discussion

Type

Documentation

Type

Epic

Type

Feature

Type

Legendary

Type

Support

Type

Task

Type

Testing

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

hurui200320

3 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks

#43 Update pipeline to include integration test and updatecli

clevermicro/user-management

Reference

clevermicro/user-management!44

No description provided.