Atlassian's developer blog on Git, Kubernetes on AWS, Node.js tooling, and building with Atlassian products such as Bitbucket and HipChat.
HN links it mainly for Git tips, including git push --force-with-lease and a bare-repo method for storing dotfiles with no extra tools or symlinks.
Perhaps an unpopular opinion around here but I see nothing but positives in this announcement.
This move towards a "good" Microsoft has been going on for a decade, ASP.NET MVC was released as Open Source in 2009. Seeing where they're going with .NET core, VSCode and TypeScript makes me pretty confident they will be good stewards of the site.
Microsoft had their own open source hosting solution Codeplex but closed it and migrated all their stuff to GitHub so they could be where the community was. That was a bold move and I think demonstrates how they see the community now. This isn't the Microsoft of the 90's.
GitHub is great but it's not profitable and I'm sure there are lots of improvements they could make with a bit of a cash injection.
On the flip side if Microsoft stuff it up or there is an exodus from Microsoft because people hate Microsoft, that's not such a bad thing either.
There are great alternatives out there, it's not the same landscape as when GitHub launched, everyone's learnt from GitHub, GitHub's biggest feature is the network effect. Everyone has an account and it's super low friction to contribute there. If we can break that a bit and everyone has an account at 2 or 3 places I think we might see some great innovation as competitors try to differentiate themselves.
Finally on that point. Bitbucket is awesome, you can build apps that are integrated directly into the UI https://developer.atlassian.com/cloud/bitbucket/
Hi scopatz, thanks for taking time to comment here. I got the feeling from the other comments here that indeed this blog post was kind of a scam.
I played with xonsh a little bit yesterday and went trough the tutorial, so far I'm pleased with it. I changed it as my default shell for the fun today, but damn, it's hard to re-educate my muscle memory. I will have to do some changes in order to make it usable:
- Customize the VI binding (I have some weird keyboard layout)
- Replace my aliases, scripts, functions, and `source` command that are [ba|z]sh specific (like ranger-cd [1]). This will be time consuming.
- Find why `ranger` takes so much time to quit.
I also have kind of a weirdo bug, but I want to be sure to understand where it's coming from before opening an Issue: It slow as hell when I try to open a terminal, and I have a warning about branch-timeout. The problem is that my home repository is not a literally a git repository. I still have some dotfiles versioned as explained in [2], but if I call `git ` commands from the home it says it's not a git repository, so I don't get why this git-related timeout.
Anyway, I will see if I try to continue right away, or if I wait a few weeks for some holidays in order to find time for the transition.
Thanks for this software!
[1] https://gist.github.com/ha7ilm/37c4272b1df6fbfdb0df30464252241e
[2] https://developer.atlassian.com/blog/2016/02/best-way-to-store-dotfiles-git-bare-repo/
So you're going to develop something for JIRA Server (internally hosted software). You'll be using Plugins2*
1. Start here https://developer.atlassian.com/jiradev/getting-started/getting-started-with-plugins2
2. Install the SDK (it has some pre-reqs) and build Hello World https://developer.atlassian.com/docs/getting-started/set-up-the-atlassian-plugin-sdk-and-build-a-project
3. Bone up on Plugins2 a bit more https://developer.atlassian.com/jiradev/jira-platform/building-jira-add-ons/jira-plugins2-overview
4. API Reference https://developer.atlassian.com/jiradev/jira-apis (I recommend the REST APIs + Webhooks wherever possible).
I'm really keen to talk with you about your experience going through that - there's a lot of history and we're aware we need to clean up the journey.
_* If you were developing for JIRA Cloud you'd be using Atlassian Connect.
> Trello users are about to get bombarded by phishing attempts and spam.
All of the emails present in this "leak" were taken from other dumps. That's how it's made, they took a list of known emails and tried to link them to a trello account.[1]
> What's the endpoint?
I think https://developer.atlassian.com/cloud/trello/rest/api-group-members/#api-members-id-field-get. The endpoint allows you to get all public info (bio and username) from a trello account by its email.[2]
> Why did it provide personal information?
So users can invite other users to their boards via their email address.
> Why wasn't it throttled?
It should've been.
[1]: https://haveibeenpwned.com/PwnedWebsites#Trello
[2]: https://www.bleepingcomputer.com/news/security/trello-api-abused-to-link-email-addresses-to-15-million-accounts/
I've been using it to build a dashboard for a web scraper with postgresql backend. Thing's it's helped with that could help you
1. Formatting tables of json from API specs
2. Keep track of growing database tables
3. Have buttons to start tasks queues
Things I've noticed are the debugging and logging experience are pretty good. You could have multiple processes dumping to different log files and grepping those.
There's a lot of formatting you can do with Python and the sister library Rich.
Have spent about 12 hours on it and it's much easier to get a UI running than say learning a flavor of the month JavaScript framework.
0: https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/#searching-for-issues-examples
Bitbucket product manager here.
Sorry to hear you've been having trouble. What you describe is most definitely unusual so I'd suggest contacting us (or having your admin contact us) at support.atlassian.com so we can look into it.
The team has spent a great deal of effort over the entire life of the product to ensure it performs at scale for broad range of load profiles. The notion that we only recently had a very large instance for test is untrue. Perhaps someone got the wrong idea from our most recent series on how we build Bitbucket Data Center to _already_ support massive scale: https://developer.atlassian.com/blog/2016/12/how-we-built-bitbucket-data-center-to-scale/