Fix pipeline #10

Merged

hurui200320 merged 1 commit from feat/#8 into develop 2025-04-30 03:38:38 +00:00

Conversation 9 Commits 1 Files changed 18 +157 -125

hurui200320 commented 2025-03-27 13:48:04 +00:00

Member

Copy link

This MR fixed the pipeline so it can run on forgejo runner. Currently we have two pipelines set up:

• One pipeline will run pytest to test the code and collect coverage data, this pipeline will run on all branches and PRs.
• One pipeline will build the wheel file and publish it to the company's pypl repo, this pipeline will only run on the master branch and develop branch.

This RP also made the following changes to make the pipeline working:

• Remove setup.py and requirements.txt, now the project is fully embraced pyproject.toml, which according to ChatGPT, is the most modern way of managing a python project.
• Move all test files to tests folder, so it won't be packed into the final wheel file and affect the coverage rate.
• Change version to X.Y.Z-dev, before building the wheel file, the pipeline will automatically add a UTC timestamp after it, so it becomes X.Y.Z-devYYYYMMDDHHmmSS. This is added due to the limitation of the pypl repo, unlike maven snapshot versions, you can't push the same version twice with our pypl repository.
• fixed some unit test that cause the pytest to fail

This MR fixed the pipeline so it can run on forgejo runner. Currently we have two pipelines set up: + One pipeline will run pytest to test the code and collect coverage data, this pipeline will run on all branches and PRs. + One pipeline will build the wheel file and publish it to the company's pypl repo, this pipeline will only run on the master branch and develop branch. This RP also made the following changes to make the pipeline working: + Remove `setup.py` and `requirements.txt`, now the project is fully embraced `pyproject.toml`, which according to ChatGPT, is the most modern way of managing a python project. + Move all test files to `tests` folder, so it won't be packed into the final wheel file and affect the coverage rate. + Change version to `X.Y.Z-dev`, before building the wheel file, the pipeline will automatically add a UTC timestamp after it, so it becomes `X.Y.Z-devYYYYMMDDHHmmSS`. This is added due to the limitation of the pypl repo, unlike maven snapshot versions, you can't push the same version twice with our pypl repository. + fixed some unit test that cause the pytest to fail

hurui200320 self-assigned this 2025-03-27 13:48:04 +00:00

forgejo-actions commented 2025-03-27 13:49:07 +00:00

Copy link

Coverage for module is 38%

Coverage for module is 38%

hurui200320 force-pushed feat/#8 from 5b9065ce84 to f67b51ad95 2025-03-27 13:50:40 +00:00 Compare

forgejo-actions commented 2025-03-27 13:51:52 +00:00

Copy link

Coverage is 38%

Coverage is 38%

hurui200320 changed title from WIP: #8 Fix pipeline to #8 Fix pipeline 2025-03-27 13:58:16 +00:00

hurui200320 requested reviews from abed.alrahman, stanislav.hejny 2025-03-27 13:58:35 +00:00

hurui200320 added a new dependency 2025-04-18 04:18:36 +00:00

#8 Migrate clevermicro / amq-adapter-python CI scripts to ForgeJo

hurui200320 changed title from #8 Fix pipeline to Fix pipeline 2025-04-21 06:49:31 +00:00

hurui200320 force-pushed feat/#8 from 7112b44ecd to 58278143b1 2025-04-21 06:55:58 +00:00 Compare

forgejo-actions commented 2025-04-21 07:02:49 +00:00

Copy link

Coverage is 38%

Coverage is 38%

forgejo-actions commented 2025-04-21 07:14:48 +00:00

Copy link

Coverage is 38%

Coverage is 38%

hurui200320 changed title from Fix pipeline to WIP: Fix pipeline 2025-04-21 07:23:10 +00:00

stanislav.hejny approved these changes 2025-04-22 07:57:22 +00:00

hurui200320 force-pushed feat/#8 from 14b7b50378 to 9fc8c08479 2025-04-23 07:37:53 +00:00 Compare

hurui200320 force-pushed feat/#8 from 9fc8c08479 to 2028b33572 2025-04-23 08:06:41 +00:00 Compare

hurui200320 force-pushed feat/#8 from 2028b33572 to 262410d70a 2025-04-23 08:14:44 +00:00 Compare

hurui200320 force-pushed feat/#8 from 262410d70a to 656d266327 2025-04-23 08:18:15 +00:00 Compare

hurui200320 force-pushed feat/#8 from 656d266327 to 3f41bc6e0d 2025-04-23 08:22:47 +00:00 Compare

