Tracker will be moving to a new hosting environment this weekend. This post contains updated information about this move, and how it will affect you.
The move will occur this Saturday, November 6th, starting at 8:00am PDT. We expect the move to take approximately 6 hours, including testing and site verification. Tracker will be unavailable during this time.
We will be posting updates throughout the move to this blog, as well as to the @pivotaltracker Twitter account.
Pivotal Tracker will be moving to new IP addresses, so if you have any firewall rules related to integrations that access internal resources (for your example your JIRA instance), you will need to update them. Tracker requests will now originate from one of two possible IP addresses: 188.8.131.52 and 184.108.40.206, on ports 80 and 443. Please add rules to allow requests from these IP addresses in advance of the move this Satuday, in order for your integrations to continue working without interruption.
We’ve set the DNS TTL low leading up to the migration, so we don’t anticipate significant DNS propagation delays. If you are in a place where DNS changes take longer to propagate, however, please keep an eye out for this. We’ll help you with workarounds if the issue persists.
Our apologies for any inconvenience caused by this hosting move. Please do not hesitate to contact us by emailing email@example.com if you have any questions.
Is it possible in Jasmine to spy on a getter such as
myObject[key]? We want to know when local storage is accessed.
Local storage has a functionally equivalent
getValue function, which you can spy on, but the spy is not triggered when you access the value via
On unicorn, the random number generator is seeded before the fork. So if you are depending on a set of unicorns to generate different random numbers, you need to reseed the random number generator manually after the fork.
If you want to make absolutely sure you aren’t generating any queries in your Rails views, try no_querying_views – which explodes if your query comes from view code.
Other ways to track down inefficient queries that folks have successfully used: bullet and query_reviewer
Skype 5 beta is out for Mac, which allows group video chat. Everyone must be on the beta for it to work.
Our NYC office is growing and we need someone to help our systems keep up with demand. We’re agile, fun, and believe in sustainable pace (no death marches), and lots of testing. We have daily catered breakfast and keep our fridges well stocked. We like to work in an open environment – no cubicles here.
You’ll be supporting our tenants’ needs first (around 40 people – assist with printers, networking, etc).
You’ll also support about 20 of our developers onsite as well as additional developers in client offices around the city.
We use Macs exclusively but our tenants will have a mixture of systems.
We’re looking for someone to take initiative and help plan and transition IT-related needs from our current office to our new office as well as provide on-going support.
Install, configure, and support:
- Workstations and laptops (Macintosh, Windows and Linux)
- Local area network (LAN), WiFi and Internet connectivity to our office
- VoIP phones
- Manage backups, onsite and offsite
Additional Skills desired:
- Experience with managed switches and VLANs
- OS X Server administration
- Linux administration
- VPN experience (IPSEC)
- Scripting languages (Shell, Ruby, Perl, Python, etc.)
- Ability to communicate with both technical and non-technical clients
If you or someone you know is interested please reach out to firstname.lastname@example.org
This is a contract-to-hire position.
Do people put bundler in the Gemfile?
Yes. Bundler is smart enough to omit it from the cache. It does, however, still follow the rules for version. We recommend using
~> 1.0.0 as the version string, because 1.x is supposed to be backwards-compatible with the current Gemfile format.
If you instead use
= 1.0.0 and your managed hosting environment updates bundler to something more recent, things will ASPLODE.
- Tech talk that was going to be today has moved to Thursday, due mostly to noise concerns. See you tomorrow.
We made a branch in git called “–track” by accident, and now we can’t get rid of it. git thinks it’s a command-line argument, even when it’s in quotes.
Here’s the command what did it:
$ git checkout -b --track origin/actual_branch_name
Branch --track set up to track remote branch refs/remotes/origin/actual_branch_name.
Switched to a new branch "--track"
Consensus: kill it through RubyMine or gitX. There is also a way through the command line:
$ git branch -d -- --track
…but make sure you get the dashes in all the right places.
reset after tail – sometimes, if your PS1 has colors (or square brackets, or … ?) you can lose your Terminal after tailing a file. To get it back, type
reset, which should work even if you can’t see it echoing. You may need an extra return before it.
The Giants seem to have won! There’s a parade tomorrow, right in front of the office. If you’re coming for the tech talk, leave extra time as streets will be closed and they’re expecting a crowd.