On Wed, Feb 11, 2015 at 9:18 AM, bob M <bobnli...@gmail.com> wrote:
> Dear groups,
>
> Greetings !!
>
> I'm very new to jenkins and looking forward to tweak my jenkins server
> further.
>
> I have configured a job which successfully build after git cloning. But how
> can I make
> reproduceable build ? The workspace simply have the cloned file and I am
> still striving to find out
> to store the build along with changes.
>
> I have one more job to build with "rsync over ssh" and its workspace is
> empty as well as
> no information about the changes at build history.
>
> Could anyone please suggest how can I store the changes in build and produce
> such build which
> can be reproduceable ?
What kind of 'changes' do you mean? Normally you want to pull
everything from your source control system including whatever command
or script it takes to do the build and just run that command, so any
time you check out that revision/tag you get the same thing whether
jenkins does the build or not. If you are making changes, you should
be committing them back, and generally tagging the ones you want to be
able to easily reference again.
--
Les Mikesell
lesmikes...@gmail.com
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAOAgVpznLHNtjgDfPDgRT6Fks_5UwfP1VwpUYPL1Di0Y-7yCVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
