Closed
Bug 362814
Opened 18 years ago
Closed 14 years ago
nagios build files check - follow app version bumps automatically
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: rail)
Details
Attachments
(1 file, 1 obsolete file)
22.86 KB,
patch
|
nthomas
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
This is a follow up to bug 342055, where the lists of monitored files where moved to CVS. That's been a great help, but having to manually bump the version in those config files each time the app version changes shouldn't be necessary. We should just pull that information from CVS, perhaps along the lines of bug 342055 comment #9 (and later).
Comment 1•18 years ago
|
||
Assigning to Rob for monitoring script changes.
Assignee: server-ops → rhelmer
Reporter | ||
Comment 2•18 years ago
|
||
aravind/justdave: could you please attach the current nagios scripts here, to help avoid regressions. Thanks!
Comment 3•18 years ago
|
||
grabbing this so I don't lose it, I'll reassign back to rhelmer once the files are posted.
Assignee: rhelmer → justdave
Comment 4•18 years ago
|
||
The current nagios scripts are in cvs as of a month or so ago, so nothing on me anymore...
Assignee: justdave → rhelmer
Updated•18 years ago
|
Component: Server Operations → Build & Release
QA Contact: justin → preed
Reporter | ||
Comment 5•18 years ago
|
||
Taking, as I'm tinkering with this problem.
Assignee: rhelmer → nrthomas
Reporter | ||
Updated•17 years ago
|
Priority: -- → P3
Updated•17 years ago
|
QA Contact: mozpreed → build
Reporter | ||
Comment 6•17 years ago
|
||
Not actively working on this, putting it back in the pool. If anyone wants to pick it up then I have some code which might be of use.
Assignee: nrthomas → nobody
Reporter | ||
Updated•16 years ago
|
Component: Release Engineering → Release Engineering: Future
QA Contact: build → release
Comment 7•14 years ago
|
||
Mass move of bugs from Release Engineering:Future -> Release Engineering. See http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → raliiev
Reporter | ||
Comment 8•14 years ago
|
||
Everything for monitoring the freshness of nightly builds is in CVS at mozilla/tools/tinderbox-configs/monitoring Example control file - Firefox_mozilla-central.txt On stage, nagios runs 'check_nightly_builds2 Firefox_mozilla-central' Everytime we do a release the application version for nightlies gets bumped, eg from 3.5.7pre to 3.5.8pre, and we have to update the control files too. So we need a script that can look up the version from cvs/hg at the time the last nightly ran, and use that when checking the latest-$branch directory.
Assignee | ||
Comment 9•14 years ago
|
||
Nick, Thanks for your tips. After my first review I can see 2 ways to implement this feature: 1. Rewrite check_nightly_builds so that it can handle URL templates, similar to yours in bug 342055. 2. Write another script which parses templates and generates *.txt files with hard coded URLs, and commit it to CVS if there is any change. Second one doesn't require any change to the current scripts, but should be run as a cronjob and have CVS commit access. From my POV first one would be more elegant. Comments are welcome.
Status: NEW → ASSIGNED
Assignee | ||
Comment 10•14 years ago
|
||
Nick, could you review the following patch, please? Some comments. 1. Instead of playing around CVS/HG and their parameters I use mxr and hg-web to get the latest versions. 2. Seamonkey_trunk.txt shouldn't mix versions in one file and should be split into 2 files. TBD. 3. Thunderbird_trunk.txt is outdated IMO, since 1.9.1 is not trunk AFAIK. TBD. 4. In normal situations wget doesn't time out, to be tested. 5. Old style files with hard coded version can be used as well. 6. I don't have dos2unix (RH specific) on my machine, replaced with "tr -d '\r'"
Attachment #429704 -
Flags: review?(nrthomas)
Reporter | ||
Comment 11•14 years ago
|
||
Comment on attachment 429704 [details] [diff] [review] Proposed patch r- for a few things we can improve but this is a great start. >Index: Firefox_electrolysis.txt >+# VERSION_URL http://hg.mozilla.org/projects/electrolysis/raw-file/tip/browser/config/version.txt Use 'default' instead of 'tip' in all these hg urls. tip can end up on the relbranch if that's the latest change, while nightlies always come from default. Lets also take this opportunity to update these configs for files we're missing, so for Electrolysis we'd want to add firefox-@VER@.en-US.linux-x86_64.tar.bz2. We can ignore the xpi, tests archives and the new .txt files. I rotted your patch by updating this file and a couple of others, sorry about that. >Index: Firefox_mozilla1.9.0.txt >=================================================================== >+# VERSION_URL http://mxr.mozilla.org/mozilla/source/browser/config/version.txt?raw=1 The seamonkey 'module' is slightly more specific to Fx3.0 than mozilla (yes really!) and is updated more frequently. Not super awesome to be depending on mxr but good enough for branches that are going to die. >Index: XULRunner_mozilla1.9.0.txt This whole file can go away. The nagios check is being removed in bug 544678. >Index: check_nightly_builds2 >+ VER=$(wget -q --timeout=7 -O- "$VERSION_URL" | grep -v ^# | grep -v ^$ | tail -n 1) grep -P '^\d\.\d.*' might be a more direct way of testing for what we want ? >+ if [ -z $VER ]; then >+ echo "Cannot parse version information" >+ exit 0 >+ fi Perhaps we should exit 1 to be a warning state in this case. Would make tweaking the timeout easier when this is first set up. What do you think ?
Attachment #429704 -
Flags: review?(nrthomas) → review-
Assignee | ||
Comment 12•14 years ago
|
||
Nick, Thanks for your review and comments. Take 2.
Attachment #429704 -
Attachment is obsolete: true
Attachment #430242 -
Flags: review?(nrthomas)
Reporter | ||
Comment 13•14 years ago
|
||
Comment on attachment 430242 [details] [diff] [review] Proposed fix Looks good, checked in to CVS: http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&sortby=Date&date=explicit&mindate=2010-03-04+17%3A43&maxdate=2010-03-04+17%3A45&cvsroot=%2Fcvsroot
Attachment #430242 -
Flags: review?(nrthomas)
Attachment #430242 -
Flags: review+
Attachment #430242 -
Flags: checked-in+
Assignee | ||
Updated•14 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•