-
Notifications
You must be signed in to change notification settings - Fork 7
/
Copy pathindex.html
1264 lines (813 loc) · 56.6 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<!--[if IEMobile 7 ]><html class="no-js iem7"><![endif]-->
<!--[if lt IE 9]><html class="no-js lte-ie8"><![endif]-->
<!--[if (gt IE 8)|(gt IEMobile 7)|!(IEMobile)|!(IE)]><!--><html class="no-js" lang="en"><!--<![endif]-->
<head>
<meta charset="utf-8">
<title>/* steve jansen */</title>
<meta name="author" content="Steve Jansen">
<meta name="description" content="The Jenkins credentials-binding plugin
provides a convenient way to securely store secrets like usernames/passwords in
Jenkins. You can even inject …">
<!-- http://t.co/dKP3o1e -->
<meta name="HandheldFriendly" content="True">
<meta name="MobileOptimized" content="320">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="canonical" href="http://steve-jansen.github.io/">
<link href="/favicon.png" rel="icon">
<link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet" type="text/css">
<script src="/javascripts/modernizr-2.0.js"></script>
<script src="/javascripts/ender.js"></script>
<script src="/javascripts/octopress.js" type="text/javascript"></script>
<link href="/atom.xml" rel="alternate" title="/* steve jansen */" type="application/atom+xml">
<!--Fonts from Google"s Web font directory at http://google.com/webfonts -->
<link href="http://fonts.googleapis.com/css?family=PT+Serif:regular,italic,bold,bolditalic" rel="stylesheet" type="text/css">
<link href="http://fonts.googleapis.com/css?family=PT+Sans:regular,italic,bold,bolditalic" rel="stylesheet" type="text/css">
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-43558425-1']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script>
</head>
<body >
<header role="banner"><hgroup>
<h1><a href="/">/* steve jansen */</a></h1>
<h2>// another day in paradise hacking code and more</h2>
</hgroup>
</header>
<div id="main">
<div id="content">
<div class="blog-index">
<article>
<header>
<h1 class="entry-title"><a href="/blog/2014/12/16/parsing-jenkins-secrets-in-a-shell-script/">Parsing Jenkins Secrets in a Shell Script</a></h1>
<p class="meta">
<time datetime="2014-12-16T14:39:54-05:00" pubdate data-updated="true">Dec 16<span>th</span>, 2014</time>
| <a href="/blog/2014/12/16/parsing-jenkins-secrets-in-a-shell-script/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>The <a href="https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Binding+Plugin">Jenkins credentials-binding plugin</a>
provides a convenient way to securely store secrets like usernames/passwords in
Jenkins. You can even inject these secrets into build steps as environmental
variables in a job like this:</p>
<p><img src="/images/2014-12-16.png" alt="screenshot of a Jenkins job using the credentials-binding plugin" /></p>
<p>For a username/password pair, the plugin will inject the pair as a single value
joined by <code>:</code>. You can split the credentials into their respective parts
using <a href="http://spin.atomicobject.com/2014/02/16/bash-string-maniuplation/">bash string manipulation operators like <code>%</code> and <code>#</code></a>.</p>
<p>Assuming you configured the job to inject a variable named <code>CREDENTIALS</code>, you can do:</p>
<figure class='code'><figcaption><span>[parsing Jenkins secret credentials with bash]</span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'><span class="nv">USERNAME</span><span class="o">=</span><span class="k">${</span><span class="nv">CREDENTIALS</span><span class="p">%:*</span><span class="k">}</span>
</span><span class='line'><span class="nv">PASSWORD</span><span class="o">=</span><span class="k">${</span><span class="nv">CREDENTIALS</span><span class="p">#*:</span><span class="k">}</span>
</span><span class='line'>
</span><span class='line'><span class="c"># proof of concept - don't echo this in real life :)</span>
</span><span class='line'><span class="nb">echo </span><span class="nv">USERNAME</span><span class="o">=</span><span class="nv">$USERNAME</span>
</span><span class='line'><span class="nb">echo </span><span class="nv">USERNAME</span><span class="o">=</span><span class="nv">$PASSWORD</span>
</span></code></pre></td></tr></table></div></figure>
</div>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2014/12/15/jenkins-job-to-export-rackspace-cloud-dns-domain-as-bind-zone-files/">Jenkins Job to Export Rackspace Cloud DNS Domain as BIND Zone Files</a></h1>
<p class="meta">
<time datetime="2014-12-15T09:39:33-05:00" pubdate data-updated="true">Dec 15<span>th</span>, 2014</time>
| <a href="/blog/2014/12/15/jenkins-job-to-export-rackspace-cloud-dns-domain-as-bind-zone-files/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>Rackspace Cloud DNS offeres a great web console, along with a solid API for managing
DNS records dynamically from CM tools like Chef.</p>
<p>The web UI @ <a href="https://mycloud.rackspace.com">https://mycloud.rackspace.com</a> doesn’t (yet) suppport an action to
export your domain(s) to standard BIND format zone files.</p>
<p>However, the API does support zone file exports,
<a href="http://docs.rackspace.com/cdns/api/v1.0/cdns-devguide/content/GET_exportDomain_v1.0__account__domains__domainId__export_domains.html"><code>GET /v1.0/{account}/domains/{domainId}/export</code></a>.</p>
<p>I wanted to create a scheduled Jenkins job to export a domain managed by
Cloud DNS to GitHub for both versioning and disaster recovery.</p>
<p>One gotcha with the API is it’s asynchronous – you request an export, then
periodically poll on the status of the export. The API also has rate limiting.
So, the export is a bit more involved than a simple <code>curl</code> call.</p>
<p>Based on <a href="https://community.rackspace.com/products/f/25/t/1743">this Rackspace community support post</a>,
I found a great python utility, <a href="https://github.com/wichert/clouddns">clouddns.py by Wichert Akkerman</a>.</p>
<blockquote><p>Note: I couldn’t use the <a href="https://github.com/rackspace/pyrax">https://github.com/rackspace/pyrax</a> official SDK,
as I’m on CentOS 6.5 with Python 2.6, and the SDK requires Python 2.7. I also tried
the <a href="https://gist.github.com/DavidWittman/4727690">gist by DavidWittman</a> but failed
to get it working with the LON region despte following
<a href="https://github.com/rackerlabs/python-clouddns/blob/master/README.rst">the clouddns README</a></p></blockquote>
<p>Here’s the basis of the script I used in a Jenkins job to export a domain and subdomains
every 15 minutes, alongw with the Git publisher for Jenkins to push the changes back to
a GitHub repo.</p>
<div><script src='https://gist.github.com/14dddef6fa0318761e3c.js'></script>
<noscript><pre><code>#!/bin/bash
# exports DNS records from Rackspace Cloud DNS to text files
# Depends on https://github.com/wichert/clouddns/blob/master/src/clouddns.py
set -e
me=export-zone
base_domain=
rackspace_region=
rackspace_rate_limit_delay=3
script_root=$(cd `dirname "${BASH_SOURCE[0]}"` && pwd)
function usage() {
cat << EOF
Usage: `basename "${BASH_SOURCE[0]}"` [domain]
exports a Racksapce Cloud DNS domain and subdomains to zone files"
domain - an optional filter for the domain to export, defaults to all
EOF
exit 1
}
[ "$1" == "-?" ] && usage
[ "$1" == "--help" ] && usage
echo "[$me] verifying Rackspace API credentials ..."
if [ -z "$OS_USERNAME" ] || [ -z "$OS_PASSWORD" ]; then
echo "[$me] error - missing rackspace credentials - you may need a openrc file" >&2
echo "[$me] see http://docs.rackspace.com/servers/api/v2/cs-gettingstarted/content/section_gs_install_nova.html#d6e1129" >&2
exit 1
fi
if echo "$OS_REGION_NAME" | grep -i "LON" >/dev/null 2>&1; then
rackspace_region=uk
else
rackspace_region=us
fi
echo "[$me] verifying python dependencies ..."
if ! python --version >/dev/null 2>&1; then
echo "[$me] error - python runtime not found" >&2
echo "[$me] see https://www.python.org/downloads/" >&2
exit 2
fi
if ! pip --version >/dev/null 2>&1; then
echo "[$me] error - missing python dependency - pip" >&2
echo "[$me] see https://pip.pypa.io/en/latest/installing.html" >&2
exit 2
fi
if ! pip install --user isodate >/dev/null; then
echo "[$me] error - pip install isodate failed" >&2
exit 3
fi
if ! pip install --user requests >/dev/null; then
echo "[$me] error - pip install requets failed" >&2
exit 3
fi
echo "[$me] downloading wichert/clouddns from GitHub ..."
curl -L -o "$script_root/clouddns.py" 'https://raw.githubusercontent.com/wichert/clouddns/master/src/clouddns.py'
if [ -z "$1" ]; then
base_domain="."
else
base_domain="$1"
fi
clouddns_command="python ""$script_root/clouddns.py"" --region ""$rackspace_region"" \
--username ""$OS_USERNAME"" \
--api ""$OS_PASSWORD"""
echo "[$me] exporting zone files for $base_domain ..."
domain_list=`$clouddns_command list | \
awk '{print $1}' | \
grep "$base_domain" | \
sort`
for domain in $domain_list;
do
echo "[$me] exporting $domain ..."
# ignore errors in exporting a subdomain, which can happen due to rate limiting
# assume the next run will export the subdomain
set +e
$clouddns_command export-zone "$domain" > "$domain.txt"
set -e
# avoid Rackspace API rate limiting errors
echo "[$me] sleeping $rackspace_rate_limit_delay seconds ..."
sleep $rackspace_rate_limit_delay
done
exit 0
</code></pre></noscript></div>
</div>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2014/12/03/troubleshooting-github-webhooks-ssl-verification/">Troubleshooting GitHub WebHooks SSL Verification</a></h1>
<p class="meta">
<time datetime="2014-12-03T10:28:37-05:00" pubdate data-updated="true">Dec 3<span>rd</span>, 2014</time>
| <a href="/blog/2014/12/03/troubleshooting-github-webhooks-ssl-verification/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>GitHub WebHooks and Jenkins go together like peanut butter and jelly.
<a href="http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/">SCM Webhook trggers are way more efficient for Jenkins over SCM polling</a>. Webhooks also give you a great UX – Jenkins reacts
immediately when you push a commit or open a pull request.</p>
<p>I am a huge fan of using <a href="https://github.com/jenkinsci/github-oauth-plugin">GitHub OAuth for single sign on with Jenkins</a>.
The security of OAuth really depends on TLS/SSL for protecting the token in transit,
so your Jenkins should use SSL when using GitHub OAuth.</p>
<p>GitHub’s Webhooks have the option to perform SSL certificate validation. I’ve
run into issues with GitHub’s “Hookshot” HTTP engine failing SSL verification for
otherwise valid certificates. Most of my problems were related to installing
intermediate CA certificates on Jenkins.</p>
<h2>GitHub WebHook configuration and SSL certificate verification</h2>
<p>Here’s an example of a pull request webhook failing SSL validation in GitHub:</p>
<p><img src="/images/2014-12-03-A.png" alt="Screenshot of a failed certificate validation in a GitHub WebHook configuratioon screen" /></p>
<p>GitHub will send a “hello, world” webhook ping when you create a new webhook. Note
that SSL verification failures will have an usual HTTP response code of <code>0</code>:
<img src="/images/2014-12-03-B.png" alt="Screenshot of a "hello, world" webhook ping from GitHub" /></p>
<p>The response tab will be empty:
<img src="/images/2014-12-03-C.png" alt="Screenshot of a "hello, world" webhook ping from GitHub" /></p>
<h2>Troubleshoot your SSL certificate with the Symantec SSL Toolbox</h2>
<p>Symantec offers a very helpful <a href="https://ssltools.websecurity.symantec.com/checker/">tool to check your certificate installation</a>
as part of their “SSL Toolbox”. The tool offers suggestions to remedy certificate
issues and links to download missing intermediate CA certificates.</p>
<p>Here’s an example of a Symantec diagnostic failure due to a missing intermediate certificate:</p>
<p><img src="/images/2014-12-03-D.png" alt="Screenshot of a failed certificate validation in the Symantec SSL Toolbox" /></p>
<h2>Using the Symantec SSL Toolbox against servers with IP ACLs</h2>
<p>A great feature of the Symantec SSL Tool is how the tool supports non-public servers
behind a firewall. The tool will first attempt to verify your cert from
a Symantec server. If your server is behind a firewall that denies public access
except for whitelisted origins, the SSL toolbox has a fallback mode to run a Java applet
in your browser. The applet will perform the SSL verification
requests from local machine rather than a Symantec server.</p>
<blockquote><p><strong>TIP:</strong> GitHub publishes their public IP range for webhooks as part of the
<a href="https://api.github.com/meta">GitHub metadata API</a> if you wish to create firewall
whitelist rules for GitHub webhook requests.</p></blockquote>
<h2>Symanetc SSL Toolbox Applet and OS X Java security</h2>
<p>Given the recent security vulnerabilities of Java applets, getting the applet to run
on OS X takes some work. Here are the setting I need to use the applet in Safari 7.1
on OS X 10.9.5 (Mavericks) using the Oracle/Sun JRE 1.7 R71.
(I never succeeded in using the applet in Firefox or Chrome despite serious effort.)</p>
<p>I needed to enable Safari to run the SSL Toolbox applets in “unsafe mode” without prompting:
<img src="/images/2014-12-03-E.png" alt="Screenshot of a Safari security settings for the Symantec SSL Toolbox" /></p>
<p>I also had to temporarily downgrade the JVM 1.7 browser security level to “Medium” and
add an execption for <code>https://ssltools.websecurity.symanttec.com</code>:</p>
<p><img src="/images/2014-12-03-F.png" alt="Screenshot of a JVM security settings for the Symantec SSL Toolbox" /></p>
<h2>Green is good!</h2>
<p>Once you’ve resolved your certificate issues, you should see green in both the
Symantec SSL Toolbox and the GitHub WebHook requests after enabling SSL verification.</p>
<p><img src="/images/2014-12-03-G.png" alt="Screenshot of a succesful certificate validation in the Symantec SSL Toolbox" /></p>
<p><img src="/images/2014-12-03-H.png" alt="Screenshot of a succesful certificate validation in a GitHub WebHook configuration screen" /></p>
</div>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2014/12/01/integrating-rackspace-auto-scale-groups-with-objectrocket-mongo-databases/">Integrating Rackspace Auto Scale Groups With ObjectRocket Mongo Databases</a></h1>
<p class="meta">
<time datetime="2014-12-01T13:00:58-05:00" pubdate data-updated="true">Dec 1<span>st</span>, 2014</time>
| <a href="/blog/2014/12/01/integrating-rackspace-auto-scale-groups-with-objectrocket-mongo-databases/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>Thanks to some pretty awesome support from Jon Fanti and John Moore at <a href="http://objectrocket.com">ObjectRocket</a>,
I learned this week that we had missed two key optimizations for using ObjectRocket MongoDBs with Rackspace
Auto Scaling groups (ASGs).</p>
<h2>ServiceNet</h2>
<p>First, ObjectRocket support can provide medium and large customers with a server FQDN that resolves to a
<a href="http://www.rackspace.com/knowledge_center/frequently-asked-question/what-is-servicenet">ServiceNet</a> private IP.
You can use this FQDN instead of the server name shown in the connect string for your instance. As long
as your cloud servers and ObjectRocket are in the same Rackspace data center, the ServiceNet connection string
will avoid data transfer charges and keep your packets from transiting the public Internet.</p>
<h2>Dynamic IP ACLs</h2>
<p>We struggled to manually maintain the list of authorized IPs for our ObjectRocket MongoDB instances
when a ASG would add a new node. We had a backlog plan to script the IP ACLs using Chef, but, hadn’t
found the time yet.</p>
<p>Fortunately, ObjectRocket already supports this! See <a href="https://app.objectrocket.com/external/rackspace">https://app.objectrocket.com/external/rackspace</a></p>
<p><img src="/images/2014-12-01.png" alt="Screenshot of ObjectRocket integration with Rackspace" /></p>
<p>According to John, the ObjectRocket integration with your Rackspace Cloud account will automatically sync
the IP ACLs with your list of current Cloud VMs. Moreover, the integration will ignore any manual IP ACLs
you create (as long as your description doesn’t use the <code>rax-</code> prefix).</p>
</div>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2014/11/20/how-to-use-jenkins-to-monitor-cron-jobs/">How to Use Jenkins to Monitor Cron Jobs</a></h1>
<p class="meta">
<time datetime="2014-11-20T17:46:46-05:00" pubdate data-updated="true">Nov 20<span>th</span>, 2014</time>
| <a href="/blog/2014/11/20/how-to-use-jenkins-to-monitor-cron-jobs/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>Cron jobs have a funny way of being ignored. Either no one knows the job is failing because the job
doesn’t tell anyone. Or, the job is spamming your e-mail inbox many times a day, regardless of success
or failure, which means you just ignore the e-mails.</p>
<p>I’ve seen the “Monitor an external job” option for new Jenkins jobs before, and never paid much attention.
Turns out it’s a great bucket for storing logs and results of cron jobs.</p>
<p>The <a href="https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs">external-monitor-job</a> plugin
seems to ship with the Jenkins war file. So, your Jenkins should have it out of the box.</p>
<p>Creating a job is pretty simple. It’s just a name and description. Click “New Item” in Jenkins and
select the “Monitor an external job” option. This creates a job of type <code>hudson.model.ExternalJob</code>.</p>
<p>The <a href="https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs">wiki</a> describes a
fairly complicated method to download the Jenkins jar files onto the server running
your cron jobs, and then use the Java runtime to run a jar with your cron script as an
argument. The jar presumably forks your a new shell to run your desired cron command and
sends the output/result to Jenkins.</p>
<p>There’s a much easier way to do this. Redirect or <code>tee</code> your job’s stdout/stderr output to a
temp file. Then post the result code and log file via <code>curl</code> to Jenkins. No need to
download jar files. No need to even have Java runtime on the server.</p>
<p>Just POST a small XML document with the log contents (binary encoded) and the
exit code to Jenkins @ <code>/job/:jobName/postBuildResult</code> where <code>:jobName</code> is the
URL encoded name of your monitoring job in Jenkins.</p>
<figure class='code'><figcaption><span>[example cron script]</span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
<span class='line-number'>18</span>
<span class='line-number'>19</span>
<span class='line-number'>20</span>
<span class='line-number'>21</span>
<span class='line-number'>22</span>
<span class='line-number'>23</span>
<span class='line-number'>24</span>
<span class='line-number'>25</span>
<span class='line-number'>26</span>
<span class='line-number'>27</span>
<span class='line-number'>28</span>
<span class='line-number'>29</span>
<span class='line-number'>30</span>
<span class='line-number'>31</span>
<span class='line-number'>32</span>
<span class='line-number'>33</span>
<span class='line-number'>34</span>
<span class='line-number'>35</span>
<span class='line-number'>36</span>
<span class='line-number'>37</span>
<span class='line-number'>38</span>
<span class='line-number'>39</span>
<span class='line-number'>40</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'><span class="c">#!/bin/sh</span>
</span><span class='line'><span class="c"># example cron script to post logs to Jenkins</span>
</span><span class='line'>
</span><span class='line'><span class="c"># exit on error</span>
</span><span class='line'><span class="nb">set</span> -e
</span><span class='line'>
</span><span class='line'><span class="nv">log</span><span class="o">=</span><span class="sb">`</span>mktemp -t tmp<span class="sb">`</span>
</span><span class='line'><span class="nv">timer</span><span class="o">=</span><span class="sb">`</span>date +<span class="s2">"%s"</span><span class="sb">`</span>
</span><span class='line'><span class="nv">jenkins_job</span><span class="o">=</span>my_monitoring_job
</span><span class='line'><span class="nv">jenkins_server</span><span class="o">=</span>http://jenkins.example.com:8080/jenkins/job/<span class="nv">$jenkins_job</span>/postBuildResult
</span><span class='line'><span class="c"># see http://jenkins.example.com:8080/me/configure to get your username and API token</span>
</span><span class='line'><span class="nv">jenkins_username</span><span class="o">=</span>myusername
</span><span class='line'><span class="nv">jenkins_token</span><span class="o">=</span>abcdef0123456789fedcba9876543210
</span><span class='line'>
</span><span class='line'><span class="k">function </span>banner<span class="o">()</span> <span class="o">{</span>
</span><span class='line'> <span class="nb">echo</span> <span class="k">$(</span><span class="nb">printf</span> <span class="s1">'#%.0s'</span> <span class="o">{</span>1..80<span class="o">}</span><span class="k">)</span> >> <span class="s2">"$log"</span>
</span><span class='line'><span class="o">}</span>
</span><span class='line'>
</span><span class='line'><span class="k">function </span>report<span class="o">()</span> <span class="o">{</span>
</span><span class='line'> <span class="nv">result</span><span class="o">=</span><span class="nv">$?</span>
</span><span class='line'> <span class="nv">timer</span><span class="o">=</span><span class="k">$((</span><span class="sb">`</span>date +<span class="s2">"%s"</span><span class="sb">`</span> <span class="o">-</span> <span class="nv">$timer</span><span class="k">))</span>
</span><span class='line'>
</span><span class='line'> banner
</span><span class='line'> <span class="nb">echo</span> <span class="s2">"`whoami`@`hostname -f` `date`: elapsed $timer second(s)"</span> >> <span class="s2">"$log"</span>
</span><span class='line'> <span class="nb">echo</span> <span class="s2">"exit code $result"</span> >> <span class="s2">"$log"</span>
</span><span class='line'>
</span><span class='line'> <span class="c"># binary encode the log file for Jenkins</span>
</span><span class='line'> <span class="nv">msg</span><span class="o">=</span><span class="sb">`</span>cat <span class="s2">"$log"</span> | hexdump -v -e <span class="s1">'1/1 "%02x"'</span><span class="sb">`</span>
</span><span class='line'>
</span><span class='line'> <span class="c"># post the log to jenkins</span>
</span><span class='line'> <span class="nb">echo </span>curl -X POST <span class="se">\</span>
</span><span class='line'> -u <span class="s2">"$jenkins_username:$jenkins_token"</span> <span class="se">\</span>
</span><span class='line'> -d <span class="s2">"<run><log encoding=\"hexBinary\">$msg</log><result>$result</result><duration>$timer</duration></run>"</span> <span class="se">\</span>
</span><span class='line'> <span class="nv">$jenkins_server</span>/job/<span class="nv">$jenkins_job</span>/postBuildResult
</span><span class='line'><span class="o">}</span>
</span><span class='line'>
</span><span class='line'><span class="nb">trap </span>report EXIT;
</span><span class='line'>
</span><span class='line'>banner
</span><span class='line'><span class="nb">echo</span> <span class="s2">"hello, world @ `date`!"</span> | tee <span class="s2">"$log"</span>
</span></code></pre></td></tr></table></div></figure>
<figure class='code'><figcaption><span>[sample `crontab -e` entry]</span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'><span class="nv">MAILTO</span><span class="o">=</span><span class="s2">""</span>
</span><span class='line'>0 * * * * /bin/sh /your/directory/myjob.sh
</span></code></pre></td></tr></table></div></figure>
<p>A sample of the build log on Jenkins with a green/red build status:</p>
<p><img src="images/2014-11-20.png" alt="Sample Jenkins Build Log" /></p>
<p>Credit to <a href="http://stackoverflow.com/a/25611940/1995977">Taytay on Stackoverflow.com</a>
for figuring out how to use <code>hexdump</code> to properly encode the XML for Jenkins.</p>
</div>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2014/10/17/finding-chef-nodes-bootstrapped-in-the-last-x-hours/">Finding Chef Nodes Bootstrapped in the Last X Hours</a></h1>
<p class="meta">
<time datetime="2014-10-17T18:47:44-04:00" pubdate data-updated="true">Oct 17<span>th</span>, 2014</time>
| <a href="/blog/2014/10/17/finding-chef-nodes-bootstrapped-in-the-last-x-hours/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>I needed to write a script to garbage collect old nodes in Chef related to
auto-scaling groups.</p>
<p>I decided to search for nodes bootstrapped in the last X hours.</p>
<p>I experimented with ways to find nodes that have been up for less than X hours.
In this example, I search for nodes that have been up for 8 hours or less.
Of course, this assumes you never restart your nodes:</p>
<figure class='code'><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
</pre></td><td class='code'><pre><code class=''><span class='line'>knife exec -E 'search(:node, "uptime_seconds:[0 TO #{ 8 * 60 * 60 }]") { |n| puts n.name }'</span></code></pre></td></tr></table></div></figure>
<p>I also tried finding nodes that converged in the last 8 hours (which would have
to be combined with some other filter of course):</p>
<figure class='code'><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
</pre></td><td class='code'><pre><code class=''><span class='line'>knife exec -E 'b = Time.now.to_i; a = (b - (8*60*60)).to_i; search(:node, "ohai_time:[#{a} TO #{b}]") { |n| puts n.name }'</span></code></pre></td></tr></table></div></figure>
<p>Overall, I think the easiest option is to just set a node attribute like
‘bootstrap_date’ at bootstrap (or set it if it’s nil). This would be a clearcut
way to find out how old a node truly is.</p>
<p>One of my colleagues pointed out that <a href="https://github.com/opscode/chef-metal">Chef Metal</a>
sets a very handy <code>node['metal']['location']['allocated_at']</code> attribute that gets
the job done if you are spinning up new nodes with metal.</p>
</div>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2014/10/03/regexes-for-the-serverspec-2-update/">Regexes for the Serverspec 2 Update</a></h1>
<p class="meta">
<time datetime="2014-10-03T18:24:25-04:00" pubdate data-updated="true">Oct 3<span>rd</span>, 2014</time>
| <a href="/blog/2014/10/03/regexes-for-the-serverspec-2-update/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>The Serverspec team just released v2 of their outstanding testing library
today, after a very long beta period. The v2 release had a
<a href="http://serverspec.org/changes-of-v2.html">few breaking breaking changes</a>
due to dropped rspec matchers that had been deprecated.</p>
<p>If your <a href="http://kitchen.ci/">test-kitchen</a> tests recently broke today,
here’s a few regexes I used with Sublime Text’s regex find/replace
to rewrite the dropped matchers for the new matchers.</p>
<figure class='code'><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
</pre></td><td class='code'><pre><code class=''><span class='line'>it\s*\{\s*(should|should_not)\s*return_(stdout|stderr)\s*\(?(\/.*\/)\)?\s*\}
</span><span class='line'>its(:\2) { \1 match \3 }
</span><span class='line'>
</span><span class='line'>it\s*\{\s*(should|should_not)\s*return_(stdout|stderr)\s*\(?(\".*\")\)?\s*\}
</span><span class='line'>its(:\2) { \1 contain \3 }
</span><span class='line'>
</span><span class='line'>it\s*\{\s*(should|should_not)\s*return_(stdout|stderr)\s*\(?('.*')\)?\s*\}
</span><span class='line'>its(:\2) { \1 contain \3 }
</span><span class='line'>
</span><span class='line'>it\s*\{\s*(should|should_not)\s*return_exit_status\s*(\d+)\s*\}
</span><span class='line'>its(:exit_status) { \1 eq \2 }</span></code></pre></td></tr></table></div></figure>
<p>Hopefully the kitchen busser project will one day add support for
Gemfile-style constraints on the test node, since busser always
<a href="https://github.com/test-kitchen/test-kitchen/issues/242#issuecomment-28991870">installs the latest version of a busser plugin gem today.</a>.</p>
</div>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2014/08/27/chefing-custom-nginx-configs-with-the-nginx-cookbook/">Chef’ing Custom Nginx Configs With the Nginx Cookbook</a></h1>
<p class="meta">
<time datetime="2014-08-27T19:41:10-04:00" pubdate data-updated="true">Aug 27<span>th</span>, 2014</time>
| <a href="/blog/2014/08/27/chefing-custom-nginx-configs-with-the-nginx-cookbook/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>The <a href="http://supermarket.getchef.com/cookbooks/nginx">nginx</a> cookbook has been
super helpful Chef’ing some web apps recently. One thing I struggled to
understand was how to use my own custom conf, like <code>/etc/nginx/nginx.conf</code>, that
is optimized for how I use nginx.</p>
<p>One solution I tried, which is probably a Chef anti-pattern, is to only include
the nginx cookbook on the initial converge:</p>
<h2>The Wrong Way</h2>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="c1"># the nginx community cookbook will relentlessly revert conf files,</span>
</span><span class='line'><span class="c1"># so avoid running it unless nginx isn't installed,</span>
</span><span class='line'><span class="c1"># or we explicitly reset/delete the node attribute</span>
</span><span class='line'><span class="n">include_recipe</span> <span class="s1">'nginx'</span> <span class="k">unless</span> <span class="n">node</span><span class="o">[</span><span class="s1">'nginx'</span><span class="o">][</span><span class="s1">'installed'</span><span class="o">]</span>
</span><span class='line'><span class="n">node</span><span class="o">.</span><span class="n">set</span><span class="o">[</span><span class="s1">'nginx'</span><span class="o">][</span><span class="s1">'installed'</span><span class="o">]</span> <span class="o">=</span> <span class="kp">true</span>
</span><span class='line'>
</span><span class='line'><span class="c1"># our custom nginx.conf</span>
</span><span class='line'><span class="n">template</span> <span class="s1">'/etc/nginx/nginx.conf'</span> <span class="k">do</span>
</span><span class='line'> <span class="n">source</span> <span class="s1">'nginx.conf.erb'</span>
</span><span class='line'> <span class="n">owner</span> <span class="s1">'root'</span>
</span><span class='line'> <span class="n">group</span> <span class="s1">'root'</span>
</span><span class='line'> <span class="n">mode</span> <span class="s1">'0644'</span>
</span><span class='line'> <span class="n">notifies</span> <span class="ss">:reload</span><span class="p">,</span> <span class="s2">"service[nginx]"</span><span class="p">,</span> <span class="ss">:delayed</span>
</span><span class='line'><span class="k">end</span>
</span></code></pre></td></tr></table></div></figure>
<p>I knew this was wrong when I wrote it. Chef is all about idempotency.
But, I couldn’t figure out a way to keep the nginx cookbook from reverting my
custom conf during subsequent converges, only to have my <code>template</code> restore my
custom conf a few seconds later.</p>
<h2>The Better Way</h2>
<p>The OpsCode blog <a href="http://www.getchef.com/blog/2013/12/03/doing-wrapper-cookbooks-right/">Doing Wrapper Cookbooks Right</a> shows the right way, and really opened my eyes on the power of
Chef’s two phase model (compile, then converge).</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="n">include_recipe</span> <span class="s1">'nginx'</span>
</span><span class='line'>
</span><span class='line'><span class="c1"># use our custom nginx.conf, rather than the one that ships in the nginx cookbook</span>
</span><span class='line'><span class="c1"># this avoids the nginx and my-app cookbooks from fighting for control of</span>
</span><span class='line'><span class="c1"># the same target file</span>
</span><span class='line'><span class="n">resources</span><span class="p">(</span><span class="s1">'template[nginx.conf]'</span><span class="p">)</span><span class="o">.</span><span class="n">cookbook</span> <span class="s1">'my-app'</span>
</span></code></pre></td></tr></table></div></figure>
</div>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2014/07/19/json-proxy-release-0-dot-2-0/">Json-proxy Release 0.2.0</a></h1>
<p class="meta">
<time datetime="2014-07-19T10:20:56-04:00" pubdate data-updated="true">Jul 19<span>th</span>, 2014</time>
| <a href="/blog/2014/07/19/json-proxy-release-0-dot-2-0/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>Happy to announce a new release of <a href="https://www.npmjs.org/package/json-proxy">json-proxy</a>, a
utility for HTML5 devs to run apps locally and proxy calls like <a href="http://localhost:9000/api">http://localhost:9000/api</a> to
a remote server, all without CORS or JSONP.</p>
<h2>Grunt Plugin</h2>
<p>This release includes better support for running as a grunt plugin.
A <a href="https://github.com/gruntjs/grunt-contrib-connect/pull/85">change in [email protected]</a>
simplifies life for proxy plugins inside the livereload task of <code>grunt serve</code>:</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
<span class='line-number'>18</span>
<span class='line-number'>19</span>
<span class='line-number'>20</span>
<span class='line-number'>21</span>
<span class='line-number'>22</span>
</pre></td><td class='code'><pre><code class='js'><span class='line'><span class="nx">livereload</span><span class="o">:</span> <span class="p">{</span>
</span><span class='line'> <span class="nx">options</span><span class="o">:</span> <span class="p">{</span>
</span><span class='line'> <span class="nx">middleware</span><span class="o">:</span> <span class="kd">function</span><span class="p">(</span><span class="nx">connect</span><span class="p">,</span> <span class="nx">options</span><span class="p">,</span> <span class="nx">middlewares</span><span class="p">)</span> <span class="p">{</span>
</span><span class='line'> <span class="c1">// inject json-proxy to the front of the default middlewares array</span>
</span><span class='line'> <span class="c1">// requires grunt-contrib-connect v0.8.0+</span>
</span><span class='line'> <span class="nx">middlewares</span><span class="p">.</span><span class="nx">unshift</span><span class="p">(</span>
</span><span class='line'> <span class="nx">require</span><span class="p">(</span><span class="s1">'json-proxy'</span><span class="p">).</span><span class="nx">initialize</span><span class="p">({</span>
</span><span class='line'> <span class="nx">proxy</span><span class="o">:</span> <span class="p">{</span>
</span><span class='line'> <span class="nx">forward</span><span class="o">:</span> <span class="p">{</span>
</span><span class='line'> <span class="s1">'/api/'</span><span class="o">:</span> <span class="s1">'http://api.example.com:8080'</span>
</span><span class='line'> <span class="p">},</span>
</span><span class='line'> <span class="nx">headers</span><span class="o">:</span> <span class="p">{</span>
</span><span class='line'> <span class="s1">'X-Forwarded-User'</span><span class="o">:</span> <span class="s1">'John Doe'</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'> <span class="p">})</span>
</span><span class='line'> <span class="p">);</span>
</span><span class='line'>
</span><span class='line'> <span class="k">return</span> <span class="nx">middlewares</span><span class="p">;</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<h2>SSL Endpoints</h2>
<p>This release adds support for proxying to HTTPS endpoints. Here’s a sample
config to forward <a href="http://localhost:9000/channel">http://localhost:9000/channel</a> to <a href="https://www.youtube.com/channel">https://www.youtube.com/channel</a> .</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
</pre></td><td class='code'><pre><code class='js'><span class='line'><span class="p">{</span>
</span><span class='line'> <span class="s2">"proxy"</span><span class="o">:</span> <span class="p">{</span>
</span><span class='line'> <span class="s2">"forward"</span><span class="o">:</span> <span class="p">{</span>
</span><span class='line'> <span class="s2">"/channel"</span><span class="o">:</span> <span class="s2">"https://www.youtube.com:443"</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<h2>HTTP Proxy Gateways and Basic Authentication</h2>
<p>You can now pass your authentication credentials to a HTTP proxy gateway on
your LAN via the <code>proxy.gateway.auth</code> config setting. The setting value
uses the <code>username:password</code> format for HTTP basic authentication
(without base64 encoding). Here’s an example config to proxying remote request
via <a href="http://proxy.example.com:8080">http://proxy.example.com:8080</a> as <code>proxyuser</code> with password <code>C0mp13x_!d0rd$$@P!</code></p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
</pre></td><td class='code'><pre><code class='js'><span class='line'><span class="kd">var</span> <span class="nx">config</span> <span class="o">=</span> <span class="p">{</span>
</span><span class='line'> <span class="s2">"proxy"</span><span class="o">:</span> <span class="p">{</span>