I am looking to get something like this put together here very soon. I found Atlassian's cookbook for setting this up on premise, looks great but would much rather use the cloud solution. Have you posted this yet? Can't find anything about it. Should I move forward with on-prem? Thanks
@Ben Locke, @Tory Netherton,
It's possible that there was no recording taken from my talk at Dreamforce unfortunately. I'll post here if it becomes available.
Have a look at https://bitbucket.org/mklinski/salesforce-bitbucket-pipelines. I put this together today. You can either fork the repo itself and set up as a production repo (and set up downstream forks from there), or if you already have repos set up for your Salesforce work, you can copy my bitbucket-pipelines.yml file and do the other set up to your existing repos.
It's just a first take at this, so the documentation isn't super thorough. I'll be curious to hear what your thoughts are, any issues you face, and any thoughts for improvement. Thanks!
Thanks for all your hard work.
I began trying to get this set up on Friday. Unfortunately, my initial attempt to fork your repo got hung up somehow and I was unable to do anything further with it. I thought perhaps I just needed to give it time although that seemed strange considering how tiny it is. Anyway, it was still frozen as "Forking" this morning so I contacted Atlassian support and they deleted the repo for me. I was then able to fork it successfully. Not sure what that was all about, but I'm happy to have overcome it.
I'm trying to set things up according to your directions. I believe I have everything set up just about right for the production repo. The link you provided for instructions on setting up SSH (https://confluence.atlassian.com/display/BITBUCKET/Set+up+SSH+for+Bitbucket+Pipelines) is no longer valid, but it had what seemed like the right link (https://confluence.atlassian.com/display/BITBUCKET/Access+remote+hosts+via+SSH) to help find it. What it contains is a little confusing because I believe a bit of it (other remote hosts) is not relevant and other parts you have already done. But, I think I got all of that set up correctly.
Now, I'm trying to get it to do an initial "save-changes" down from Salesforce. So, I made a change to the update_to_trigger_pipelines.txt file. This caused Pipelines to run as expected, but it halts and acts like it's waiting for passphrase input at the "git fetch" step.
Pipelines currently just says "In progress" and spins like it's doing something, but this is how the log stands now and has for some time (skipping the lengthy and I believe irrelevant "Build setup" step):
(mkdir -p ~/.ssh ; cat my_known_hosts >> ~/.ssh/known_hosts; umask 077 ; echo $SSH_KEY | base64 -d > ~/.ssh/id_rsa)
git remote set-url origin firstname.lastname@example.org:$BITBUCKET_REPO_OWNER/$BITBUCKET_REPO_SLUG.git
git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/*
Warning: Permanently added the RSA host key for IP address '126.96.36.199' to the list of known hosts.
Enter passphrase for key '/root/.ssh/id_rsa':
Do you have any thoughts on why it would be expecting a passphrase there? I certainly didn't use a passphrase in any of my key generation steps. I'm just not sure exactly what '/root/.ssh/id_rsa' represents in this case.
Any assistance is greatly appreciated.
As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot