Dusty Mabe

> For a channel to log to, would we eventually want a separate channel for the Jenkins pipeline rather than `#fedora-coreos`, e.g. `#fedora-coreos-jenkins`? Depends on how chatty it would be....

> For IRC, once we get fedora messaging working, I wonder if there's a bot in the Fedora infra which could do what we want already (i.e. fedmsg to IRC)....

There now exists a matrix plugin for jenkins: https://github.com/jenkinsci/matrix-communication-plugin since we are moving more and more away from IRC because of the libera/matrix bridge being down maybe we should explore...

In the most recent [design proposal](https://github.com/coreos/fedora-coreos-tracker/issues/194#issuecomment-669524131) we have (snippet): ---- ### Proposal: Have a tool that runs independently of the pipeline like `bump-lockfile` and `sync-stream-metadata` jenkins jobs. This tool will...

For `jobs/generate-release-notes.Jenkinsfile` are we sticking by the [design proposal](https://github.com/coreos/fedora-coreos-tracker/issues/194#issuecomment-669524131) (snippet): ---- #### Git repository manipulation - look at the `release-notes.yaml` file for the related branch (i.e. `testing`) - if an...

> > jobs/generate-release-notes.Jenkinsfile basically polls the release metadata to see what the latest release > > @dustymabe Yes, the only portion that I depend on `Jenkinsfile` was the retrieving the...

> From [coreos/fedora-coreos-config#550 (comment)](https://github.com/coreos/fedora-coreos-config/pull/550#discussion_r472494658) I've reorganized the logic to reflect the workflow without a `next-release` field: > > ``` > # Before promotion, engineers add yaml snippets under release-notes.d in...

I think this should fix issues like seen in https://jenkins-fedora-coreos-pipeline.apps.ocp.fedoraproject.org/blue/organizations/jenkins/release/detail/release/465/pipeline Before this change: ``` job starts: - takes build lock job 2 starts: - wait on build lock job approaches...

> Hmm, I think the problem here is that `cosa push-container` doesn't support taking the build ID and always tries to use the latest build. Independently of what we do...

did some trivial testing on this. It seems to work