Last modified: 2014-03-05 12:44:34 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T64155, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 62155 - bundle install creates .bundle/install.log file in qa/browsertests
bundle install creates .bundle/install.log file in qa/browsertests
Status: RESOLVED INVALID
Product: Wikimedia
Classification: Unclassified
Quality Assurance (Other open bugs)
wmf-deployment
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-03-03 18:09 UTC by Vikas
Modified: 2014-03-05 12:44 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Vikas 2014-03-03 18:09:22 UTC 
Intention:
Was trying to make changes to qa/browsertests and commit it. But when I did git status I got a untracked folder .bundle/

Steps to Reproduce:
1. git clone https://gerrit.wikimedia.org/r/qa/browsertests
2. cd tests/browser
3. bundle install

Actual Results:  
It creates a .bundle/install.log file 

Expected Results:  
Nothing to happen or if it so happens it should have been ignored, when git status is run

Reproducible: Always

.bundle should be added in .gitignore
Comment 1 Chris McMahon 2014-03-03 18:16:01 UTC 
I am not aware that we create a .bundle directory in any other repo e.g. MobileFrontend.  There is nothing valuable in the .bundle repo, probably best not to create it at all
Comment 2 Željko Filipin 2014-03-05 12:40:32 UTC 
Vikas, I think this is caused by an old version of bundler. This should fix the problem:

gem update bundler

I am closing the bug as invalid, please reopen if updating bundler does not fix the problem.
Comment 3 Vikas 2014-03-05 12:44:34 UTC 
Thank you Zeljko, updating bundler fixed it.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links