New answers tagged

0

If you have the option, Github offers Actions which allow you to run workflows on different events - one of them being push. If Github is not an option, I would recommend creating a build where deployment of the artifacts only happens if the build is done on master. On your feature branches, on checkin, a build will happen which will pull the latest code, ...


0

I realize it's because the link for tomcat I was deploying to was: https://localhost:portNo, instead of simply, http://localhost:portNo


0

Take a look on this project to manage your ansible vault encrypting passwords https://github.com/Smile-SA/ansible-vault-manager It handle multiple keyring storage platforms with plugins (for now only AWS SSM implemented). Morehover integration with a current Ansible project is very easy...


2

Since you have a single released version product one thing to consider would be keeping the Develop branch or not: keeping it would have the advantage that at any moment you can bring in a hotfix in master even if Develop isn't stable enough for a merge into master. But this means you'd need to have 2 focus points instead of a single one - both branches ...


0

If you check the Git plugin documentation, you can see that there is a GIT_BRANCH environment variable that you can use in your pipeline. GIT_BRANCH - Name of the remote repository (defaults to origin), followed by name of the branch currently being used, e.g. "origin/master" or "origin/foo" So, in your pipeline: stage('Push to ...


1

Monorepos have been getting a lot of attention in recent years since google popularized them. If you aren't on a similar scale as google it might not work out as well for you. I've been in a startup that moved to monorepos and we quickly found that: most tools are built with one repo leading to one artifact that gets deployed. You will have to rework all ...


1

We also switched from Git Flow to GitLab Flow several months ago and so far we're very happy with our decision. It works very well with GitLab, it's easy to understand and less error-prone and you don't need additional Git commands (which are quite slow on Windows). We use Docker Compose to organize our microservices and have a separate project/repository ...


3

The Git Server It's best practice to setup a Git server for the team to access. This way you have a central server that can be maintained, backed up, and focus on serving the source code. While you could create your own, there are also several popular commercial options available that often have free private repositories (non-exhaustive list): Bitbucket ...


Top 50 recent answers are included