hurui200320 force-pushed feat/#8 from 3f41bc6e0d to efe219ea21 2025-04-23 08:28:14 +00:00 Compare

hurui200320 force-pushed feat/#8 from efe219ea21 to 54b8f8176a 2025-04-23 08:35:31 +00:00 Compare

hurui200320 force-pushed feat/#8 from 54b8f8176a to 51a6addf03 2025-04-23 08:41:28 +00:00 Compare

hurui200320 force-pushed feat/#8 from 51a6addf03 to f80ece3de2 2025-04-23 08:50:50 +00:00 Compare

hurui200320 force-pushed feat/#8 from f80ece3de2 to 06e92531c7 2025-04-24 03:48:27 +00:00 Compare

hurui200320 force-pushed feat/#8 from 06e92531c7 to cef99950f8 2025-04-24 04:39:45 +00:00 Compare

hurui200320 force-pushed feat/#8 from cef99950f8 to c7445237c9 2025-04-24 04:41:54 +00:00 Compare

hurui200320 force-pushed feat/#8 from c7445237c9 to fc59cf3318 2025-04-24 04:45:19 +00:00 Compare

hurui200320 force-pushed feat/#8 from 5dcb5675f0 to f8d072f53d 2025-04-24 04:51:45 +00:00 Compare

forgejo-actions commented 2025-04-24 04:53:03 +00:00

Copy link

Coverage is 42%

Coverage is 42%

hurui200320 force-pushed feat/#8 from f8d072f53d to 6b830b19e7 2025-04-24 04:53:08 +00:00 Compare

hurui200320 commented 2025-04-24 04:56:35 +00:00

Author

Member

Copy link

Currently, the pulp registry is not fully working due to a permission issue: when uploading the wheel files, it got 403.

As a temporary solution, the pipeline is now uploading the wheel files to forgejo: https://git.cleverthis.com/clevermicro/amq-adapter-python/actions/runs/73/artifacts/amq-adapter-dist.zip

You can also see the artifacts in the side bar of the publishing pipeline. This will be removed once the pulp registry is fully working. The retention of the artifacts is 7 days, which should be enough for us to fix the pulp registry.

Currently, the pulp registry is not fully working due to a permission issue: when uploading the wheel files, it got 403. As a temporary solution, the pipeline is now uploading the wheel files to forgejo: https://git.cleverthis.com/clevermicro/amq-adapter-python/actions/runs/73/artifacts/amq-adapter-dist.zip You can also see the artifacts in the side bar of the publishing pipeline. This will be removed once the pulp registry is fully working. The retention of the artifacts is 7 days, which should be enough for us to fix the pulp registry.

hurui200320 force-pushed feat/#8 from cb00b61b04 to 6b830b19e7 2025-04-25 04:37:49 +00:00 Compare

forgejo-actions commented 2025-04-25 04:39:03 +00:00

Copy link

Coverage is 42%

Coverage is 42%

hurui200320 force-pushed feat/#8 from ff1b93bc84 to 6b830b19e7 2025-04-28 04:46:29 +00:00 Compare

hurui200320 force-pushed feat/#8 from 6b830b19e7 to 8f93811155 2025-04-29 10:05:59 +00:00 Compare

hurui200320 force-pushed feat/#8 from 8f93811155 to c6d7e9c003 2025-04-30 03:27:37 +00:00 Compare

hurui200320 force-pushed feat/#8 from c6d7e9c003 to 046cfea8f6 2025-04-30 03:33:25 +00:00 Compare

hurui200320 force-pushed feat/#8 from 046cfea8f6 to 472ae0c2f1 2025-04-30 03:36:03 +00:00 Compare

hurui200320 changed title from WIP: Fix pipeline to Fix pipeline 2025-04-30 03:36:37 +00:00

forgejo-actions commented 2025-04-30 03:37:07 +00:00

Copy link

Coverage is 42%

Coverage is 42%

hurui200320 merged commit bde74c82b5 into develop 2025-04-30 03:38:38 +00:00

hurui200320 deleted branch feat/#8 2025-04-30 03:38:39 +00:00

hurui200320 referenced this pull request from a commit 2025-04-30 03:38:41 +00:00

Fix pipeline (#10)

Sign in to join this conversation.

Reviewers

No reviewers

abed.alrahman

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

#8 Migrate clevermicro / amq-adapter-python CI scripts to ForgeJo

clevermicro/amq-adapter-python

Reference

clevermicro/amq-adapter-python!10

No description provided.