Simply keep pushing stuff between the repositories. Git pushes are designed for exactly that.
So, if origin is the old repository, and newis the new one, and you want to move new stuff in the master branch from origin to new, then, locally:
git checkout master && git reset --hard # to clean up any local changes, optional
git pull origin
Infrastructure as code means that the infrastructure configuration is stored in a version control system (VCS). If changes will be applied, it is traceable who changed the code and when.
Although it is unclear to me what the aim is of your question, it is possible to use a continuous integration (CI) tool like, Jenkins, gitlab, circleci that pulls the code ...
This question runs two risks:
of being marked as "primarily opinion-based", and
its answers might age poorly.
However, I think it's useful to express an opinion, if only for posterity; if and when things change, there may be better answers -- but there will always be blank slates.
I would split the problem up into four sections:
If you use python and GitLab like I do, you can include a test coverage report in your CI/CD pipeline. You pip install coverage and then just run coverage in your pipeline. The following is an excerpt from an AWS lambda pipeline, but you should be able to find something similar for your environment:
- pip install -r ./awslambda/requirements.txt
Apologies for not directly answering your question, but by the sounds of your question, you are trying to build an update management system to mitigate the threats of vulnerable operating system components and tools having unpatched vulnerabilities which expose you to risk.
This functionality is actually already available for both Windows and Linux via ...
I'm looking this fact:
I have an ASP.NET Core 3.0 application for which I have a full CI/CD setup in Azure DevOps. The Application is hosted on a Ubuntu 18.04 server machine.
Therefore I can safely assume that you are developing ASP.NET Core 3.0 app to be hosted in Ubuntu. Any .NET Core 3.0 (or later) application means that you should rely on the dotnet ...
I use separate pipeline for each app
you could use powershell task to restart IIS, but I dont think there is a way to do this without shutting down the website. You can also reconfigure website, so copy new code to location X, repoint website to location X, restart website. Then you can easily point it back if something fails and switch is almost ...
From what I can see you have done everything correctly, you have stored both the certificate material (i.e. the PFX) and the password for the PFX in a secure location that presumably no one else can access. Assuming you don't give anyone else permissions on your Azure tenant and you don't blindly accept pull requests that change azure-pipelines.yml then you ...
The error message you have provided indicates that this is a problem with the configuration that could be permission related. Here are some steps to help resolve this issue:
You can follow guides where other people have configured the two. Pay special attention to the permission settings that are selected.
Double check your permissions on the servers. ...
There are actually many ways to link work items to other objects in Azure DevOps. Microsoft's documentation is pretty extensive on this topic. However, for the particular task at hand, linking code commits (I'll assume Git is in use for this example), can be done in several different ways.
In your commit message - By including the work item ID in the ...
I noticed that the description for the filepath properties of the pack command is different than the descriptions in the test and publish commands:
Pattern to search for csproj or nuspec files to pack.
You can separate multiple patterns with a semicolon, and you can
make a pattern negative by prefixing it with '-:'. Example:
Lets take this line by line:
My additions are added as comments.
# The branch you are building.
# The type of VM your code will run on.
#This ends up defining which webconfig file to use.
- script: dotnet restore
displayName: Restoring Dependencies
This is an indication that someone removed a field from work item configuration that was represented by 25. It's more of an issue of clean-up not being done when fields are removed. See more about this error on Microsoft's Developer Community.
This other item in the community suggests a different problem when using a particular extension and a fix has ...
You can separate the steps, especially as it would let you do divide the work among different agents. You can also leave them in a single agent if you wish.
The primary advantage I see is leveraging different pools for different sets of work.
With releases last I checked variable scope was limited (as of 2018) to the "phase".
I wouldn't necessarily ...
Do not trigger Build 2 automatically from Build 1. Instead add a last step to Release 1 to queue Build 2. There are a few ways to do it, e.g. https://stackoverflow.com/questions/52821204/how-to-queue-build-pipeline-as-task-from-release-pipeline
Microsoft added a new hosted agent: Hosted Windows 2019 with VS 2019.
So you should use this image to build for windows-1809 or windows-2019
Source : https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#use-a-microsoft-hosted-agent
FWIW, I ended up creating a windows server 2019 vm on ...
Activity Logs can only able to show the resource level logs like creating a resources,deleting a resources modify the SKU of the resources etc,
Assuming from your question you are saying web app deployment from azure devops,which is more like a deployment of code to an existing webapp which will not be covered by activity logs. You need to go to that azure ...
This is a general issue with react apps that is independent of what CI/CD stack you use that is discussed at https://stackoverflow.com/questions/49975735/rendering-an-environment-variable-to-the-browser-in-a-react-js-redux-production
With the Azure family of CI/CD products it is expected you create a release artefact then release that same artefact into ...
Yes this can be done, Azure Pipelines can ingest a yaml file, configuring the pipeline as code. These yaml files should be source controlled and the pipeline can be set up to build in an automated way.
You can also reuse steps within the pipeline
Since on-premise TFS and the newly renamed Azure DevOps Server 2019 still have the concept of collections, which is the highest level of separation of data you can have (separate physical databases), you'd need to treat a code repo in Collection 1 as an external repository rather than try to discover it as a known internal repository.
You can do this in the ...
Openstack is something you might install to setup an self-service IaaS platform that manages VMs, storage and network. Whereas the top three cloud providers have written their own proprietary IaaS platforms a small cloud provider, or a large company, cannot feasibly code there own cloud-like management software, so they might setup their “private cloud” ...
It can happen that your next DevOps job finds you if you have a well elaborated LinkedIn profile and patient enough to deal with and filter/process requests.
Though, my market observations are that many offerings are like:
DevOps Engineers seen as "full stack developer 2.0", that is as an addon to specific developer skill set you can also setup automation ...
Understand that the term DevOps refers to both a Strategies and Tactics.
For instance, the strategies of Continuous deployment and Consistent development/production environment.
The tactics may be using Kubernetics for deployment to the cluster with Docker for development/production environment.
With that said, a DevOps shop will likely use Kubernetics and ...
@Shayki's answer was a large portion of what I was looking for (thanks!), but I was eventually able to figure out a solution that met all of my requirements. It involves a less than ideal use of the Release Description to propagate state between jobs.
The updated flow diagram looks like this:
I was originally thinking of the conditional flow as an if else ...
Maybe is not a full resolution for you, but you can start with this:
After the "Critical Task" add an "Agentless job"
Add a "Manual Intervention" task
In the "Additional options" in the job specify "Run this job - Only when a previous job has failed"
I'm using https://docs.gitlab.com/ee/workflow/repository_mirroring.html#pushing-to-a-remote-repository to push everything into a repository in VSTS, easily done via access token with the right permissions.
I have a repository in GitLab that is used by our development team. On
the other hand, there is a VSTS setup (at xyz.visualstudio.com) that
we use to manage our scrum board.
First impression is that you should either choose one repository or check the API of both products to investigate whether the tools could be integrated. From a DevOps perspective, ...