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
Related
I'm new to Bamboo and currently learning & using the Bamboo as a standalone server in my company. There I can see the much-advanced options like creating the Build Plans, separate deployment projects based on different environments and also can integrate with notifications and triggers.
I wanted to do a lot of research and learning by myself at home so I was looking for a cloud-based version of Bamboo which I can straight away use to perform similar task like creating build plans, etc. I do not see anything cloud version of Bamboo but I can see BitBucket (cloud-based). What I know is that it is a source code repository like GitHub and GitLab and it has integration with inbuilt CI/CD.
Q1. Is BitBucket a cloud version of source code repository plus Bamboo?
Q2. If not, then do we have cloud version of Bamboo with exact options like build plans, deployment projects, etc
Q3. Also, I'm looking if there is any Bot which I can use like SlackBot or DeployBot to invoke or trigger the Bamboo Build Plan with a chat command? Slack I'm familiar but not DeployBot. I can get the Bamboo build notifications to my Slack channel but not the other way around.
I'm learning and doing research & development hence required clarification on my doubts from experts in this DevOps field to show me the right path.
Please suggest as I'm looking for setting up Bamboo with Bot instructing my build plans.
Thank you
Doing hands-on experience in company on Bamboo and learning as much as I can and playing around with it.
Bamboo Cloud was discontinued in January 2017. Bitbucket Cloud can still notify your Bamboo instance via webhook, assuming you configure Bamboo and your firewall and the webhook properly, or you can use Bitbucket Pipelines for the all-in-one approach.
You can also use Bitbucket Server if you'd prefer to keep everything behind the firewall.
I am working on a Visual Regression Testing project, that requires Percy. I followed the instructions for Repository Integrations. The instructions only show 'Connect your GitHub or GitLab repositories to add visual testing to pull/merge requests.', but I want to integrate with Gerrit. And also Jenkins, I cannot find any relative stuff that helps me for the integration on manage Jenkins page as I follow the instructions on Percy.
While Percy doesn't have a native Gerrit integration yet, you can use Percy webhooks to get notifications about when Percy builds are finished, visual changes are ready for review, and when they've been reviewed and approved, which you could use to set statuses in Gerrit. For Jenkins, please see https://docs.percy.io/docs/jenkins — I would suggest you try getting the local setup working first with your application and then go from there, since it should be pretty easy to port that setup into your CI system (just need to set PERCY_TOKEN environment variable).
How can i integrate Jira and Gitlab and status will change on request!
Git commit -> ED-1511 #AutomationState Running
Jira ticket (ED-1511) - >> will change AutomationState on Running
I don't think that you can do this with the out of the box functionality of Jira and Gitlab.
From the structure of your commit message it looks like you are trying to use the smart commits functionality in Jira. Smart commits only allow you to perform three actions:
Log time
Comment on an issue
Transition an issue to a new workflow state
This is not something you can do with smart commits. In addition the current Jira Gitlab integration doesn't seem to support smart commits.
If you wanted to build this functionality you could probably build something yourself that:
Listens for Gitlab webhooks
On receipt of a Gitlab webhook calls the Jira REST api to modify the issue
If I understand your question correctly, the GitLab integration with JIRA described here should do what you want. I only recently set this up with our JIRA cloud instance and GitLab running in an AWS instance, and I haven't tried to integrate transitioning JIRA tickets from Git commit messages. However, the documentation seems to indicate that it is possible.
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.
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