continuous-delivery

Background: We have one Jenkins job ( Production ) to build a deliverable every night. We have another job ( ProductionPush ) that pushes out the deliverable over a proprietary protocol to production machines the next day. This is because some production machines are only available during certain hours during the day (It also gives us a chance to fix any last-minute build breaks). ProductionPush needs access to the deliverable built by the Production job (so it needs access to the same workspace). We have multiple nodes and concurrent builds (and thus unpredictable workspaces) and prefer not

I have a web application where we deploy to production whenever a feature is ready, sometimes that can be a couple of times a day, sometimes it can be a couple of weeks between releases. Currently, we don't increment our version numbers for our project, and everything has been sitting at version 0.0.1-SNAPSHOT for well over a year. I am wondering what is the Maven way for doing continuous delivery for a web apps. It seems overkill to bump up the version number on every commit, and never bumping the version number like we are doing now, also seems wrong. What is the recommend best practice for

I have several projects that use a Jenkinsfile which is practically the same. The only difference is the git project that it has to checkout. This forces me to have one Jenkinsfile per project although they could share the same one: node{ def mvnHome = tool 'M3' def artifactId def pomVersion stage('Commit Stage'){ echo 'Downloading from Git...' git branch: 'develop', credentialsId: 'xxx', url: 'https://bitbucket.org/xxx/yyy.git' echo 'Building project and generating Docker image...' sh "${mvnHome}/bin/mvn clean install docker:build -DskipTests" ... Is there a way to preconfigure the git

The project is an MVC website coded and built using VS2017 and (on premises) TFS2017. The Build Definition is currently working and publishing to the staging location upon check-in. The PowerShell script below, derived from David Kittle's website , is being used but it uploads all files every time. I abbreviated the listing using comments to focus on the part of the script for which I'd like to ask for help/guidance. # Setup the FTP connection, destination URL and local source directory # Put the folders and files to upload into $Srcfolders and $SrcFiles # Create destination folders as

What's the difference between these three terms? My university provides the following definitions: Continuous Integration basically just means that the developer's working copies are synchronized with a shared mainline several times a day. Continuous Delivery is described as the logical evolution of continuous integration: Always be able to put a product into production! Continuous Deployment is described as the logical next step after continuous delivery: Automatically deploy the product into production whenever it passes QA! They also provide a warning: Sometimes the term "Continuous

I am invoking a Jenkins job remotely using: wget http://<ServerIP>:8080/job/Test-Jenkins/build?token=DOIT Here Test-Jenkins job is invoked and DOIT is the security token that I have used. Now I need to pass some parameters to the build.xml file of this job i.e. Test-Jenkins . I have not yet figured out how to pass the variables yet. Peter Schuetze See Jenkins documentation: Parameterized Build Below is the line you are interested in: http://server/job/myjob/buildWithParameters?token=TOKEN&PARAMETER=Value Zacky Pickholz To trigger a build with own/custom parameters, invoke the following URL