continuous-integration | Bazel 's Continuous Integration Setup | Continous Integration library

I have a React frontend and a Node backend, I've made several E2E tests with Cypress for the frontend and run them locally. I love how end to end testing allows me to catch errors in the frontend as well as on the backend! so I'd like to have a way to run them automatically when sending a PR.

I'm using bitbucket pipelines, and I've configured it to run the npm test command which works perfectly to run my unit tests, but what I still don't understand is how to be able to run my Cypress tests automatically, because I'd need to have access to the backend repository from my pipeline that runs on the frontend repo.

What I've tried

I've read the documentation and played with the example repo, but I still don't understand how could I automate running my tests, on the example both backend and frontend are on the same repository.

I'm sorry if this is a vague question, I just don't seem to get if this is even possible with bitbucket pipelines, if it's not, what other tool could help me run my Cypress test in a similar way that I do locally? (running both backend and frontend).

I've really tried to search for an answer to this, maybe it's too obvious and I'm just missing something but I don't seem to find anything on the internet about this, any help will be very appreciated!

I need a help to access a linked service parameter during Azure Data Factory deployment or find some other way to set a parameter during deployment even if the parameter is not automatically added for editing.

I am using continuous integration for Azure Data Factory using Azure DevOps pipeline (i.e. all pipelines and connections are first created in a test resource and then deployed through Azure DevOps pipeline to production resource, https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-delivery). For authentication I use Key Vault but Databricks Workspace URL cannot be added as a secret from Key Vault. I created a parameter for the value (DatabricksUrl) but I am not able to access that parameter during deployment because it is only created on the linked service. Only parameters added to ARMTemplateParametersForFactory.json file in the publish branch can be accessed. Is there a way to solve this? Any help appreciated.

I'm on the CI part of the course

I'll start by saying all works well, and I could follow the process with ease. However, there something that works, and I cannot figure out how. Lets take this part of the main.yml file:

In GitHub Enterprise, we have Project A under Organization A. When I submit a PR (pull request) to Project A, the continuous-integration/jenkins/pr-merge is triggered which runs a Jenkins pipeline to build the code and perform unit tests. This allows us to prevent the PR from being merged into master if the unit tests fail.

For example, this is what I see on a PR for Project A in GitHub that includes a broken unit test:

Now I am trying to configure Project B under Organization B to behave the same way. However, it is not working. This is what I see on a PR for Project B in GitHub that includes a broken unit test:

Notice that Project B's PR did not kick off the continuous-integration/jenkins/pr-merge.

GitHub -> Settings -> Branches -> Branch protection rules

Project A in GitHub has a branch protection rule for master with only one setting enabled:

• Require pull request reviews before merging

Interestingly, the "Require status checks to pass before merging" setting is not enabled. Out of curiosity, I enabled it (without saving it) and noticed that "continuous-integration/jenkins/pr-merge" showed up below it as an option.

I configured Project B to have the exact same branch protection rule for master with only "Require pull request reviews before merging" enabled. Out of curiosity, I enabled "Require status checks to pass before merging" (without saving it) and it doesn't even show continuous-integration/jenkins/pr-merge as an option. It just says "No status checks found. Sorry, we couldn’t find any status checks in the last week for this repository."

GitHub -> Settings -> Hooks -> Webhooks

Project A in GitHub has a webhook configured with:

• Payload URL https://jenkins.mycompany.com/github-webhook/
• Content type application/json
• Let me select individual events: Pull requests, Pushes, Repositories are checked
• Active: checked

I created a webhook for Project B with the exact same settings. After I submitted a PR for Project B, I see a couple of items under "Recent Deliveries" for Project B's webhook with green checkmarks and "200" response codes, so I think it is configured correctly.

CloudBees Jenkins Enterprise

In Jenkins Enterprise, Project A's pipeline is of type "GitHub Organization" and has the following settings:

