Thank you a lot guys. My question was - what do you use for this type of
deployment - build from each feature branch.
On Tuesday, May 31, 2016 at 1:04:30 PM UTC+2, Tomáš Bohuněk wrote:
>
> What do you recommend for deployment of multiple git repository (one
> project with few feature branches).
You might consider fingerprinting the artifacts then you can use the
Jenkins fingerprint lookup to steer what created that artifact
On Tue, May 31, 2016, 12:07 PM Thomas Zoratto
wrote:
> Tomáš was talking about Docker so let’s take it for example. You could
> build a new Docker image for each on
Tomáš was talking about Docker so let’s take it for example. You could build a
new Docker image for each one of your branches and tag it with the branch name,
build number or whatever you prefer.
Regarding Nexus or Maven specifically you could use a plugin such as the Maven
build number plugin
Hi,
The interesting question for me is how to handle and identify the different
artifacts which are built by the several branches. I. e. in Maven you
specify a version 1.0.0-snapshot and this is then used to build the Jar.
When you're going to deploy this on a machine or a repository (i. e. Nex
Hello,
You can achieve this with a Jenkinsfile per branch in your repository. Then
create a new multibranch pipeline job in Jenkins pointing to your repository
and you're done. See
https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Multibranch+Plugin
Thomas
> Le 31 mai 2016 à 14:00, Tomáš B
I would like to deploy and run each jar file for each feature branch.
Project is written in Java and JavaScript. Jar file is built by maven. I
need to deploy somehow to one machine each of jar built from each feature
branch.
On Tuesday, May 31, 2016 at 1:55:21 PM UTC+2, Mark Waite wrote:
>
>
I think you'll need to provide more details about the problem you're trying
to solve, and the languages you're using to solve it. For example, since
you mentioned that you're deploying to tomcat, are you writing in Java or
some other JRE supported language (like Scala)?
Are you building your jar
Sorry for mistake. You are right. I have one single git repository (one
project) with a few feature branches.
On Tuesday, May 31, 2016 at 1:44:19 PM UTC+2, Mark Waite wrote:
>
> Could you explain further what you mean by "multiple git repository (one
> project with few feature branches)"?
>
> Th
Could you explain further what you mean by "multiple git repository (one
project with few feature branches)"?
The phrase "multiple git repository" seems to be in conflict with the
phrase "one project". I typically place a project in a single git
repository with a few feature branches as necessary
What do you recommend for deployment of multiple git repository (one
project with few feature branches). Final artifact is JAR with bundled
Tomcat application server. I usually run this JAR in Docker container. What
do you prefer?
--
You received this message because you are subscribed to the
10 matches
Mail list logo