tracehubpm / pmo Goto Github PK

I suggest this model of managing private repositories in a PMO:

• 1 free private project to try the platform
• $10 for each private project, the user paying once

All public projects will be free forever with support of all features.

@hizmailovich WDYT?

lets document steps required, to create a new project in a PMO

Lets send an invite to @tracehubgit in repo when project is created

We should think about JIRA Identity Provider, so we can retrieve information from JIRA and operate there. API should be similar to existing GitHub Identity Provider

The puzzle 2-e54979ee from #2 has to be resolved:

The puzzle was created by @hizmailovich on 15-Jan-24.

Estimate: 90 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

we are using

$ mvn clean install -DskipITs

to run default build cycle without integration tests, lets simplify it by removing failsafe-maven-plugin from the default maven profile, and including it only on a special profile, called simulation or something similar.

so it should look

$ mvn clean install

and for integration tests

$ mvn clean install -Psimulation

Lets change email to login, since we are not operating the emails for now, only with logins on GitHub, GitLab, and other platforms.

Emails can be added lately

The puzzle 1-ed8090c3 from tracehubpm/pmo-java-sdk#1 has to be resolved:

The puzzle was created by @rultor on 23-Jan-24.

Estimate: 45 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 44-48bf6f8b from #44 has to be resolved:

The puzzle was created by @hizmailovich on 20-Feb-24.

Estimate: 30 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 1-bb3b3f26 from tracehubpm/pmo-java-sdk#1 has to be resolved:

The puzzle was created by @rultor on 23-Jan-24.

Estimate: 45 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

we should customize our Keycloak application, so it should use our custom color palette and icons

Lets define a proper database schema and create a Liquibase migrations.

We need a project that has:

• id PRIMARY KEY, UUID
• name VARCHAR (32) NOT NULL
• description VARCHAR (512)
• active is it active or not (Boolean type)
• performers: probably we will need a new table called performer with all of the performer data and project FK

Besides things above, we need to store this data too:

• secrets which is a simple key-value pairs a.k.a secret variables, described here
• dependencies, I think it can just an array of strings in project table
• tickets the same as performers, should be a separate table with project FK, these puzzles will help you understand what kind of fields we need to store:
  • tracehubpm/tracehub#33
  • tracehubpm/tracehub#32
  • tracehubpm/tracehub#31

something does not work

More convenient way is RSE. It would be automatically handled by Spring

Can be replaced with