• API endpoint: kubernetes-cbs-automation (https://git.mycompany.com/api/v3)
• Credentials: [credentials specific to Project A]
• Owner: [Project A's GitHub organization]
• Behaviors: Repositories: Filter by name (with regular expression): Regular expression: [name of Project A's GitHub repo]
• Behaviors: Within repository: Discover pull requests from origin: Strategy: Merging the pull request with the current target branch revision
• Project Recognizers: Pipeline Jenkinsfile: Script Path: ci-cd/jenkins/ProjectA-pipeline.groovy
• Property strategy: All branches get the same properties
• Scan Organization Triggers: "Periodically if not otherwise run" checked: Interval: 1 day
• Orphaned Item Strategy: "Discard old items" checked
• Child Orphaned Item Strategy: Strategy: Inherited
• Child Scan Triggers: "Periodically if not otherwise run" checked: Interval: 1 day
• Automatic branch project triggering: Branch names to build automatically: .*

I created an item under Project B in Jenkins Enterprise of type "GitHub Organization" with the same settings (except any settings specific to Project A were replaced with the appropriate Project B specific settings).

Given that GitHub PRs for Project B are failing to launch the continuous-integration/jenkins/pr-merge, it seems like there is some configuration that I am missing. Unfortunately, our GitHub/Jenkins admins have not been able to figure out what is wrong.

UPDATE

We have confirmed that Project B is actually launching a build on the Jenkins agent when a PR is submitted. The problem is that GitHub is not showing the continuous-integration/jenkins/pr-merge on the web page for the PR. We need that so the PR can be blocked if the build fails, and also so that we can quickly see what went wrong.

As I understand the documentation, whenever I add these lines to the config:

We use Synapse git Integration to deploy artifacts such as linked services generated by a Data Warehouse automation tool (JSON files) It is different then deploying ARM template in ADF.

We created one Azure Key Vault (AKV) per environment so we do have an Azure Key Vault LinkedService in each environment and the linked services has the same name. But each AKV as his own URL so we need to change the URL in the deployed linked services during the CI/CD process.

I read this https://docs.microsoft.com/en-us/azure/synapse-analytics/cicd/continuous-integration-deployment#use-custom-parameters-of-the-workspace-template

I think I need to create a template to change "Microsoft.Synapse/workspaces/linkedServices" But I didn't find any example on how to modify the KV url parameters. Here is the linked services I want to modify,https://myKeyVaultDev.vault.azure.net as to be changed when deploying

I am following the new recommended ci/cd set up for ADF published here: https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-deployment-improvements

One section that isn't clear to me is if you now need an additional "dev" ADF where the pipeline publishes to.

Under the old model you would do your development work in an ADF linked to git, do a pull request to merge back into the collaboration branch and then click publish. This would publish to the adf_publish branch in the same ADF.

With the new model do you have an ADF linked to git where you do your dev work as before - but does the pipeline deploy to a new separate "dev" ADF (which is not linked to git)?

I have some errors when trying to publish my changes automatically following this [Microsoft Documentation][1]. Please, need some support to fix this :)

Kind regards,

Dickkieee

ERROR === LocalFileClientService: Unable to read file: /home/vsts/work/1/s/arm-template-parameters-definition.json, error: {"stack":"Error: ENOENT: no such file or directory, open '/home/vsts/work/1/s/arm-template-parameters-definition.json'","message":"ENOENT: no such file or directory, open '/home/vsts/work/1/s/arm-template-parameters-definition.json'","errno":-2,"code":"ENOENT","syscall":"open","path":"/home/vsts/work/1/s/arm-template-parameters-definition.json"} WARNING === ArmTemplateUtils: _getUserParameterDefinitionJson - Unable to load custom param file from repo, will use default file. Error: {"stack":"Error: ENOENT: no such file or directory, open '/home/vsts/work/1/s/arm-template-parameters-definition.json'","message":"ENOENT: no such file or directory, open '/home/vsts/work/1/s/arm-template-parameters-definition.json'","errno":-2,"code":"ENOENT","syscall":"open","path":"/home/vsts/work/1/s/arm-template-parameters-definition.json"

I'm trying to test a bundle on different versions of Symfony with github actions. I tried to configure my job as explained in Best practices for reusable bundles

Here is my job: