Hi, Brent:
You are basically right. I am adding a Nexus component to the pipeline
and trying to figure out what role and how it should play in the pipeline.
Thanks.
On Thursday, August 20, 2015 at 7:47:45 PM UTC-4, Brent Atkinson wrote:
>
> Hi Martin,
>
> The way you describe is similar to approaches I have seen before. However,
> as Jeff said, how you would do this is a matter of what you are looking to
> achieve and how you have setup your processes and environments.
>
> Given how you describe [5] I assume you may be manually configuring from
> some sort of deployment script? Other organizations may use their build
> pipeline to automatically deploy built and tested artifacts to one or more
> environments (like qa, preview, production).
>
> They key idea to the type of configuration you are talking about is
> ensuring that you can't put code into production without it being checked
> in, built off a developer's machine, unit and integration tests pass, and
> whatever else your organization treats as pre-release requirements.
>
> HTH,
>
> Brent
>
>
>
>
>
> On Thu, Aug 20, 2015 at 7:12 PM, Martin <[email protected] <javascript:>>
> wrote:
>
>> If I use Nexus OSS as a repository manager, the normal for code goes to
>> production system is something like below:
>>
>> 1) Jenkins grabs code from Perforce or GIT server
>> 2) Jenkins retrieves dependencies from Nexus
>> 3) Jenkins test and build the project
>> 4) The build is deployed to Nexus from Jenkins
>> 5) Web application server, i.e. JBoss Application Server or Apache Server
>> grabs code from Nexus, for production service.
>>
>> In this flow, the build in Jenkins doesn't directly go or deploy to Web
>> server, but first parked at Nexus, and goes to Web server.
>>
>> Is this understanding right? I would appreciation an explanation for this
>> cycle.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/5ff2816c-3d23-42f4-bfde-103e7f8626fb%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/jenkinsci-users/5ff2816c-3d23-42f4-bfde-103e7f8626fb%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/47041edd-34ea-4c7a-87f2-1e7832e81082%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
