Continuous Deployment Bluemix with existing Bitbucket repo - bitbucket

I'm experiencing an issue with Bluemix DevOps continuous integration system when it comes to linking the project to an existing private Bitbucket repository.
I tried the steps presented in this link and although I'm able to see the content of the Bitbucket folder, the devOps is still stuck to the initial commit and it does not take the appropriate files during the building stage.
Can anyone provide any tips or suggestions?
Many thanks

Those instructions, although it mentions "private", are only valid for a Public repository, as you have noted without a similar style to the GitHub integration we don't have a way to setup a shared token you would need to be able to authenticate. That said today, you cannot really use a pull method to pull changes from BitBucket to DevOps Services, you will need to use a push method from somewhere that you can authenticate to your private repo and the DevOps Services git repo to keep them in sync.
https://developer.ibm.com/answers/questions/197619/continuous-delivery-with-bitbucket-and-jazzhub.html

Related

Can I use a gitlab-ci.yml with a Bitbucket repo to create a pipeline?

So we migrated all our Gitlab projects to Bitbucket. We'd like to use the existing gitlab-ci.yml files for Bitbucket pipelines. Could we do that? If yes, could someone please give some steps to carry that out?
Thanks!
No, you can not, recently I did the same job and I wrote all the pipeline yamls from scratch. They don't behave the same.
Gitlab supports mirroring repositories between git servers, but it’s only free for public/open source repositories. Otherwise you have to be on a paid plan, regardless if you use gitlab.com or an on-premise installation. Pushing from Gitlab to another server is free, but pulling from elsewhere to Gitlab is a Premium feature. You can read more about this in the docs
Otherwise, there are open source utilities that will mirror repositories for you but they have to be configured and maintained properly. One such utility is gitlab-mirror.

GitHub action Manual approval process

I know that GitHub Action manual triggers is a very discussed issue, manual approval is a bit less discussed but still present in the community.
I have a question for those who use Github actions for CD purposes.
As you know Bitbucket, Gitlab, Azure Devops etc. have a feature Manual approval which means that a pipeline can reach a certain step in the process for example: build -> test -> deploy to staging.
The next step is deploy to production yet it needs a manual approval or trigger. So my question is this, were any of you achieve that functionality in GitHub action with the same information (branch name, same test results) without running the whole pipeline again? (It's kind of the reason why I am not migrating us from Bitbucket to GitHub yet)
Thank you for your answers
Recently, the GitHub team has announced Environments in beta. With this feature, you can add Manual approvals into your CI/CD.
Environment workflow syntax
However, there is a restriction for private repositories - Only GitHub Enterprise service plan can use Environments within private repositories.
So in GitHub there are two ways to do manual approval for deployments .
Using Environments
Using GitHub action

How we can trigger jenkins job which takes source code from one repository, whenever a developer push changes to their beanstalk-git repository?

I want to run(trigger) my jenkins job whenever a push happens to developer repository.
Firstly,
i'm storing all my automation scripts in my personal GitHub.
All of my developer's code is another GitHub, i.e in beanstalk which is top of GitHub
Now whenever dev's pushes their changes to their repository, then i want trigger my jenkins job which takes source code from my personal GitHub.
So, after some research on it, i came to know Webhooks will help in this.
Bu in my case as per their are two separate repositories, i couldn't able to get what exactly i have to do.
Any solution appreciated.
One of the solution, I can think of is you can build a WebHook and Git integration on your Dev's repository to trigger your Jenkins job, and in the build steps you can perform the check-out of your git repository source code using git commands.

BitBucket Hook option not visible

The below link talks about bitbucket hooks option which can be configured at repository level.
https://developer.atlassian.com/server/bitbucket/how-tos/hooks-merge-checks-guide/
I do not see this option in my bit bucket account under repository settings. Can anybody let me know where I can find this option.
You're looking at Bitbucket Server documentation but attempting to use Bitbucket Cloud. Bitbucket Cloud does not currently support custom hooks.

Automatically build and validate VS Team Services git pull requests on local jenkins server

I have been struggling with this problem for a few days. I have built successfully my project on Team Services git repository with all tests included, but I was unable to validate my pull requests automatically. Anyway, here' s my project configuration:
https://snag.gy/d49iaL.jpg
https://snag.gy/jWuMNf.jpg
The part that confused me is what should i write in Refspec field for this particular project.
NOTE: I have to do this without service hooks if there's any chance.
It is impossible with TFS for now, where Jenkins could not signal the result of the build which shows up in the code view of the branch.
Supporting Pull Requests
With the "GitHub" or "Bitbucket" Branch Sources, Multibranch Pipelines
can be used for validating pull/change requests. This functionality is
provided, respectively, by the GitHub Branch Source and Bitbucket
Branch Source plugins. Please consult their documentation for further
information on how to use those plugins.
Source Link
Also take a look at this similar question:Validate pull request with jenkins in VSTS and you could vote up the related uservoice to get more attention.

Resources