Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • deb-build-jobs deb-build-jobs
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.

  • Librem5
  • deb-build-jobsdeb-build-jobs
  • Merge requests
  • !435

pipeline: Notify about attempted builds

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Dorota Czaplejewicz requested to merge dorota.czaplejewicz/deb-build-jobs:notify into pureos/byzantium Nov 30, 2022
  • Overview 16
  • Commits 1
  • Pipelines 1
  • Changes 1

Right now there's no way to find out if the tag has been accepted, making it compulsory for the committer to interrupt their packaging work. It's very frustrating, especially for those who aren't confident in their packaging.

This sends a message whenever a tag is considered.


Of course, this is completely untested. I'm not going to mark it as a draft, because this repo doesn't provide any instructions for testing, so I did my homework.


This has been a pain since forever. The build process is trying to be as quiet as possible, making failures as easy to forget about as possible, only posting on an obscure mailing list that you basically have to know about. Email notification is the opposite: delivered to a known place, and before the long build starts, so that my attention doesn't have time to wander, either.

Consider this part of my mission to fix the dread of releasing for pureOS.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: notify