In my Bitbucket I have projects X,Y,Z
In my OnDemand I also created projects X,Y,Z
I connected OnDemand and Bitbucket.
How can I tell OnDemand that the OnDemand project X is the same as the BitBucket project X (so that OnDemand knows what to do with updates in the repository?)
The projects wouldn't be linked together per se. In other words, the DVCS connector in your OnDemand instance is dedicated to syncing Bitbucket/Github commits with JIRA issues.
More details here:
Hope this helps!
(mmm... my answer just got lost in the login process...)
I am a complete noob on these kind of systems, but wouldn't a automatic connection not be much better? So I commit something to Bitbitbucket, project X: 'Fixed issue #1' and - because of the connection - the issue status is changed in the OnDemand X counterpart automatically? Why are BitBucket and OnDemand separate products in the first place? When I started my trial, I thought it would just be an (huge) upgrade of my BitBucket issue page, in stead of a separate product with a connector which I have to instruct with commit messages.
(not meant as criticism, I am just trying to guess why the current setup is as it is :)
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot