#258 Create a bot account for CI/CD pipelines
Closed: Fixed 5 years ago by gnaponie. Opened 6 years ago by rayson.

Using an API key identifies the API caller as the key creator. Making a comment via Pagure API appears like the comment is made from a person.

Can we create a bot account for non-human operations? If it is, how should we manage that account?


An example of comments from Jenkins: https://pagure.io/fork/rayson/waiverdb/pull-request/9

Create only FAILED comments please. I'm not interested in getting lot of "build started" or even "succeeded" mails -- this is already happening with some other project (in Gerrit) and sometimes it's hard to find the important comments.

Shorter message would be also nice, e.g.:

[Build FAILED!](https://jenkins-waiverdb-test.cloud.paas.upshift.redhat.com/job/waiverdb-test/job/waiverdb-test-stage-waiverdb-dev/61/)

Would this be a pagure bot account? We can store its creds in our secrets repo internally.

@lucarval Yeah, a Pagure account for bots. Should I create it or someone else?

@lholecek Thanks. Now it only creates failed comments.
I would like to put the commit sha256 to make distinguish of rebuilds and mention Rebase or make new commits to rebuild. because some developers may not know how to re-trigger a build. See https://pagure.io/fork/rayson/waiverdb/pull-request/9 again as an example.

@pingou Is there a way to create bot accounts in Pagure?

@pingou Is there a way to create bot accounts in Pagure?

Not yet, but there is a ticket to track this feature: https://pagure.io/pagure/issue/3553

I am planning to create a bot account of Paugue. Which email address should I use (is the mailing list safe?) and where should I keep the password?

This is gonna be addressed by something that @csomh is working on. We are going to use factory2-jenkins account.

Metadata Update from @gnaponie:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Metadata Update from @gnaponie:
- Issue status updated to: Open (was: Closed)

5 years ago

@gnaponie Can I please ask if there's a reason for this to be reopened?

I have no idea why I re-opened it. Let's close it.

Metadata Update from @gnaponie:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Log in to comment on this ticket.

Metadata