The indentation looks incorrect for the artifacts section in your buildspec-test.yml file. It is nested under the phases section. That way it is not being output properly and can't be picked up by the next build.
It should be the same as in your second file.
- $ANDROID_HOME/tools/bin/sdkmanager "build-tools;...
Gitlab CI/CD offers Docker Engine. If you can create a docker image, you can serve the application the same way as you were doing with Jenkins. You can find more details on how to integrate both here.
Hope it helps.
Most CI/CD tooling will support permissions of some sort. For example:
All of AWS CI/CD tooling supports limiting permissions via IAM. IAM also ties into AD which would give you that SSO (single sign on) feel. Virtually every major cloud provider will have equivalent permission based functionality (e.g. Azure, Google Cloud).
Bamboo supports limiting who ...
My general experience is that CI/CD tools don't support impersonation or claims based authentication well or at-all. In addition you probably want the CI/CD tool to have more access than your users, because you want them to only use the CI/CD tool to change things.
The way I have handled this in the past, however, was as follows:
Have the pipeline call ...
You don't need any plugins. You can send an e-mail from your Pipeline using the mail() step. You can respond to the input step by using the REST API as documented in this answer on Stack Overflow. Put the two together and you should be able to craft an e-mail that contains buttons for responding to the input.
There are a few different things you can do:
In your CI process, run your new SQL update scripts against a Dockerized SQL Server. This will allow your CI server to reject the changes if there are basic errors in the script.
If you are fully containerized look into tools like Kubernetes. These tools have ways to handle rolling back failed production updates....
There are some fundamental misunderstandings in your bullets which makes your question unclear:
Apple will not allow you to develop/build using a virtual system. I believe this is a legal constraint. That said, you can run pretty much anything in VirtualBox as long as you have a legally provided image (e.g. a Linux image).
You can only run the Windows ...
GitOps is a technique of using Git to manage infrastructure provisioning and software deployments. This technique uses many of the features of Git such as Pull Requests to manage and trigger deployments, and allows "diffing" (looking at the difference between commits) to view the differences between deployments.
DevOps is more of a culture or philosophy. ...
You need to separate the 2 concepts a bit:
the integration part - how are the changes integrated into your master branch (or some other integration branch, that's also possible), which may be continuous or not. Technically neither approach you describe is actually continuous integration unless your feature branches have a very short lifespan - typically ...
Please below where I address specific questions.
2: do we need to use docker? if not how it should be done
By using Docker you can automate the configuration of your server images as well as application images to use to deploy to staging and into production.
Docker use standard images that you build on by adding your custom software installation and ...