Age | Commit message (Collapse) | Author | Files | Lines |
|
subject line of notification emails
|
|
|
|
where the build environment changed between two builds
|
|
that any status change on this package should be mailed to the maintainers. Also teach the build script how to handle that, emailing $pkgname@packages.debian.org
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
not-for-us packages
|
|
|
|
not-for-us packages
|
|
|
|
|
|
|
|
|
|
useless here
|
|
|
|
|
|
|
|
much to unstable now
|
|
|
|
|
|
|
|
hardcoding /var/lib/jenkins/userContent (that's about to change rather soon)
|
|
reproducible→unreproducible status change
|
|
|
|
|
|
* new column in the database, schedule table
* turn $SAVE_ARTIFACTS a true boolean, 0→no artifacts, 1→yes artifacts
* $NOTIFY in the build script is text containg a keyword:
+ if empty no notification will be sent
+ if "debbindiff" a "$DBDVERSION had trouble with these" will be sent
+ if "failure" a "no artifacts could have been saved"-like will be sent
+ any other value trigs a normal message
* adapt the maintenance script and the manual scheduler to cope with the new
column
|
|
jenkins log
|
|
|
|
|
|
|