public class SomeExcpetion extends ResponseStatusException { 

Response:

HTTP/1.1 404
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
Date: Sat, 26 Dec 2020 19:38:09 GMT

{
    "timestamp": "2020-12-26T19:38:09.426+00:00",
    "status": 404,
    "error": "Not Found",
    "path": "/some/path"
}

We should implement a few endpoints for getting ticket information, in the database we need to store issue number, repo and full file path to the related job, and status; for instance:

issue number: #34
repo: tracehubpm/pmo
job: .trace/jobs/fix-blah-blah-blah.yml
status: status of the ticket, opened or closed.

Probably, we need 2 read-endpoints that will return us issue number by full path + repo and full path by issue number + repo.

And we need 1 write-endpoint for submitting ticket.

blocks: tracehubpm/tracehub#31, tracehubpm/tracehub#32, tracehubpm/tracehub#33

We should conduct those tickets to implement it right

The puzzle 1-ecd686dc from tracehubpm/pmo-java-sdk#1 has to be resolved:

The puzzle was created by @rultor on 23-Jan-24.

Estimate: 45 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

As I described here, we need to store secrets inside our database, to give a possibility to a user to reference the values from it:

# we are in project.yml
...
backlog:
 type: JIRA
 jira-url: ${jira-url}
...

we should create and maintain API in PMO for storing secrets, data schema probably should be something like this:

• key: the key of the secret
• value: the value of the secret

API should be simply stupid:

• save the secret with key, value
• get the value by the key

Its something new

It something new

now we doing something like this:

throw new ResourceAlreadyExistsException(...);

and we do support exception handling via Spring Exception Handlers:

We actually can get rid of this by making all our custom exceptions extend HttpStatusException. After this all of them will be handled by Spring

@hizmailovich wdyt?

section tells us:

but we have added new maven profile called simulation that runs integration tests:

needed to be fixed

The puzzle 2-24aad16a from #2 has to be resolved:

The puzzle was created by @hizmailovich on 15-Jan-24.

Estimate: 60 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

we should prepare pmo project for being deployed to cloud VM with public IPv4, I'm looking forward Yandex cloud, Selectel, and Timeweb.

Besides that, we should have PostgreSQL instance for pmo + keycloak. Timeweb cloud database service looks quite good.

On deploy, rultor should be able to pull the image with version we providing and deploy it with an environment variables bundle to the Cloud VM.

We should create an all-events webhhok, right after the project was registered in pmo.

Docs: https://docs.github.com/en/webhooks/webhook-events-and-payloads

Lets create a few labels in GitHub repo when project is created:

here is the docs: https://docs.github.com/en/rest/issues/labels?apiVersion=2022-11-28

The puzzle 44-ef410327 from #44 has to be resolved:

The puzzle was created by @hizmailovich on 20-Feb-24.

Estimate: 30 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 1-da767492 from tracehubpm/pmo-java-sdk#1 has to be resolved:

The puzzle was created by @rultor on 23-Jan-24.

Estimate: 45 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

Lets buy a domain like pmo.tracehub.git or something similar

pmo GitHub repository, does not have a README that explains how to install, run and test the pmo software, we should fix that

The puzzle 49-dbcd9483 from #49 has to be resolved:

The puzzle was created by @h1alexbel on 23-Feb-24.

Estimate: 60 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 44-57fcb942 from #44 has to be resolved:

The puzzle was created by @hizmailovich on 20-Feb-24.

Estimate: 30 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

It's not so convenient to start pmo application and docker compose services separately, let's add it to docker compose services

lets configure GitLab OAuth

something new

We should provide an alternative way of running PMO application. So, since its an open source product, each user can pull the code and run on its own servers. Lets prepare docs on how to do so. Check this one for a reference:

s3:
  region: us-east-1
  bucket: xml.0pdd.com
  key: AKIAI..........UTSQA
  secret: Z2FbKB..........viCKaYo4H..........vva21
sentry: https://[email protected]/229223
dynamo:
  region: us-east-1
  key: AKIAI..........UTSQA
  secret: Z2FbKB..........viCKaYo4H..........vva21
github:
  client_id: b96a3b5..........87e
  client_secret: be61c471154e2..........66f434d33e0f63a5f
  encryption_secret: some-random-text
  login: 0pdd
  pwd: GitHub-Password
smtp:
  host: email-smtp.us-east-1.amazonaws.com
  port: 587
  key: AKIAI..........UTSQA
  secret: Z2FbKB..........viCKaYo4H..........vva21
id_rsa: |
  -----BEGIN RSA PRIVATE KEY-----
  MIIJKAIBAAKCAgEAoE94Xy8TGMbnoK5cKJXWccr9qLLDc/liKpMAMlnQEFDCgi0l
  ...
  NaaFpowFg8LKSiwc04ERduu72Imv5GJBCkhS8F7laURXFcZiYNqBnWYzY0U=
  -----END RSA PRIVATE KEY-----

taken from https://github.com/yegor256/0pdd/?tab=readme-ov-file#how-to-contribute

how to create a project using RESTful API? I can not find any examples in neither in integration test cases nor in on Swagger UI

right after this form submitted, I got redirected to "We are sorry" on a Keycloak:

Let's remove number part from URI, soit will be /ticket/$repo/$number

for now, when keycloak just started, we need to setup secrets manually. Maybe we should think about some automation for that?

@rultor release, tag=0.0.1

The puzzle 8-e2415ebf from #8 has to be resolved:

The puzzle was created by @rultor on 06-Feb-24.

Estimate: 30 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

I enter to the GitHub sign in in Keycloak PMO:

and I got following:

What is the problem with that?
Its maybe because backend service is not running and keycloak wants to send something, but I'm not sure.