Linette Atlassian Team

I'd echo @Tobias D , to watch this issue as that's where updates will be shared. We want to make sure if it's done it's done right, which means no unusuable sections because someone forgot to update the text color for that deeply nested error message, or 'checkerboard' experiences which are even worse on the eye. Turns out…

I do not have a green thumb. I’ve killed a variety of different plants (even ones ‘impossible to kill’). I started to get more into succulents, and I brought a ‘desk plant’ from the store. It’s a dwarf fig on a rock sitting in a little tray. You just have to make sure the tray always has water in it. This is much more my…

Hi Radu, Hmm... seems like something odd is going on for you! I did a little test here: https://bitbucket.org/lvoller/testing-things/addon/pipelines/home#!/results/53/steps/%7B613c22a2-ea37-4cd0-bce2-db8460eda54c%7D and when I committed to feature/newproject/issue1, the pipeline for feature/*/* ran. Hopefully having a peek…

She likes to think she's doomy, but she can't compete with the bottom one, who is the major peril maker in the household!

My three

There are a few ways it can be done, but the easiest is probably to do it in settings > pipelines > ssh keys. Here you can either generate a key that you then need to add to your linux machine, or if you've generated a key on your linux machine already (using the guide I linked to), you can add them into pipelines by…

Each step runs in a separate docker container. How the container behaves, and which shell it uses depends on the docker image used. Each line of script inside a step executes in the same shell session. I hope that helps!

An SSH public and private key pair must be added to the Bitbucket Cloud repository and the public key must be added to the remote service or machine (in this case your linux machine). in answer to your questions: What exactly does "~/.ssh/config" mean? This is a file called 'config' located in a directory called .ssh which…

It might be worth you using the firebase deploy pipe to simplify things: https://bitbucket.org/atlassian/firebase-deploy/src/master/README.md that way you could have: - step: name: Deploy to production deployment: production script: - pipe: atlassian/firebase-deploy:0.2.1 variables: FIREBASE_TOKEN: $FIREBASE_TOKEN…

Sorry for the long time in responding to you. Are you still experiencing this? There was a brief issue a while back, but should not be an issue now. If it is then I'd really like to help you out.

@ryanbannonGenerally community is a great place to see how other people are using Bitbucket. You could even start a thread asking people about them? I'm also planning on putting something in the docs to gather together examples of how people might use pipelines in different ways. I think it's much easier when you can see…

Great question, and sorry for the confusion! That is a example generic name for a python script you might have in your repo to test and deploy your work. Replace that with the name of your script, or add in commands there to run the tests and deploys that you want to do with your code. Working out what to put in examples…

Hi @hwozniak! Yes, you'll find it here: https://community.atlassian.com/t5/Bitbucket-questions/How-to-deploy-to-remote-server-after-building-assets-in-pipeline/qaq-p/937061? Hope that helps!

Probably good to create your own question as it's a bit buried at the bottom here, and as it's marked as solved, people won't be necessarily looking at this one... (and it will be super useful for others in a similar situation when yours is solved ;) )

@Matthew Hailwoodthere's a few moving pieces to get in place, but one of the pieces, 'tasks' is now available in alpha (you can peek here: https://confluence.atlassian.com/bitbucket/tasks-958765631.html). The idea behind them is to make configuration of your yaml much easier. We're still increasing the number of tasks…

oh, and in answer to your questions 1) and 2) the difference is how far through the directory structure you'll go. the first example (dist/*/folder) could find dist<span>/test/</span>folder but not dist<span>/test/reports/</span>folder<br> Where as dist/**/folder would find dist<span>/test/reports/</span>folder as it keeps…

Hi Victor, I have a basic little example pipeline that might help make things clearer here: https://bitbucket.org/lvoller/testing-things/src/fc5f1e247f835fc81dd73a8151c36207c74d8d4d/bitbucket-pipelines.yml Essentially though: * a single asterisk will pick up any files in the folder (including hidden) * a double asterisk…

You know, if you have a little bit of time up your sleeve, I'd recommend maybe holding off for a little bit, as we have something new coming up soon that should make deployments in general much easier... keep your eye out! If you are keen to get going now though, I'm sure we'll do all we can to get it working for you!

Great call, @Doohickey Wiggins! I've added a note in the docs that if you are not using the default Docker image, to make sure it's installed or install it. Hopefully that will make people's life much easier!

Great news! We made it happen: https://community.atlassian.com/t5/Bitbucket-discussions/Reduce-effort-with-Branching-Model-now-in-BitBucket-Cloud/m-p/919133#M1322 Thanks for asking, and I hope it makes things much easier for you!

You could add your SSH key to pipelines specifically following this guide: https://confluence.atlassian.com/bitbucket/use-ssh-keys-in-bitbucket-pipelines-847452940.html?_ga=2.131578383.1856844316.1538948135-298513200.1517436601 The section at the bottom about multiple keys looks quite like what you are already doing, and…

If you just wanted to validate your yml file you could use: https://bitbucket-pipelines.prod.public.atl-paas.net/validator But from the look of what you linked to, you are wanting to run your pipeline end to end locally, which does not currently exist from the Atlassian side. Currently the closest you can really get is to…

Wahoooooo!!! So glad you got it working!

Hi there, You are really close, but unlike a branch there can't be a HEAD of a tag, so the first example can only work for branches. In order to trigger on a tag, you'll also have to specify the commit and hash, so it knows what to work from. If you format it in the style of the second example on the API page, it should…

Hi Rasmus, You are SO CLOSE!! In your example, if you escape the asterisks with slashes it will work for you so the command should be: - zip -r $BITBUCKET_REPO_SLUG.zip . -x *.git* *.yml *.js *.wbl *.json \*src* \*node_modules* you could also try using quotes, but this seemed the most direct method to me.

What great news @[deleted]!!! Feel free to link and I'll also update our documentation to try and make this all a bit clearer! :)

oooh! I'll keep my fingers crossed for you!! I'm sure we can figure out something if that doesn't work for you, but here's hoping it all works like a charm!

@Bryan Copelanddoes the explanation above help?

@André Ferro CadeteGood call! I've updated the environment variables page accordingly. Sorry you had such a painful experience, but hopefully now others won't have the same. Linette (Pipelines writer)

Hi @Bryan Copeland, you're not being daft, it's a confusing area!! Probably the most straightforward order of operations would be: * Create a bot user account in BB * As a repo admin, give the bot user account write permission to the repository in Repo settings > general > user and group access * Go into Repo settings >…