Atlassian Blog

Atlassian had a great blog post about tig that convinced me to start using it: - https://blogs.atlassian.com/2013/05/git-tig/

The model sounds like it might be inspired by git. If it truly is, that would be wonderful. (Example git extension: http://blogs.atlassian.com/2013/04/extending-git/ ) The idea of supplying a convenient set of low-level primitives and then letting you compose them, in any language, and become a first-class citizen (at least in cli exposure) is wonderful. I could see a world where docker plugins simply work by "docker XYZ" doing a "docker run XYZ" and bind-mounting the docker.sock in as well as providing a few additional convenience sockets / functions / potentially container links. Making docker plugins also docker containers sounds really appealing to me and if anyone has more information on the actual details being considered I'd love to hear.

Didn't Linus mention this in his talk at Google, Mercurial offers similar speeds, but Perforce would be the option for large binary files. I personally haven't come across any need to use anything except shallow clones in large repos. Most of the time, you want to keep those other topic branches regardless. They've linked to their previous most regarding submodule in the post[1], but it's worth re-mentioning that if you need to use submodule, you should almost always use subtree. [1]: http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-s…

> Also, instead of passing any arguments to "git-log", I usually just use "tig", an ncurses display of the commits: https://blogs.atlassian.com/2013/05/git-tig/ +1 for tig. Definitely my favourite git interface. Its status view is also very handy for viewing diffs, and adding/removing files to the index, as well as reverting changes. Also, it now has mouse support. I know this, cos I added it :)

My personal favorites: > git-rerere will prevent you from getting stuck resolving the same merge conflicts repeatedly, by remembering how you resolved them the last time. Also, instead of passing any arguments to "git-log", I usually just use "tig", an ncurses display of the commits: https://blogs.atlassian.com/2013/05/git-tig/ Finally, when I was first taught Git, I was told that I should never need to comment out code again. I never understood how this was possible until I learned how to use 'git add -p' and 'git rebase -i' in tandem.

> Also, instead of passing any arguments to "git-log", I usually just use "tig", an ncurses display of the commits: https://blogs.atlassian.com/2013/05/git-tig/ Agree, tig is awesome and in my opinion the best git GUI (or at least representation). Use the normal commandline tools for commiting/cutting/rebasing/... and tig to see where everything is at!

I think Scala is great as long as you stay on the road and not end up in the deep depths of academic hell (i.e. http://blogs.atlassian.com/2013/01/covariance-and-contravariance-in-sc… I should say one thing however: I'm using Scala because of Akka. An extremely powerful library that does a good job of hiding the complexities while still allowing you to be flexible.

I can't recommend any Atlassian products. They removed the markup editor from their wiki product; their sole remaining choice -- the rich text editor -- its a piece of shit that is actively hostile to any dev stuck using it. They're doing it to, in effect, crap on developers in order to prefer people who won't use a markup language [1]. It sucks beyond belief for entering code or tables, and is the usual very annoyingly broken rich text experience: tab and enter don't do what you think they will and aren't consistent; they make chrome freeze regularly; and you can't really use it without repeatedly taking your hands of the keyboard to touch a mouse. Just awful. [1] http://blogs.atlassian.com/2011/11/why-we-removed-wiki-markup-editor-i…

> By far, my biggest complaint to Atlassian is upgrades, which are a huge PITA. There has to be an amazing new feature for me to go through that. Just as a FYI - the latest version of JIRA (4.4) and the soon to be released (next week) version of Confluence (4.0) have had the install and upgrade process rewritten from the ground up. If you've been bitten in the past, I'd strongly recommend taking another look. A summary of the features here: http://blogs.atlassian.com/jira/2011/06/jira-44-sneak-peek--the-new-up…

Ranking these companies based on their website traffic is misleading at best. For example, #12 is a software vendor that just hit $100M in sales. It's clearly doing much better than similarly ranked companies. http://blogs.atlassian.com/news/2009/02/from_startup_to.html Also, calling this site a startup (#42) seems like a stretch: http://www.deadharddrive.com/ There seem to be several random websites with little traffic on the list, I just clicked on this one at random.

This is interesting. I never thought of using vim commands to power the browser, but I do love text interfaces. (I type 150 wpm's and find keyboard navigation markedly faster than the point-and-click interface -- especially since keyboards are so much more precise.) In 2008, back when I used Firefox, Mozilla tried an experimental interface called Ubiquity[0]. It was awesome! I don't know if the plugin still works, but I think text interfaces are really the way of the future for power users (everything old is new again)? Has anyone found anything quite like Ubiquity for Chrome or something like Vivaldi? Other examples that come to mind: ChatOps[1] (seemingly popularized lately by Slack), Alfred[2], and even OS X's own Spotlight[3]. Nowadays, though, I just rely on the default keybindings of Chrome for most things. One of my favorites is Cmd+L, which highlights the contents of the address bar. [0]: https://wiki.mozilla.org/Labs/Ubiquity [1]: http://blogs.atlassian.com/2016/01/what-is-chatops-adoption-guide/ [2]: https://www.alfredapp.com/ [3]: https://support.apple.com/en-us/HT204014

Great to hear you're already using JIRA and Confluence. Adding Bitbucket to the mix will give you access to a bunch of great integration features. We've been working on making it easier for the entire development team to collaborate and give them the right information at the right time. Here is a selection of features that I think you will find useful: JIRA's Release Hub, to let you know if you're ready to release or not: http://blogs.atlassian.com/2015/04/jira-6-4-release-confidence-sanity The development panel, to turn every issue into a dashboard for it's development work: http://blogs.atlassian.com/2014/03/visualize-development-jira-6-2/ Automated issue transitioning, because it's easy to forget to move that issue to "In Review": http://blogs.atlassian.com/2014/08/jira-6-3-untangle-development/ Hope this helps. For a good overview, you can also take a look at the documentation that outlines the above integrations: https://confluence.atlassian.com/display/BitbucketServer/JIRA+integrat…

Thanks for the reply mentioning us! There’s quite a few independent developers selling their add-ons in our Atlassian Marketplace with yearly bookings of anywhere from a few thousand $$ to over $1,000,000 in some cases. Some have even been acquired by larger partners who double down on investment and now what started as a solo thing is effectively a big startup. We think it really makes sense and is a great option for developers to consider. Here’s a couple of examples we wrote up: Atlassian Marketplace developer Wittified, a successful solo dev business, acquired recently by AppFire https://www.atlassian.com/customers/wittified. Atlassian customer Twilio, who use several add-ons from such developers and they talk about how it really makes their Atlassian products more valuable https://www.atlassian.com/customers/twilio-case-study. There’s Bob Swift Software, a long-standing solo independent developer who started with us years ago and who has tens of thousands of customers, also acquired by AppFire. Theres’s our Marketplace developer eazyBI, a reporting tool started as a side-project by one person and now a profitable company with 7 employees. There’s even agile planning features now part of JIRA Software itself, which started as an add-on known as Greenhopper from an independent developer that we ourselves acquired some years ago. And these are just some of the smaller, solo and indie devs. The larger business that emerged on our platform are something to behold (one…

> For anything common, a CLI is almost always quicker and more consistent. I'm also a command line fan, but when it comes to git there are 2 areas where a GUI is nice: - After slashing through dozens of files, it's nice to have a nice GUI that gives you a list of all changed files, and manually select the lines you want to stage. I use git-cola (https://git-cola.github.io/) or git extensions (https://gitextensions.github.io/, although there's no screenshot of this exact functionality) depending on the platform I'm on - When I need to explore a repo's history, I like having some interactivity: filtering branches/tags, quickly searching for a commit or its ancestor, search where a commit is included... the git cli is absolutely not the right tool for that. I could get used to tig (https://blogs.atlassian.com/2013/05/git-tig/) because it fits the bill for both cases, I just haven taken the time. Sometimes a mouse may be the best tool.

I think the question betrays the authors bias and assumes too much; by claiming that "almost every article comparing mercurial and git" and saying "it seems like Mercurial has a better command line UX", the author is obviously a fan of Mercurial; neither of those points seem to be true. While I can understand the sour grapes at seeing an "inferior" technology win, it's not that clear cut. I haven't used Mercurial enough to really compare, but I can say that most of the supposed "advantages" of Mercurial versus Git seem moot to me. The CLI "UX" differences are negligible, it doesn't matter what languages they are written in, and git is ultimately more flexible due to less dogmatism. Perhaps the question should be closed with an "already answered" link to this: http://stackoverflow.com/questions/1598759/git-and-mercurial-compare-a… Edit: Followup with some more links: http://schacon.github.com/2008/11/24/on-mercurial.html http://tomayko.com/writings/the-thing-about-git http://blogs.atlassian.com/2012/03/git-vs-mercurial-why-git/

DVCS does not discourage Continuous Integration as long as the developer pushes remotely on a regular basis to their own branch and the CI server is setup so that it builds the known active branches. I've been working on solving this problem over the last year. We added the ability to Bamboo (CI server by Atlassian) to detect new branches as they are created in the remote repository and automatically test the merge with master and optionally push the branch to master if everything is OK. If the merge or the tests fail, Bamboo lets you know immediately via email/XMPP/HipChat/etc. Yes, it relies on developers being disciplined (read: responsible and professional) enough to push back to master in order to have the merge tested and the tests run. Developers actually do it though because the benefits to having their feature branch tested regularly against master are huge: code is regularly merged and tested with master to ensure integration state and other team members are isolated from changes that can potentially damage development velocity. Anyhow, if your interested in learning more, see my blog post called "Making Feature Branches effective with CI". I'd love more comments and thoughts if you have them. http://blogs.atlassian.com/2012/04/bamboofeature-branch-continuous-int… Disclaimer: I am product manager for Bamboo @ Atlassian

I think they just like making puns. A founder had a blog called "rebelutionary". slide 4 here: https://slideplayer.com/slide/5874486/ http://blogs.atlassian.com/rebelutionary/archives/000834.html (dead link)

Little bits in CLI interface https://blogs.atlassian.com/2014/06/happened-git-2-0-full-goodies/

I believe tig [1] and gitk [2] are the standard tools for doing this. Either the author did not know about them or he did wrote anyway as a fun project. --- [1] https://blogs.atlassian.com/2013/05/git-tig/ [2] https://www.kernel.org/pub/software/scm/git/docs/gitk.html

Trello is a JIRA competitor based on providing simplicity to task boards. Why would they JIRA-ify it? They would lose their audience who sought a JIRA alternative in the first place. From their blog post on the subject https://blogs.atlassian.com/2017/01/atlassian-plus-trello/ they seem to acknowledge this I happen to use, and like, both products. JIRA at work (where I want a lot of the features) and Trello for personal/small group projects and even family/household stuff where I just need _simple_

Atlassian's blog post on it: https://blogs.atlassian.com/2017/01/atlassian-plus-trello/

"If you currently use Trello as either a free or paid user, you can rest assured that we will continue to offer Trello as a standalone service." https://blogs.atlassian.com/2017/01/atlassian-plus-trello/

I like how Atlassian handled an incident that was different, but also included calls to fire the engineer: http://blogs.atlassian.com/2014/06/failing-values-team-industry/ > I know the engineer responsible well. I hired him. I know the slide does not reflect his values any more than it reflects Atlassian’s, and he is as deeply sorry as we are. It was an error in judgment, but one the company shares responsibility for making. > As Atlassian, we don’t stand behind the slide – but we stand as a team. When we do good, and when we do bad. Today, we failed as a team. We will help him learn from this, as we all must. Our engineer, our event, our issue, our learning, our growing – as a team.

The awesome `tig` gives you a lot of that in a standalone tool. I'm not sure how much overlap there is in functionality, I have not even used all the features. Here's a good blog article on it: http://blogs.atlassian.com/2013/05/git-tig/

Wouldn't git subtrees be a better option than git submodules? (see: http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-s… and https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-s… )

Nice overview! Don't forget Bitbucket Pipelines (in-house), which is intended to replace Bamboo Cloud: http://blogs.atlassian.com/2016/05/introducing-bitbucket-pipelines-bet… (Atlassian employee here)

Here's some good posts about submodules and alternatives, so you can make up your own mind: http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-s… https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-s…

Interesting, i've put together exactly this at a startup I just joined. Based it off Atlassian's own article (which also goes into hardware): https://blogs.atlassian.com/2014/03/jira-asset-management-overview/

You may know about this already but Jira has Github integration as well [1]... [1] http://blogs.atlassian.com/2014/04/connecting-jira-6-2-github/

Yes. http://blogs.atlassian.com/2012/02/mercurial-vs-git-why-mercurial/ (For fairness, if you want the arguments in favor of git, try this: http://blogs.atlassian.com/2012/03/git-vs-mercurial-why-git/ . But honestly, I prefer Mercurial. It doesn't matter, because the vast majority of the people I collaborate with are using Git, but if I could make the choice, I would use Mercurial.)