ci: add ci pipeline #4

New Issue

Elara6331 · 2024-04-15T18:30:10Z

Elara6331 commented

2024-04-15 18:30:10 +00:00

Add a CI pipeline that builds the Python project and publishes it to this gitea and pypi

Here's the current plan:

music-kraken-stable will be built from git tags
music-kraken will be built on every push to experimental
Version numbers will be determined automatically using git tags and commits

Edit: updated package names

Add a CI pipeline that builds the Python project and publishes it to this gitea and pypi Here's the current plan: - `music-kraken-stable` will be built from git tags - `music-kraken` will be built on every push to `experimental` - Version numbers will be determined automatically using git tags and commits Edit: updated package names

Elara6331 self-assigned this 2024-04-15 18:30:10 +00:00

Elara6331 added this to the ready for big release project 2024-04-15 18:30:10 +00:00

Hazel commented

2024-04-15 18:47:09 +00:00

This all sounds very solid.

Though I suggest naming it music-kraken-stable and music-kraken-unstable. My reasoning here consists of 2 main points:

Our capacities for testing is limited, so it gets faster noticed when more people use changes, thus making music-kraken-stable more stable (this one will be controversial and I don't know if I really want to make that argument)
Due to the nature of webscraping and the early stages of the program the stable version will more likely have more bugs than the experimental one

Thus I reccomend the experimental version, which makes the only logical conclusion imo to name it music-kraken and music-kraken-stable.

This all sounds very solid. Though I suggest naming it `music-kraken-stable` and `music-kraken-unstable`. My reasoning here consists of 2 main points: 1. Our capacities for testing is limited, so it gets faster noticed when more people use changes, thus making `music-kraken-stable` more stable (this one will be controversial and I don't know if I really want to make that argument) 2. Due to the nature of webscraping and the early stages of the program the stable version will more likely have more bugs than the experimental one Thus I reccomend the experimental version, which makes the only logical conclusion imo to name it `music-kraken` and `music-kraken-stable`.

Hazel commented

2024-04-15 18:47:59 +00:00

Also does the experimental branch need tags?
I just want to know its up to you.

Also does the experimental branch need tags? I just want to know its up to you.

Elara6331 commented

2024-04-15 18:48:42 +00:00

Thus I reccomend the experimental version, which makes the only logical conclusion imo to name it music-kraken and music-kraken-stable.

No problem

Also does the experimental branch need tags?

It doesn't. Only the stable release needs tags.

> Thus I reccomend the experimental version, which makes the only logical conclusion imo to name it music-kraken and music-kraken-stable. No problem > Also does the experimental branch need tags? It doesn't. Only the stable release needs tags.

Hazel commented

2024-04-15 18:57:23 +00:00

It doesn't. Only the stable release needs tags.

But it still bumps the version which is then also bumped for the main branch?

> It doesn't. Only the stable release needs tags. But it still bumps the version which is then also bumped for the main branch?

Elara6331 commented

2024-04-15 19:04:59 +00:00

But it still bumps the version which is then also bumped for the main branch?

No. The stable releases get their version numbers from the tags. The experimental ones are based on git revisions. Stable ones will look like 0.0.1 while experimental ones will look like 0.0.1.dev976+g2f29ad2.

> But it still bumps the version which is then also bumped for the main branch? No. The stable releases get their version numbers from the tags. The experimental ones are based on git revisions. Stable ones will look like `0.0.1` while experimental ones will look like `0.0.1.dev976+g2f29ad2`.

👍 1

Hazel added the

Kind/Enhancement

Priority

Medium

labels 2024-04-15 19:14:02 +00:00

Elara6331 added reference ci/add-pipeline

2024-04-15 23:46:51 +00:00

Elara6331 referenced a pull request that will close this issue

2024-04-16 17:46:09 +00:00

ci: add pipeline #8

Hazel closed this issue