GitLab

GitLab 8.12.4 released

2016-10-05T00:00:00+00:00

Today we are releasing version 8.12.4 for GitLab Community Edition (CE) and Enterprise Edition (EE).</p>

This version contains two security fixes for GitLab, plus fixes for minor regressions and bugs in the recent 8.12 release</a>.</p>

Please read on for more details.</p>

EE:</strong> Indexer works with smaller batches of repositories to not exceed NOFILE limit. (!774</a>)</p> </li>
CE/EE:</strong> Fix tooltip text when Copy to cliboard is clicked. (!6294</a>)</li>
CE/EE:</strong> Fix build sidebar build details padding. (!6506</a>)</li>
CE/EE:</strong> Changed compare dropdowns to dropdowns with search input. (!6550</a>)</li>
CE/EE:</strong> Fix race condition on LFS Token. (!6592</a>)</li>
CE/EE:</strong> Fix bug when trying to cache closed issues from external issue trackers. (!6619</a>)</li>
CE/EE:</strong> Fix lint-doc error. (!6623</a>)</li>
CE/EE:</strong> Skip wiki creation when GitHub project has wiki enabled. (!6665</a>)</li>
CE/EE:</strong> Fix issues importing services via Import/Export. (!6667</a>)</li>
CE/EE:</strong> Restrict failed login attempts for users with 2FA. (!6668</a>)</li>
CE/EE:</strong> Fix project deletion when feature visibility is set to private. (!6688</a>)</li> </ul>
Further improvements for security of Import/Export projects.</h2>
Prevented access to foreign entities using the Import/Export functionality. This could be achieved altering the foreign key IDs in the project JSON of an exported GitLab project file. The foreign keys are now always being ignored at the time of importing a project. See #20821</a> for more information.</p>
Exported projects were world-readable in the filesystem</h2>
Exported projects are no longer world-readable in the GitLab server filesystem as permissions are set to owner access only. See #22757</a> for more information.</p>
Upgrade barometer</h2>
This version has no migrations and should not require any downtime.</p>
Please be aware that by default the Omnibus packages will stop, run migrations, and start again, no matter how “big” or “small” the upgrade is. This behavior can be changed by adding a /etc/gitlab/skip-auto-migrations</code> file</a>.</p>
Updating</h2>To update, check out our update page</a>.</p> Enterprise Edition</h2> Interested in GitLab Enterprise Edition? Check out the features exclusive to EE</a>.</p> Access to GitLab Enterprise Edition is included with a subscription</a>. No time to upgrade GitLab yourself? Subscribers receive upgrade and installation services.</p>

