Can all of this be done using Bitbucket and Pipelines rather than Stash and Bamboo?

[Tory Netherton]

For us at least, keeping everything cloud is really helpful.

[Mark Klinski]

Tory, absolutely! We're giving a talk at Dreamforce on how to use Bitbucket Cloud and Pipelines for the same essential workflows. We'll make updates here to include the steps to set everything up.

[Tory Netherton]

That is awesome. Now if only I were able to attend that talk...

I breathlessly await your updates sir.

[Tory Netherton]

Any progress? I'm quite anxious for this.

[Mark Klinski]

@Tory Netherton, I'm working on creating a blogpost that'll show the set up that I did. I'm waiting to find out if the Dreamforce presentation was recorded, too. I'll post that as soon as I'm able. Thanks for your patience!

[Tory Netherton]

Excellent. You're awesome.

I look forward to your post.

[Ben Locke]

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

[Mark Klinski]

@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!

[Tory Netherton]

Hi Mark,

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)

commitmsg="$(<update_to_trigger_pipelines.txt)"

git remote set-url origin git@bitbucket.org:$BITBUCKET_REPO_OWNER/$BITBUCKET_REPO_SLUG.git

git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/*

git fetch

Warning: Permanently added the RSA host key for IP address '104.192.143.3' 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.

Thanks,

Tory Netherton

[Tory Netherton]

Ah, nevermind. Found it.

Apparently for some reason it doesn't like PuttyGen keys even when they are passphrase-less.

ssh-keygen to the rescue.

Sorry to bother.

[Mark Klinski]

@Tory Netherton, glad to hear you found a solution to that issue. Thanks for posting your experience with this thus far! I'd be eager to hear you thoughts after trying to use this for a bit.

[Carlos García Abella]

Hi Mark, 

First of all, great job! 

My question is. How can be "package.xml" file up to date? or your package.xml is a standard one which not need to be updated? 

Thank you very much!

[Binh Do]

Hi Mark,

your account for the salesforce pipeline is no longer active. Do you think you can reactivate it?  Thank you.

https://bitbucket.org/mklinski/salesforce-bitbucket-pipelines