YC application office hours 2016-10-03T00:00:00+00:00 Following our blog last Friday about What Founders Ask Founders About Getting Into Y Combinator</a> we got a lot of responses through HackerNews</a> to have Sid, our CEO, read through people's application. Sid figured talking in person would be way easier than leaving comments and we set up some office hours during the weekend and today to help founders applying with making their application as clear as possible.</p> With the blog post trending on the HackerNews homepage</a> last Friday, a lot of applicants wanted to know if their answers were clear and concise; like Sid advised in our blog. During the office hours and a few one-on-one meetings Sid read and talked through the application form answers and asked questions and discussed what applicants could improve.</p> Below are a few examples of the calls Sid did over the weekend. We posted the recordings on our YouTube account so everyone can have a look at the advice mentioned and hopefully adjust the last few details before sending in their own application</a>.</p> Color Search</a> lets you choose a paint color online, and TrueJob</a> is a data-driven startup job search. Both company founders have graciously agreed to let us post their call with Sid to help out other founders.</p> Below is the video of Sid's call with Color Search and they also shared their application form</a>.</p> </iframe> </figure> </p> TrueJob also sent us a link for their application form</a> and their call with Sid is below.</p> </iframe> </figure> </p> Good luck to both company founders.</p> GitPitch Slideshow Presentations for Developers on GitLab 2016-10-03T00:00:00+00:00 Today I would like to introduce GitPitch</a>, a slideshow presentation service for developers on GitLab</a>. GitPitch supports building, sharing, and presenting online and offline slideshow presentations. Presentations powered entirely by Markdown and Git.</p> As developers and advocates, we often need to communicate with diverse audiences about our code. We find ourselves needing to present everything from designs and best practices, to code snippets and complete frameworks. Our audiences include colleagues, clients, customers, end-users, and sometimes meetups and conferences.</p> With GitPitch, we no longer need to turn to external toolsets like Keynote or Powerpoint to prepare for these kinds of presentations. In fact, now the only tools we need are the tools we live in, our preferred code editor and a GitLab repo. And with these tools we can quickly create compelling, responsive, online and offline slideshow presentations.</p> </p> How GitPitch Works</h2> As GitLab users, we are already familiar with the convention of adding a README.md</strong> to our projects. GitPitch introduces a new convention for GitLab users, called PITCHME.md</strong>.</p> As soon as we add a PITCHME.md</strong> markdown file to the root directory of our GitLab.com project, GitPitch instantly creates an online slideshow presentation based on the content in that file. That slideshow presentation is then automatically made available at its public URL:</p> https://gitpitch.com/user/project/branch?grs=gitlab </code></pre> Here user</code> and project</code> matches our GitLab.com user and project names respectively and branch</code> matches the repository branch where we commited our PITCHME.md</strong> file. Note, the /branch</code> can be omitted from the slideshow URL if we are referencing the master</code> branch.</p> GitPitch In 60 Seconds</h2> To experience just how simple it is to create a GitPitch slideshow presentation follow along with this short tutorial.</p> Step 1: Create PITCHME.md</strong></h3> Using the GitLab web editor</a>, or your preferred code editor, create a file called PITCHME.md</strong> in the root directory of your repo, then add and save the following Markdown content:</p> # Flux An application architecture for React #HSLIDE ### Flux Design - Dispatcher: Manages Data Flow - Stores: Handle State & Logic - Views: Render Data via React #HSLIDE ![Flux Explained](https://facebook.github.io/flux/img/flux-simple-f8-diagram-explained-1300w.png) </code></pre> Before moving on to the next step it's worthwhile to note the following:</p> The PITCHME.md</strong> file name is case sensitive.</li> The PITCHME.md</strong> file content is standard Markdown</a>.</li> The #HSLIDE</code> markdown fragment acts as a delimiter between slides.</li> </ol> Using #HSLIDE</code> is another GitPitch convention, acting as a delimiter to denote the separation between content on different slides in your presentation. You can use custom delimiters</a> if you prefer. For this example, when GitPitch processes the Markdown content it will result in a simple presentation with just three slides.</p> Step 2: Commit PITCHME.md</strong></h3> If you used the GitLab web editor in step 1 then go directly to step 3. Otherwise, manually add this file to the root directory of your Git repo and push to GitLab:</p> git add PITCHME.md git commit -m "Added my first GitPitch slideshow content." git push </code></pre> Step 3: Done!</h3> Your GitPitch slideshow presentation is now waiting for you to share or present at its public URL. To see a live demonstration of this slideshow presentation click here</a>. Your own presentation should look a lot like this:</p> </p> Immediately you can download</a> your slideshow for offline presentation, print</a> it as a PDF document, or share</a> it on social media. But first, you might want to apply some personal touches using GitPitch customization, the topic we'll look at next.</p> Note that beyond support for standard Markdown on presentation slides, GitPitch delivers a number of features tailored for developers, including support for code blocks</a>, GitHub GIST</a>, math formulas</a> along with image</a>, and video</a> support. The full set of GitPitch features are documented on the GitPitch Wiki</a>. To see a live slideshow demonstration of these features try out the GitPitch Kitchen Sink</a>.</p> GitPitch Customization</h2> As with any presentation, a GitPitch presentation not only needs to capture and render compelling content, it also needs to be able to reflect the style, image or brand of the associated project, product or organization. To help us develop a strong visual identity for our slideshow presentations, GitPitch offers six distinct visual themes out-of-the-box. See the GitPitch Themes</a> Wiki page to learn more.</p> </p> Building on these base themes we can further customize the look and feel</a> of our slideshow presentations using background images, our own logo, and even custom CSS to bend the pixels to our needs.</p> </p> GitPitch and GitLab Workflow</h2> The PITCHME.md</strong> markdown for our slideshow presentation becomes just another file in our GitLab project repo. Therefore all of the benefits we currently enjoy when working with GitLab Workflow apply equally when developing our slideshow presentations.</p> Given GitPitch can render a slideshow presentation for any branch within a public GitLab repo, using feature branches also offers an excellent way to customize a presentation's content for different target audiences. For example:</p> Branch to tailor code snippets for a Scala rather than Java audience.</li> Branch to adjust the presentation focus for a dev-ops audience.</li> Branch to emphasize participation of a partner or customer for a specific conference.</li> </ol> Some common, in-person workflows are also greatly improved when working with GitPitch presentations. For example, how often have you heard this simple request following a successful presentation:</p> Can you please send me your slides?</p> </blockquote> If our presentation lives outside of our GitLab project it is very easy to misplace or forget to follow up. With GitPitch, a simple answer is always at hand:</p> The slideshow presentation is part of the project on GitLab, just click on the GitPitch Badge</a> found in the project README.md</strong>.</p> </blockquote> Going Faster from Idea to Presentation</h2> GitLab champions new, modern development tools and practices that foster collaboration and information sharing to help developers go faster from idea to production</a>. GitPitch embraces and extends this approach by helping individuals, teams and organizations to promote, pitch and present their ideas and code to ever wider audiences.</p> Note, by default the GitPitch service on GitPitch.com</a> integrates with GitLab.com</a>. If you are interested in using GitPitch with your own GitLab server see this note</a> on the GitPitch Wiki.</p> Like GitLab, GitPitch itself is an open source project</a>, built on some wonderful open source software. See the GitPitch website</a> for details. And remember, getting started couldn't be easier. GitPitch requires no sign-up. And no configuration. Just add PITCHME.md</strong> ;)</p> About Guest Author</h2> David Russell is a freelance developer, consultant for-hire, open source contributor</a> and the creator of GitPitch</a>. You can reach David on Twitter @gitpitch</a>.</p> What Founders Ask Founders About Getting Into Y Combinator 2016-09-30T10:31:00+00:00 Update: There is a followup post about the YC application office hours</a> as a response to this post.</p> You’ve got a great idea and feel you can make a great company and product out of it. You’ve worked on a basic version and feel like you’re ready to enter the big leagues.</p> Maybe the accelerator program of Y Combinator is a good idea? But you’ve got so many questions. When are you ready for the next step? How can Y Combinator help you? What are some tips or tricks to get in and what should you highlight in the application process?</p> The deadline to apply</strong></a> for the Y Combinator program is Tuesday October 4th 2016 by 8pm PT</strong>.</p> In combination with the blog post we released the application of GitLab to YC</a> as an example. Below some questions that Reinder Visser from Placker</a> asked Sid about applying at Y Combinator a few days ago.</p> Reinder: Why should I apply?</h4> Sid:</strong> The reason we applied for Y Combinator with GitLab was that we had lost our first customer mid 2014. The customer explained that while they liked GitLab they were standardizing on an alternative solution. Dmitriy and I figured every company would standardize on one solution to do innersourcing</a> and we wanted that solution to be GitLab. The need to grow faster became the main reason to apply since there was a window of opportunity of a couple of years before people would standardize on one tool and be decided.</p> We feel that the time to apply for Y Combinator is when you have mainly outlined your product vision, you’re still working somewhat on the market, and are still trying to figure out how to sell it, and how to scale to accommodate your customers. The Y Combinator program is ideal when you have a solid team of founders that have been working together for a while but you are ready to hire the rest of the team after you complete the Y Combinator program.</p> Reinder: So why choose Y Combinator if there are more than 2000 accelerator programs in the world?</h4> Sid:</strong> We feel that Y Combinator has the best network, the best partners, the best advice to give you because they see the most companies, and they are very strong at selecting them. Going where the other strong applicants are, you will have a program where they have the largest set of data to offer you advice. Investors have noticed the Y Combinator pattern which helps you raise funding under better terms with better investors. Our Y Combinator experience exceeded our high expectations.</p> Reinder: Is it a problem that I'm a single founder?</h4> Just last week Craig Cannon posted an article on the most common misconceptions about applying for Y Combinator</a>. A concern people have sometimes is being a single founder, which is addressed in this article. While Y Combinator does suggest having a cofounder</a> because startups are hard and cofounders definitely help, of the Summer 2016 batch, 8.5% had a solo founder. Here’s how the rest breaks down: 2 Founders (61.3%), 3 Founders (20.8%), 4 Founders (7.5%), 5+ Founders (1.9%). It may feel like being a single founder would make it harder to get the same load of work done, where it’s not so much that Y Combinator will be hard on your own, running a company on your own will be too.</p> Reinder: If you decide to apply, how do you get in?</h4> Sid:</strong> Take your time working on your answers for the application. Apply ahead of the deadline and don’t wait until the last minute if you can. But even last minute and late applications get a fair review so feel free to sleep on it. Describe what your company does and why it’s unique. Be concise and opt for simple descriptions with the use mundane language, because a main reason why you get declined is that a reviewer doesn’t understand you business. Have other people review your application. Then ask them “what does my company do”? and write down their answer. Take that answer they have given you and use it to improve your description. Writing down what your company does is one of the hardest things, and if you don’t agree with their answer than your first answer wasn’t clear enough.</p> Everyone feels their product is is better, faster, easier, so get down to specifics why you feel that way but keep it simple. If people can’t recite back to you what it is you do and why you’re different, you have to change your answers. There are a few question in the application that are of high importance to highlight you as a founder, one of them being: “Please tell us about the time you most successfully hacked some (non-computer) system to your advantage.” Don’t gloss over any questions but this one in particular is important. Choose answers or situations that show you’re an independent thinker and are creative. When you get invited to do a 10 minute interview after you’ve sent in your application make sure to prepare for the interview in detail. They will ask you questions which are to be found on the internet so make sure to write down your answers and practice those. Your answers need to be concise and clear, when they are too long you will get cut off. I had someone ask me the questions over and over and interrupt me if my answer was longer than one breath.</p> Reinder: So spill the beans; what’s it like?</h4> Sid:</strong> Y Combinator raises your ambition level; everyone is motivated by the feeling of progress, and that’s what fast growth gives you. You’re in a batch with the best people in the world, it’s a form of healthy peer pressure that motivates you to work harder and set that high pace to keep developing your product. The first thing they ask you to do is launch, in case you haven’t done that yet. Y Combinator teaches you not to want your feature or product to be a certain way before shipping. Ship today, and make it better or nicer over time. As soon as it’s live you’ll have more information and data on what the real problems are. Figuring out who your ideal customers are, how to reach them, how to raise your financing, how to hire people, these are questions that everyone in the program has. The team of Y Combinator is really good at helping you to answer these questions, both during and after the 3 month prgram. But the best part are the other founders, they are all interesting people and I'm very glad to call some of them my friends.</p> GitLab's Application for Y Combinator Winter 2015 2016-09-30T10:30:00+00:00 This application was created in October 2014. We released it together with out blog post What founders ask founders about getting into Y Combinator</a></p> Company</h2> Company name:</strong></p> GitLab</p> </div> </div> Company url, if any:</strong></p> https://about.gitlab.com/</a></p> </div> </div> If you have an online demo, what's the url?</strong></p> http://demo.gitlab.com/users/sign_in</p> Note:</strong> this URL no longer works, in 2016 our sign up url is https://gitlab.com/users/sign_in</a></p> </div> </div> What is your company going to make?</strong></p> We’re making open source software to collaborate on code. It started as ‘run your own GitHub’ that most users deploy on their own server(s). GitLab allows you to version control code including pull/merge requests, forking and public projects. It also includes project wiki’s and an issue tracker. Over 100k organizations use it including thousands of programmers at <Redacted>. We also offer GitLab CI that allows you to test your code with a distributed set of workers.</p> </div> </div> Where do you live now, and where would the company be based after YC?</strong></p> The Netherlands, Ukraine (with employees in San Francisco), we don't know yet where will be based after YC</p> </div> </div> Founders</h2> Please enter the url of a 1 minute unlisted (not private) YouTube video introducing the founders.</strong></p> https://www.youtube.com/watch?v=KzvDHA5323o</a></p> </div> </div> Please tell us about an interesting project, preferably outside of class or work, that two or more of you created together. Include urls if possible.</strong></p> We created GitLab together (https://about.gitlab.com/gitlab-ce/</a>) and now over 100.000 organizations are using it. We also created GitLab CI and GitLab CI Runner together https://about.gitlab.com/gitlab-ci/</a>. This pair of programs allow organizations to distribute their code testing over a number of workers.</p> </div> </div> How long have the founders known one another and how did you meet? Have any of the founders not met in person?</strong></p> In 2011 Dmitriy started GitLab. We met in 2012 via email when Sytse started building GitLab.com. In 2013 we formally started a company together and went on team trips a few times since than.</p> </div> </div> Progress</h2> How far along are you?</strong></p> Over 100.000 organizations are using GitLab. <Redacted>, Boeing, Disney, Qualcomm, NASA, Nasdaq OMX and Interpol are paying customers. Over 600 people have contributed to it. It is the most popular open source version control software. It has more installations than anything else (including GitHub Enterprise and Atlassian Stash).</p> </div> </div> If you've already started working on it, how long have you been working and how many lines of code (if applicable) have you written?</strong></p> Since 2011, over 10,000 commits, see http://contributors.gitlab.com/</a></p> </div> </div> Which of the following best describes your progress?</strong></p> Launched</p> </div> </div> When will you have a prototype or beta? How many users do you have?</strong></p> We estimate more than 1M</p> </div> </div> Do you have revenue?</strong></p> Yes</p> </div> </div> How much revenue?</strong></p> $1m annual Revenue Run Rate</p> </div> </div> What is your monthly growth rate?</strong></p> About 60% in revenue each month.</p> </div> </div> If you've applied previously with the same idea, how much progress have you made since the last time you applied? Anything change?</strong></p> No</p> </div> </div> If you have already participated or committed to participate in an incubator, "accelerator" or "pre- accelerator" program, please tell us about it.</strong></p> We have not applied to or participated any others.</p> </div> </div> Idea</h2> Why did you pick this idea to work on? Do you have domain expertise in this area? How do you know people need what you're making?</strong></p> Dmitriy wanted a solution he could use at his previous job. All employees except our account managers (8-2=6) are software developers. We listen closely to the community via direct customer feedback, pull/merge requests, issues, twitter, mailinglists, chatrooms and the non GitLab B.V. employees on the GitLab core team.</p> </div> </div> What's new about what you're making? What substitutes do people resort to because it doesn't exist yet (or they don't know about it)?</strong></p> We offer the a better way of collaborating on digital products ( the feature branch workflow) to organizations that prefer to work on open source tools. Open source is interesting for large companies because they can inspect and modify the code. They also can and do contribute back changes that are important to them. Substitutes are closed source alternatives (GitHub Enterprise, Atlassian Stash) or less functional open source alternatives (Gitorious, Gogs). GitHub currently has a lot of mind-share but they are under- serving the on-premises (behind the firewall) market. We can see us grow into the leading solution for those installations (which is currently the majority of the market). In the long run most software will live on some (hybrid-)cloud and we think there are many ways to differentiate our offering (open source/distributed/integrated). In the short term we are emulating the Netflix strategy, shipping DVD’s (focus on the on-premise installations) when the competitors focus on the video-on-demand (SaaS) offering.</p> </div> </div> Who are your competitors, and who might become competitors? Who do you fear most?</strong></p> GitHub Enterprise and Atlassian Stash are our primary competitors. We fear Atlassian Stash most since the GitHub Enterprise offering is weak (black box VM that doesn’t scale or cluster) and overpriced (4x more expensive than Stash or our standard subscription). We compete with Stash on usability, integration (no need to install Jira and Confluence separately), flexibility (you can inspect and adapt the source) and price.</p> </div> </div> What do you understand about your business that other companies in it just don't get?</strong></p> An open source development process allows you to market your product for free. It also allows a good product market fit at a low cost. We believe that version control is infrastructure software and that open source is the natural model for this kind of software . But to create and grow a competitive open source offering you need to have a proprietary commercial version to generate scalable revenue, support income alone is not enough.</p> </div> </div> How do or will you make money? How much could you make?</strong></p> Mostly by selling subscriptions that entitle our customers to support and our proprietary GitLab Enterprise Edition. Our most sold subscription by revenue costs $49 per user per year. Most or our revenue comes from organizations with more than 100 paying users. Every company with a substantial number of developers needs software like ours. We already declined an acquisition offer from a competitor for $10M because we want to grow this into a large company.</p> </div> </div> How will you get users? If your idea is the type that faces a chicken-and-egg problem in the sense that it won't be attractive to users till it has a lot of users (e.g. a marketplace, a dating site, an ad network), how will you overcome that?</strong></p> Currently we get users through word of mouth (amplified by twitter). During our time at YC we would like to grow our marketing, our continuous integration product GitLab CI and our SaaS (GitLab.com). GitLab.com currently has only 15k monthly active users but we see a lot of possibilities to grow and differentiate it.</p> </div> </div> Others</h2> If you had any other ideas you considered applying with, please list them. One may be something we've been waiting for. Often when we fund people it's to do something they list here and not in the main application.</strong></p> N/A</p> </div> </div> Please tell us something surprising or amusing that one of you has discovered.</strong></p> Before GitLab Sytse has build recreational manned submarines from scratch, the company he started is currently the largest producer of them in the world and is called U-Boat Worx http://www.uboatworx.com/</a></p> </div> </div>